Hands-on practice · no signup
Practice: writing the report after a mistake
Something has gone wrong and you need to tell someone. The hard part is not the form — it is knowing what belongs in it and what does not.
Free, and nothing here is real. No account, no download, and no message, payment, or account is ever actually touched.
Part of Incident Reporting and First Response. Free, plain-English practice for everyday work technology.
What you'll do
- Start from the moment you realise something is wrong.
- Fill in what happened, when, and which system was involved.
- Decide what to leave out: the private details themselves, passwords, and who you think is to blame.
- Submit it and see what a normal response looks like.
- Understand why reporting early genuinely helps you.
What it teaches
Report early with the plain facts: what happened, when, which system, and who is affected. Leave out the private details, any passwords, and any guess at blame.
support request vs reportable incidentfirst response and early reportingprivacy-safe evidencepreserving the sceneapproved reporting route
Want the full lesson?
The simulation is the practice. The lesson explains the why, in plain English, in about five minutes.