Handoff Check
Evidence for the workflow you were promised.
Independent browser evidence for one agreed acceptance workflow before you approve delivery or release payment.
The exact workflow, expected result, environment, and untested boundaries are locked before execution. A real browser then submits a unique test marker, checks independent sessions, waits a declared delay, and produces individually hashed evidence.
"I paid for this app. How do I know the workflow I need is really saving my data?"
Runs locally. Public HTTP and HTTPS targets only; private, internal, loopback, and credential-bearing URLs are refused.
What the self-serve check proves
- Lock the approved workflow definition and its SHA-256 before execution.
- Load the public application in desktop and mobile browser viewports.
- Run one unauthenticated fill-click-observe workflow that you declare.
- Create a unique test marker and observe it in a fresh browser session.
- Repeat the immediate observation to detect inconsistent results.
- Wait a declared delay and observe the same marker from another fresh session.
- Record expected versus observed and a PASSED, FAILED, or INCONCLUSIVE status for every step.
- Produce a downloadable ZIP with evidence IDs, individual file hashes, a manifest hash, and a final package hash.
Assisted services
Request a scope through Endstorm before purchasing.
The tool itself is free. Paid services begin with a short intake, then continue to the existing Stripe checkout. Payment is confirmed only by Stripe's signed webhook and never starts an automatic test.
How to read the result
Passed means the declared workflow met the recorded observations.
Failed means the declared workflow produced evidence of a defect.
Inconclusive means the tool could not make a reliable determination.
Not tested means exactly that. It is never silently treated as passing.
Download
Windows only. Unzip the package and run Handoff Check.exe. First launch may download the pinned Chromium browser engine.
Reports and delayed-job state are stored locally. Every package records file and package SHA-256 hashes. Hashes detect alteration but are not a third-party digital signature.