Before publishing
Check the promise, factual sources, destination, mobile readability and resource delivery. Record the content identifier.
Give recurring work a clear owner, a visible result and a way to recover. Keep the routine small enough to sustain.
A failed email, duplicated event or inaccessible download should have a visible status. Record what failed and the next safe action. Check whether the original action completed before retrying it.
Use a stable order, booking or event identifier where the provider supplies one. A retry should not create a second customer action accidentally. Handle refunds, cancellations and access changes through the source system.
Subscriber responses should use approved answers for known questions. Missing information, billing exceptions and uncertain cases need a clear route to a person. Keep the response record limited to what the task requires.
Try the response exampleWrite down the problem, the evidence, the change and the reason it should help. Decide when you will review it and which outcome would support keeping, adapting or stopping the change.
If the evidence is sparse, choose an investigation: test the journey with a reader, check the reporting source or ask a focused question. A clear unknown is useful information.
Keep cash received, approved commissions, pending amounts, costs and working time separate. A successful workflow test demonstrates delivery; business demand needs its own evidence.
Use the review worksheets