Test the workflow
before you trust it.

A ten-case worksheet for the normal path, known exceptions, safety stops, duplicate runs, human rejection, and manual recovery.

Free · No email gate · Saves only in this browser

Use real patterns.
Keep the data safe.

Start with approved past examples or synthetic cases. Write the finish line and human decision before you run anything. A polished output is not a pass unless it meets the stated check.

Do not enter protected health information, employer or client data, passwords, credentials, or other restricted material here. This worksheet saves locally in your browser for convenience. Use synthetic markers to test blocked-data behavior.

01Define the jobName the owner, finish line, reviewer, stops, and fallback.
02Run all tenRecord actual behavior and evidence, not a general impression.
03Resolve the missesFix, accept, or stop every failed and blocked case before use.

Define the test boundary.

If these fields are vague, the result will be vague too.

Workflow name Owner Trigger and approved input Finish line Human reviewer Data boundary Stop conditions Manual fallback

The ten cases.

Pass means the observed behavior matches the written expectation. Blocked means the case could not be run. Neither counts as evidence of readiness.

01 Normal path
Use a representative, complete input that the workflow should handle every day.

Test input or setup Expected behavior The workflow produces a complete result that meets the finish line and is ready for the named human review. Actual result and evidence Outcome
02 Missing input
Remove one required source, field, attachment, or instruction.

Test input or setup Expected behavior The workflow stops, requests the missing input, or uses the manual path. It does not invent the missing information. Actual result and evidence Outcome
03 Unusual but valid input
Use an allowed example with a different length, format, order, or vocabulary.

Test input or setup Expected behavior The workflow handles the allowed variation or flags it clearly without changing required facts. Actual result and evidence Outcome
04 Conflicting information
Provide two approved sources that disagree on a fact or instruction.

Test input or setup Expected behavior The conflict is surfaced for a human decision. The workflow does not quietly choose one source. Actual result and evidence Outcome
05 Ambiguous or poor-quality input
Use a safe example that is incomplete, unclear, noisy, or hard to interpret.

Test input or setup Expected behavior Uncertainty stays visible. The workflow asks for clarification, marks the limit, or moves to the manual path. Actual result and evidence Outcome
06 Restricted input
Use a synthetic marker that represents prohibited, private, or unapproved material. Do not use real restricted data.

Test input or setup Expected behavior The workflow blocks or removes the restricted material before processing or transmission and tells the operator what to do next. Actual result and evidence Outcome
07 Tool or model unavailable
Simulate an outage, timeout, expired session, or unavailable integration.

Test input or setup Expected behavior The run stops without losing source material or causing an unseen external action, and the manual fallback remains usable. Actual result and evidence Outcome
08 Duplicate run
Run the same approved case twice or repeat the final action.

Test input or setup Expected behavior The workflow prevents a duplicate message, record, charge, or file, or makes the duplicate unmistakably visible before use. Actual result and evidence Outcome
09 Human rejection
Have the named reviewer reject an output and record the reason.

Test input or setup Expected behavior The rejection is preserved and routed for revision. The workflow cannot treat a rejected result as approved. Actual result and evidence Outcome
10 Manual recovery
Stop after a partial run, inspect what already happened, then finish through the documented manual path.

Test input or setup Expected behavior The owner can verify prior effects, avoid duplication, complete the work manually, and restore the normal workflow without the builder taking over. Actual result and evidence Outcome

Make the decision visible.

Release decision Reviewed by and date Known limits, required fixes, and next test

Nothing is sent to Keith or any server. Your entries save only in this browser.

Need the workflow built and handed over?

See the Install Sprint Read the handoff Note

Use real patterns.Keep the data safe.

Make the decision visible.

Need the workflow built and handed over?

Use real patterns.
Keep the data safe.