Plain Form, Polite Form, and Where Grammar Meets Social Distance

Core examples: 行く/行きます, です/だ, ございます, だと思います, 行くこと, レポートである, 友達との会話.

Plain and polite are not just “rude” and “nice”

Beginners often learn:

行く = plain 行きます = polite

Then they conclude:

plain = casual/rude polite = safe/respectful

This is too simple.

Plain forms appear inside polite sentences. Academic writing uses plain-like forms. News and essays use だ or である styles. Friends may use polite forms jokingly or to create distance. A workplace chat may mix plain and polite. A quoted thought may be plain inside a polite conversation.

The key principle is:

Plain and polite forms are grammatical resources that interact with relationship, genre, sentence structure, and discourse.

Politeness is part of the issue, not the whole issue.

Polite main clauses: です and ます

In ordinary polite speech, main predicates often end in です or ます:

明日行きます。 I will go tomorrow.

これは本です。 This is a book.

今日は暑いです。 It is hot today.

This style is common with strangers, teachers, customers, coworkers, and public-facing situations.

Plain forms in casual conversation

Friends, family, and close peers often use plain forms:

明日行く。 I’m going tomorrow.

これ、本だよ。 This is a book.

今日暑いね。 Hot today, isn’t it?

Plain form can signal closeness, informality, self-talk, or directness. It can also sound rude if used where polite form is expected.

Embedded plain forms inside polite sentences

This is where learners get confused.

明日行くと思います。 I think I will go tomorrow.

The embedded content 行く is plain, but the main sentence is polite because of 思います.

Other examples:

日本語を勉強することは大切です。 Studying Japanese is important.

田中さんが来るかどうか分かりません。 I don’t know whether Tanaka will come.

Plain forms often appear before と思う, こと, の, か, なら, and in relative clauses. This is grammar, not rudeness.

だ and です

Noun and na-adjective predicates often use だ in plain style and です in polite style:

学生だ。 学生です。

But だ is not simply casual speech. It also appears in essays, narration, and assertion depending on style. Meanwhile, some spoken contexts omit だ:

これ、私の。 This is mine.

Learner action: pay attention to genre.

である style

Formal writing, academic prose, essays, and reports may use である:

これは重要な問題である。

This is not conversational politeness. It is formal written style. It may sound stiff or inappropriate in ordinary speech.

A learner who uses である in casual conversation will sound like a textbook or academic essay.

ございます and higher politeness

ございます

is a more formal/polite version connected to あります and です-like expressions in certain contexts.

Examples:

ありがとうございます。 Thank you.

ご質問はございますか。 Do you have any questions?

This belongs to formal, service, business, or set-phrase usage. It is not simply “better です.”

Mixed register

Japanese often mixes levels.

A speaker may use polite main endings but casual fillers. A workplace chat may use plain forms for efficiency but polite closings. A teacher may use plain forms during explanation and polite forms for address. A speaker may shift to plain form to quote inner thoughts.

Register shifts can signal:

• closeness,
• distance,
• authority,
• irritation,
• seriousness,
• joking,
• narrative voice,
• genre change.

Example bank walkthrough

行く / 行きます

Plain versus polite main verb.

Learner action: choose by relationship and sentence position.

です / だ

Polite versus plain copula-like forms.

Learner action: genre matters.

ございます

Higher/formal politeness.

Learner action: learn as service/business/formulaic register.

だと思います

Plain だ inside polite 思います.

Learner action: embedded plain form is normal.

行くこと

Plain form before nominalizer こと.

Learner action: not casual; grammatical embedding.

レポートである

Formal written style.

Learner action: avoid in ordinary conversation.

友達との会話

Conversation with friends often uses plain forms.

Learner action: match intimacy and group norms.

Register decision tree

Ask:

1. Is this main clause or embedded clause?
2. Who am I speaking to?
3. Is this speech or writing?
4. What genre: chat, email, essay, report, news, presentation?
5. Is the sentence quoted or thought?
6. Is the relationship close, distant, hierarchical, or public?
7. Is a register shift intentional?

Politeness is not just respect; it is genre

Learners often think plain form means casual and polite form means respectful. That is a useful first approximation, but it breaks quickly.

Plain forms appear in:

• casual conversation,
• subordinate clauses,
• quotations,
• dictionary entries,
• essays,
• news-style writing,
• academic definitions,
• thoughts in fiction,
• grammar before nouns.

Polite forms appear in:

• conversation with distance,
• service encounters,
• presentations,
• business communication,
• classroom speech,
• interviews,
• public-facing announcements.

So plain/polite choice depends on relationship and grammar and genre.

Embedded clauses usually use plain form

Even in polite speech, embedded clauses often use plain form.

明日行くと思います。 I think I will go tomorrow.

Not usually:

明日行きますと思います。

The sentence as a whole is polite because of 思います. The quoted/thought content uses plain form.

Other examples:

田中さんが来るかどうか、確認します。 I will check whether Tanaka is coming.

日本語を勉強することは大切です。 Studying Japanese is important.

A learner who tries to make every verb polite inside a polite sentence will over-politen the grammar.

だ, です, and zero copula

For nouns and na-adjectives, the plain/polite contrast includes copula choice.

学生だ。 学生です。

But in some embedded environments, だ may disappear or change:

学生だと思います。 I think he/she is a student.

学生であること the fact of being a student

学生の田中さん Tanaka, who is a student

Copula behavior is one reason register and grammar interact.

である style

Written Japanese has a plain formal style often called である style. It is not casual conversation.

本稿では、日本語の敬語について考察する。 This paper examines Japanese honorifics.

This is plain in form but formal in genre. A learner who equates plain with casual will misunderstand essays, academic writing, and reports.

Mixed register

Real speech can mix levels.

A speaker may use polite forms toward the listener while quoting casual speech:

友達が「行きたくない」って言っていました。 My friend said, “I don’t want to go.”

The outer frame is polite: 言っていました. The quoted content is casual/plain: 行きたくない.

This is not inconsistency. It is layered speech.

Register decision tree

When choosing form:

1. Who is the listener?
2. Is this main clause or embedded clause?
3. Is this spoken or written?
4. Is the genre conversation, essay, news, email, fiction, or presentation?
5. Is the sentence quoted thought/speech?
6. Is the style supposed to be warm, distant, institutional, academic, or intimate?
7. Does the surrounding text already establish a style?

Plain/polite choice is a discourse decision, not a suffix swap.

A strong tool for this article would convert sentences across styles.

Suggested functions:

1. Casual conversation: 行く, だ, だよ.
2. Polite speech: 行きます, です.
3. Business polite: いたします, ございます.
4. Essay style: である.
5. Embedded clause mode: 行くと思います.
6. Register warning: unnatural combinations.
7. Context selector: friend, teacher, customer, report, email.

Final rule

Plain and polite forms are not a moral ladder from rude to respectful. They are grammar plus social distance plus genre.

Use polite forms for appropriate main-clause address. Use plain forms inside embedded grammar. Use である for formal writing. Use casual forms with real closeness.

Good Japanese register is not always more polite. It is correctly placed.