Inspect the customer’s path
Create an acceptance list for actual services, coverage, hours, contact destinations, forms, mobile navigation, existing URLs, ownership and measurement dependencies. Identify which checks require the operator, website maintainer or business owner. Record unresolved items and the intended rollback path.
A worked example
Fictional signoff: the design is approved, but the quote form’s delivery destination is still unverified. Mark design complete and contact handling incomplete. Another low-priority text correction may be acceptable with an owner and date. Combining both into a single “mostly done” status hides a potentially material business failure.
Choose the next action
Test the priority journeys in a production-like build, then verify the actual public domain after deployment. Keep synthetic submissions isolated or coordinated so they do not contact prospects or create meetings. Approve real business claims and permissions before publication. Avoid treating a successful build as proof the correct deployment serves the domain.
Check whether it worked
Save the release date, source revision, deployment target and evidence for the critical checks. Revisit the public site on mobile after promotion. If an established contact flow materially regresses, use the documented rollback process and investigate. Close the release only when remaining issues are explicit and owned.
Put it to work
A record you can use
- Critical journey and acceptance criterion
- Responsible reviewer
- Observed evidence
- Unresolved severity and owner
- Deployment and rollback record
Plain text. No email required. Store completed records in your approved business systems.
Next useful step
Need help applying this to your marketing? A strategy call starts with your business and the evidence you have.
Talk through your next step →For a general editorial question, email Chris. Please leave out customer details. Questions are private, and no response time is promised.