A website redesign brief should make a proposed investment assessable before anyone starts drawing pages. It identifies the customer problem, what will change, who supplies the necessary information, and how the business will accept the work. A mood board alone cannot do that job.
For a small business, the most useful brief is a decision record that separates essential requirements from ideas still needing investigation. Write it before requesting comparable proposals, then update it when discovery changes the facts.

Start your website redesign brief with an observable problem
Describe a real situation rather than a design preference. A hypothetical equipment supplier might report that customers cannot tell which products require an installation assessment. That gives a project direction: make suitability and the assessment route clear. “Look more premium” leaves those decisions unresolved.
Gather supporting evidence such as customer questions, failed tasks, inaccurate information, or a verified technical limitation. Record when and how each observation was obtained. Analytics may indicate where to investigate, but a drop in visits does not prove that a new design is the remedy.
Omnicom Adobe’s operating-model perspective connects work to shared customer outcomes. Apply that idea here by giving design, content, and sales the same practical definition of success.
Define the deliverables that make proposals comparable
Write a page inventory with a decision for each important URL: retain, revise, combine, investigate, or replace. Add the reason and the person who can confirm it. An inventory prevents a project scope from quietly becoming “every page we discover later.”
Separate deliverables from aspirations. “A usable request form with tested delivery” is a deliverable. “More sales” depends on traffic, offer, price, follow-up, and other conditions. A provider should explain how the site supports the aspiration without guaranteeing the commercial outcome.
Specify content migration, copywriting, photography, integrations, measurement setup, and training individually. Mark assumptions about third-party access and subscriptions. If a booking platform remains undecided, request a discovery step or a separately priced option rather than pretending the requirement is settled.
Assign content and approval ownership
List the service facts, brand assets, authorized examples, and existing materials needed for each page type. Put an owner and a realistic due date beside missing items. Missing content can change layout and timing, so it belongs in the project plan.
Name the final decision-maker and explain how feedback will be consolidated. Specialists can review different matters: operations checks service accuracy, a responsible adviser checks regulated claims when relevant, and the project owner resolves competing preferences.
Define what counts as a revision and how a new requirement is assessed. This is useful scope clarification, not a substitute for reviewing the actual proposal and contract terms.
Turn requirements into acceptance checks
For every critical requirement, write an observable check. If customers must find coverage information, ask a representative reviewer to locate it from the relevant entry page. If a form must reach a named team, submit an authorized test and confirm receipt as well as the on-screen message.
Include mobile tasks, keyboard access, content accuracy, important existing URLs, and measurement needs. Agree how defects are recorded and who confirms repairs. A screenshot proves appearance at one moment; it does not prove that an integration works.
The redesign brief should also state which changes need a specialist implementation plan, such as moving URLs or replacing an enquiry system. Do not treat launch as a single visual approval.
Compare proposals against the same brief
Ask each provider to distinguish included work, assumptions, exclusions, dependencies, and continuing responsibilities. Compare those answers before comparing headline prices. A cheaper proposal may leave necessary content or migration work with your team.
For a phased project, identify the smallest complete customer journey worth improving first. Preserve a list of deferred work and the reason it was deferred. That makes a later phase a considered choice rather than unfinished work disguised as a launch.
Blakk Brikk’s website design approach can be discussed against a concrete project scope. Bring your current URLs, evidence of the problem, and open requirements to a planning conversation. A clear website redesign brief helps both sides decide what the project actually needs.
Editorial note on website redesign brief: This article was researched and drafted with AI assistance. Cited research and illustrative examples are identified in the text.
