The Complete Guide to Japanese Keigo for Professionals

The System Behind Professional Japanese

If you've studied Japanese, you've encountered keigo (敬語). It's usually introduced as "polite language" — but that undersells it dramatically.

Keigo is a grammatical system that encodes social relationships directly into the language. It tells the listener who holds higher status, who is showing deference, and how formal the situation is — all through verb forms, vocabulary choices, and sentence structure.

In casual conversation, you can mostly avoid it. In business, you can't. Keigo is the operating language of Japanese professional life, and understanding it is the difference between sounding competent and sounding like an outsider.

This guide covers the three types of keigo, when to use each, and the mistakes that trip up even intermediate speakers.

The Three Types of Keigo

1. 尊敬語 (Sonkeigo) — Respectful Language

Sonkeigo elevates the actions of the other person. You use it when describing what a superior, client, or respected person does.

The core principle: make their actions sound more important and dignified.

How it works:

• Special verb forms replace standard verbs. "To say" changes from 言う (iu) to おっしゃる (ossharu). "To go" changes from 行く (iku) to いらっしゃる (irassharu).
• The お/ご + verb stem + になる pattern works for most verbs: 読む → お読みになる (to read, respectfully).

Example:

部長がお読みになりました。 "The department head read it." (Elevated — their action is honored)

Compare with the plain version:

部長が読みました。 Same meaning, but no social elevation. Fine for casual reporting, inappropriate in a formal email.

When to use it: Describing what clients, executives, senior colleagues, or anyone of higher status does. In emails, when referencing the recipient's actions.

2. 謙譲語 (Kenjougo) — Humble Language

Kenjougo is the mirror of sonkeigo. Instead of elevating the other person, it lowers your own actions — expressing humility about what you do.

How it works:

• Special humble verb forms. "To say" becomes 申す (mousu). "To go" becomes 参る (mairu). "To do" becomes いたす (itasu).
• The お/ご + verb stem + する pattern: 送る → お送りする (to send, humbly).

Example:

私からお送りいたします。 "I will send it." (Humbled — your action is lowered)

Compare with standard polite:

私から送ります。 Correct, but doesn't signal deference. In a client email, the humble version is expected.

When to use it: Describing your own actions when writing to or about someone of higher status. In business emails, this is how you describe what you'll do for the recipient.

3. 丁寧語 (Teineigo) — Polite Language

Teineigo is the most familiar type — the です/ます endings that most learners study first. It doesn't elevate or humble anyone. It simply makes speech polite and appropriate for general professional use.

Example:

明日会議があります。 "There's a meeting tomorrow." (Polite, neutral)

When to use it: Everyday workplace communication, presentations to mixed audiences, general professional writing. It's the baseline — appropriate with colleagues at a similar level, but not sufficient for upward-facing or client-facing communication.

How the Three Types Work Together

In practice, you rarely use just one type. A single email to a client might contain all three:

先日はお忙しい中お時間をいただき、誠にありがとうございました。（sonkeigo — elevating their action of giving time） ご依頼いただいた資料を作成いたしましたので、お送りいたします。（kenjougo — humbling your actions of creating and sending） 添付ファイルをご確認ください。（teineigo — neutral polite request）

The interplay is what makes keigo challenging — and what makes it powerful. Each type does a specific job, and using them in combination creates a coherent social signal.

Quick Reference: Common Verbs in All Three Forms

| Meaning | Plain | Sonkeigo (Respectful) | Kenjougo (Humble) | |---------|-------|-----------------------|--------------------| | To say | 言う | おっしゃる | 申す | | To do | する | なさる | いたす | | To go | 行く | いらっしゃる | 参る | | To come | 来る | いらっしゃる | 参る | | To see | 見る | ご覧になる | 拝見する | | To eat | 食べる | 召し上がる | いただく | | To give | あげる | くださる | 差し上げる | | To receive | もらう | — | いただく | | To know | 知る | ご存知 | 存じる | | To be | いる | いらっしゃる | おる |

Bookmark this table. Even experienced Japanese speakers refer back to keigo verb forms regularly — there's no shame in looking them up.

When to Use Which Level

The decision framework comes down to three questions:

Who are you communicating with?

• Client or external partner → Sonkeigo for their actions, kenjougo for yours. Maximum formality.
• Senior manager or executive → Sonkeigo for their actions, kenjougo for yours. High formality.
• Colleague at similar level → Teineigo is usually sufficient. Occasional sonkeigo shows respect without overdoing it.
• Junior colleague or direct report → Teineigo. Using heavy keigo downward can feel sarcastic or distant.

What's the channel?

• Formal email → Full keigo expected. Cushion phrases, proper closings, consistent register.
• Slack or Teams → Lighter keigo. Teineigo with selective honorific forms. Too much formality feels stiff in chat.
• Face-to-face meeting → Depends on who's in the room. Default to the highest-status person present.
• Phone call → Similar to email formality, especially for first contact or client calls.

What's the situation?

• First contact → Maximum formality. You can always relax later; you can't undo a too-casual first impression.
• Ongoing relationship → Match the level your counterpart uses. If they soften, you can soften.
• Apology or request → Elevate formality one level above your default for that person. Showing extra deference in sensitive situations is always appropriate.
• Delivering bad news → Use humble forms for your own role in the situation and respectful forms when referencing the impact on the recipient. An email about a project delay to a client looks very different from the same update to your team.
• Thank-you or follow-up → Maintain the same level as your last exchange, or slightly elevate if the other person did you a significant favor.

The Hardest Part: Switching Levels in Real Time

Here's what makes keigo genuinely difficult: in a single meeting or email chain, you might need to switch between all three types.

Example scenario — reporting to your manager about a client meeting:

先日、田中様がおっしゃったのですが…（sonkeigo — elevating the client's words） …私から資料をお送りいたしました。（kenjougo — humbling your own action） 来週のミーティングで確認します。（teineigo — neutral statement to your manager）

Three types of keigo in three sentences. Each one is correct for its context: you elevate the client, humble yourself, and speak politely to your manager.

This level switching is what native speakers do instinctively. For non-native speakers, it takes practice — but understanding the system makes it much more manageable than memorizing phrases.

Common Keigo Mistakes

Even intermediate and advanced speakers make these errors:

Using sonkeigo for your own actions

❌ 私がおっしゃいました。("I said" — but おっしゃる elevates the speaker, which is you. This is backwards.) ✅ 私が申しました。(Humble form — correct for your own actions.)

This is the most common keigo mistake. Sonkeigo is only for other people's actions. Using it for yourself sounds either confused or arrogant.

Double keigo (二重敬語)

❌ お読みになられました。(Two layers of respectful forms stacked — grammatically excessive.) ✅ お読みになりました。(One layer is correct and natural.)

Stacking multiple keigo markers on a single verb is a common overcorrection. One honorific form per verb is the rule.

Using the wrong level of kenjougo

❌ 拝見いたしました。(拝見 is already humble; adding いたす doubles the humility unnecessarily.) ✅ 拝見しました。(Clean and correct.)

Some humble verbs like 拝見する are inherently kenjougo. Adding いたす on top creates the humble equivalent of double keigo.

A Typical Day in Keigo

To see why this matters in practice, consider a typical Tuesday at a Japanese company:

9:00 AM — You email a client to confirm a meeting. Sonkeigo for their actions, kenjougo for yours, formal closing. Full keigo.

10:30 AM — You Slack your teammate about the meeting agenda. Teineigo is fine, maybe even casual depending on how well you know them.

1:00 PM — You present project status to your department head. Sonkeigo when referencing their decisions, kenjougo for your team's work, teineigo for neutral facts.

3:00 PM — You draft an apology email because a deliverable is late. Maximum keigo — elevated even beyond your usual level with this client, because the situation demands extra deference.

4:30 PM — You message your manager with a question. Polite with selective honorific forms — respectful but not stiff.

Five communications, five different keigo configurations. Each one is "correct" only in its specific context. This is why learning keigo as a fixed set of rules doesn't work — you need to develop a sense for which combination fits the moment.

Making Keigo Practical

Keigo is learnable, but it takes time. In the meantime, you still need to send that email today.

Veltone maps its tone control directly to keigo levels. Set the tone and the recipient context, and it automatically selects the right combination of sonkeigo, kenjougo, and teineigo for each part of your message — including the cushion phrases, closing expressions, and greeting patterns that native speakers choose instinctively.

The part that accelerates learning: every translation labels which keigo type was used in each phrase and why. "Used 拝見しました (humble form of 見る) because you're describing your own action to a superior." After a few weeks of reading these notes, the decision-making process starts to feel natural.

Try Veltone free → and let keigo work for you instead of against you.

---

See keigo mistakes in action: 5 Japanese Email Mistakes That Cost Foreigners Promotions. Or understand the bigger picture: Why Tone Matters More Than Accuracy in Japanese Business.