9.1 Short Reading Comprehension: Notices, Emails & Memos (短文読解)

9.1 Short Reading Comprehension: Notices, Emails & Memos (短文読解)

In the JLPT N3, the Reading Comprehension section (読解, dokkai) is administered jointly with Language Knowledge (Grammar) in a single 70-minute testing block. Efficient time allocation and disciplined reading protocols are the defining factors that separate passing candidates from those who run out of time.

Problem 4 (問題4 短文読解, tanbun dokkai) forms the frontline of the reading section. It evaluates your capacity to comprehend concise, functional Japanese texts encountered in everyday social, academic, and professional environments.

┌─────────────────────────────────────────────────────────────────────────────────┐
│                     JLPT N3 READING COMPREHENSION OVERVIEW                      │
├──────────┬─────────────────────────────┬──────────────┬──────────┬──────────────┤
│ Problem  │ Section Type                │ Passages     │ Questions│ Time Target  │
├──────────┼─────────────────────────────┼──────────────┼──────────┼──────────────┤
│ 問題4    │ Short Passages (短文読解)   │ 4 passages   │ 4 items  │ 12 minutes   │
│ 問題5    │ Mid-Length Passages (中文)  │ 2 passages   │ 6 items  │ 16 minutes   │
│ 問題6    │ Long Passage (長文読解)     │ 1 passage    │ 4 items  │ 12 minutes   │
│ 問題7    │ Information Search (情報検索)│ 1 document   │ 2 items  │ 6 minutes    │
├──────────┴─────────────────────────────┴──────────────┴──────────┼──────────────┤
│ TOTAL READING ALLOCATION (Remaining ~24 mins for Grammar)        │ 46 minutes   │
└──────────────────────────────────────────────────────────────────┴──────────────┘

1. Problem 4 Architecture & Pacing Targets

Problem 4 presents 4 separate short texts, each containing approximately 150 to 200 Japanese characters. Each short text is paired with exactly one multiple-choice question (4 questions in total).

The 3-Minute Rule

You must spend no more than 3 minutes per passage, giving a cumulative target of 12 minutes for all of Problem 4. Because these short passages appear right after the grammar section, many test takers make the fatal error of reading them multiple times in relaxed pursuit of 100% translation perfection. Doing so depletes the time reserves needed for the complex arguments in Problem 5 (中文) and Problem 6 (長文).

┌─────────────────────────────────────────────────────────────────────────────────┐
│                     THE 3-MINUTE PER PASSAGE PACING ENGINE                      │
│                                                                                 │
│  0:00 - 0:30 (30 sec) : Read Question Stem & Options (Establish Search Target)  │
│  0:30 - 1:45 (75 sec) : Targeted Scan & Request Marker Triangulation           │
│  1:45 - 2:30 (45 sec) : Match Text Evidence to Options & Eliminate Traps       │
│  2:30 - 3:00 (30 sec) : Final Selection & Answer Bubble Marking                │
└─────────────────────────────────────────────────────────────────────────────────┘

2. Text Genres & Authentic Formats

Unlike longer philosophical essays, Problem 4 passages are strictly functional and situational. The test creators draw from four dominant real-world communication genres:

A. Business & Workplace Emails (社内・社外電子メール)

• Visual Markers: Headers containing 件名: (Subject), 送信者 / 差出人: (Sender), 宛先: (Recipient), 日時: (Date/Time).
• Core Content: Rescheduling internal meetings, reporting business trip outcomes, requesting document approval, requesting urgent feedback, announcing office policy changes.
• Key Register: Keigo (敬語) formulations such as 〜ていただけないでしょうか (could you please do...), ご査収のほどよろしくお願いいたします (please review the attached document), 〜の件でご連絡いたしました (I am contacting you regarding...).

B. Apartment & Residential Notices (マンション・掲示板のお知らせ)

• Visual Markers: Bold central titles like 【重要】定期清掃のお知らせ (Notice of Periodic Cleaning) or 断水に関するお願い (Request Regarding Water Outage).
• Core Content: Fire alarm testing, elevator maintenance, garbage disposal rule revisions, bicycle parking spot reallocations, plumbing inspections.
• Key Register: Impersonal administrative notifications ending in 〜こと (must do), 〜はご遠慮ください (please refrain from), ご協力をお願い申し上げます (we ask for your cooperation).

C. School, University & Community Circulars (学校・地域のお便り)

• Visual Markers: Addressed to 学生の皆様へ (To all students) or 保護者の皆様へ (To all parents/guardians).
• Core Content: Class room cancellations/relocations, tuition payment deadlines, scholarship application windows, cultural festival volunteer signups.
• Key Register: Neutral polite form (です / ます), deadlines marked with 〜までに (by [time]), conditions marked with 〜希望者は (those who wish to...).

D. Store, Clinic & Service Guidelines (店舗・クリニックの案内・お詫び)

• Visual Markers: 営業時間変更のお知らせ (Notice of Change in Business Hours), 臨時休業のお知らせ (Notice of Temporary Closure).
• Core Content: System maintenance windows, holiday schedule alterations, relocation announcements, appointment booking protocols.

3. Core Question Archetypes in Problem 4

Almost every Problem 4 question belongs to one of three standardized query formulas:

┌─────────────────────────────────────────────────────────────────────────────────┐
│                     THREE CORE QUESTION ARCHETYPES IN PROBLEM 4                 │
├──────────────────────┬─────────────────────────────┬────────────────────────────┤
│ Question Archetype   │ Japanese Question Pattern   │ Strategic Focus            │
├──────────────────────┼─────────────────────────────┼────────────────────────────┤
│ 1. Action / Next Step│ この後、何をしなければ     │ Locate imperative verbs,   │
│    (行動指示・義務)  │ ならないか / まず何をするか │ deadlines, and prerequisites│
├──────────────────────┼─────────────────────────────┼────────────────────────────┤
│ 2. Primary Purpose   │ この文書で最も伝えたいこと  │ Identify opening/closing   │
│    (伝達目的・主旨)  │ は何か / 何の連絡か         │ intent markers (〜の件)    │
├──────────────────────┼─────────────────────────────┼────────────────────────────┤
│ 3. Cause / Reason    │ 〜とあるが、なぜか /        │ Locate causal connectives   │
│    (理由・原因)      │ 理由として合っているものは  │ (〜ため, 〜から, 〜につき)  │
└──────────────────────┴─────────────────────────────┴────────────────────────────┘

4. The Systematic 3-Step Reading Protocol

To solve Problem 4 items in under 3 minutes with 100% accuracy, apply the following 3-step operational procedure:

Step 1: Read the Question Stem First (Targeted Scaffolding)

Never begin by reading the Japanese passage cold. Read the question stem first to install a cognitive filter in your mind.

• If the question asks "What must the student do by Friday?", your brain is primed exclusively to hunt for dates (金曜日), action verbs (提出する, 連絡する), and obligation markers (〜こと, 〜てください).
• You can ignore background pleasantries (e.g., いつも大変お世話になっております) and zero in on the exact sentence that answers the prompt.

Step 2: Scan Metadata & Structural Frame

Inspect the header and footer before reading the body text:

• Who is writing to whom? (e.g., Manager → Team; Landlord → Residents; Clinic Director → Patients).
• What is the subject line? (件名: 会議室変更 immediately tells you the passage is about a change in meeting room).
• Are there bulleted points (箇条書き)? Information formatted in bullet points (記, 1., 2., 日時:) almost always contains the factual answers.

Step 3: Triangulate Request Markers & Conditional Clauses

The correct answer to JLPT N3 short reading questions is virtually always attached to specific grammatical pivot expressions:

┌─────────────────────────────────────────────────────────────────────────────────┐
│                   HIGH-YIELD OPERATIONAL GRAMMAR PIVOTS                         │
├──────────────────────┬─────────────────────────────┬────────────────────────────┤
│ Category             │ Grammar Formulations        │ Communicative Meaning      │
├──────────────────────┼─────────────────────────────┼────────────────────────────┤
│ Direct Requests      │ 〜てください                │ "Please do [action]"       │
│                      │ 〜ていただきたく存じます    │ "We would like you to..."  │
│                      │ 〜お願いいたします          │ "We request that you..."   │
├──────────────────────┼─────────────────────────────┼────────────────────────────┤
│ Official Directives  │ 〜こと (Nominal Directive)  │ "Must do [mandatory rule]" │
│                      │ 〜必要があります            │ "It is necessary to..."    │
│                      │ 〜なければならない          │ "Must do..."               │
├──────────────────────┼─────────────────────────────┼────────────────────────────┤
│ Exceptions & Caveats │ ただし (tadashi)            │ "However / Provided that"  │
│                      │ なお (nao)                  │ "Furthermore / Note that"  │
│                      │ ※ / （注）                 │ Asterisk footnote caveat   │
│                      │ 〜に限り / 〜以外           │ "Only limited to..."       │
└──────────────────────┴─────────────────────────────┴────────────────────────────┘

5. Authentic Sample Passage & Step-by-Step Breakdown

Let us examine an authentic N3 Problem 4 passage simulation to observe this protocol in action.

Sample Text: Office Maintenance Notice (社内通知)

社員各位
総務部

【重要】オフィス内電気設備点検に伴うお願い

今週末の10月14日（土）午前9時から午後5時にかけて、本社ビルの電気設備点検
を実施いたします。点検中は全館停電となるため、以下の点にご注意ください。

1. 金曜日の退社時には、各自のパソコンの電源を必ず切り、コンセントを抜いて
   ください。データの破損を防ぐため、作業中のファイルは事前に保存してください。
2. 当日はビル内への立ち入りが一切できません。休日出勤を予定している方は、
   前日17時までに総務部へ申請し、作業日を変更してください。
3. 冷蔵庫内の私物は、金曜日中にすべて持ち帰るようお願いいたします。

ご不便をおかけしますが、ご協力のほどよろしくお願いいたします。

Vocabulary Breakdown

• 社員各位 (shain kaki): To all employees
• 総務部 (sōmubu): General Affairs Department
• 電気設備点検 (denki setsubi tenken): Electrical equipment inspection
• 全館停電 (zenkan teiden): Building-wide power outage
• コンセントを抜く (konsento o nuku): Unplug from the electrical outlet
• 破損 (hason): Damage / corruption (of data)
• 立ち入り (tachiiri): Entry / access

Sample Question Stem

問題: 社員は今週の金曜日に何をしなければならないか。 (Question: What must employees do on Friday of this week?)

Step-by-Step Resolution

1. Question Analysis: The prompt asks for actions required on Friday (金曜日).
2. Text Scanning: We scan the text for 金曜日 and 退社時 (leaving the office).
   • Item 1 states: 金曜日の退社時には、各自のパソコンの電源を必ず切り、コンセントを抜いてください。 (When leaving on Friday, make sure to turn off your PC and unplug it.)
   • Item 3 states: 冷蔵庫内の私物は、金曜日中にすべて持ち帰るようお願いいたします。 (Please take home all personal belongings in the refrigerator during Friday.)
3. Option Evaluation: We match our synthesized requirements against the four options:
   • Option 1: 土曜日の午前9時までに総務部に休日出勤の申請をする。(Wrong: Application must be made by Friday 17:00, and Saturday work is forbidden entirely during the outage).
   • Option 2: 土曜日の停電中にビルに入ってパソコンのコンセントを抜く。(Wrong: Entry is completely prohibited on Saturday; unplugging must occur Friday upon leaving).
   • Option 3: パソコンの電源を切ってコンセントを抜き、冷蔵庫の私物を持ち帰る。(CORRECT: Perfectly captures both mandatory Friday tasks).
   • Option 4: 金曜日の17時までに電気設備点検の作業を完了させる。(Wrong: The inspection is conducted by contractors on Saturday, not by employees on Friday).

6. High-Yield Distractor Traps in Problem 4

Test writers use four recurring structural traps to mislead rushed candidates:

┌─────────────────────────────────────────────────────────────────────────────────┐
│                     FOUR CLASSIC PROBLEM 4 DISTRACTOR TRAPS                     │
├────────────────────┬────────────────────────────────────────────────────────────┤
│ Distractor Trap    │ How the Trap Operates on the Test                          │
├────────────────────┼────────────────────────────────────────────────────────────┤
│ 1. Subject Swap    │ An action mentioned in the text is attributed to the WRONG │
│    (主語のすり替え)│ agent (e.g., what the teacher will do vs. what student must)│
├────────────────────┼────────────────────────────────────────────────────────────┤
│ 2. Optional vs.    │ Presenting an optional suggestion (`〜ば幸いです`) as an  │
│    Mandatory       │ absolute mandatory requirement (`必ず〜しなければならない`)│
├────────────────────┼────────────────────────────────────────────────────────────┤
│ 3. Chronological   │ Picking Step 2 or Step 3 when the question explicitly      │
│    Inversion       │ asks: 「まず何をしなければならないか」 (What must be done FIRST?)│
├────────────────────┼────────────────────────────────────────────────────────────┤
│ 4. Overlooked      │ Missing a critical restriction introduced by `ただし`     │
│    Exceptions      │ (however) or an asterisk footnote `※` at the bottom.      │
└────────────────────┴────────────────────────────────────────────────────────────┘

Trap 1: Subject Swap (主語のすり替え)

In business emails, the sender frequently outlines actions they will undertake personally (私から取引先に連絡しておきます), followed by a request for the recipient (佐藤さんは企画書を手直ししてください). Distractor choices will take the sender's action and state that the recipient must execute it. Always underline who is performing each verb!

Trap 2: Optional Suggestion vs. Mandatory Requirement

Pay close attention to auxiliary verbs:

• Mandatory: 〜こと, 〜てください, 〜なければならない, 〜が必須です.
• Optional / Conditional: 〜ても構いません (it is fine even if...), 〜ことをお勧めします (we recommend...), ご希望の方は (for those who wish...). If a question asks what everyone is required to do, eliminate options based on optional clauses.

Trap 3: Chronological Inversion (「まず」の罠)

When a passage outlines a sequence of procedures (1. Download form → 2. Fill in details → 3. Obtain manager's stamp → 4. Submit to HR), questions asking まず何をしなければならないか (What must be done FIRST?) will offer all four steps as options. You must strictly select Step 1, even if Step 4 is the ultimate goal.