A useful website redesign brief states what buyers must do on the site and what is failing today. Send that brief before asking for a fixed quote. It lets suppliers price the same work and name what they still need to learn.
You do not need a finished design. Start with the questions below, then mark any answer you cannot yet confirm. A short, honest brief is more useful than a long wish list with no owner.
State the business goal and the buyer's next step
Name your main audience and the one action you want from them. That might be a quote request, appointment request, call, or purchase. Say how that action works now and where buyers get stuck. Give suppliers the current site address and two or three examples of pages that matter most.
Set one practical measure, such as valid quote requests per month. Record the current number if you know it. If you do not, say so. A redesign cannot promise a result without a starting point and a way to count it.
List pages, content, and owners
Make a page list with a purpose for each page. Mark which pages stay, need new copy, or need new photos. Name the person who can approve the text, images, and legal wording. Ask suppliers to state whether writing, photography, translation, and content upload are included in their price.
Use a clear page title and headings that describe the content. Google's title guidance explains why descriptive titles and visible headings help identify a page. W3C's heading guidance also recommends a logical heading order for readers who navigate by headings.
Describe forms and other working parts
List every form, booking step, payment step, language, search tool, and outside system the new site needs. For each form, say who receives the result and what visitors see after sending it. Include a test enquiry in the launch checks so the team can confirm delivery.
Ask how the supplier will label fields and show errors. W3C's form guidance calls for labels that identify each control. Do not accept a screenshot as proof that a form works; test it on a phone and a desktop.
Set launch checks before the quote
Tell suppliers what you expect to review: phone layouts, page text, form delivery, links, and access for your staff. Ask who fixes issues found before launch and how long support lasts afterward. Name the person who gives final approval.
If page addresses or the domain will change, include an old-to-new URL list and redirect checks. Google recommends mapping old URLs to relevant new pages and testing redirects. The separate website migration checklist covers that move in detail. A redesign does not always require new URLs.
A brief you can copy
- Our current site and the main buyer action we want to improve.
- The pages we need, plus who owns copy, images, and approval.
- The forms, bookings, languages, and systems the site must support.
- Any URL or domain changes, with the old page list.
- The phone, form, link, and content checks required before launch.
- Our target date, budget range if set, and support needs.
Ask each supplier to separate design, development, content, integrations, testing, and support in the proposal. That makes differences easier to compare. CIT offers custom website development. Send CIT your brief through the quote form to discuss the scope.

