Trust repair protocol: what to do when the mistake is yours
Practicum for Book 3, The Economics of Trust (the Verifiability and Creation house). Version: 2026-07. Time: 30 minutes on the first day, then another hour a week later. A worksheet for an independent professional, small business, or team manager.
Authenticity capital takes years to build and one evening to spend. A mistake alone rarely destroys trust. Your response to the mistake can. People may forgive someone who fell short. They are less likely to forgive someone who pretends nothing happened.
This worksheet is not reputation management and will not teach you how to talk your way out of trouble. It focuses on one practical move: make the event verifiable before someone else does it for you.
1. The fork: what broke?
Before you speak, answer one question. The answer can require an opposite response.
| Competence failed | Integrity failed |
|---|---|
| You could not deliver: missed a deadline, made a calculation error, overlooked a defect, or took on more than you could handle | You deceived someone: hid information, exaggerated, broke a promise, or presented another person's work as your own |
| The client's question: "Can you do this work?" | The client's question: "Can I trust you?" |
| Acknowledgment works. An apology and a clear repair plan can rebuild trust after a competence failure | An admission confirms the accusation. If you truly did not do it, respond with a direct denial supported by facts, not an apology |
What actually broke in my situation: __________
Red line: never deny a real fact. Denial works only when you are innocent. Otherwise, it turns a competence failure into an integrity failure, which is much harder to repair. Ask yourself: What happens if evidence appears tomorrow?
This distinction is not just common advice. Kim, Ferrin, Cooper, and Dirks tested it in an experiment. Trust recovered better when people apologized for a competence violation and denied an integrity violation, but denial worked only when later evidence supported innocence. When evidence showed guilt, acknowledgment worked better.
2. The first hours: speak before others find out
Speed matters more than a complete explanation. Silence can look like concealment.
- We spoke first. A person who hears about your error from you can stay a client. A person who hears it elsewhere first becomes a witness to the accusation.
- We separated three things: what we know, what remains unknown, and when we will report again.
- We gave a time for the next update and kept it, even when there was no new information.
- One named person owns the response, not "customer support."
- We did not promise what we cannot know. "We will investigate and update you at 18:00." is stronger than "This will never happen again."
Who speaks for us: __________ Time of the next update: __________
3. A week later: show the repair
Words can cover the first hours. After that, show what happened and what changed.
- Timeline with facts and times: what happened and when, without commentary.
- Cause, not scapegoat: what in the process allowed the error.
- What changed: a specific process change instead of a promise to be more careful.
- What you chose not to change, and why: this shows that the review was honest rather than promotional.
4. Public review checklist
Publish a review if the error affected many people. The same structure works for a service outage, an error in professional advice, or a damaged order.
- Timeline with times.
- The mechanism that failed, not "human error."
- Who was affected and how, with scale: number of people and what they lost.
- Immediate actions.
- Process changes and deadlines.
- What will not change and why.
- Name of the person responsible for completion.
A detailed review is itself a costly signal. Only someone who looked inside the event can write it. Faking that account costs more than producing the original work.
5. What not to do
- Use legal language instead of human language. "In connection with the situation that has arisen" sounds like a refusal to answer.
- Say "We apologize for any inconvenience" without one fact. That is the most visible form of silence.
- Delete the trail, including posts, messages, or old promises. Deletion turns a competence error into an integrity question.
- Shift blame to a client, contractor, or AI. "The model wrote it" is not a defense. The channel's owner is responsible for its words.
- Promise "never again." Promise something verifiable about the process instead.
Result: one move
- What broke, competence or integrity:
__________ - What I will say today, and to whom:
__________ - What I will show in a week:
__________ - What I will change in the process:
__________
Sources
- Kim, P. H., Ferrin, D. L., Cooper, C. D., Dirks, K. T. "Removing the Shadow of Suspicion: The Effects of Apology Versus Denial for Repairing Competence- Versus Integrity-Based Trust Violations," Journal of Applied Psychology, 2004, 89(1), 104 to 118. Research record, verified 2026-07-29. The paper supports the distinction between responses to competence and integrity violations.
Related worksheets: Trust footprint map, what you have before an error; Honest AI policy, where responsibility is stated in advance; and Trust compass.