How to prepare a useful website redesign brief

“The website needs to look better” is a reasonable starting point. It becomes a stronger brief when you can explain what feels missing, who the website needs to serve, and what a visitor should be able to do next.

You do not need to arrive with a finished design. Bring the material your business already knows, then use the brief to connect that material with a clear direction. The aim is to make the scope understandable before the work begins.

Describe the problem in everyday terms

Start with a few concrete observations. Perhaps customers cannot find a service. The homepage may feel dated compared with the quality of the actual business. You might be spending time answering the same questions because the website does not explain the process.

Describe those situations without rushing to a technical solution. “We need customers to see our remodeling work before calling” is more useful than immediately requesting a particular gallery plugin. “People cannot tell which package they need” gives a designer a clear content problem to explore.

Choose a main priority for the first phase. That might be a stronger first impression, a clearer contact route, easier service comparisons, or better presentation of the work. Other ideas can be recorded for later without making the initial scope impossible to define.

Bring the business facts and the content you own

Gather the current services, service area, contact details, team introduction, and public hours. Confirm which information is still accurate. A redesign can accidentally give old content a more polished appearance without making it more useful.

Collect the logo files and photographs you are allowed to use. For project images, identify what the picture shows and any permission limits. A short explanation of the work is often as valuable as the image itself. Avoid sharing client information that is not needed for public presentation.

If you have genuine feedback, bring the original quote and permission to publish it. If you do not, project descriptions and transparent design reviews can still provide useful detail. The website should distinguish what a client actually said from the business’s own explanation of its work.

Choose visual references for a reason

Pick a few websites you like and explain the parts that matter. You might be drawn to large readable type, warm photography, a restrained layout, a dramatic opening, or a particular use of color and motion.

That explanation helps your designer understand the quality you want. A reference can guide the atmosphere while your website keeps its own identity. Copying another business’s claims, awards, photographs, or customer stories does not establish those facts for your business.

Think about the audience as well as your personal taste. A family exploring home care may need reassurance and a calm explanation. A craft brand can benefit from material detail and a distinct personality. A construction business may want to communicate the scale and finish of its work. The visual direction should support that conversation.

Map the important pages and journeys

List the pages that customers actually need. A focused service website may include a homepage, distinct service pages, work or project pages, an About page, and a contact route. A blog can add useful guidance when there is a clear editorial purpose.

Then trace a few journeys. Where does a person researching a service arrive? What evidence helps them decide? How do they contact the business? What happens after they submit the form? Pages and features become easier to scope when they support those journeys.

If the existing website has important URLs, record them before changing the structure. A domain or URL change needs a deliberate migration plan. Where appropriate and within your control, map old pages to relevant new destinations and check the redirects. Changing the design does not automatically preserve search traffic or make every old platform URL redirectable.

Separate the essentials from later features

Booking, commerce, memberships, custom integrations, and operational automations can add useful capabilities. They also introduce setup, maintenance, and verification work. Name the systems your team already uses and explain the result you want before choosing a replacement.

For each feature, define what is included in the initial scope. A link to an existing booking system is different from a new booking workflow. A product presentation is different from a working checkout. A form that prepares an email draft is different from a form that saves an inquiry and sends a notification.

Be clear about revisions too. Agree on the pages, design review points, content responsibilities, and included changes. A useful brief leaves room for creative work while making the boundaries of the project understandable.

Discuss ownership and ongoing costs

Ask who will own the domain, hosting account, source files, licensed assets, and submission records. Find out how updates will be published and what is needed if the website moves to another provider later.

Review actual recurring costs instead of relying on an assumed saving. Hosting, subscriptions, email services, booking tools, and paid integrations can all affect the total. A platform change may create more creative control, but the right comparison uses the services your business really needs.

Also decide how ordinary maintenance will work. Contact information changes, service pages need updates, and photographs become available after a project is complete. A documented publishing process makes those changes less dependent on a one-off manual upload.

Finish with a practical review plan

Before launch, review the content and the important customer journeys at desktop and phone widths. Check the menu, service links, project pages, contact details, form errors, and successful submission path. Include accessibility and performance checks appropriate to the project rather than treating a visual preview as a complete audit.

Agree on the launch date only after the necessary material and account access are ready. Keep a recoverable version of the previous release and a record of the new one. Those details make the final transition easier to assess and support.

Your brief can be a short document or a guided conversation. Umanifest’s website redesign approach starts with your current site, your customers, and what you want to improve. When you have a direction in mind, share your project.