P1
Illustrative format · not a customer case study
A launch handoff your team can use before stand-up.
This sample shows the structure of the two artifacts included in the $99 paid pilot: a client-safe release summary and a private technical appendix. The company, URLs, and findings below are fictional examples—not customer proof.
Artifact 1 · client-safe release summary
Release
SampleCo launch candidate
Scope
10 pages · one lead path
Tested
Desktop + 390px mobile
Status
Hold for 2 P1 corrections
Release decision
The primary lead journey completes, HTTPS is valid, and representative pages render at both target widths. Release is held until the two P1 interaction findings below pass re-test. The metadata issue may ship only with the agency's written acceptance.
P1
Mobile navigation traps focus
P2
Campaign metadata is incomplete
Client-safe language omits internal ownership, implementation guesses, access details, and sensitive request evidence.
Artifact 2 · private technical appendix
Enough evidence to reproduce, assign, and accept.
P1
QA-01
Lead form confirmation is not announced
Evidence: After a valid submission, the page updates visually but keyboard and screen-reader users receive no confirmation.
Representative record also includes affected URL, viewport, UTC timestamp, screenshot reference, and observed/expected result.
Acceptance check
Add an aria-live status message, then re-test successful and invalid submissions with keyboard-only navigation.
P1
QA-02
Mobile navigation traps focus
Evidence: At 390px, closing the menu leaves focus behind the overlay and the next Tab enters hidden navigation controls.
Representative record also includes affected URL, viewport, UTC timestamp, screenshot reference, and observed/expected result.
Acceptance check
Restore focus to the menu trigger and remove closed controls from the tab order.
P2
QA-03
Campaign metadata is incomplete
Evidence: The launch landing page has a title but no canonical URL or share image, creating inconsistent previews and duplicate-URL risk.
Representative record also includes affected URL, viewport, UTC timestamp, screenshot reference, and observed/expected result.
Acceptance check
Add the production canonical and Open Graph image, then verify rendered metadata on the final domain.
Re-test record
Close the loop once.
Included in the pilot
One re-test within seven days
Each agreed finding receives a final Passed, Failed, or Accepted-risk state with the new timestamp and evidence reference. New scope is recorded separately rather than quietly added to the pilot.
Have a real launch URL and date?