Measurement
A preview is not a launch.
A website can look finished while its enquiry routing, production configuration and operational responsibilities remain untested.
The screen is one layer of readiness.
A local preview can demonstrate layout, navigation and browser behavior. It may use simulated data or stop at a local confirmation. That is useful evidence for the experience, but it does not prove a real enquiry will reach the business.
Treat visual acceptance and operational acceptance as related, separate checks.
Follow a real submission.
| Layer | What needs evidence |
|---|---|
| Browser | Validation, accessibility and confirmation |
| Submission service | Successful receipt and error behavior |
| CRM or inbox | Correct record, destination and context |
| Ownership | The responsible person can act on it |
| Measurement | A success event represents actual success |
Test the unsuccessful path.
An unavailable endpoint, rejected input or duplicate submission should not produce a false success message. The user needs an honest state and a sensible recovery route. The team needs enough visibility to diagnose the failure without exposing personal information unnecessarily.
Check the configuration that changes at release.
Production domains, search indexing, analytics identifiers, consent behavior and service credentials require deliberate configuration. A preview should not create production conversion events simply because someone tests its form.
Make the launch decision reviewable.
Record which checks passed, under what conditions and who owns unresolved work. Do not replace missing evidence with a broad statement that the website is ready. A clear release record helps the business decide when the remaining risk is acceptable.