The Vocabulary of Korean Apologies by Severity

Article body

Korean apology vocabulary is a scale. The words do not simply differ by politeness level; they differ by severity, responsibility, relationship, and whether repair is expected. 미안해, 죄송합니다, 사과드립니다, 송구합니다, 유감입니다, and 양해 바랍니다 do different social work.

미안해 is personal and casual. It fits friends, close relationships, and small mistakes. 미안합니다 is polite but can still feel personal. It is not the safest choice for formal institutional apology.

죄송합니다 is the everyday polite apology workhorse. It fits service situations, workplace mistakes, public inconvenience, and respectful personal apologies. It acknowledges burden more strongly than 미안해.

사과드립니다 is formal and explicit. It is common in written statements, corporate apologies, official apologies, public incidents, and serious mistakes. It names the act of apologizing.

송구합니다 is highly deferential and often formal. It can express deep regret or humility toward someone burdened by one’s action. It may sound excessive in small everyday situations.

유감입니다 is tricky. It can mean “regrettable,” and it often expresses regret about a situation without fully accepting personal responsibility. In public statements, it may sound distant or strategic.

양해 바랍니다 / 양해 부탁드립니다 asks for understanding. It is not exactly an apology. It often appears in notices: delays, construction, service interruption, schedule changes. It can be appropriate, but if harm is serious, it may sound evasive.

Severity ladder

Guided reading

서비스 이용에 불편을 드려 죄송합니다. 현재 문제를 확인 중이며, 복구가 완료되는 대로 다시 안내드리겠습니다.

This apology has three parts: burden acknowledged, problem status, future update. That is stronger than a bare 죄송합니다 because it includes process and repair.

Compare:

• 늦어서 미안해. Casual personal apology.
• 답변이 늦어 죄송합니다. Polite/apologetic.
• 이번 사고에 대해 깊이 사과드립니다. Formal public apology.
• 이용에 불편을 드린 점 양해 부탁드립니다. Notice-style request for understanding.

Learner traps

Do not use 유감입니다 when you need to accept responsibility. Do not overuse 송구합니다 in casual contexts. Do not think 양해 바랍니다 is automatically warm; it can sound bureaucratic. And do not apologize so intensely for tiny issues that the interaction becomes uncomfortable.

Reusable workflow

1. Rate the mistake: small inconvenience, delay, personal hurt, public harm, serious incident.
2. Identify relationship and hierarchy.
3. Choose apology phrase.
4. Add responsibility if needed: 제 실수로, 확인이 늦어, 불편을 드려.
5. Add repair or next step if the burden is real.

Suggested interactive/tool module

An apology-severity selector that changes phrase, ending, responsibility statement, and repair sentence based on mistake size and relationship.

Additional practice and repair

What this pass strengthens

Apology vocabulary is easy to overteach as a politeness list. This pass makes the article more diagnostic by tying each apology form to severity, responsibility, relationship, and repair.

Severity-and-responsibility matrix

Before/after repair lab

Weak learner apology:

늦어서 유감입니다.

Repair:

늦어서 죄송합니다. 기다리게 해서 정말 죄송해요.

Why: 유감입니다 can sound detached. Being late to a person usually calls for responsibility, not just regret.

Weak institutional apology:

시스템 오류가 있었습니다. 양해 바랍니다.

Stronger version:

시스템 오류로 이용에 불편을 드려 죄송합니다. 현재 복구 작업을 진행 중이며, 완료되는 대로 다시 안내드리겠습니다. 양해 부탁드립니다.

Register guardrail

양해 부탁드립니다 is not magic politeness. It asks the listener to tolerate something. If overused without responsibility or repair, it can feel dismissive.

The apology selector should ask four questions: who was affected, how severe, who is responsible, and what repair is offered? It should output phrase bundles, not single words: apology + burden acknowledgment + repair/follow-up.

Publication hardening checklist

Add examples from friend, workplace, customer-service, public notice, and institutional apology. The article should warn against both under-apologizing and melodramatic over-apologizing.