AI Apology or Write It Yourself?

Ask yourself one thing: do you already know the sentence?

If the specific thing you did is clear in your head, type it. A draft adds nothing except a delay, and your own phrasing will sound more like you than anything generated.

If you know something is wrong but cannot get the first sentence out, a draft helps. The blank box is a real obstacle and there is nothing noble about losing to it.

If you do not know what you did wrong, neither approach works. Both will produce something general, and general apologies tell the person you wanted the situation closed rather than understood.

That third case is worth sitting with. A vague apology does more damage than silence, because it uses up the opening you had.

These are not close calls. In each one, writing it yourself is the reasonable choice.

Serious harm. Broken trust, a betrayal, something that changed how the person sees you. The effort of finding your own words is part of what the apology proves, and the effort is visible in the result.

A repeat apology. Naming a pattern honestly is not something to delegate. I have said this before and then done it again has to come from you, because the sentence costs something to write and that cost is the point.

A relationship with its own language. Long friendships and marriages carry a register built over years. Generated text lands outside it, and the person notices immediately even if they cannot say why.

When they have asked for something specific. If someone told you what they needed to hear, write that. A draft will optimize for a general structure rather than for the thing they asked for.

Three cases where starting from a draft produces a better outcome than starting from nothing.

Everyday mistakes. Being late, forgetting something small, a bad mood that landed on someone. The situation is common, the structure is standard, and spending twenty minutes on wording is disproportionate.

Professional apologies. Work apologies follow a narrow formula: name the error, state the fix, give a date. That formula is exactly what a draft is good at, and personal voice matters less than precision.

When you keep making it worse. Some people write three versions, each more defensive than the last. A structured draft breaks that loop by showing what the shape should be.

In all three, the draft is a starting point. Sending it unread is the failure mode, not using it at all.

Sometimes, and the tells are consistent.

The first tell is register. Text pitched slightly more formal or more polished than how you normally write is what people notice first, before they consciously think about it.

The second is missing specifics. A draft fills gaps with plausible detail, and plausible detail sounds slightly wrong to someone who was there. Naming the wrong day or describing a reaction they did not have is worse than naming nothing.

The third is symmetry. Generated sentences tend to be evenly weighted. Real apologies are lopsided, because one part of what happened usually matters more than the rest.

All three are fixable in editing. Change the phrasing to sound like you, correct anything untrue, and let one part carry more weight than the others.

The honest test is whether you would tell them you used a draft. If not, keep editing until the answer changes.

Five steps, and the middle three are the ones people skip.

Describe the situation specifically. What you type is the only information the draft has, so vague input guarantees a vague result.

Read the output completely before doing anything else. Not skimming, reading.

Correct every factual claim. If it says something that did not happen, that sentence is worse than no sentence.

Rewrite anything that does not sound like you. Read it aloud if you are unsure. Speaking exposes wrong register faster than reading does.

Add one detail only the two of you would recognize. This is the single highest-value edit available, and a draft cannot do it for you.

The four parts do not change based on who assembled the sentences.

Name the specific action, with a time attached. Say what it cost the other person, in their terms. Own it with no reason following. Give one concrete change described as already happening.

The banned constructions do not change either. No but, no if, no passive voice, no apologizing for their reaction, no asking for forgiveness, no describing how bad you feel.

Length does not change. Under 180 characters, three sentences, because room invites explanation and explanation reads as excuse.

What changes is only how the first draft appears on the page. Everything after that is the same work.

Worth stating properly rather than dismissing.

The strongest version goes like this: an apology is valuable partly because it is uncomfortable to produce. Sitting with what you did, finding words for it, and exposing yourself in writing are all part of the repair. Remove the discomfort and you remove some of the meaning.

That argument is correct for serious harm, which is why the four situations above exist.

It is weaker for a card apologizing for being twenty minutes late. Not every apology needs to be an ordeal, and treating a small mistake as one has its own problems.

The distinction is proportion. Use your own words when the situation is large enough that the effort is part of the message. Use a draft when the situation is small and the effort would be theatre.

Most people land here once they have tried both.

Write the first sentence yourself. The specific action, in your words, with the day attached. This is the sentence that carries the apology and it takes thirty seconds once you have decided to be honest.

Use a draft for the structure around it if you are stuck on what comes next.

Then replace anything generated that touches a fact. Facts are yours. Phrasing is negotiable.

You end up with something specific and structured, produced in a few minutes rather than an hour of staring at a blank field.

This is the structural limit, and it is not something a better model fixes.

Three of the four parts of a working apology require facts about your life. The action, the impact, and the repair are all things that happened or will happen, and a model has access to none of them until you type them.

Only ownership can be generated cleanly, and it is the shortest part.

That ratio explains why the input box matters more than the model behind it. You are supplying three quarters of the content regardless.

It also explains why generated apologies feel hollow when sent unedited. They are structurally correct and factually empty, which is a combination people detect without being able to name it.

There is a real cost to spending an hour on wording, and it is usually invisible.

The gap between the harm and the acknowledgment is itself a message. A card sent the next morning at eighty percent quality outperforms a perfect one sent a week later, because the person spent that week deciding what your silence meant.

If a draft gets you sending tomorrow instead of next Tuesday, that trade is worth making for most everyday situations.

The exception is serious harm, where a slightly later apology with your own words beats a fast generic one. There, the delay reads as consideration rather than avoidance.

Judge which one you are in, then act accordingly rather than defaulting to whichever feels safer.

Trust that feeling. It is usually detecting something real.

If it feels too smooth, it is. Real apologies have rough edges because the person writing them is uncomfortable.

If it feels like it is about you, check the sentences. Anything describing your guilt, your intentions, or your difficulty should come out.

If it feels generic, it is missing a fact. Add the day, the room, or the exact words you used.

If it still feels wrong after editing, write it yourself. That instinct is worth more than a faster path.

The card marks the moment. The change does the repair, and that is identical either way.

Do the thing you named. An apology followed by no change becomes a data point, and the next one gets read against it regardless of who wrote it.

Do not follow up asking whether they read it. That converts a gift into a request.

If they respond with more detail about what hurt, listen without defending. People who have written you off do not bother explaining.

Nobody has ever been forgiven because of sentence construction. They are forgiven because something changed.