Inkuntri
Korean Grammar & discourse

When Korean Grammar Depends More on Relationship Than Rule

The reader can map relationship before choosing endings, address terms, honorific verbs, humble verbs, pronouns, and omission.

Published January 25, 2026 Korean

The sentence can be grammatical and still wrong

A learner says to a senior manager:

너 내일 회의 와?

The grammar works. The relationship does not. Korean grammar often encodes who is speaking to whom before it encodes the bare information.

A more appropriate workplace version might be:

팀장님, 내일 회의에 참석하시나요? 팀장님, 혹시 내일 회의 참석 가능하실까요?

The change is not just . The address term, honorific predicate, question style, and burden management all change.

Relationship variables

Before choosing a sentence, map these:

VariableQuestions
AgeIs one person older? Does age matter in this setting?
RoleTeacher, manager, customer, stranger, friend, junior, senior?
RankIs there workplace hierarchy?
FamiliarityFirst meeting, acquaintance, close friend, family?
SettingWorkplace, school, service encounter, online, family, public?
BurdenIs the speaker requesting, informing, correcting, refusing, or apologizing?
AudiencePrivate message or group-visible statement?

Honorific and humble verbs

Plain ideaRespect/humble formUse
있다계시다respected person exists/stays
말하다말씀하시다 / 말씀드리다respected speaking / humble speaking to respected person
주다주시다 / 드리다respected gives / speaker gives humbly
보다보시다 / 뵙다respected sees / speaker meets humbly
먹다드시다respected person eats
자다주무시다respected person sleeps

The system is not “add 시 everywhere.” If the subject deserves respect, may appear. If the speaker humbly gives or says something to a respected listener, 드리다 may appear.

Address terms replace pronouns

Korean often avoids , 당신, and personal names where English would use “you.” Address terms do social work:

  • 선생님 — teacher, instructor, respected professional
  • 팀장님 — team leader
  • 사장님 — business owner/boss/customer address in some service settings
  • 선배 — senior in school/work/community
  • 후배 — junior
  • 어머님 / 아버님 — polite parent address
  • 고객님 — customer

Sometimes the safest choice is to omit the second-person term entirely.

Politeness level is not enough

makes a sentence polite, but relationship errors remain possible.

Grammatically polite but offWhyBetter direction
선생님, 밥 먹었어요?먹다 can be too plain for respected subject식사하셨어요?
팀장님, 내가 보낼게요.pronoun/register mismatch제가 보내드리겠습니다.
고객님, 기다려.ending is too low잠시만 기다려 주세요.
교수님, 당신 생각은 어때요?당신 is inappropriate교수님 의견은 어떠신가요?

Relationship-driven omission

Korean often omits subjects and objects when relationship and context make them obvious:

  • 확인했습니다. — I checked it / we confirmed it.
  • 보내드리겠습니다. — I will send it to you.
  • 괜찮으시면 내일 뵙겠습니다. — If it is okay with you, I will see you tomorrow.

This is not vague to insiders. It is efficient because the relationship supplies missing roles.

Reusable workflow

  1. Map the relationship.
  2. Choose address term or omit address.
  3. Choose speech level: casual, polite, deferential, formal written.
  4. Check subject honorifics: does the subject require or an honorific verb?
  5. Check humble verbs: is the speaker doing something for a respected listener?
  6. Check pronouns: can they be omitted?
  7. Check burden: request, refusal, apology, correction, reminder.

Relationship rewrite lab: users input one base message, then choose relationship settings: friend, older acquaintance, professor, manager, customer, junior colleague. The tool rewrites address terms, endings, honorific verbs, and request framing.

Additional practice and repair

This article needs the most Korean-specific caution. Relationship-driven grammar is not “add honorifics.” It is a system of address, reference, humility, verb choice, endings, omission, and topic management.

Relationship factorWhat it changesExample issue
Age/seniorityaddress terms, speech level선배, 언니, ,
Institutional roletitle and reporting verb팀장님께 보고드리다
Familiaritypronoun avoidance, endings, name, title, or zero address
Speaker humilityverb choice드리다, 말씀드리다, 여쭙다
Referent respectsubject honorific계시다, 말씀하시다, 주시다
Mediumemail vs chat vs speech확인 부탁드립니다 vs 확인해 줘

Add a consistency audit. Learners often mix levels:

Mixed sentenceProblemRepair
팀장님, 네가 확인했어요?title respect plus intimate pronoun팀장님, 확인하셨나요?
선생님한테 물어봤습니다 in formal respectful contextcasual 한테 may be too low선생님께 여쭤봤습니다
제가 너에게 말씀드렸어요humble verb mismatched to lower addressee제가 너한테 말했어요 / 제가 말씀드렸습니다 depending context
당신은 어떻게 생각하세요? to a normal coworker당신 can sound confrontational/odduse name/title or omit subject

Relationship-map workflow

Before writing or interpreting a sentence, map:

  1. Speaker role.
  2. Addressee role.
  3. Person being talked about.
  4. Relative rank or age.
  5. Public/private setting.
  6. Medium: chat, email, meeting, announcement, service counter.
  7. Desired social action: request, report, refuse, apologize, disagree, thank.

The interactive rewrite lab should include a relationship matrix. Users should select “employee to manager,” “manager to team,” “student to professor,” “friend to friend,” “customer to staff,” and “public notice to residents.” The same informational content should then produce different address terms, endings, and verbs.

Related reading