How to repair trust after a mistake at work

You sent the wrong numbers. Now you are drafting an apology that explains the rushed handoff, the confusing spreadsheet and how awful you feel.

Some context may be necessary. So is a sincere apology. The missing piece is often what the affected person can expect next: what is being corrected, who is handling it, and when they will hear from you.

Trust is not something you can declare restored. Your job is to give the other person accurate information and carry out a credible repair.

What research says about apologies

Ohio State's summary of research by Roy Lewicki and colleagues describes two experiments with 755 participants evaluating written apologies in a hypothetical hiring and tax-error scenario. Acknowledgment of responsibility and an offer of repair were rated especially important.

The six elements also included regret, explanation, a declaration of repentance and a request for forgiveness. The study did not show that feelings or explanations are useless, that shorter is always better, or that one apology restores workplace trust. Participants rated hypothetical apologies; researchers were not measuring colleagues' trust recovery over months.

The practical takeaway is modest: do not let the explanation crowd out responsibility and repair.

A useful apology and repair structure

1. Name your action. “I sent the invoice using the old rate.”
2. Acknowledge the known impact. “You had to pause payment and contact us again.”
3. Apologize. “I'm sorry for the extra work.”
4. Explain what matters for prevention. “I used an outdated rate sheet rather than checking the approved record.”
5. Give a repair and update time. “I'll issue the corrected invoice today and confirm by 4pm.”
6. Ask what you missed. “Is there another cost or dependency I need to address?”

You can use several sentences. There is no useful apology word limit. Remove repetition, not information someone needs to understand the error.

A worked example: the wrong customer invoice

All dialogue in this guide is fictional.

The first update

I sent Northstar's invoice using the old rate sheet. They were charged $600 too much and have paused payment. I'm sorry—I should have checked the approved rate.

I'll correct the invoice today, send you the draft before it goes to the customer, and confirm completion at 4pm. I'm adding a comparison against the approved source record before future invoices are sent. Is there another customer impact I should address?

The completion update

The corrected invoice has been sent and the account owner has the confirmation. The customer hasn't yet confirmed payment can resume. I'll check tomorrow morning. The source-record check is now on the invoice checklist.

The later check

Did the corrected invoice resolve the payment hold? Was there any additional admin work or customer concern that we still need to handle?

Adding a check lowers a specific risk; it does not make recurrence impossible. If the failure also involved confusing ownership or missing access, raise that separately and own your part without claiming sole control of the whole system.

Scripts for a manager, peer or stakeholder

To your manager

I missed the dependency check, so the launch estimate I gave you was incomplete. I'm sorry. I've now checked with the data team; their earliest delivery is Wednesday. I'll send a revised plan by noon with the options that still meet the customer commitment.

To a peer you affected

I changed the draft after the cutoff without telling you, which made you review it twice. I'm sorry. I can reconcile the two versions today so you don't have to. For the next round, I'll flag post-cutoff changes before editing.

To a stakeholder

The delivery delay came from an error in my estimate. I'm sorry for the disruption. The revised delivery is Thursday at 3pm, with review still included. I'll confirm the remaining dependency tomorrow at noon and tell you immediately if that changes the plan.

Only use a delivery promise you have enough information and authority to make. If the date is uncertain, give a time for the next reliable update instead.

Timing and unresolved concerns

For an active operational problem, notify the people who can contain it immediately; do not wait until you have a polished apology. Separate “what we know now” from the facts still being checked. For a less urgent mistake, acknowledge it promptly once the core facts are sufficiently clear.

If the other person remains distant, you do not know why without asking. They may need more repair, time, or a different working arrangement. Avoid asking them to reassure you after every update. Keep agreed commitments and revisit the concrete issue at an appropriate check-in.

If you concealed information or blamed someone else, correct that record explicitly as well as the original error. If you need to address another person's part, use a separate feedback conversation rather than attaching it as a “but” to your apology.

Try this today

Write four lines: what you did, the known impact, the repair you can commit to, and the next update time. Add a sincere apology and any causal explanation needed to understand prevention. Check every “done” against what is actually complete.