A place to begin

To reflect on a mistake at work, describe exactly what happened, identify any correction still needed and choose one useful change for next time. Record what is done and what is waiting. You can take responsibility without making the incident a verdict on your ability.

Go straight to the template

First, check whether anything needs attention now

Before opening a journal, ask whether someone needs a correction, an update or a warning about the error. If the mistake has an immediate safety, privacy or other serious consequence, follow the appropriate workplace process promptly. A reflection exercise is not a reason to delay that response.

This guide is for the review that comes afterwards: the wrong slide in a meeting, an overlooked message, a missed detail in a draft. Start with one incident. Avoid combining it with every awkward thing you can remember from the past year.

Write a description another person could check. “I sent the earlier version of the deck” gives you something to work with. “I am a disaster at this job” does not tell you which file to replace or which part of the process needs attention.

Choose a repair that matches the impact

Ask what the error actually changed. Did someone act on incorrect information? Is a colleague waiting for the right file? Was the problem caught before the work went further? Use what you know, and label anything you still need to find out.

A useful repair names the correction, the person who needs it and the next update. For an ordinary wrong attachment, that might be: “The attachment I sent was an earlier draft. Please use this version. The delivery date in section two has changed.” Add an apology when appropriate, without turning the message into a request for repeated reassurance.

Do not promise an outcome you cannot control or invent a deadline to make the discomfort go away. If you need someone else to confirm the impact, make that the action: ask the project owner whether the earlier figures were used. Then record that you are waiting for an answer.

Find a change you can actually repeat

Look at the conditions around the mistake. Were two files almost identically named? Did the request change midway through the task? Was there a check you skipped, or a decision you did not have authority to make? These questions help describe the work; they do not remove your part in it.

Choose one small, relevant change. “Be more careful” is difficult to carry out. “Open the attachment from the outgoing message and check its date before sending” names a repeatable check. A clear file owner or a short handover might be more useful than another personal reminder.

If the same issue keeps happening because the workload or instructions are unworkable, it may need a specific request for help. A personal checklist cannot replace resources or decisions that belong to the team.

Put the event and the response on one page

Suppose you shared an old project deck, spotted it after the meeting and sent a correction. Your note could separate the remaining uncertainty from the steps already taken:

What happened
I attached Monday’s draft instead of the updated deck.
What I know about the impact
The team saw an old delivery date. I do not yet know whether anyone copied it into another plan.
What I have done
I sent the correct deck, identified the changed date and asked the project owner to confirm where it needs updating.
What happens next
I will check for that answer during tomorrow’s project review.
What I will change
I will open the outgoing attachment and check the date before sending.

Notice what the note does not require: certainty about everyone’s opinion of you. It keeps a record of the issue and the response. If new information arrives, you can update the part that actually changed.

Give the review a stopping point

Ask whether another reread is producing a new action or repeating the same accusation. If the repair is done and the next check is scheduled, you can close the note even while you still feel uncomfortable. You do not need to reach a perfectly reassuring conclusion first.

Try a factual stopping sentence: “The correction is sent; the remaining question is with the project owner.” Then return to the activity you had chosen for the evening. If you want a broader ending to the day, use the end-of-workday reflection rather than extending the mistake review.

If writing repeatedly leaves you more distressed or interferes with everyday life, stop the exercise and consider talking with someone you trust or a qualified professional. The page is optional; it is not a test you need to pass.

Make it yours

Your copyable template

Use this in your own notebook or notes app. Keep what fits; leave out the rest.

The specific mistake was:
The impact I know about is:
What still needs checking is:
The correction I have made or will make:
Who needs the update:
One practical change for next time:
I will review the remaining question at:
For now, my response is:

A little space, with Sera

Make room for the thought behind the mistake.

If the practical correction is clear but the thought still needs words, bring one part of it to Sera. Check what it understood before choosing a small next step.

Try a free reset

First reset free · No account or card needed.
Want to keep going? Explore Sera Plus.

A few things you might wonder

Should I apologise again if I still feel embarrassed?

Check whether another message would provide new information or address an unmet need. For an ordinary corrected mistake, embarrassment alone does not tell you that another apology is useful. Respond to the situation and the people affected.

What if my manager is disappointed?

You cannot settle their reaction in a private note. If feedback is needed, ask a specific question about the work and the expected correction. The difficult-conversation guide can help you separate what was said from what you are assuming.

How long should I reflect?

There is no required duration. Stop when you have a factual description, a proportionate response and a useful next check. Repeating the review without new information is not a requirement for taking responsibility.

Further reading & scope

Australian Public Service Commission: Seek, Reflect, Develop

The APSC discusses specific feedback and learning through reflection. The repair note and scenario here are SeraNook’s own examples, not an APSC procedure or an endorsed intervention.

How we make these guides · Contact SeraNook