# Website redesign proposal scope and acceptance worksheet

Source: https://lindo.ai/guides/website-redesign-proposal
Updated: 2026-09-14
Published by: Lindo Team

A fictional four-page example, scope-to-test matrix, commercial fields, and handoff checklist to adapt after discovery.
Illustrative planning aid, not market data or a guarantee. Do not store credentials or private client data here.

## Working brief

### Client situation / evidence / customer action

- Notes:
- Owner / decision:
- Evidence / next action:

### Existing URL and dependency inventory

- Notes:
- Owner / decision:
- Evidence / next action:

### Pages / content quantities / included journeys

- Notes:
- Owner / decision:
- Evidence / next action:

### Client inputs / content owner / approval date

- Notes:
- Owner / decision:
- Evidence / next action:

### Project fee / currency / recurring costs / payer

- Notes:
- Owner / decision:
- Evidence / next action:

### Exclusions / optional work / change approval

- Notes:
- Owner / decision:
- Evidence / next action:

### Milestones / dependencies / review rounds

- Notes:
- Owner / decision:
- Evidence / next action:

### Acceptance test / evidence / owner / exception

- Notes:
- Owner / decision:
- Evidence / next action:

### Commercial agreement review / unresolved terms

- Notes:
- Owner / decision:
- Evidence / next action:

## Acceptance checklist

- [ ] The problem is verified and the intended customer action is stated.
  Owner / evidence / date:

- [ ] Pages, content quantities, and visitor journeys are bounded.
  Owner / evidence / date:

- [ ] Existing URLs and dependencies have owners.
  Owner / evidence / date:

- [ ] Fees, ongoing costs, exclusions, and optional work are separated.
  Owner / evidence / date:

- [ ] Schedule depends on named inputs and approvals.
  Owner / evidence / date:

- [ ] Each deliverable has an acceptance test.
  Owner / evidence / date:

- [ ] Production handoff and unresolved exceptions are recorded.
  Owner / evidence / date:

- [ ] Commercial terms are reviewed separately; no ranking or revenue guarantees are implied.
  Owner / evidence / date:

## Examples and templates from the guide

### Fictional proposal opening: Cedar Garden Studio

Purpose: help referred homeowners understand garden-design services and submit a suitable project enquiry.
First release: Home, Garden Design, Projects, Contact.
Preserve: approved service facts, domain ownership, and useful existing URLs where practical.
Change: service-area explanation, project captions, enquiry instructions.
Not included: booking software, payments, ongoing articles, multilingual content.
Schedule: agreed after approved content and required account access are available.
Fee: insert the agreed project amount, currency, and treatment of ongoing costs.
Decision requested: approve scope and responsibilities, resolve open dependencies, then agree commercial terms.

### Commercial and schedule fields to resolve

Project fee / currency:
Included pages, records, and review rounds:
Ongoing services / estimated cost source / payer:
Optional work / separate approval needed:
Content deadline / named approver:
Draft milestone begins after:
Review window and consolidated feedback owner:
Launch prerequisites:
Change request: description → impact → written approval before work
Commercial agreement and unresolved terms:

## Working tables

### Fictional four-page release: a scope-to-test matrix

| Deliverable | Client input | Acceptance evidence |
| --- | --- | --- |
| Home: offer and service-area summary | Approved positioning and contact details | Owner confirms wording and CTA destination |
| Garden Design: service, process, enquiry CTA | Approved scope and exclusions | Visitor can identify project fit and next step |
| Projects: three project summaries | Licensed photos and factual captions | All three records match approved source material |
| Contact: agreed enquiry fields and delivery | Recipient and privacy wording | Authorized test reaches the recipient; errors are clear |
| URL preservation and agreed redirects | Existing URL inventory and access | Kept URLs load; changed URLs reach relevant destinations |

### A handoff record the client can inspect

| Test | Evidence | Owner |
| --- | --- | --- |
| Contact submission and validation | Authorized test received; required-field errors checked | Agency tester + client recipient |
| Mobile service-to-contact journey | Device/browser and observed result | Agency tester |
| URLs and search access | URL map results, canonical/indexability checks | Technical owner |
| Routine edit and account access | Client performs an approved content update | Client editor |
| Unresolved exception | Impact, approver, responsible person, next date | Named decision owner |

## Sources and next steps

- Use the local-business discovery questions: https://lindo.ai/guides/how-to-sell-websites-to-local-businesses
- Use the migration SEO checklist: https://lindo.ai/guides/website-migration-seo-checklist
- W3C: accessible forms: https://www.w3.org/WAI/tutorials/forms/
- Google Search Central: site moves with URL changes: https://developers.google.com/search/docs/crawling-indexing/site-move-with-url-changes
- Work through website project pricing: https://lindo.ai/guides/how-to-price-website-design
- Define the maintenance plan separately: https://lindo.ai/guides/how-to-create-website-maintenance-plans
- Open the free web design proposal worksheet: https://lindo.ai/tools/web-design-proposal-generator
- Compare agency builders by their handoff requirements: https://lindo.ai/best/website-builder-for-agencies