IN BRIEF
- Separate business objectives from a list of visual preferences.
- Agree on content ownership, approvals and what “finished” actually means.
- Record constraints early so design and engineering solve the same problem.
Start with the business problem
“We need a modern website” describes a preference, not a useful problem statement. What has stopped working? Perhaps users cannot distinguish services, updates require developer intervention or the mobile experience fails to generate inquiries. A brief should explain the present situation and the outcome the business needs. It should avoid presenting a preferred solution as the problem itself.
Describe the business model, audiences and desired actions. A service studio may prioritize qualified conversations; an information portal may prioritize discovery and content completion. Define what success would look like in observable terms, even if precise historical metrics are unavailable.
- Describe what the current website does poorly with specific examples.
- Define primary and secondary audiences, including language needs.
- Choose one primary action for each important page type.
- Record measurable outcomes without inventing a baseline.
Map the page scope before discussing screens
List the pages, essential sections and key behaviors. Common items include homepage, services, projects, about, contact, privacy, blog and individual articles. For each item, record why it exists and what content it requires. An eight-page site and an eight-template site are different scopes; repeated articles should share a template, not become eight custom developments.
Mark items as required for launch, optional for launch and future phase. This prevents a speculative admin dashboard or customer portal from quietly becoming part of the initial website delivery. It also gives the team a credible roadmap for later additions.
- Build a sitemap with a purpose attached to every page.
- List interactive behavior, forms, search and filtering separately.
- Distinguish reusable templates from unique page designs.
- Maintain an explicit post-launch backlog.
Assign content responsibility
Content delays frequently look like design delays. The team cannot make final layout decisions around missing project photography, unapproved service descriptions or unknown legal information. Specify who supplies text, images, brand assets, translations, project permissions and contact details, and when each item is due.
If content will be written during development, state who approves the facts. Editorial drafts are not permission to invent customers, awards or numerical results. For multilingual sites, decide whether both languages launch together and who reviews each edition for natural professional language.
- Assign one owner and a deadline to every content category.
- Define formats, permissions and image quality expectations.
- Separate copy drafting from factual and legal approval.
- List the page templates that require localized content.
Document design and engineering constraints
Include hosting access, expected traffic, domain and HTTPS ownership, email handling, analytics preferences, existing systems and integrations. If deployment uses cPanel without terminal access, that is a material architectural constraint. A solution that requires SSH to build or restart is not appropriate for that workflow without an agreed alternative.
For visual direction, provide references and explain what you like about them: typography, pacing, density, motion or imagery. “Make it like this” is less useful than “keep editorial hierarchy, small-radius surfaces and smooth but restrained transitions.” Write accessibility, responsiveness and performance expectations as requirements rather than last-minute requests.
- Capture available hosting tools and deployment permissions.
- Specify supported browsers, responsive breakpoints and languages.
- Define motion preferences and accessibility expectations.
- Record search, structured data, sitemap and analytics requirements.
Make the approval process visible
Every project needs named decision makers. Agree who reviews strategy, content, visual concepts, implementation and launch readiness. Define the number and nature of review rounds, how consolidated feedback is delivered and how scope changes are accepted. A single agreed source of decisions is much more efficient than contradictory messages scattered across channels.
Distinguish a defect from a new request. A broken language switch is a defect against agreed requirements. Adding a member portal after the homepage has been approved is new scope. Both can be handled constructively when responsibility and change control are clear.
- Name the final approver and backup contact.
- Set review milestones and structured feedback windows.
- Record decisions, tradeoffs and accepted changes.
- Keep changes to scope visible to everyone involved.
Define launch and handover criteria
“The pages look finished” is not a sufficient completion criterion. The website should pass tests for its supported languages, links, forms, responsive layout, basic accessibility, metadata, search directives and HTTPS. The team should know what needs manual sign-off, which analytics and cookies are enabled and which obligations remain after release.
Write a handover checklist covering hosting, backups, asset ownership, content editing, access credentials and update procedures. For a site that may later add an admin panel, document the current content storage and routes, so the next phase does not begin with reverse engineering.
- Validate pages, status codes, sitemap, canonical and hreflang.
- Test form delivery using verified infrastructure.
- Record backups, credentials, documentation and maintenance ownership.
- Obtain explicit content, legal and launch approval.
Frequently asked questions
How detailed should a website brief be?
Detailed enough to remove ambiguity about goals, scope, content, technical constraints and approvals. A concise, specific document is more useful than a long collection of inspiration images.
Who should approve website text?
Someone authorized to confirm the business facts and claims. Designers or copywriters can draft, but factual and legal sign-off should have a named owner.
Can an admin panel be added later?
Often, if routes, templates and content are sensibly separated. Requirements around authentication, data storage and permissions still need their own design phase.
A well-written brief protects creative quality by making constraints explicit. It keeps the team focused on the right problem and reduces the cost of avoidable changes.
Services