# The &ldquo;low-information apology&rdquo; is what most people give. It almost never works.

*Published:* 2026-05-11
*Author:* Alex Williams

 By  
 **Alex Williams**  
 Modern Manners Column · [credentials](/about/modern-manners-columnist)


.vl-byline-block {
  margin: 12px 0 20px; padding: 12px 0; border-top: 1px solid #CFE0DE; border-bottom: 1px solid #CFE0DE;
  font-family: 'Inter', system-ui, sans-serif; font-size: 0.9rem; color: #677075; display: flex; flex-wrap: wrap; gap: 8px; align-items: center;
}
.vl-byline-block .vl-byline-eyebrow { text-transform: uppercase; letter-spacing: 0.16em; font-size: 11px; color: #44706E; font-weight: 600; }
.vl-byline-block .vl-byline-name { color: #154543; font-weight: 600; }
.vl-byline-block .vl-byline-role { color: #677075; font-style: italic; }
.vl-byline-block .vl-byline-link { color: #44706E; text-decoration: underline; text-underline-offset: 2px; }
.vl-byline-block .vl-byline-reviewer { display: block; width: 100%; padding-top: 8px; border-top: 1px dashed #CFE0DE; margin-top: 8px; color: #3E4855; font-size: 0.85rem; }
.vl-byline-block .vl-byline-reviewer strong { color: #154543; }
**The pattern, named.** 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” — and the recipient cannot tell whether you understand what actually happened, what you regret, or what you intend to do differently. I am calling this the *low-information apology*, and it is doing more damage in modern 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.

What the text does contain: the word “sorry,” a reason that is structurally an excuse, a heart emoji, and forward momentum past the moment. The recipient is left holding the question: *do they actually understand what they did?* And the recipient often answers, after some thought: *probably not*.

Why the pattern is everywhere
-----------------------------

The low-information apology is the natural product of three modern conditions. **One:** texting compresses everything. A long apology feels disproportionate to the small medium. **Two:** the cultural script for being Cool says don’t make it a thing. Acknowledging hurt feels like making it a thing. **Three:** the actual work of a real apology — sitting with how the action landed, owning a specific behavior, naming a forward repair — is uncomfortable. The low-information apology is faster. It is also a way to keep moving past the moment without ever actually meeting it.

None of these conditions are bad in themselves. The result is the pattern: a generation of polite, well-intentioned, ostensibly-emotionally-literate people who text apologies that look like apologies and do not actually do the work of one.

  THE PATTERN, IN ONE PHRASE### &amp;ldquo;Sorry about all that&amp;rdquo;

The phrase that signals the low-information apology, almost without exception. Watch for it in your own outgoing messages. It is the polite-sounding version of *I do not want to think about what actually happened, but I want credit for having addressed it.* A real apology cannot use this phrase. The work begins where it ends.






.vl-callout-block {
  --vl-paper: #F5F9F9; --vl-ink: #154543; --vl-ink-soft: #3E4855;
  --vl-line-cool: #CFE0DE; --vl-line-warm: #FFF5F3;
  --vl-accent: #44706E; --vl-accent-mid: #FF685D; --vl-accent-soft: #E8F0EF;
  position: relative; display: flex; gap: 0; margin: 28px 0;
  background: var(--vl-paper); border: 1px solid var(--vl-line-cool); border-radius: 14px; overflow: hidden;
  font-family: 'Source Serif 4', Georgia, serif; color: var(--vl-ink);
}
.vl-callout-block, .vl-callout-block *, .vl-callout-block *::before, .vl-callout-block *::after { box-sizing: border-box; }
.vl-callout-block .vl-callout-bar { width: 4px; background: var(--vl-accent-mid); flex-shrink: 0; }
.vl-callout-block.vl-callout-warning { background: var(--vl-line-warm); }
.vl-callout-block .vl-callout-inner { padding: 20px 24px; flex: 1; }
.vl-callout-block .vl-callout-eyebrow { font-family: 'Inter', system-ui, sans-serif; font-size: 11px; font-weight: 600; letter-spacing: 0.18em; text-transform: uppercase; color: var(--vl-accent-mid); display: block; margin-bottom: 6px; }
.vl-callout-block .vl-callout-title { font-family: 'Fraunces', Georgia, serif; font-weight: 500; font-size: 1.25rem; line-height: 1.3; margin: 0 0 8px; color: var(--vl-ink); }
.vl-callout-block .vl-callout-body { font-size: 1rem; line-height: 1.6; color: var(--vl-ink-soft); margin: 0; }
.vl-callout-block .vl-callout-body p { margin: 0 0 8px; }
.vl-callout-block .vl-callout-body p:last-child { margin-bottom: 0; }
.vl-callout-block .vl-callout-body strong { color: var(--vl-ink); font-weight: 600; }
.vl-callout-block .vl-callout-body em { color: var(--vl-accent-mid); font-style: italic; }
What the recipient actually feels
---------------------------------

The recipient of a low-information apology often cannot articulate why it bothers them. The apology was, technically, made. Refusing to accept it would seem petty. So they accept it, briskly, and the friendship or the relationship moves on.

What does not move on is the underlying question of whether the other person really understood. That question stays in the background. It compounds. The next small breach feels heavier than it should because the previous one was never properly closed. Six months later, the relationship has texture-of-distance neither person can name. They are sure it is something else.

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.

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. That’s it. 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.”

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. Notice what happens.

Frequently asked questions
--------------------------

What if the other person says my long apology is &amp;ldquo;too much&amp;rdquo;?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, without dwelling). Adjust to them — but err toward specificity over brevity.



Is it okay to apologize over text at all?Yes, for most situations. The cornerstone, [how to apologize over text](/love-and-couples/communication/how-to-apologize-over-text/), walks 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 but 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.





{"@context": "https://schema.org", "@type": "FAQPage", "mainEntity": [{"@type": "Question", "name": "What if the other person says my long apology is &ldquo;too much&rdquo;?", "acceptedAnswer": {"@type": "Answer", "text": "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, without dwelling). Adjust to them &mdash; but err toward specificity over brevity."}}, {"@type": "Question", "name": "Is it okay to apologize over text at all?", "acceptedAnswer": {"@type": "Answer", "text": "Yes, for most situations. The cornerstone, how to apologize over text, walks through when a text is enough and when a phone call is the right move."}}, {"@type": "Question", "name": "What if I genuinely don't know what they were upset about?", "acceptedAnswer": {"@type": "Answer", "text": "That is its own opening: &ldquo;I want to apologize but I want to make sure I am apologizing for the right thing &mdash; can you walk me through what landed wrong?&rdquo; This is not a low-information apology. It is the structurally honest first move."}}]}


.vl-faq-block { margin: 36px 0 24px; font-family: 'Source Serif 4', Georgia, serif; color: #154543; }
.vl-faq-block .vl-faq-title { font-family: 'Fraunces', Georgia, serif; font-weight: 500; font-size: 1.6rem; margin: 0 0 16px; color: #154543; }
.vl-faq-block .vl-faq-item { border-top: 1px solid #CFE0DE; padding: 14px 0; }
.vl-faq-block .vl-faq-item:last-child { border-bottom: 1px solid #CFE0DE; }
.vl-faq-block .vl-faq-q { font-family: 'Fraunces', Georgia, serif; font-weight: 500; font-size: 1.1rem; cursor: pointer; color: #154543; list-style: none; padding-right: 28px; position: relative; }
.vl-faq-block .vl-faq-q::-webkit-details-marker { display: none; }
.vl-faq-block .vl-faq-q::after { content: "+"; position: absolute; right: 0; top: 0; color: #44706E; font-weight: 400; font-size: 1.4rem; line-height: 1; }
.vl-faq-block .vl-faq-item[open] .vl-faq-q::after { content: "\2212"; }
.vl-faq-block .vl-faq-a { margin: 10px 0 0; color: #3E4855; line-height: 1.6; font-size: 1rem; }
.vl-faq-block .vl-faq-a p { margin: 0 0 8px; }
.vl-faq-block .vl-faq-a p:last-child { margin-bottom: 0; }
### Cite this article

When citing this article, attribute as: Modern Manners Columnist, “The &amp;ldquo;low-information apology&amp;rdquo; is what most people give. It almost never works.,” *VibeLovely*, May 2026, <https://vibelovely.com/love-and-couples/communication/low-information-apology/>.


.vl-citation-block { margin: 32px 0 16px; padding: 18px 22px; background: #F5F9F9; border: 1px solid #CFE0DE; border-radius: 10px; font-family: 'Source Serif 4', Georgia, serif; color: #154543; }
.vl-citation-block .vl-citation-title { font-family: 'Inter', system-ui, sans-serif; font-size: 11px; font-weight: 600; letter-spacing: 0.18em; text-transform: uppercase; color: #44706E; margin: 0 0 8px; }
.vl-citation-block .vl-citation-text { margin: 0; font-size: 0.95rem; line-height: 1.55; color: #3E4855; }
.vl-citation-block a { color: #44706E; text-decoration: underline; text-underline-offset: 2px; }
.vl-citation-block em { font-style: italic; color: #154543; }