Map the journey beyond the browser
Choose one important action and follow it through the business. For an enquiry, list submission, validation, storage, notification, assignment, response and closure. Record the system and owner at each stage. Two teams assuming the other will reply is a process defect even when the website looks polished.
For a hypothetical installation company, the enquiry may need an area check before a survey is offered. The website should acknowledge receipt while the team confirms coverage, rather than implying that an installation has already been accepted.
Specify the handoffs
| Stage | Evidence of completion | Recovery question |
|---|---|---|
| Enquiry received | A stored request with a reference | Can the visitor retry without duplication? |
| Assigned | A named owner or monitored queue | Who handles absence or reassignment? |
| Appointment requested | A recorded request | What if the preferred slot is unavailable? |
| Appointment confirmed | Verified calendar state | Who informs the customer if it changes? |
Use the lead-generation structure guide when planning the public journey and workflow automation when several systems must coordinate.
Design the failure path before launch
Test an unavailable integration, a delayed notification and a duplicate submission. Decide which work can be retried automatically and which requires a person. Preserve the original request and its status so staff can investigate without asking the customer to start again.
Limit data collection to what the process needs. Avoid putting customer messages or confidential documents into public analytics events. Access decisions and retention rules should follow the business's approved handling requirements.
Make maintenance part of ownership
Keep a record of form destinations, integration owners, subscription dependencies and escalation contacts. Review that record when staff or providers change. A website that depends on one person's inbox needs a continuity plan.
For custom website development, include these requirements in acceptance criteria. The handover checklist should cover how the system is operated, not only how pages are edited.
FAQ
Is this only relevant to complex websites?
No. A simple enquiry form still needs reliable receipt, ownership and follow-up. Complexity increases the number of handoffs, but does not create the underlying requirement.
Should every process be automated immediately?
No. A clearly owned manual step may be appropriate while volume is low or rules are uncertain. Automate after the team can describe the successful process and its exceptions.
What should be included in launch acceptance?
Verify normal submissions, one realistic failure, duplicate handling and staff access to the resulting work. Record which stages were tested and which remain dependent on external systems.
If your website generates requests that staff must chase across systems, get in touch with one complete example of the handoff.