FILE: ARCH-AFT-028 / STATUS: ACTIVE
I made a mistake at work and I cannot stop replaying it
Do the next ten minutes first. They are below.
AFTER THE FACT / PATTERN: The Perfectionism Trap
One mistake, and the day keeps replaying. It went out with your name on it. You have reread the thing eleven times, and now you are checking the inbox for a reply you are afraid of.
This page is not going to tell you whether you are good at your job. That is a verdict and this is a record. What is here is what to do in the next ten minutes, and then, if you want it, what the replay is.
The next ten minutes
Send the correction, if it has not gone. One message, to the person the error reached, and nothing else tonight.
[INTERRUPTION SCRIPT]
Write this, or something this size:
There is an error in what I sent. The correct figure is X. I have fixed it in the file. Sorry for the trouble.
No account of how it happened. No list of what else you have now checked. No question that asks them to tell you it is fine.
Then close the inbox and leave it closed until morning. The reply, if one comes, is a morning problem. Refreshing does not make it arrive sooner. It only keeps the error in front of you.
If the correction has already gone, the ten minutes are simpler. Close the laptop. Do not open the other files to look for more mistakes. That sweep is the thing this page is about, and it has already begun.
What the replay actually is
It feels like learning from the mistake. It is not. Learning takes one pass. You have done eleven, and the eleventh found nothing the first did not.
The replay is the checking sequence running on something that can no longer be checked. Before the thing went out, one more pass could still change it. Now nothing can. The sequence does not know that. It keeps reaching for a pass that would make the error not have happened.
The replay is not a correction. It is the last pass, repeated, on a file that has already left.
That is also what the sweep is. Opening last month's work to look for other errors feels like diligence. It is the same pass, pointed at files nobody has questioned.
Why it will not stop by itself
Because it runs on a signal that arrives before the thought. For this sequence it is usually the jaw, and a drop in the stomach. Three to seven seconds later the email is open again. By the time you are telling yourself to stop, your hand has already done it.
That jaw is the body signal, which is what you feel as the pattern starts. It is worth more to you than any thought about the mistake, because it arrives first every time, and the thought only ever arrives second.
The window is the few seconds between the jaw and the reopening. Three to seven is a working figure, not a measurement. Tonight the window has closed many times. It also opens again every time, which is the only reason a page like this can exist.
What to say tomorrow
If somebody raises it, one sentence about the error and one about the fix. Not a sentence about you.
[REWRITE FRAME]
In the room, in an ordinary voice:
That one was mine. It is corrected, and I have added a check at that step.
Then stop. Do not offer the list of other things you went looking for overnight. Do not ask whether it has changed how they see you. That question gives them a second job.
The next time the jaw sets and your hand goes to the inbox, the different action is to leave it closed and say, out loud if you can: it is sent. Repeat that until it is easier to reach than the refresh. A late catch still counts. Closing the file on the third reread instead of the eleventh is a repetition.
What to do with the dread
Part of the dread is pointing at something true. An error went out with your name on it, and you would rather it had not. Keep that part. It is the reason for the check at that step, and it is the size of one mistake, not the size of your job.
The other part says this is the one that shows what you really are. That is a verdict, and there is nowhere in this archive to file one. One wrong figure is a wrong figure. It is not a character.
The sweep for what else you got wrong is the dread asking for more files to run on. Do not feed it tonight. If something else needs checking, it can be checked in daylight, once, with the sequence quiet.
Eat something, drink some water, and sleep. Going over it does not pay anything back. It is load, and load lowers the threshold for tomorrow's first email.
What tonight actually is
An entry. Filed after the fact, which is an ordinary thing a record accepts rather than a failure being reopened.
There is no shame register here and nowhere for a guilt entry to be filed. The error is out and corrected. The next time the jaw sets is the one available to you, and a closed inbox is what goes there.
The full file on this sequence, including why one more pass never feels like avoidance, is at /patterns/why-cant-i-finish-anything when you want it. It will keep.