What are TOPIK II writing questions 51 and 52?

On the paper-based TOPIK II, questions 51 and 52 are short completion tasks. You fill missing parts of a text so the grammar, meaning, register, and connection between sentences are natural.

What should I study for questions 51-52?

Practice common connectors, formal written endings, requests and notices, cause-result relationships, conditions, and sentence patterns that complete short practical or explanatory texts.

Do I need difficult vocabulary for 51-52?

Usually precision matters more than fancy vocabulary. A simple, grammatically natural completion that fits the surrounding text is better than an ambitious sentence that changes the meaning.

Does this guide apply to TOPIK II IBT?

The numbered 51-52 convention belongs to the PBT format. TOPIK II IBT has a different number of writing tasks, so use the official IBT samples if you registered for IBT.

TOPIK II Writing 51-52: Sentence Completion Guide

Questions 51 and 52 on TOPIK II PBT are small writing tasks with a big lesson: you do not get points for writing whatever is grammatically possible. You need to write what fits the text.

That means four things must line up:

meaning
grammar
register
logical connection

These questions are often described as “fill in the blank,” but treating them like vocabulary blanks is too shallow. The missing phrase has a job inside the passage.

For the full exam format, see the TOPIK study guide. If you registered for IBT, use the official IBT writing samples because the task count and delivery differ.

Step 1: read around the blank, not only the blank

Before writing anything, identify:

who is speaking/writing
what kind of text it is
what happened before the blank
what must happen after it

A missing sentence in a notice, email, invitation, explanation, or short narrative will use different language.

Do not begin conjugating until you know the relationship.

Step 2: name the relationship

Common relationships include:

reason → result
problem → request
condition → action
invitation → response
plan → change
fact → explanation
action → purpose

If you can label the relationship in English or Korean first, choosing the grammar becomes easier.

For example:

비가 많이 옵니다. ________. 우산을 준비하시기 바랍니다.

The blank likely connects heavy rain → advice/preparation. You need a phrase that makes the warning coherent, not a random weather sentence.

Step 3: match the register

This is where many otherwise-correct answers become awkward.

If the surrounding text uses formal written Korean, do not suddenly insert casual 요-style speech.

Notice endings around the blank:

-습니다 / -ㅂ니다
-기 바랍니다
-주시기 바랍니다
-기로 했습니다
-기 때문에
-(으)면

Copy the level of formality, not necessarily the exact ending.

Review the formal polite grammar reference and honorifics guide if register still feels unstable.

Step 4: use the simplest grammar that does the job

Do not try to impress the grader with obscure grammar.

A reliable connector used correctly is better than an advanced form used strangely.

High-value patterns to recognize and produce include:

-아서/어서: reason/result
-(으)니까: reason
-(으)면: condition
-기 때문에: explicit reason
-려고 / -기 위해서: purpose
-지만 / -는데: contrast/background
-고: sequence/addition
-(으)ㄹ 예정입니다: plan/schedule

Use the grammar library and grammar encyclopedia to review any pattern that repeatedly appears in your mistakes.

Step 5: check what the next sentence assumes

After you draft a completion, reread the next sentence.

Ask:

Does “therefore” now make sense?
Does the pronoun refer to something clear?
Did I introduce a reason that the next sentence uses?
Did I accidentally contradict the result?

A sentence can be grammatically correct and still fail the passage logic.

Common trap: writing too much

These are short completion tasks. Long answers create more opportunities for:

spelling errors
wrong particles
register mismatch
unnecessary meaning

Write enough to complete the intended relationship, then stop.

Common trap: copying nearby words without changing grammar

The surrounding text gives clues, but copying a noun phrase directly may not produce the needed structure.

If the passage needs a cause, turn the idea into a reason clause.

If it needs a request, use an appropriate request form.

If it needs a condition, build a condition.

The task is about connecting ideas, not word matching.

Practice by function

Instead of doing random 51-52 questions, create mini sets.

Reason/result day

Write completions using:

-아서/어서
-(으)니까
-기 때문에

Condition day

Use:

-(으)면
-아/어야 하다 where obligation fits

Request/notice day

Practice formal requests and public-notice style.

Plan/change day

Use future, schedule, cancellation, or rescheduling language.

This builds reusable templates without memorizing full answers.

A review checklist

Before you mark a practice answer correct, check:

Meaning: does it say what the text needs?
Connection: does it link before and after?
Register: does it match the text?
Particles: are noun roles correct?
Ending: is the verb/adjective ending complete?
Spacing/spelling: any avoidable errors?

Do not memorize one “magic sentence”

TOPIK changes the content. Memorized sentences only help if you understand the function behind them.

Memorize frames, not full answers:

___기 때문에 ___습니다.
___(으)면 ___ 수 있습니다.
___려고 ___했습니다.
___주시기 바랍니다.

Then adapt them to the passage.

A 15-minute Q51-52 routine

5 minutes: complete two tasks under time pressure.

5 minutes: compare with a model answer and classify the missing relationship.

3 minutes: rewrite each answer with a second valid grammar pattern if possible.

2 minutes: add one repeated mistake to your review list.

This trains flexibility instead of answer memorization.

What to study next

For 51-52, the winning question is not “What grammar can I use?” It is “What does this text need me to say next?”