In This Article
In my experience, the most common failed apology is not the one that refuses to apologize. It is the one that technically apologizes without actually apologizing for anything. “Sorry about earlier” is the canonical example.
It is structurally an apology. It contains the word sorry. Yet you cannot tell whether the other person understands what happened, what they regret, or what they intend to do differently. I call this the low-information apology, and it is doing more damage in your relationships than the apologies people refuse to make at all.
What the pattern looks like
You know it when you see it. A friend cancels on you twice in two weeks. The third week you say something light about it. They text back: “sorry about all that, life has been crazy. let's catch up soon ❤️”
Read that text again. Notice what it does not contain. It does not name the thing they did (canceled twice, in a way that may have left you sitting alone at a restaurant). It does not name what they understand about how it landed.
It does not propose anything specific (the “let's catch up soon” is famously code for “not actually anytime soon”). It does not signal any intention to do differently next time.
Now notice what the text does contain: the word “sorry,” a reason that is structurally an excuse, a heart emoji, and forward momentum past the moment. You are left holding one question: do they actually understand what they did? And after some thought, you often answer it yourself: probably not.
Why the pattern is everywhere
The low-information apology is the natural product of three modern conditions. One: texting compresses everything, so a long apology feels disproportionate to the small medium. With the vast majority of adults now reaching for a phone first, more and more of our hardest conversations happen in a format built for brevity. Two: the cultural script for being Cool says don't make it a thing, and acknowledging hurt feels like making it a thing.
Three: the actual work of a real apology is uncomfortable. It means sitting with how your action landed, owning a specific behavior, and naming a forward repair. The low-information apology is faster, and I have watched it become the default. It lets you keep moving past the moment without ever actually meeting it.
None of these conditions are bad in themselves. But put together, they produce the pattern. You get a generation of polite, well-intentioned, ostensibly emotionally literate people. They text apologies that look like apologies and don't actually do the work of one.
What the recipient actually feels
If you are on the receiving end of a low-information apology, you often cannot articulate why it bothers you. The apology was, technically, made. Refusing to accept it would feel petty. So you accept it, briskly, and the friendship or the relationship moves on.
What does not move on is your underlying question of whether the other person really understood. That question stays in the background, and it compounds. The next small breach feels heavier than it should, because the previous one was never properly closed.
Relationship researchers at the Gottman Institute describe a successful repair attempt as the thing that keeps conflict from poisoning a relationship. A low-information apology, by that definition, is a repair attempt that never lands. I have seen it happen slowly, almost politely, over months.
Six months later, the relationship has a texture of distance that neither person can quite name, and both of you are sure it is something else.
Example Switcher
I have been on both sides of this exchange. Click between the three moments to see how the unsaid part quietly compounds without anyone naming it.
What I would actually text back
"Okay. Yes, soon. Take carehope things settle down for you. heart."
The accepted apology
I accepted it the only polite way I could, briskly. The underlying question never closed and I knew that before I hit send.
The compounding
Each unclosed apology adds a little weight to the next small breach. The math is silent and neither of us would call it math.
The cost
Six months of distance neither of us can name, because we never named what the first low-information one was.
How to spot the low-information apology in your own outgoing texts
Read your draft. If it does any of the following, you are writing the low-information version.
- Uses the word “sorry” without naming what specifically you are sorry for.
- Includes “life has been crazy” or “things have been a lot.”
- Closes with “let's catch up soon” with no specific plan.
- Includes any emoji as the dominant emotional signal.
- Is shorter than three sentences.
Mistake Audit
I have written every one of these and watched them quietly fail. Open the row you suspect is in your last sent message.
You used the word sorry without naming what you are sorry for.
I write Sorry about all that and stop there. The apology word is doing 100 percent of the work and saying 0 percent of the thing. You can already feel the recipient holding the question, do they actually know what they did?
Why it fails: the apology word is the whole draftLife has been crazy is your explanation.
Or things have been a lot. I have leaned on both. They are not explanations. They are gentle gestures at busyness that quietly ask the other person to forgive me without me ever saying what I did. The honest version is shorter and more uncomfortable to write.
You closed with let us catch up soon and no date.
I have written this exactly. It is, almost without exception, code for not anytime soon. If you mean it, you propose a Friday. If you do not, you leave the soon to do all the work and the recipient knows you did.
An emoji is doing the emotional labor.
I sent a heart and called it a feeling. The emoji is a deposit of warmth that costs me nothing and asks the other person to accept warmth in place of accountability. The work belongs in the sentence, not in the heart.
The whole draft is shorter than three sentences.
Real apologies do not fit in one line. If you can write yours in one line, you are leaving something out. You are skipping the part where you say what you did, what you understand, and what you will do next. That is the entire technology of repair, and it lives in the second and third sentence.
What to write instead
Three sentences. The first names what you did. The second names what you understand about how it landed. The third names a specific small thing you will do differently.
This is not just a tidy formula. Research from Ohio State on the elements of an effective apology found that acknowledging responsibility and offering to repair carry the most weight. Those are exactly the parts a low-information apology leaves out. Six examples follow, drawn from real reader letters in our inbox:
- “I cancelled on you twice in two weeks. I know that probably felt like I was prioritizing everything else above you. I want to make this right, can I take you to dinner Friday, on me, and not move it?”
- “I missed your birthday. I am ashamed of missing it. Can I take you out next weekend, your pick of place, and we make it the do-over?”
- “I left you on read for three days. I'm sorry, that was avoidant and not fair. The honest reason was that I didn't know how to respond and I let it sit. I should have at least said ‘writing a real reply this weekend.’ To the actual question:…”
- “I jumped in with my opinion about the job thing before I'd actually heard you out. I am sorry. Can we restart? Tell me what you've been thinking, and this time I'm just going to listen.”
- “I told the story about your mom at brunch and I shouldn't have. It wasn't mine to tell. I am sorry. I'll be more careful.”
- “I have been distant for a few weeks and I want to acknowledge that, because I haven't said anything about it and I should have. The honest version is […]. I am sorry. I am back.”
Field Guide
Trust me, three sentences is enough. Click each move and read what a real reader actually sent. Borrow the cadence, not the words.
The takeaway, briefly
The opposite of an apology is not silence. It is the apology that looks like an apology and does no work. If you take one thing from this column, it is this: specificity is the entire technology of repair. Three real sentences will accomplish more than three months of polite forwardness.
Try it this week, and notice what happens. For more on the medium itself, the companion piece on modern texting etiquette is a good next read.
TL;DR
I have come back to these three lines more times than I want to admit. Screenshot the card. Send it to yourself. Try it this week.
Sentence 01
What you did
The action, said plainly. No softening, no excuse, no busy-life prelude. If you cannot write it, you are not ready to apologize for it yet.
Sentence 02
How it landed
What you understand about it from their seat, not yours. This is the sentence the low-information apology skips, and the one that does the most work.
Sentence 03
The specific next move
Not a promise about future you. A concrete thing: a Friday, a question, a guarantee about a thing you will not move again.
Frequently asked questions
What if the other person says my long apology is “too much”?
Real apologies are usually not too long; they are too rare. If a recipient says a three-sentence apology is too much, they may be telling you something about how they want to handle the breach, briskly and without dwelling. Adjust to them, but err toward specificity over brevity.
Is it okay to apologize over text at all?
In my experience, yes, for most situations. The cornerstone piece on how to apologize over text walks you through when a text is enough and when a phone call is the right move.
What if I genuinely don't know what they were upset about?
That is its own opening: “I want to apologize. I want to make sure I am apologizing for the right thing. Can you walk me through what landed wrong?” This is not a low-information apology. It is the structurally honest first move. I have a related piece on sorry-for-mistake messages if you want that next.
