What to Include in a Factual Review After a Workplace Mistake
After an ordinary workplace mistake, write down what was expected, what you did, what happened next, what the practical impact was, and what you will do now. Keep the account specific enough that another person could follow the sequence. Separate what you observed from what you assume, then finish with a concrete correction or prevention step. This gives you a useful record for a conversation with your manager and a way to improve the task next time.
1. State the task and expected result
Begin with brief context: the task, its purpose, the relevant deadline or handoff, and the instruction or process you were following. Describe the expected result in practical terms. For example: “Send the approved version of the weekly report to the project group by 3 p.m.” This makes clear what standard you were comparing the actual result with.
If the expectation was unclear, say what information you had and what remained uncertain. Note whether you used a checklist, template, written instruction, or verbal request. Do not reconstruct an instruction as if it were exact if you are unsure of its wording; mark it as approximate or identify the source you can check. A review of an event is easier to use when the planned result and actual result are both visible. Structured after-action reviews likewise compare what was intended with what occurred and examine why the difference arose. (FEMA’s after-action review guidance)
2. Record the observable facts
Write the core facts before interpreting them: when the task took place, what action you took, what file, message, order, or system entry was involved, and when you noticed the issue. Include details that help locate the relevant record, such as a document name, version, order number, or message timestamp, where appropriate and consistent with workplace practices.
Use neutral, specific wording. “I sent the draft spreadsheet at 2:42 p.m.; the approved file was in the shared folder” is more useful than “I was careless.” The first statement can be checked and discussed; the second is a judgment that does not explain the sequence. If you do not know a detail, mark it as unknown instead of filling the gap from memory. OSHA’s incident-investigation guidance emphasizes looking beyond a quick label such as carelessness and examining the conditions and factors that contributed to what happened. Its context is workplace safety, but the fact-first approach is useful for an ordinary task review too. (OSHA, Incident Investigation)
3. Put events in chronological order
List the sequence in short steps, from the point the work began through discovery and response. Include only events relevant to understanding the mistake. A compact timeline might record: the request arrived; you selected a file; you made a change; you sent it; a colleague identified a discrepancy; you checked the approved version; you sent a corrected copy.
Keep the timeline separate from your explanation of why each event happened. This prevents hindsight from blending what you knew at the time with what became clear later. If two events’ order or timing is uncertain, say so. Official investigation guidance commonly separates gathering information from analysing it; the UK Health and Safety Executive’s workbook, for example, describes gathering information, analysing it, identifying controls, and planning implementation as distinct steps. (HSE, Investigating accidents and incidents)
4. Describe the impact and the response so far
Explain what changed because of the mistake. Focus on observable work effects: a deadline moved, a recipient received an outdated file, a colleague needed to repeat a check, an order needed correction, or no further work was affected after a prompt fix. Distinguish confirmed effects from possible ones. If you are still checking whether someone relied on the incorrect information, write that the impact is not yet confirmed.
Then record what you have already done: who you informed, what you corrected, which version is now current, and whether a follow-up is still pending. This prevents a review from sounding as though the problem remains untouched when action has already been taken. For significant workplace safety incidents, OSHA guidance includes both a description of events and corrective actions; for a routine work error, the scale can be much smaller, but the same distinction between the event and the response makes the record clearer. (OSHA, Incident Investigation)
5. Explain contributing conditions without guessing
Ask what in the task or surrounding process made the mistake more likely. Useful prompts include: Was the source file clearly identified? Were two versions easy to confuse? Was an instruction incomplete? Was a handoff or approval step missed? Did an interruption occur at a critical point? Was the process different from the one you usually follow?
Treat each answer as a possible contributing factor unless the evidence supports it. “The shared folder contained two files with similar names” is an observation if you checked the folder. “I was rushed” is more useful when tied to specifics, such as the deadline, competing task, or interruption. If there is no clear explanation yet, say that and identify what you need to check. OSHA advises that investigations look beyond the immediate act and consider why a procedure was not followed or why a shortcoming existed. The practical lesson for an individual review is to examine the step and its working conditions rather than stop at a broad personal label. (OSHA, Incident Investigation)
6. Choose practical next steps and follow through
End with actions that address both the current mistake and the chance of repeating it. Separate immediate correction from a change to the next run of the task. For example: “Today: confirm that all recipients have the corrected report. Next time: open the approved file from the shared folder and check its version date before sending.” If the fix depends on another person or a process change, record who needs to take it forward and when you will check in.
Make each action verifiable. “Be more careful” does not describe a step someone can observe. “Compare the file’s version date with the approval message before attaching it” does. A useful action is also within your control or clearly identifies the support needed. UK government lessons-management guidance recommends evidence-based findings and practical actions, with responsibility and ownership made clear; it also describes monitoring and evaluating implementation. That guidance concerns organisational resilience, but its action-planning principle transfers well to a small workplace improvement. (GOV.UK, Lessons Management Best Practice Guidance: Executive Summary)
A concise review structure
Use these prompts as a one-page note rather than a lengthy report:
Task and expected result: What was I asked to complete, and what should the outcome have been?
Facts and timeline: What did I do, when, and what happened in sequence?
Impact: What is confirmed to have changed or needed correction? What remains unknown?
Contributing conditions: What process, information, or working condition may have played a part?
Response and next steps: What have I corrected, what will I change, who else needs to act, and when will I check the result?
A useful factual review is specific, proportionate, and forward-looking. It preserves the sequence, shows the real impact without exaggeration, and turns what you learned into a next step you can actually carry out.