Count pages, templates and other content separately
Count reusable templates separately from individual pages. A service template may cover ten URLs, but each needs approved text, images, links and a next step. List downloads, forms and language versions separately, then mark what stays, changes, comes from your team or falls outside the scope.
Use a small content register with a URL, template, content owner, approval state and expected action. For example, an invented service page might require a scope paragraph, an exclusion list and a route to the right enquiry form. This example is a scoping aid, rather than evidence of a completed client project.
Test the edits your team will make
Choose actual maintenance tasks before selecting a static site or content management system. A marketing owner might update a service paragraph, replace an image and prepare a resource draft. Ask the proposed editor to complete those tasks in the agreed test environment.
Record who can edit, who approves publication and how a previous version is restored. Confirm which changes need a developer. A screenshot of an editing screen gives little evidence about permissions or recovery. Request the operating instructions and acceptance record for the chosen platform.
Follow a test enquiry from submission to receipt
Define what the visitor supplies and where an accepted enquiry must arrive. The form should identify its fields and communicate errors in language the visitor can act on. W3C recommends associated labels for form controls and clear submission feedback. W3C form labels, W3C user notifications.
Agree separate checks for invalid input, an unavailable destination and an uncertain response. Ask to inspect the accepted record or agreed recipient acknowledgement as well as the screen message. Define test-record handling and whether retrying uses the same operation reference. A local stub can demonstrate interface states; actual delivery needs a test in the authorized receiving system.
List migration requirements and acceptance checks
If URLs or platforms will change, export an inventory of the existing pages and important files. Map each old URL to its intended new destination or a documented removal decision. Check that the destination contains the expected information. Assign responsibility for implementing redirects and reviewing exceptions.
Google's site-move guidance recommends preparing a URL map and monitoring the old and new URLs. It also warns that search positions can fluctuate while changed URLs are processed. Treat retained rankings as a measurement question rather than a guaranteed deliverable. Google's site-move guidance.
Keep a baseline and a rollback owner in the migration plan. A redesign that retains URLs has different work from a move that changes them. Compare those scopes explicitly.
Assign ownership and continuing costs
Ask who owns the domain, hosting, repository and editing accounts. Record the licences for selected themes, images, fonts and components. Separate the build from hosting, subscriptions, ongoing content and support. Agree training, revision allowances and the process for estimating later changes.
For teams working across the US, UK and Australia, put the actual review windows, response expectations and escalation contacts in the agreement. A country name does not establish a local office or around-the-clock support.
Review the acceptance checklist at handover
Use one row per agreed task: requirement, person performing it, expected result, observed evidence and unresolved issue. Include narrow-screen and keyboard journeys alongside the editing and enquiry tasks. The buyer should be able to identify which version was checked and what remains open.
Bring the inventory, desired editing tasks and the enquiry destination to a business website scope discussion. The proposal comparison guide can help align the remaining commercial and ownership questions before an estimate is accepted.
