Agree scope and criteria
Before analysis, agree URLs, areas and handover criteria.
Hand over a site against one documented standard.
Agree handover criteria and scope before the analysis. Then compare the agreed scope with the result, retain the date and sources, and pass items for manual verification.
An audit run after the fact does not create contractual obligations on its own — handover criteria must be agreed first.
Handover without a shared result ends in disputes
Without a date, scope and signal sources it is hard to tell whether the site meets the agreement. Insight gives a shared handover result — with clear limits of automated analysis.
Common friction
- Each side of the dispute brings a different report and thresholds.
- Date and scope are missing — nobody knows what the handover covered.
- Automated signals get mixed with expert requirements.
How it works in practice
Retain the result
Document the result with its date, sources and measurement limits.
Verify manually
Complement automated signals with the required expert tests.
Sample output
Handover report — scope, date, sources and items for manual verification (example scenario).
Example
Handover report
Automated
Performance · SEO · A11y
Manual review
4 items · expert WCAG
What you walk away with
- A handover report with scope, date and signal sources
- Automated results separated from the manual-test list
- A shared reference point for client and team
What Insight does not do here
- It does not replace the handover protocol or contractual decision.
- It does not certify WCAG or security.
- It does not close handover without required expert tests.
To get started you need
- An agreed scope of URLs and areas
- Handover criteria agreed before analysis
- A split between automated and expert tests
Run handover on shared thresholds.
A free scan shows the analysis scope — no account, no card.
No card on Free Honest scope, no overclaims Thresholds from public standards