# Website Redesign Decision Worksheet

Use this worksheet before committing to a rebuild. Record the problem, affected visitor task, and available evidence, then choose the smallest scope that can address it. This is a planning tool, not a website score or a promise of business results.

Do not include passwords, private client files, patient records, or personal inquiry details. Use public URLs, aggregate observations, and synthetic test records.

## 1. Name the problem

- Website:
- Business owner:
- Person coordinating the review:
- Important visitor or buyer:
- Task they need to complete:
- Problem observed:
- Affected URL or journey:
- How the problem was observed:
- Date, device, browser, and relevant conditions:
- Evidence link or aggregate export:
- What remains uncertain:

## 2. Choose the intervention to investigate

| Option | Useful when | Evidence to gather before committing | Completion check |
| --- | --- | --- | --- |
| Targeted repair | A specific form, resource, link, or integration is failing | Reproduction steps, affected URLs, expected and actual behavior | Repeat the original task and confirm the cause is fixed |
| Content or design refresh | The platform is usable but the offer, evidence, or page hierarchy is unclear | Buyer questions, current copy, editing constraints, representative page review | Readers can find the relevant service, understand scope, and take the intended step |
| Larger rebuild or migration | Required journeys, content structures, or integrations exceed the existing system's practical capabilities | Requirements, platform limitations, URL history, content inventory, ownership and handover needs | The written scope is accepted on staging and verified after the production release |
| Further diagnosis | The symptom is known but the cause is uncertain | Search Console, browser traces, delivery records, staff observations, or qualified review as appropriate | A testable cause and a proportionate next action are recorded |

These are planning options, not automatic package assignments. A site can need a targeted repair now and a broader project later.

## 3. Write a decision for each observed issue

| Issue / URL | Visitor task | Evidence | Proposed option | Why this scope | Owner | Acceptance check | Open question |
| --- | --- | --- | --- | --- | --- | --- | --- |
| | | | | | | | |
| | | | | | | | |
| | | | | | | | |

## 4. Preserve what is useful

- Priority landing pages and the questions they answer:
- Public pages with known external links:
- Useful copy and evidence that must remain available:
- Existing domains, accounts, code, and content access:
- Current CMS tasks staff can perform:
- Existing integrations and their owners:
- Content, imagery, or licensed assets that can be reused:
- Material that requires permission or review before reuse:

## 5. Record URL decisions for any rebuild

| Existing URL | Keep / move / combine / retire | Intended destination or status | Content to preserve | Reason / evidence | Implementer | Verification result |
| --- | --- | --- | --- | --- | --- | --- |
| | | | | | | |
| | | | | | | |

Keep an existing useful URL when its purpose remains the same and there is no reason to move it. Map a moved page to a relevant destination. Record intentionally retired material separately rather than sending unrelated URLs to the homepage.

## 6. Define scope and responsibilities

- Page templates and populated pages:
- Content the business will supply:
- Content the agency will draft or edit:
- Facts and claims requiring approval:
- Content approver and backup:
- Integrations and required access:
- Editing and handover requirements:
- Migration and redirect responsibilities:
- Performance and accessibility checks in scope:
- Form-delivery acceptance checks and recipient:
- Recurring subscriptions, licenses, and care:
- Excluded work and future options:
- Dependencies that affect the schedule:

## 7. Decide what evidence closes the work

- Expected behavior:
- Test URL and conditions:
- Test owner:
- Result and evidence link:
- Content approval:
- Deployment approval:
- Production verification owner:
- Restore or rollback owner, where relevant:
- Inquiry delivery verified by:
- Review date and remaining issues:

For search-related work, record the baseline period, search type, countries, device grouping, and affected URLs. Record recrawl dates separately from release dates. Compare relevant periods before attributing search movement to a change.

## 8. Fictional example: repair a failed inquiry route

This example is illustrative and is not a client result.

- Task: send a project inquiry from a service page on a phone.
- Observation: the page reports success, but the intended recipient has no matching test record.
- Evidence to gather: synthetic request, server response, saved backend record, recipient routing, and notification status.
- Initial scope: investigate and repair the delivery path while keeping the existing pages and visual design.
- Acceptance: the server accepts a valid test request, the agreed system and recipient receive it once, and an unsuccessful request shows a useful retry path.
- Reconsider a wider scope if: the current platform cannot support the agreed delivery and editing requirements within a maintainable arrangement.
- What this does not establish: increased inquiry volume, lead quality, search rankings, or a need to replace the entire website.

## Working resources

- Website redesign checklist: https://www.spaceagency.online/blog/website-redesign-checklist/
- Scope and pricing examples: https://www.spaceagency.online/blog/how-much-does-a-website-redesign-cost/
- SEO migration planning: https://www.spaceagency.online/blog/redesign-without-losing-rankings/
- Website RFP: https://www.spaceagency.online/templates/website-rfp-template/
- Launch checks: https://www.spaceagency.online/templates/website-launch-checklist/

Prepared November 11, 2026 by Space Agency. Free to adapt for your website planning.
