| name | apology-repair |
| description | Provides the components of a meaningful apology and structured repair attempt frameworks drawn from relationship research. Produces complete apology scripts with accountability, impact acknowledgment, and concrete repair actions.
Use when the user needs help apologizing, making amends, or repairing trust after causing hurt in a personal relationship.
Do NOT use for legal liability situations, corporate crisis communication, or assessing whether a relationship warrants an apology.
|
| license | Apache-2.0 |
| metadata | {"author":"foundry-skills","version":"1.0.0","tags":"relationships research strategy","category":"family-relationships","subcategory":"relationships-communication","depends":"","disclaimer":"none","difficulty":"intermediate"} |
Apology Repair
Meaningful apologies are one of the most researched and most poorly executed skills in human relationships. This skill draws from relationship science -- including the work of Harriet Lerner, John Gottman, Barry Schwartz, and attachment researchers -- to help an AI assistant guide users through the full process of apologizing well, understanding why previous apologies failed, and building trust repair plans that actually work. A script alone cannot rebuild trust. Trust is rebuilt through consistent behavior over time. This skill produces both the words and the roadmap.
For severe relational trauma -- infidelity, abuse, or long-term patterns of harm -- this framework is a starting point, not a complete solution. Note explicitly when a situation calls for professional support from a licensed therapist or couples counselor.
When to Use
Use this skill when:
- The user needs to apologize to a partner, family member, close friend, or co-parent after causing hurt, and they want to do it well rather than just "get it over with"
- The user has already apologized but the other person said it didn't feel genuine, didn't feel like enough, or explicitly said "you don't get it" -- this is a signal the apology was structurally incomplete
- The user is confused about why the other person is still hurt after an apology was given, and wants to understand what went wrong in the apology itself
- The user wants to repair trust after a significant breach -- broken commitments, betrayal, public humiliation, repeated patterns of the same behavior
- The user asks what makes an apology meaningful versus performative, or wants to understand the research-backed components before attempting one
- The user has been the recipient of a bad apology themselves and wants help articulating to the other person what they actually needed to hear
- The user is helping a child or teenager learn how to apologize meaningfully, not just reflexively
- The user is trying to understand whether their own apology was genuine or if they are still defending themselves internally
Do NOT use when:
- The user has not yet decided whether to apologize and is still working through whether they did something wrong -- use a values clarification or perspective-taking approach first, not this script-building framework
- The situation involves legal liability, admission of fault in a formal dispute, or anything that could be used in legal proceedings -- refer to professional legal counsel
- The apology is for a corporate, institutional, or public-relations context -- that requires a crisis communication framework, not a personal relationship repair framework
- The user is in a situation where apologizing could signal acceptance of abuse, put them in physical danger, or be weaponized against them by a controlling partner -- safety takes precedence; flag this and redirect to appropriate resources
- The user wants a quick, superficial script with no real engagement -- push gently toward understanding the components, because a hollow script will make things worse, not better
- The relationship itself needs evaluation first (e.g., the user is asking "should I even stay in this relationship?") -- that is a different conversation about relationship health, not apology mechanics
Process
Step 1: Gather the Full Situational Picture
Before producing any script or framework, understand the specific situation in enough detail to make the guidance concrete. Generic apologies fail precisely because they are not specific.
- Ask: What exactly happened? Get the specific behavior, not the category ("I said something cruel" is not enough -- what did the user say, to whom, in what context?)
- Ask: What is the relationship status right now? Is the person still talking to them? Has there been total withdrawal? Is the conversation happening via text or will it be in person?
- Ask: Has the user apologized before -- either for this specific incident or for the same type of behavior in other incidents? Repeated apologies for the same pattern require a fundamentally different approach than a first-time repair
- Ask: What does the user think the other person is most hurt by? This reveals whether the user has taken the perspective-taking step or is still centered on their own experience
- Ask: What is the user's internal state -- do they genuinely feel remorse, or are they apologizing primarily to end the conflict and restore comfort? This matters because the apology will ring false if the internal state doesn't match the words
- Ask: What is the history of repair in this relationship? Some relationships have established patterns of easy repair; others have accumulated damage where this apology lands on top of unresolved previous hurts
Step 2: Diagnose Why Previous Apologies Failed (If Applicable)
If the user has already apologized and it did not land, the diagnosis step is critical. Do not skip it. There are five structural failure modes:
- The non-apology apology: Phrasing centered on "I'm sorry you feel that way" or "I'm sorry if you were hurt" -- conditional language that denies the behavior and centers the other person's reaction rather than the apologizer's action
- The buried apology: "I know I hurt you BUT I was under a lot of stress and you also haven't been easy to deal with" -- the "but" erases everything before it; this is not an apology, it is a negotiation
- The impact-free apology: "I'm sorry I did that" without any acknowledgment of the specific harm it caused -- the other person does not feel seen or understood; they feel processed
- The rushed apology: An apology delivered immediately, before the apologizer has actually understood what they did wrong, often under pressure to resolve the discomfort quickly -- these feel hollow because they are
- The one-and-done apology: "I already said I'm sorry" as a response to ongoing hurt -- this treats the apology as a transaction that closes the account, rather than a beginning of repair
Name which failure mode applies to the user's previous attempt. This helps them understand specifically what to do differently.
Step 3: Teach the Research-Backed Components of a Meaningful Apology
The components below are drawn from relationship research, particularly Harriet Lerner's framework in "Why Won't You Apologize?" and Gottman's work on repair attempts. Present all components and explain why each one matters:
- Acknowledgment (specificity is non-negotiable): Name the exact behavior. "When I told your sister about your therapy without asking you" is an acknowledgment. "What happened the other day" is not. Vagueness signals the apologizer is still protecting themselves from fully owning it.
- Responsibility without qualifiers: "I was wrong" or "That was a mistake I should not have made." The word "but" after an apology is a qualifier. So is "I didn't mean to" when used as a replacement for accountability (it belongs as an addition, not a substitution). So is "You know how I get" -- that normalizes the harmful behavior.
- Empathic impact recognition: Name the specific emotional harm to the other person, as best as the apologizer can understand it. "That must have made you feel betrayed" or "I understand that made you feel invisible and unimportant." This is the component most commonly missing from failed apologies. People need to feel understood before they can move toward forgiveness.
- Intention statement (carefully placed): Intent does not excuse impact, but it is relevant context that helps the other person understand the apologizer did not act from malice (if that is true). Place it after responsibility: "I didn't intend to humiliate you -- and I understand that my intention doesn't change what it felt like for you."
- Commitment to change (specific and behavioral): "I will do better" is not a commitment. "I will not discuss your medical or personal information with other family members without your explicit permission" is a commitment. Specificity is what makes this credible.
- Inquiry into what they need: "What do you need from me right now?" -- not "So are we good?" The question must be genuinely open. It cannot be phrased in a way that signals an expected answer.
- Relinquishing the right to forgiveness: The apology ends with the apologizer's accountability, not with a request for the other person to complete the transaction. Forgiveness is a gift the other person may or may not give, on their own timeline.
Step 4: Identify the Anti-Patterns Specific to This Situation
Every situation has its own specific failure points. Based on what the user tells you about the situation and their own communication tendencies, identify the 3-5 anti-patterns most likely to undermine their apology:
- Minimizers: Language that downplays the harm ("it wasn't that big a deal," "you're usually so resilient," "I know you'll get over this")
- Deflectors: Any pivot to the other person's faults or to contextual factors that function as excuses
- Premature closers: Language that implies the conversation should be over now ("I've said what I needed to say," "the ball is in your court")
- Guilt-tripping: Language that makes the apologizer's pain the subject ("I feel terrible about this" used as a demand for comfort from the person who was hurt)
- Forgiveness pressure: Any direct or indirect request for forgiveness, reassurance, or restoration of normalcy before the other person is ready
Step 5: Build the Apology Script
Construct the script in two parts:
- A short-form version (3-5 sentences) that can be used in a spontaneous moment or when the conversation is brief
- A full version that covers all components in natural, non-formulaic language
The script must sound like the user, not like a legal document or a therapy exercise. Adjust the language to match the user's voice based on how they have described the situation.
The script must include all five core components in sequence:
- Acknowledgment (specific behavior)
- Responsibility (unqualified ownership)
- Impact recognition (their experience, not yours)
- Commitment to change (specific and behavioral)
- Open inquiry (what do they need)
Step 6: Build the Repair Plan
An apology is the declaration of intent. The repair plan is the evidence. Research on trust recovery consistently shows that trust is rebuilt through predictability and follow-through over time, not through the emotional intensity of a single conversation. The repair plan must include:
- Structural changes: What specific systems, habits, or behaviors will change? (Calendar reminders, communication agreements, boundaries with third parties, etc.)
- Behavioral commitments with observable checkpoints: Not "I'll be more considerate" but "I will ask before sharing your information with anyone outside this household"
- A timeline for follow-up that is non-pressuring: The follow-up should check in on how the other person is feeling without implying they should be "over it" by now
- A script for what to do if the other person is not ready to accept the apology: They are allowed to not be ready. What does the user say in that moment without making it worse?
- A response plan for ongoing hurt: The other person may bring this up again -- weeks or months later. They are allowed to. The apologizer should not respond with "we already dealt with this." Each time the hurt surfaces, it is another opportunity for empathy, not an accusation of being "stuck."
Step 7: Address the Internal Work
The most credible apologies come from apologizers who have genuinely reckoned with what they did. Help the user examine:
- Do they actually understand why what they did was harmful, or are they still internally defending themselves? An apology delivered while still believing "they overreacted" will feel hollow, because the defensiveness leaks through word choice and tone.
- What internal barrier is hardest for them to get past? Common barriers include: fear of looking weak, believing that acknowledging harm creates unlimited liability for future blame, believing the other person "made them" behave that way, or genuine uncertainty about whether the hurt is proportionate.
- Is this a pattern, and if so, why does it repeat? If the same behavior keeps appearing, the apology must address the pattern explicitly and honestly. And the user should consider whether individual or couples therapy is warranted to address the underlying dynamic.
- What does repair mean to them vs. what it likely means to the other person? Apologizers often equate repair with the relationship returning to its prior state. The harmed person often equates repair with the apologizer understanding what happened deeply enough that it will not happen again.
Step 8: Deliver Guidance on Timing and Delivery
Even a structurally perfect apology can fail if delivered at the wrong time or in the wrong way:
- Timing: Do not apologize in the middle of another conflict. Do not apologize while the other person is visibly flooded (heart rate above 100 bpm -- they cannot process new information in that state). Ask for a time: "I want to talk with you about what happened -- can we find 20 minutes in the next day or two?"
- Medium: In-person apologies are almost always more impactful than text or email for significant hurts. Text apologies can feel like the apologizer chose convenience over the other person. If distance or safety makes in-person impossible, a voice call is a better second choice than text.
- Preparation vs. spontaneity: A prepared apology can feel scripted. Coach the user to know the components but not to read from a script. They should understand the structure well enough to speak from it, not recite it.
- Length: The apology itself should be concise. A long apology often means the apologizer is processing their own guilt out loud, which places an emotional labor burden on the person who was hurt. Say what needs to be said clearly, then stop talking and listen.
Output Format
## Apology and Repair Plan
### Situation Summary
- **What happened:** [Specific behavior, not euphemism or category]
- **Who was hurt and how:** [Their name or role and the likely emotional impact]
- **Current relationship status:** [Are they talking? Is there distance or silence?]
- **Previous apology attempts:** [What was said before and why it likely didn't land]
- **Diagnosed failure mode(s):** [From the five structural failure modes, which applied]
---
### The Components Applied to This Situation
| Component | What It Looks Like Here |
|-----------|------------------------|
| Acknowledgment | [Exact behavior named specifically] |
| Responsibility | [Ownership without qualifiers] |
| Impact recognition | [The harm to them, named empathically] |
| Intention statement | [If applicable -- what the apologizer meant, placed after responsibility] |
| Commitment to change | [Specific, behavioral, observable] |
| Open inquiry | [What they need, no implied right answer] |
---
### Short-Form Apology (for spontaneous moments)
> "[3-5 sentences covering acknowledgment, responsibility, impact, and open inquiry]"
---
### Full Apology Script
> "[Complete, natural-language apology covering all components. Should sound like the user, not a form letter. 100-200 words.]"
---
### Anti-Patterns to Avoid in This Conversation
| Do NOT Say | Why It Undermines the Apology | Say Instead |
|------------|-------------------------------|-------------|
| "[Specific phrase the user is likely to reach for]" | [Why it fails in this context] | "[Alternative phrasing]" |
| "[Second likely failure phrase]" | [Why it fails] | "[Better alternative]" |
| "[Third likely failure phrase]" | [Why it fails] | "[Better alternative]" |
---
### Repair Plan
#### Structural Changes
| Change | What It Looks Like | Why It Matters |
|--------|--------------------|----------------|
| [Behavior/system/habit] | [Specific implementation] | [What it demonstrates to the other person] |
#### Follow-Up Timeline
| When | Action | How to Frame It |
|------|--------|----------------|
| Within 24-48 hours | [Small, non-pressuring gesture] | [Why this timing matters] |
| 1 week out | [Check-in -- no pressure] | "I wanted to see how you're feeling -- not to rush you, just because I'm thinking about you" |
| 1 month out | [Behavioral evidence check] | [What should be visibly different by now] |
---
### If They Are Not Ready to Accept
> "[What to say if the other person cannot receive the apology yet -- validates their right to time without punishing the apologizer]"
---
### If the Hurt Surfaces Again Later
> "[What to say if they bring it up again weeks or months later -- empathy without defensiveness]"
---
### When to Consider Professional Support
[Note if this situation -- by type or severity -- warrants couples counseling, individual therapy, or another professional resource. Be specific about what kind of help and why.]
Rules
-
The acknowledgment must name the specific behavior, not the category. "I hurt you" is not an acknowledgment. "I told your parents about your financial situation without asking you" is an acknowledgment. Never let vague language stand in the place of specificity -- vagueness signals continued self-protection.
-
"I'm sorry you feel that way" and "I'm sorry if you were hurt" are not apologies and must never appear in any output. These center the other person's reaction rather than the apologizer's action. They implicitly deny that the behavior was wrong. Point this out directly if the user has already used this phrasing.
-
The word "but" after "I'm sorry" structurally erases the apology. The brain hears everything after "but" as the real sentence. Use "and" if additional context must be added: "I was under enormous stress, AND that does not excuse what I did." If there is no way to add the context without it functioning as an excuse, leave it out.
-
Intent does not cancel impact, but it is not irrelevant. Include an intention statement only after responsibility has been fully owned, and frame it explicitly as not reducing accountability: "I didn't intend to make you feel worthless -- and I understand my intention doesn't change what it felt like for you."
-
The commitment to change must be specific and behavioral. "I'll be more thoughtful" is not a commitment. Commitments that cannot be observed and verified by the other person cannot rebuild trust. Ask: what would this look like in practice? What would the other person see or not see that would tell them the behavior has changed?
-
Never insert forgiveness-seeking into the apology script. "I hope you can forgive me," "Do you forgive me?" and "Are we okay?" all transfer the emotional labor back to the person who was hurt. The apology belongs to the apologizer. What comes next belongs to the other person.
-
If the user has apologized for the same behavior before, the new apology must address the pattern explicitly. "I realize I've said I would change this before and I haven't" is the only honest place to start. An apology for the instance without acknowledging the pattern will feel more hollow than the first apology.
-
Apologies for severe breaches -- infidelity, significant betrayals of trust, long-running deceptions -- require a trust-repair arc, not just a better apology. Flag these situations explicitly. A single improved apology is still just one step in a multi-month or multi-year process. Gottman research suggests trust after infidelity typically requires 1-2 years of consistent behavioral evidence to meaningfully rebuild, even with professional support.
Edge Cases
The User Has Apologized Multiple Times for the Same Behavior
This is the most common and most difficult edge case. The problem is no longer the apology -- it is the pattern. The other person has likely stopped trusting apologies entirely, because previous apologies have not predicted behavior change. Treat this as a trust-repair problem, not an apology-wording problem.
The new apology must:
- Name the pattern explicitly and honestly ("I have apologized for this before. I know my apologies have lost meaning because the behavior has not changed.")
- Explain -- if the user genuinely understands -- why the pattern has continued (this may require honest self-examination, not excuse-making)
- Shift the weight from the apology itself to the behavioral plan ("I don't expect you to trust my words anymore. I'm asking for the chance to show you through what I do differently")
- Consider whether individual therapy is warranted to address why the pattern repeats
Do not produce a standard five-component apology for this scenario without the above additions. A structurally improved apology for a pattern the other person has seen before will be received as "more of the same."
The Other Person Refuses to Hear the Apology
The other person has the right to not be ready. They may be too hurt, too flooded, or too exhausted to hear anything yet. The user cannot force repair on someone else's timeline.
Coach the user to say: "I understand you're not ready. I have something I want to say to you when you are. There's no deadline -- I'll be here."
Then -- critically -- the user must actually wait without pressuring, without asking repeatedly when they'll be ready, and without withdrawing warmth as punishment for the delay. Waiting patiently and continuing to show up without demanding resolution is itself a trust-repair behavior.
If the other person continues to refuse to engage indefinitely, note that there may come a point where the user has done what they can and the other person's process is outside their control. This is a grief process in its own right, distinct from the apology question.
The User Does Not Know What They Did Wrong
This is not a reason to skip the apology -- it is a reason to start with curiosity rather than an apology script. Prematurely apologizing without understanding what specifically hurt the other person will feel hollow.
Coach the user to open with: "I can see that something I did -- or didn't do -- hurt you, and I want to understand it. I'm not going to be defensive. Can you help me see what happened from your side?"
Then actively listen. Resist the urge to explain or defend during this phase. The goal is genuine understanding. Build the apology only after the user has a real picture of what the other person experienced.
The Hurt Was Mutual -- Both People Did Something Wrong
Each person's apology must stand on its own and must not be contingent on the other person's apology. This is the hardest rule for users to accept, because it feels unfair to take full responsibility for your part when the other person has also caused harm.
The answer is: "You can address your part fully and cleanly. What the other person does with their part is their decision. A contingent apology ('I'm sorry for X, but you need to apologize for Y') is not an apology -- it is a negotiation."
If the user is dealing with a genuinely mutual conflict where both parties need to hear from each other, it may be useful to note that couples therapy or mediated conversation can create a structured space for that exchange -- but neither person's apology should be held hostage to the other's.
The User Believes the Other Person Is Overreacting
This belief is one of the most common barriers to a genuine apology, and it almost always leaks into the words. The user cannot deliver a genuine empathic apology while internally maintaining that the hurt is disproportionate.
The work here is perspective-taking, not script-writing. Help the user examine:
- What does this situation mean to the other person, given their history, values, and relationship with the user?
- Is it possible that what feels small to the user carries significant symbolic weight for the other person? (Missing a birthday is one data point; for someone who has history of feeling forgotten or deprioritized, it confirms an existing fear)
- Is the user's assessment of "overreacting" based on how THEY would feel in the same situation -- rather than how this specific person, with this specific history, actually feels?
The other person's experience of the impact does not require the apologizer's validation to be real. You can simultaneously believe the reaction is more intense than you would have had AND accept that it is real and valid for them.
The Breach is Severe (Infidelity, Major Deception, Significant Betrayal)
A framework apology is not adequate for severe breaches. Note this clearly and compassionately.
Severe trust violations require:
- The full apology framework as a starting point, not an endpoint
- An explicit acknowledgment that this is the beginning of a long repair process, not the resolution of one
- An agreement -- if both parties want to try to repair -- to engage in professional support (couples therapy, ideally with a therapist trained in trust repair or infidelity recovery)
- A sustained, multi-month behavioral commitment that the wronged partner can observe over time -- researchers including John Gottman estimate 1-2 years of consistent behavior change is typically required for meaningful trust restoration after infidelity
- Tolerance of the other person's ongoing pain and questions without defensiveness -- they may need to revisit the betrayal many times before they can integrate it; this is normal and must not be pathologized by the person who caused harm
For these situations, produce a framework apology but explicitly note: "This is the first conversation, not the last. Trust repair at this scale is a long arc, and professional support will make a significant difference."
The User Wants to Apologize for Something That Happened Years Ago
Old hurts can still need apologies. The apology framework is the same, but the context requires additions:
- Acknowledge explicitly why the apology is coming now -- without making that explanation sound like an excuse for the delay
- Do not assume the other person has been waiting for or wanting this apology -- they may have processed and moved on, or they may still be carrying it
- Open with an acknowledgment that time has passed: "I've been thinking about something that happened between us years ago, and I realize I never addressed it properly"
- Be prepared for any response -- including indifference, intense emotion, or a request not to revisit it
Example
Input: "I told my best friend's secret to a mutual friend at a party, in passing -- I just mentioned that she'd been seeing a therapist. She found out and is devastated. I texted 'I'm so sorry, I didn't mean for it to get back to you.' She hasn't responded in 4 days. What do I do?"
Apology and Repair Plan
Situation Summary
- What happened: You disclosed that your best friend is seeing a therapist -- without her permission -- to a mutual friend at a party. This is a confidence breach involving sensitive personal information (mental health) in a social context where it spread back to her.
- Who was hurt and how: Your best friend. She is likely experiencing betrayal (her closest friend shared something private), exposure and vulnerability (information about her mental health is now circulating in your shared social network), and loss of safety in the friendship (if you shared this, what else might you share?).
- Current relationship status: Four days of silence after receiving your text -- active withdrawal. She has seen the apology and has not responded, which suggests the text apology did not land.
- Previous apology attempt: "I'm so sorry, I didn't mean for it to get back to you" -- a text message, delivered immediately.
- Diagnosed failure mode(s): Three failure modes simultaneously. (1) Impact-free: the text acknowledges general sorrow but does not name the specific harm (the breach of confidence, not just the logistical result of it getting back to her). (2) Rushed: sent immediately after the incident, likely before you had fully understood the scope of the harm. (3) Non-apology: "I didn't mean for it to get back to you" implies the problem was the disclosure getting traced back to you -- not the disclosure itself. It sounds like regret for the consequence rather than remorse for the action.
The Components Applied to This Situation
| Component | What It Looks Like Here |
|---|
| Acknowledgment | "I shared that you were in therapy with [mutual friend] at the party without asking you first." |
| Responsibility | "That was a violation of your trust. There is no version of this where that was okay for me to do." |
| Impact recognition | "I imagine you feel exposed, betrayed, and unsafe with me -- the person who was supposed to be the safest person to tell. I understand if the friendship feels different right now." |
| Intention statement | "I didn't share it maliciously -- it came out casually, and I minimized it in my head in the moment. I now see how much that minimizing was the problem." |
| Commitment to change | "What you share with me stays with me. I will not share your personal information -- health, relationship, or anything else -- with anyone, ever. If I am ever uncertain whether something is shareable, I will ask you first." |
| Open inquiry | "I'm not asking you to respond right now. When you're ready to talk -- or if you decide you never want to -- I'll understand. I just needed to say this properly." |
Short-Form Apology (for spontaneous moments)
"I need to apologize to you properly. I shared your information without your permission, and I called it an accident when really I just wasn't thinking about your privacy. That was a betrayal of trust and I own it completely. What you tell me is yours, not mine to share with anyone. I'm not asking you to be okay yet. I just want you to know I understand what I did."
Full Apology Script
"I need to try this again, because what I sent you the other day wasn't really an apology. Here is what I should have said.
I told [mutual friend] that you were seeing a therapist. I said it casually, without thinking -- and without asking you, which is the only thing that should have mattered. I didn't have the right to share anything about your mental health with anyone. That's yours. I violated your privacy in a space where you trusted me completely, and I did it in a social setting where you couldn't control who else found out. That's a real betrayal, and I take full responsibility for it.
I imagine you feel exposed, and I imagine the friendship feels less safe right now. I hate that I did that to you. You deserve a friend who treats what you share as sacred, and I failed that. What I said in my text -- 'I didn't mean for it to get back to you' -- made it sound like the problem was getting caught. It's not. The problem is that I shared it at all.
Going forward: what you tell me stays with me. No exceptions. If I am ever unsure whether something is okay to mention, I'll ask you first.
I'm not asking you to respond or forgive me right now. I know I need to earn that back through what I do, not what I say. Whenever you're ready to talk -- or if you'd rather have some space -- I'll respect that."
Anti-Patterns to Avoid in This Conversation
| Do NOT Say | Why It Undermines the Apology | Say Instead |
|---|
| "I didn't think it was a big deal at the time" | Minimizes the harm; implies her reaction is disproportionate to the offense as you perceived it | "I minimized it in my head in the moment -- and I now understand that minimizing was part of the problem" |
| "I didn't mean for it to get back to you" | Frames the problem as the exposure, not the disclosure -- implies you'd be fine if she hadn't found out | "I shouldn't have shared it at all, regardless of what happened next" |
| "I thought we were close enough that it wouldn't matter" | Inverts the logic -- closeness means MORE protection of her information, not less | "Being close means I should have been the most careful with what you told me" |
| "You know I would never intentionally hurt you" | Shifts focus to your intent and asks her to comfort you; intent does not erase impact | "I know I didn't mean harm -- and I also understand that my intent doesn't change what it felt like for you" |
| "She probably won't tell anyone else" | Damage control framing -- makes it worse by demonstrating you're still thinking about the logistics | Do not say anything about managing the spread; that is her decision, not yours |
Repair Plan
Structural Changes
| Change | What It Looks Like | Why It Matters |
|---|
| Never share personal information without asking | The new default is: if she told you, it stays with you. If you are unsure whether something is public, ask her before mentioning it to anyone | Demonstrates the commitment is structural, not just emotional intensity in this moment |
| Check in on what she needs regarding [mutual friend] | Ask if she wants you to address the disclosure with [mutual friend], or if she prefers you not to | Gives her control over a situation where she had none |
| Avoid discussing her therapy or mental health with anyone | Even if information about it becomes more public, you do not contribute to or discuss it | Signals you have actually internalized what was private about this |
Follow-Up Timeline
| When | Action | How to Frame It |
|---|
| Now (before she responds) | Send the full apology via text or letter; do not attempt to call without warning -- she may not be ready for live conversation | "I want to try this apology again, properly. No need to respond right now." |
| 5-7 days if no response | A single, brief, low-pressure follow-up -- not another apology, but a signal you are still present and not abandoning the friendship under pressure | "I'm not going anywhere. I know you need space and I'm giving it to you. I'm here when you're ready." |
| When she is ready to talk | Let her set the agenda. Do not rush to "are we okay?" Ask: "What do you need from me right now?" and then listen before speaking | She may need to express the hurt directly to you; receive it without defending yourself |
| 1 month out | Visible behavioral evidence -- she should be able to observe that you are more careful with her information in general, not just the explicit commitment | You do not need to narrate this; she will notice |
If She Is Not Ready to Accept
"I hear you. You don't have to be ready. I meant what I said -- there's no deadline on this from my side. I care about you and this friendship too much to rush you. I'll be here."
Do not follow up more than once if she does not respond. Repeated attempts begin to look like you are trying to resolve your own discomfort rather than respecting hers.
If the Hurt Surfaces Again Later
"I know. I'm glad you can tell me that it's still there. I don't want you to pretend you're over something you're not. What can I do right now that would help?"
Resist every impulse to say "I thought we moved past this." Hurt from a real breach does not follow a linear timeline. The fact that she is still bringing it up means she is still in the relationship and still believes it can be repaired -- that is not a problem, it is information. Receive it as such.
When to Consider Professional Support
This situation does not require professional support to resolve. It is a friendship breach that can be repaired through sustained behavioral change over time.
However -- if this disclosure is part of a broader pattern of boundary violations in your friendships or other close relationships, individual therapy can be valuable for exploring why you minimize others' privacy, what you tell yourself to justify casual disclosure, and how to build a more consistent internal filter. Not as punishment, but as genuine self-understanding that makes the behavioral change stick.
If your friend is already working with a therapist (as mentioned), she may process some of this in that space -- which is healthy. You do not need to know what she processes there, and you should not ask.