A website redesign does not need to begin with a blank page. Your existing site may contain useful explanations, familiar customer routes and material that took time to approve. Before discussing a new visual style, record what the site contains and what needs to change. That inventory gives a designer a practical brief and helps you avoid paying to recreate work you already have.
Inventory the pages and their jobs
Create a spreadsheet with one row per important page. Record the current address, page title, intended audience, primary action and person responsible for the content. Include less visible pages such as thank-you screens, account access, booking instructions and campaign landing pages. Follow your navigation and recent campaign links to find routes that a simple homepage review might miss.
Describe each page’s job in a short sentence. ‘Explains emergency call-out coverage’ is more useful than ‘service content.’ If you cannot explain why a page exists, flag it for review rather than deleting it immediately. Someone else may rely on the address in printed material, an email sequence or a customer support reply.
Sort decisions into keep, change and remove
Use ‘keep’ for content that is accurate and serves a clear purpose, even if it needs a new layout. Use ‘change’ when the offer, wording, photographs or next step is outdated. Use ‘remove’ only after confirming that the content no longer has a role and identifying what should happen to its old address.
Give each proposed change a reason and an owner. A request to make a page ‘more modern’ does not tell the team what problem to solve. A request to separate commercial and residential enquiries identifies a customer decision, a content change and a form requirement. Keep visual preferences in the brief, but distinguish them from functional requirements.
Illustrative inventory row
Current page: /repairs/. Decision: change. Reason: the page mixes workshop drop-offs with on-site visits. Keep the approved repair descriptions and workshop photos. Add separate next steps for the two service routes. Content owner: operations manager. Old address: retain unless the agreed structure requires a mapped replacement.
Protect the routes that already matter
List the actions people can take today: submit a form, call, book, download, sign in or purchase. Record the destination and who receives or manages the result. Your redesign brief should state which routes must remain available and which are intentionally changing. Include confirmation messages and follow-up notifications in that inventory.
Ask the developer to document how old page addresses will be handled when the structure changes. Do not assume a new menu automatically deals with old links. Preserve a copy of the address inventory so you can test representative links after launch. Keep access credentials out of the spreadsheet; record the account owner and use the agreed secure handover method for access.
Separate launch essentials from later improvements
Mark each requirement as essential for the agreed launch or suitable for a later phase. Essentials might include accurate service information, usable contact routes and the existing customer login. A new resource library could be valuable without being necessary for the initial redesign. This distinction gives the team a way to make decisions when time or budget is limited.
Write an acceptance condition for each essential item. For example, ‘The enquiry form sends the selected service and message to the responsible inbox, and the customer sees a confirmation.’ That condition is testable. ‘The contact page works better’ leaves room for different expectations and makes sign-off harder.
- Each essential page has an approved content owner.
- Existing customer and campaign routes are recorded.
- New features have a defined purpose and acceptance condition.
- Later ideas are retained without silently joining launch scope.
Build the handover into the brief
Decide who will maintain the site after delivery and what they need to change without help. Tell the designer which text, images, opening hours or service details change regularly. Ask for a demonstration using one of those real edits, followed by instructions the responsible person can follow later.
Agree how you will review the redesign before it replaces the current site. Use the inventory to check that retained pages and functions are present, changed items match the brief and removed pages have an intentional destination. Keep a list of open issues with an owner and decision; do not let an attractive homepage stand in for checking the rest of the site.
Your next step
Inventory your ten most important pages first. Add one keep, change or remove decision and one reason to each row, then review the list with the people who handle customers and maintain the site.
