It is 11:40 at night and you have just seen it. The figure in the proposal you sent to the client at four o'clock is wrong. It isn't off by a rounding error. It is off by a whole digit. Your stomach drops, and then the bargaining starts. Maybe they won't notice. Maybe you can fix it in the next draft and call it a revision. Maybe if you wait until morning, the right words will arrive on their own.

They won't. And the thing keeping you awake is not the mistake. It is the belief that the mistake, once named, will rewrite how everyone sees you.

That belief is mostly wrong. It is also one of the more expensive wrong beliefs in working life.

The fear is real, and it is aimed at the wrong target

People who hide errors are usually not dishonest by nature. They are protecting something fragile: the picture of themselves as someone competent. Admitting the error feels like handing over the evidence.

But look at what the other person is actually evaluating. They are not tallying whether you ever fail. Everyone fails, and your manager and your client know it. They are quietly asking a different question: when something goes wrong, will this person tell me, or will I find out on my own?

That question is the one your silence answers badly. A mistake you report is a data point about the work. A mistake you conceal, once discovered, becomes a data point about you.

What the pratfall effect actually says

In 1966, the psychologist Elliot Aronson and his colleagues ran a now-classic experiment. Participants listened to recordings of a person answering quiz questions. In some versions the person was highly competent, and in others merely average. In half the recordings, the speaker also clumsily spilled coffee on himself.

The result became known as the pratfall effect. The highly competent person who spilled the coffee was rated more likable than the same person who didn't. The average person who spilled it was rated less likable.

That second half matters, and it is the part people leave out. The effect is not a license to be careless. It says that a visible flaw can make a capable person feel more human and approachable, while it only confirms the doubts people already had about someone they weren't sure of.

What does that mean for your 11:40 p.m. email? If you have a track record, an honest correction reads as the confidence of someone with nothing to hide. If you are newer and still earning trust, the lesson is not to hide. It is to make the correction so clean and so competent that it becomes the proof of your competence.

Speed and substance repair trust. Excuses don't.

Researchers who study trust repair, including work by Peter Kim, Donald Ferrin, and colleagues in 2004, found that the best response depends on what kind of violation occurred. When people doubt your competence, as with a wrong figure or a missed deadline, an apology tends to restore trust better than a denial. When the doubt is about your integrity, the picture changes, and a flat denial can actually work better than a confession, if you are in fact innocent.

Most workplace errors are competence errors. A wrong number. A forgotten attachment. A date you misread. For these, the research points the same direction your conscience does: say it plainly, and take responsibility.

Notice what that leaves out. It leaves out the long preamble, the passive voice ("an error was made"), and the quiet redistribution of blame to a tight timeline or an unclear brief. Those moves feel protective. To the reader, they read as someone managing their image instead of managing the problem.

The shape of an email that works

A good correction has four parts, and it fits in a few short paragraphs.

Lead with the fact. Put the error in the first sentence, in plain words. "The total in the proposal I sent today is wrong: it should read $48,000, not $480,000." The reader should not have to dig.

Say what it affects. One sentence on the consequence, honestly sized. Not minimized, not dramatized. "This changes the budget summary on page three, and nothing else."

Say what you've done and what happens next. This is the part that carries the competence signal. A corrected file is attached. You've checked the other figures. You will confirm by noon tomorrow that the revised version matches the source data.

Take ownership once, briefly. "That was my mistake, and I'm sorry for the confusion." One sentence. Not three. Over-apologizing hands the reader a second job: reassuring you.

What you leave out matters as much. No explanation of how tired you were. No "unfortunately." No "just wanted to flag." If context truly helps them, like a process gap that could repeat, offer it after the fix and frame it as prevention, not as defense.

Why it's so hard to write

The difficulty is rarely the words. It is that the first draft you produce while embarrassed is almost always one of two things: a cringing wall of apology or a stiff, defensive memo. Both come from the same place. You are writing to your fear of the reader instead of to the reader.

There is a simple way around this. Say it out loud first, to no one, as if explaining it to a colleague you trust. Out loud, people tend to state the fact first and the fix second, because that is how you'd talk to a friend across a desk. The defensive padding mostly appears when we sit down to compose.

Your next moves

  • Send it today, not tomorrow. If you've found the error, the clock is already running, and the delay will cost you more than the mistake. Aim to write and send within the hour.
  • Write the first sentence before anything else. Finish this line: "The [thing] I sent on [day] has an error: [what's wrong and what's right]." If you can't complete it plainly, you don't yet understand the error, so check that before you write the rest.
  • Attach or include the fix. Do not send a correction that only announces the problem. Include the corrected file, figure, or date so the reader has nothing to chase.
  • Cut your apology down to one sentence. Reread the draft and delete every second or third "sorry," "unfortunately," and "I feel terrible." Keep one clear ownership line.
  • Add one forward-looking line. Name the check you'll run so it doesn't happen again: a second pair of eyes, a source-data cross-check, a reminder. Make it specific enough that you could be held to it.

Where a voice helps

This is a place where speaking the draft aloud earns its keep. When you're rattled, your spoken version is usually the shorter and more honest one. You say "I got the number wrong, here's the right one, I've checked the rest" without decoration.

That is how we use Quill. You talk through what happened, the way you'd tell a colleague, and it turns your speech into clean text on your device, in whatever app you're already in, without sending your words to the cloud. Then a one-tap rewrite can tighten the tone: shorter, more direct, less apologetic. The correction that comes out sounds like a calm professional, because the first draft was you thinking out loud rather than you bracing for impact. If you'd like to try that on your next awkward email, you can find Quill at https://quill.lumenlabs.works.

And if that 11:40 p.m. stomach drop arrives tonight anyway, remember what the reader is really asking. Make the answer easy: you'll tell them, early, plainly, with the fix in hand.