JAM Digital / Websites
Website redesign checklist: what to decide before the design starts
Use this website redesign checklist to agree objectives, content, functionality, accessibility and measurement before design and development begin.
Before you dive in
The key points.
Agree audiences and outcomes before choosing layouts.
Plan content, functionality and responsibilities early.
Include accessibility, migration and acceptance in the brief.
A useful website redesign checklist begins with the decisions the site needs to support. Before choosing layouts, agree who the website is for, what those people need to understand and which actions matter to the business. That gives the design a purpose and the project a way to judge progress.
An ageing visual style may prompt the conversation, but the underlying problem could be unclear services, poor content, a difficult enquiry journey or a platform nobody can maintain. Diagnose the problem before committing to a solution.
Write a brief around outcomes
Choose a small set of outcomes that can guide trade-offs. Examples include making a complex service easier to understand, enabling the marketing team to edit pages or improving the quality of enquiries. Define how you will assess each one.
Avoid using “modern” as the only acceptance criterion. A more useful requirement is: a prospective buyer can find the relevant service, understand its scope and reach the enquiry form on a mobile phone without relying on a sales call to explain the basics.
Discuss commercial priorities through marketing consultancy if the brief is still a list of disconnected requests.
Inventory content before drawing templates
List the existing pages and decide which to keep, improve, combine or retire. Identify the main audience, business purpose and content owner for each. Check performance before removing pages that attract useful visitors.
Then map the proposed navigation and page types. A service page, case study and technical resource may need different content structures even if they share a visual system. Agree the real content requirements rather than designing around placeholder text.
Make ownership explicit. Who writes the copy? Who approves technical claims? Who supplies suitable images? Content delays can hold up a project even when development is ready.
Use this project checklist
| Decision | What to record | Done when |
|---|---|---|
| Audience | Priority buyers and their questions | Stakeholders agree the main journeys |
| Outcomes | Business goals and measures | Each goal has an assessment method |
| Content | Page inventory and owners | Retain, improve and retire decisions exist |
| Functionality | Forms, search and integrations | Requirements include failure states |
| CMS | Editing and publishing needs | Editors can describe routine tasks |
| Accessibility | Design, content and testing responsibilities | Checks are part of acceptance |
| SEO | Important pages and URL changes | Migration work has an owner |
| Launch | Hosting, domains and release plan | Responsibilities and sign-off are clear |
Use the final column to record evidence, rather than ticking a box because a discussion happened.
Specify how the site will work
Describe what each feature needs to do. For an enquiry form, include fields, validation, recipient routing, confirmation, spam handling and what happens if delivery fails. For an integration, identify the system owner and how the connection will be tested.
Select a CMS around actual editing tasks. Ask for a demonstration of adding a service, changing navigation and publishing an article. Confirm who owns the domain, hosting account, source files and third-party licences, and what ongoing support includes.
These decisions shape website development scope and make supplier proposals easier to compare.
Include accessibility from the beginning
Make readable content, keyboard operation, visible focus, labelled forms and appropriate contrast part of the design discussion. Test important journeys with different devices and input methods. Accessibility needs responsibility across content, design and development.
The W3C accessibility planning resources can help structure that work. Agree the project’s specific checks and involve relevant users where possible, rather than leaving all evaluation until launch week.
Separate redesign decisions from migration execution
This checklist establishes the project. The SEO migration checklist covers mapping URLs, redirects, release checks and monitoring when pages or platforms move. Include that work in the project plan rather than expecting it to happen automatically.
Use the website cost guide to compare scope, then record acceptance criteria for the complete site: approved content, working journeys, measurement, performance checks, handover and access.
If you need an initial view of the current site’s priorities, request a website review. It is a starting assessment, not a substitute for a fully scoped redesign or technical audit.
Your next steps
Put it into practice.
- Write down the priority journeys and business outcomes.
- Inventory content and assign owners.
- Specify functionality, accessibility and migration requirements.
- Agree launch responsibilities, testing and handover.
