Free working pack / Version 1.0
Check what the automation actually did.
Trace a request from acceptance to the saved record and delivered result. Keep evidence for each required step before calling the job complete.
4-page PDF + editable CSV. No email or sign-in required.
Four separate checks
Each stage needs its own evidence.
A green dashboard or an HTTP success response may cover only one step. This pack helps a business owner and their provider record what happened across the whole agreed workflow.
Was this request received?
Match the request reference, intended system and time.
Did the worker finish?
Inspect the final state, including failed or skipped steps.
Was the result saved?
Read back the exact record or file at its destination.
Did it reach the destination?
Check the required receipt or destination within the agreed window.
These are proof categories, not a fixed technical sequence. A saved record and a delivered notification need separate checks. Delivery evidence does not by itself prove that a person read or acted on the result.
Inside the pack
A working record for your next test.
- 1. Define the outcomeFour proof stages and safe test setup.
- 2. Trace one requestReferences, destinations, expected result and evidence.
- 3. Check failure and recoveryFive controlled checks and an owned retest process.
- 4. Record the decisionSynthetic example, scope, monitoring and responsible owner.
Use with your provider
Keep the test controlled.
Use invented details and business-owned destinations. Have the system owner isolate anything that sends messages, creates bookings, changes records or causes charges.
Never disable a production connection or replay an old live request just to test a failure. Keep private evidence in your approved storage and put only references in the log.
The worksheet records your assessment. It is not certification or a guarantee of business results.
For a failing connection, send an enquiry describing the step and expected result. Do not send customer data or credentials.