When a website task moves from an agency team to a production partner, missing context becomes rework. A clear brief does not need to be long, but it should answer the questions that affect implementation: what is the outcome, what inputs are authoritative, what constraints matter, and who can decide when something is unclear?
1. State the goal and audience
Open with the purpose of the work in plain language. Is the task a new service page, a landing page from an approved design, a migration, or a specific integration? Describe who will use it and what they need to do. Do not start with a list of components before explaining the outcome; the goal helps the implementer make sensible choices when the brief leaves details open.
2. Define deliverables and exclusions
List the pages, templates, features, and environments included. Be explicit about what is not part of the assignment, such as copywriting, brand design, SEO research, hosting configuration, or third-party subscriptions. If the scope is exploratory, label it as discovery rather than implying that the final build is already defined.
For each deliverable, link to the latest approved design, copy, assets, and source documents. Identify which version is authoritative. Mark placeholders clearly and note who will supply final content.
3. Document the platform and constraints
Record the CMS, theme or builder, key plugins, hosting environment, browser support, and any coding or naming conventions the agency needs followed. Include relevant version information when known. Describe integrations and dependencies, including APIs, analytics, forms, or payment services.
Do not send passwords in the brief. Explain how access will be granted through the agency’s secure process and which permissions are needed. Identify who can approve access and who will remove it after delivery.
4. Set acceptance criteria
Acceptance criteria say how the agency will judge completion. Examples include: matches the approved design at specified viewport widths; uses supplied copy and assets; navigation links work; form submissions reach the agreed destination; and the page is reviewed on current target browsers. Specify any required accessibility, performance, or security review standard the project actually uses. Avoid broad language like “make it perfect.”
For WordPress tasks, note expected behavior in the editor and front end, as well as plugin or theme constraints. If the work includes updates to an existing site, document the current behavior that must remain unchanged.
5. Identify dependencies and decision makers
List what must happen before work can start: final copy, design approval, API access, staging credentials, stakeholder decisions, or third-party configuration. Name one day-to-day contact and one person with authority to approve scope changes. State how the partner should proceed if a dependency is late or contradictory.
6. Agree on review and change handling
Define status updates, review dates, feedback format, and how the agency will consolidate client comments. Specify how many review cycles or what acceptance process applies, and how new requests are estimated. A single prioritized feedback list is easier to implement than conflicting comments from multiple stakeholders.
Copyable handoff outline
- Goal and intended user
- Deliverables and exclusions
- Approved designs, copy, assets, and version links
- Platform, integrations, and technical constraints
- Acceptance criteria and test cases
- Dependencies, owners, and decision process
- Access method and data handling
- Milestones, review windows, and change process
Review the brief together before production begins. A short conversation can expose assumptions that would otherwise emerge late, when they are more expensive to resolve.
Keep a handoff usable during production
Store the brief where the agency and production partner can both find the current approved version. A short change log helps prevent someone from implementing an outdated design or content file. When a question comes up, record the decision and the person who approved it beside the affected requirement. If the answer changes scope, pause that portion of work until the agency has confirmed the impact with its client. At closeout, archive the final brief with the delivered assets and note any item intentionally left out. This gives the agency a reliable reference if the client later asks why a feature behaves a certain way or requests related work.
Related resources
Explore the topic hub and these related guides:
For work involving WordPress, the official WordPress documentation is a useful reference for maintenance responsibilities and recovery planning.