How to Say Sorry in Japanese Politely: 8 Scenarios with Email Templates

Table of contents

Who this guide is for

• Expats 1–5 years into a Japanese company, stuck between gomen nasai (too informal) and mōshiwake gozaimasen (too formal) every time something goes wrong.
• JLPT N4–N2 learners who memorized both phrases but never learned the decision rule between them.
• Foreign-affiliated, SaaS, consulting, or technical staff in Japan offices who apologize to Japanese clients or managers more than once a week.
• Readers who finished our keigo guide or keigo mistakes guide and now need an apology-specific deep dive with paste-ready emails.

This is a build-it guide, not a flashcard set. Use the 30-second self-diagnostic at the top to find your situation, then jump straight to the section you need.

30-second self-diagnostic: three questions to find your tier

Answer yes/no:

1. Is the recipient external (client, customer, another company)?
2. Did the impact land on money, deadline, or trust as real damage?
3. Is the channel face-to-face or formal email (not chat or a quick verbal aside)?

Count your yeses.

This diagnostic is a coarse filter, not a final ruling. When borderline, round up one tier. Over-apologizing creates mild awkwardness; under-apologizing erodes trust. The first is recoverable in five minutes; the second can take months.

The three politeness tiers, applied to apologies

Real-World Japanese organizes politeness as a three-tier A/B/C framework (full breakdown in the keigo guide). Mapped to apologies:

In an office, level A barely exists — it shows up only with the closest peers, the ones you’d hang out with after hours. The everyday decision is B (internal) vs. C (external).

The uchi-soto (内外) modifier

Layer the inside/outside axis on top. Inside your own organization → lean B. Outside → lean C. A one-day delay is a B-level apology to a teammate and a C-level apology to a client, even though the underlying mistake is the same.

The 8-scenario × tier matrix — 24 paste-ready lines

Eight scenarios you’ll hit weekly, broken into A/B/C levels with paste-ready completed sentences. Find your row, then take the cell that matches your recipient tier.

How to read the matrix

• Each cell is a one- or two-sentence finished line (apology + impact + next step).
• A short note on common mistakes follows each table.
• The fourth column flags the most frequent non-native error for that tier.

Scenario 1: Running late

Scenario 2: Work mistake (caught internally)

Scenario 3: Missed deadline

Scenario 4: Wrong-recipient email

Scenario 5: Same-day cancellation

Scenario 6: Noise or other inconvenience to people nearby

Scenario 7: Declining a favor or invitation

Scenario 8: Cultural or etiquette misstep

The escalation rubric — when sumimasen is not enough

When you’re unsure whether sumimasen covers it or you need to climb to mōshiwake gozaimasen, score the situation on five axes from 0 to 2.

The five axes

Score → recommended tier

Worked example: one-week deadline miss on a client project

• Impact severity: 1 point (operations disrupted)
• Relationship distance: 2 points (client)
• Repeat offense: 1 point (second time)
• External involvement: 2 points (client directly affected)
• Channel: 2 points (formal email)

Total: 8 points → C+ (heaviest). Use the full five-part anatomy with fukaku owabi mōshiagemasu in the email, followed the next day by a phone call or in-person visit.

The five-part anatomy of a polite apology

Picking the right tier alone won’t carry the apology. A polite Japanese apology has five parts in this order:

1. Cushion phrase     ← Softens the entry
2. Apology statement  ← A/B/C tier selection
3. Reason             ← 1–2 sentences. No excuses.
4. Commitment         ← What changes so this doesn't repeat
5. Close              ← Re-apology + signal you want the relationship to continue

Each part is shown below as a bad → good pair.

Part 1: Cushion phrase

A cushion sets up the apology. Without it, the apology feels abrupt.

Bad (no cushion):

Mōshiwake gozaimasen. Shiryō no teishutsu ga okuremasu.

Good (with cushion):

O-isogashii tokoro kyōshuku desu ga, mōshiwake gozaimasen.
Shiryō no teishutsu ga okuremasu.

Common cushion phrases: osore irimasu ga (恐れ入りますが), o-isogashii tokoro kyōshuku desu ga (お忙しいところ恐縮ですが), taihen mōshiage nikui no desu ga (大変申し上げにくいのですが), go-renraku ga osoku nari kyōshuku desu ga (ご連絡が遅くなり恐縮ですが).

Part 2: Apology statement (tier selection)

This is where the escalation rubric pays off.

Bad (tier too light):

Sumimasen, nōhin-butsu ni fuguai ga arimashita.
(external production-bug context with real financial impact)

Good (tier matches situation):

Kono tabi wa nōhin-butsu ni fuguai ga ari, makoto ni
mōshiwake gozaimasen.

Sumimasen and mōshiwake gozaimasen are two tiers apart. Using the former for a serious external impact reads as “they didn’t think this was a big deal.”

Part 3: Reason (the 1–2 sentence rule)

State the reason in one or two factual sentences. Longer reads as excuse-making.

Bad (long, excuse-flavored):

We also checked on our side, and it didn't reproduce
in the test environment, and the reviewers missed it
too, so it only surfaced once it was in production.
Nobody on the team anticipated this.

Good (1–2 factual sentences):

Jizen no tesuto-kankyō de wa saigen sezu, honban
rirīsu-go ni hajimete hakaku itashimashita.

“Nobody anticipated this” distributes blame and reduces perceived sincerity.

Part 4: Commitment or corrective action

The heavier the apology, the more this part needs to carry weight.

Bad (vague):

Kongo wa ki o tsukemasu.

Good (specific):

Kongo wa honban rirīsu-mae ni, honban-dōtō kankyō de
no saigen tesuto o kanarazu jisshi suru furō ni henkō
itashimasu.

“I’ll be careful” is functionally noise. Name what changes, when, and how in one or two points.

Part 5: Close

End with a second, lighter apology and a signal that the relationship continues.

Bad (no close):

(ends after Part 4)

Good (with close):

Kono tabi wa tadai no go-meiwaku o okake shi, kasanete
o-wabi mōshiagemasu. Kongo tomo dōzo yoroshiku
o-negai itashimasu.

For lighter apologies, igo ki o tsukemasu. Yoroshiku onegai itashimasu. is enough. For serious cases, kasanete owabi mōshiagemasu and fukaku owabi mōshiagemasu belong in the close.

Four paste-ready apology email templates

The five-part anatomy applied to four common scenarios. Each template includes subject → body → signature. Line breaks follow the 15–25-character rule from the Japanese business email guide.

Template 1: Wrong-recipient email (the highest-volume search query)

件名：先ほどのメール（破棄のお願い）
Subject: Re my last email — please discard

○○株式会社
△△様

いつもお世話になっております。
□□株式会社の□□でございます。

大変失礼いたしました。
先ほどお送りしたメールは、
宛先を誤ったものでございます。

恐れ入りますが、内容のご確認はなさらずに、
そのままご破棄いただけますと幸いです。

今後は送信前に宛先と内容の二重確認を
徹底し、再発防止に努めてまいります。

このたびはお手数とご迷惑をおかけし、
重ねてお詫び申し上げます。

―――――――――――
□□株式会社
□□（フルネーム）
―――――――――――

Why it works: Wrong-recipient corrections land best when fired within 30 seconds. Don’t pile on apologies; deliver the “please discard” instruction first so the recipient knows what action you need from them.

Template 2: Missed internal deadline

件名：【遅延のお詫び】○○資料の提出について
Subject: [Apology for delay] re submission of XX document

○○部
△△さん

お疲れさまです。□□です。

期限を1日過ぎてしまい、申し訳ありません。
○○資料は本日18時までに必ず送付いたします。

遅延の理由は、想定よりレビュー工程に時間が
かかってしまったためです。

今後は、提出期限の3営業日前に進捗確認を
行うフローに変更し、同様の遅れが起きない
よう運用を見直します。

ご迷惑をおかけし、申し訳ありません。
引き続きどうぞよろしくお願いいたします。

―――――――――――
□□部 □□
―――――――――――

Why it works: Internal context, so the opener is otsukaresama desu (not itsumo osewa ni natte orimasu). Tier B (mōshiwake arimasen) is the right register for one-day internal delays.

Template 3: Day-of cancellation (external)

件名：本日15時のお打ち合わせについて（欠席のお詫び）
Subject: Re today's 15:00 meeting — apology for cancellation

○○株式会社
△△様

いつもお世話になっております。
□□株式会社の□□でございます。

本日急なご連絡となり、
誠に申し訳ございません。

朝から発熱がございまして、
本日15時のお打ち合わせは
欠席させていただきたく存じます。

代わりの日程といたしまして、
来週以下の候補日でご再設定を
お願いできれば幸いです。

・○月○日（火）14時以降
・○月○日（木）終日

ご迷惑をおかけし、誠に恐縮でございます。
何卒よろしくお願い申し上げます。

―――――――――――
□□株式会社
□□（フルネーム）
―――――――――――

Why it works: Even when you’re sick, always propose 2–3 concrete re-schedule windows. Leaving “let me know when works” to the recipient looks like you’re handing off your own labor and reads as weak.

Template 4: Project spec error to a client

件名：【お詫び】○○機能の不具合について
Subject: [Apology] re XX feature defect

○○株式会社
△△様

平素より大変お世話になっております。
□□株式会社の□□でございます。

このたびは納品しました○○機能に
不具合があり、誠に申し訳ございません。
深くお詫び申し上げます。

【不具合の内容】
本日13時に貴社環境にてご確認いただいた際、
○○の操作で○○が表示されない事象が
発生していたとのこと、確認いたしました。

【原因】
事前のテスト環境では再現せず、本番環境
固有の設定差分が原因と判明いたしました。

【対応】
本日中に修正版をリリースいたします。
進捗は随時、本メールにてご報告いたします。

【再発防止】
今後は本番リリース前に、本番同等環境での
再現テストを必須工程として組み込みます。

多大なご迷惑をおかけし、
重ねてお詫び申し上げます。

何卒よろしくお願い申し上げます。

―――――――――――
□□株式会社
□□（フルネーム）
―――――――――――

Why it works: For serious incidents, the four-section structure — Defect / Cause / Action / Prevention — beats a single wall of text. Recipients have to forward this internally, and the headed structure makes that forwarding faster, which reads as competent.

Bowing — three tiers paired with the phrase you use

For in-person apologies, the bow and the phrase must travel together. Heavy phrase + shallow bow reads as insincere. Deep bow + light phrase reads as performance.

Common failure modes

• Heavy words, shallow bow: Saying taihen mōshiwake gozaimasen while half-nodding signals lip service.
• Deep bow, light words: A 45-degree bow paired with sumimasen looks dramatically out of proportion.
• Apologizing while moving: Apologies delivered while walking or with eyes off the recipient don’t register. Stop, square up to the recipient, then bow.
• Repeat-nod apologies: Saying sumimasen, sumimasen on a loop while bobbing reads as panic. One deeper bow is more credible than five shallow ones.

Five apology mistakes non-natives make

The keigo mistakes guide covers the broader register failures. Below are five errors that surface in apology contexts specifically, with the corrected line for each.

Mistake 1: Sumimasen overuse dilutes the apology

Common pattern:

Sumimasen, o-tesū de sumimasen.
Sumimasen, honjitsu-chū ni sumimasen, saisō shimasu.

Three or more sumimasen in a row makes the word lose weight.

Better:

O-tesū o o-kake shite mōshiwake arimasen.
Honjitsu-chū ni saisō itashimasu.

One apology, then state the facts and the next step.

Mistake 2: Jumping to top-tier phrasing makes light things look heavy

Common pattern:

(stepping away from your desk)
Taihen mōshiwake gozaimasen, go-fun seki o
hazushi-sasete-itadakimasu.

Using taihen mōshiwake gozaimasen for a five-minute desk absence prompts the recipient to wonder if something is wrong.

Better:

Sumimasen, go-fun seki o hazushimasu.

Light situations stay at tier B.

Mistake 3: Apology with no reason reads as evasive

Common pattern:

Mōshiwake gozaimasen. Hontō ni mōshiwake gozaimasen.
Fukaku owabi mōshiagemasu.

Stacking apologies without naming what happened leaves the recipient unsure of the situation. Sincerity reads from specificity, not from intensity.

Better:

Mōshiwake gozaimasen. Honjitsu no nōhin yotei deshita
ga, rebyū kōtei de minokoshi ga hassei shi, ashita
gozen-chū no nōhin to narimasu.

Apology → what happened → when it will resolve, in one block.

Mistake 4: -sasete itadakimasu overuse deflects responsibility

Common pattern:

Go-shiteki no ten, kakunin sasete itadakimasu.
Shūsei sasete itadakimasu. Saihatsu-bōshi ni
tsutomete-sasete-itadakimasu.

-Sasete itadakimasu (させていただきます) literally asks for permission to act. Stacking it reads as continually asking the listener to authorize your own work, which obscures who owns the fix.

Better:

Go-shiteki no ten, kakunin itashimasu.
Shūsei no ue, ashita-chū ni saisō itashimasu.
Saihatsu-bōshi-saku o honjitsu-chū ni torimatomemasu.

Switching to itashimasu / shimasu restores the speaker as the responsible party.

Mistake 5: Wrong tense — present where past is required

Common pattern (for an already-completed mistake):

Mōshiwake gozaimasen.

Using present tense for a completed failure suggests it is currently happening.

Better:

Mōshiwake gozaimasen deshita.

Past mistake → past tense (mōshiwake gozaimasen deshita). Pre-emptive apology for trouble you’re about to cause → present tense (mōshiwake gozaimasen). The two are not interchangeable.

”Looks like an apology but isn’t” — three traps

Three phrases new learners mistake for apologies.

Shitsurei shimasu (失礼します) / ojama shimasu (お邪魔します)

These are pre-action politeness markers, not apologies.

• Shitsurei shimasu: said when leaving a room or stepping away.
• Ojama shimasu: said when entering someone’s home or office.
• Shitsurei shimashita (past tense): a real apology for a past rudeness.

Shitsurei shimasu and shitsurei shimashita look almost identical but live in different categories. Present = greeting / preview; past = apology.

Osore irimasu (恐れ入ります) is a cushion, not an apology

Osore irimasu opens an ask; it does not stand alone as an apology.

Good: Osore irimasu ga, mō ichido o-okuri itadakemasu deshō ka.
Bad:  Osore irimasu. (as a standalone apology)

Used standalone, the recipient is left waiting for the rest of the sentence.

When sumimasen means “thank you”

When someone holds a door, gives up a seat, or hands you something, Japanese speakers say sumimasen — and it’s gratitude expressed through “sorry to trouble you.”

(after being given a seat)
Sumimasen, arigatō gozaimasu.

Stopping at sumimasen leaves a non-native confused about whether you’re apologizing. Pairing it with arigatō gozaimasu removes ambiguity and matches how natives often express the same complex emotion.

Frequently asked questions

Five additions to the FAQ block at the top.

What if I get no reply within 24 hours of a serious apology email?

Send a confirmation, not a chase. The framing matters: you’re checking that the recipient has bandwidth, not asking why they haven’t replied.

件名：先日のお詫びについて（ご確認のお願い）
Subject: Re my recent apology — checking in

先日お送りした○○の件、もしご確認に
お時間がかかっておりましたら、追って
こちらから電話差し上げます。
○月○日（○）の午前中であれば、
お電話可能でしょうか。

“Why haven’t you replied?” is the wrong frame. “I’ll take the burden off you” is the right one.

Should I CC my manager when apologizing to a client?

Yes for anything tier C or above. CC’ing your manager signals to the client that the incident is being escalated internally, which by itself raises the apology’s credibility. Do not put the manager in TO — that reads as offloading.

How do I apologize in Slack to a Japanese colleague?

Drop the cushion phrase, keep the apology and the next step.

○○の件、私の確認漏れでした。すみません。
14時までに修正版を送ります。

Slack is a tier-B medium for internal use. Save C-tier vocabulary for client-facing email and in-person serious apologies.

Can I use translation tools for apology emails?

For routine apologies, yes — with one rule: check the tier of the output. Translation tools default to mōshiwake gozaimasen even when sumimasen would land better. Adjust before sending.

What if my Japanese isn’t strong enough to write the C tier from scratch?

Use Template 1–4 above as scaffolds. Replace the bracketed company/name fields, adjust the reason and prevention paragraphs, and the rest will read correctly. Drafting from scratch is the long-term goal; templates are how you stay safe today.

Related reading

• Pillar: Keigo guide — the A/B/C politeness framework
• Sibling: Keigo mistakes — non-apology register failures
• Sibling: Keigo examples — full worked dialogues
• Sibling: Keigo cheat sheet — phrase lookup tables
• Sibling: Polite Japanese phrases for office — chronological office-day phrases
• Sibling: How to write a Japanese business email — 8-step process guide
• Sibling: Japanese business email templates — finished templates
• Sibling: Japanese business phrases PDF — 30 scenarios with print-friendly layout

Take the matrix with you: the Essential 30 PDF

A single-sheet, print-and-save PDF with the same A/B/C × scenario logic used in this article, expanded to 30 scenarios spanning greetings, apologies, requests, declines, confirmations, and reports. Add it to your phone home screen for instant access in the middle of an apology you can’t get wrong.

→ Get the Essential 30 PDF on Gumroad

The phrase you reach for isn’t the point; the situation you’re in is. With the 8-scenario matrix, the escalation rubric, and the five-part anatomy, you should be able to draft your next apology in under a minute and ship it confidently.