A controlled demonstration
What a clear
report looks like.
Successful checks, planted problems, and a receipt that remains unverified. Each has its own place in the report.
Weekly evidence report
| Check | State | Fixture path | Evidence or limitation | Time (UTC) |
|---|---|---|---|---|
| Availability | Success | /healthy | HTTP response observed | 15:10:32.713 |
| Contact | Success | /healthy | Static contact element observed; delivery not tested | 15:10:32.754 |
| Link | Success | /about | HTTP response observed | 15:10:32.755 |
| Availability | Success | /broken | HTTP response observed | 15:10:32.760 |
| Contact | Success | /broken | Static contact element observed; delivery not tested | 15:10:32.762 |
| Link | Failure | /missing | HTTP 404 | 15:10:32.762 |
| Availability | Success | /no-contact | HTTP response observed | 15:10:32.764 |
| Contact | Failure | /no-contact | Agreed contact element absent in returned HTML | 15:10:32.766 |
| Availability | Failure | /failed | HTTP 500 | 15:10:32.766 |
| Availability | Success | /form | HTTP response observed | 15:10:32.768 |
| Contact | Success | /form | Static contact element observed; delivery not tested | 15:10:32.770 |
| Form receipt | Incomplete | /form | Submission observed; receipt unverified (simulated) | 15:10:32.770 |
Read the evidence
What it means.
HTTP success means a response was received at the recorded time. Contact checks inspect returned HTML only. They do not prove human usability, accessibility, every browser experience, or inbox delivery.
Links outside the exact agreed list are not fetched. Network failures are incomplete observations. A confirmed failure is a sampled condition, not an estimate of lost sales.
The simulated form result remains “submission observed; receipt unverified.” An uncertain message, payment, or form must not be retried until the original provider and recipient evidence are reconciled.
Act within the scope
The next steps.
For this controlled example, the report identifies three follow-up actions:
- Restore the planted broken destination.
- Restore the missing contact element.
- Investigate the page returning HTTP 500.
Real client work first needs written page scope, recipients, permissions, service dates, and a functioning delivery route. Client edits need a preview, backup, verification, and rollback on failure.