N3 内容理解（短文）: Four Texts, Four Fast Points
N3's short-passage block grows up from N5: now it's 4 texts of 150–200 characters — business e-mails, workplace notices, explanatory snippets, mini-essays — with one question each. The reading is denser (kanji compounds, formal register, embedded reasons), but the questions remain single-target: what does the writer want, what must the reader do, why did something happen. This chapter upgrades your short-passage method for N3 text types and drills the two most common formats: the business e-mail and the opinion snippet.
1. The N3 Question Repertoire
| Question | Typical phrasing | Answer lives in… |
|---|---|---|
| Writer's purpose | この文章を書いた目的は何か。／何を知らせたいのか。 | the opening + the request sentence (〜てください／〜お願いします) |
| Reader's obligation | このメールをもらった人は、何をしなければならないか。 | deadline + action phrases: 〜までに〜こと／〜てください |
| Reason | 〜のはなぜか。 | ため／ので／から clauses — often mid-text |
| Writer's view | 筆者の考えに合うものはどれか。 | after しかし／つまり — usually the last sentence |
| Referent | 「それ」とは何か。 | the sentence immediately before |
2. Reading Business Japanese (the E-mail/Notice Kit)
N3 introduces workplace documents. Their formal furniture repeats — learn it once and these texts become transparent:
| Phrase | Meaning |
|---|---|
| お世話になっております | standard business e-mail opener ("thank you for your continued support") |
| 〜の件（けん） | regarding the matter of ~ (subject lines!) |
| 〜につきまして／〜について | concerning ~ |
| 〜ことになりました | it has been decided that ~ (announcements) |
| 〜までに〜てください／〜こと | please do ~ by (deadline) |
| お手数ですが／恐れ入りますが | sorry to trouble you, but… (a request follows!) |
| ご確認ください／ご連絡ください | please check / please contact |
| よろしくお願いいたします | closing formula |
| なお、〜 | additionally… (the fine-print flag — read what follows!) |
| ただし、〜 | however… (the exception flag) |
Structural insight: in business texts the real action request hides behind お手数ですが or 恐れ入りますが, and the catch hides behind なお／ただし. Question writers know this — so should you.
3. Worked Text 1: The Office E-mail
件名：会議室の予約について
営業部のみなさま
お世話になっております。総務部の林です。来月から、会議室を使う場合は、前の日までにパソコンで予約することになりました。当日の予約はできませんので、ご注意ください。なお、キャンセルする場合は、必ず前日の夕方5時までにご連絡ください。よろしくお願いいたします。
Question: 会議室を使いたい人は、どうしなければなりませんか。
① 当日の朝、電話で予約する ② 前の日までにパソコンで予約する ③ 林さんにメールで連絡する ④ 夕方5時までに会議室に行く
Walkthrough: the obligation question → hunt the rule sentence: 前の日までにパソコンで予約することになりました. Answer ②. ① contradicts 当日の予約はできません; ③ confuses the sender with the procedure; ④ misattaches the cancellation deadline (なお-clause) to booking. Notice how every distractor is made of REAL text fragments re-glued — N3 reading is precision work, not gist work.
4. Worked Text 2: The Opinion Snippet
「早起きは体にいい」とよく言われる。私も長い間そう信じて、無理に朝5時に起きていた。しかし、最近の研究によると、人によって合う生活リズムは違うそうだ。大切なのは、起きる時間ではなく、自分に合ったリズムで十分に眠ることなのだ。
Question: 筆者が一番言いたいことは何か。
① 早起きは体にいい ② 朝5時に起きるべきだ ③ 自分に合ったリズムで十分眠ることが大切だ ④ 研究の結果は信じられない
Walkthrough: classic opinion architecture — common belief (とよく言われる) → writer's old behavior → しかし + research → conclusion flagged by 大切なのは…のだ. Answer ③. Option ① is the opening belief the writer rejects — the #1 trap in all JLPT opinion reading: quoting the setup as if it were the claim. The claim lives after しかし and usually wears 〜のだ／〜と思う／大切だ.
5. The N3 Short-Passage Method (updated)
- Identify the text type in 3 seconds (件名/みなさま = business; とよく言われる = opinion; 〜のお知らせ = notice). Type predicts structure; structure predicts answer location.
- Read the question, classify it (obligation? reason? claim? referent?).
- Read the full text once — 150-200 characters is still one-breath territory — flagging しかし／なお／ただし as you pass.
- Point at the evidence sentence, then eliminate options by exact comparison (who/when/deadline/polarity).
Budget: ~2.5 minutes per text. Four texts = 10 minutes of the 読解 clock.
6. Vocabulary That Decides These Questions
A compact set of "reading operators" recurs in N3 short texts — miss one and the logic inverts:
- 〜までに (by/deadline) vs 〜まで (until/duration) — 5時までに連絡 = call BY 5:00.
- 必ず (without fail) / 〜なければならない — obligation markers = answer bait for obligation questions.
- 〜ことになりました (new rule) vs 〜ことにしました (my decision) — who decided matters.
- 当日・前日・翌日 (that day / the day before / the next day) — date-shifting vocabulary.
- できません／ご遠慮ください — prohibition in polite clothing (ご遠慮ください means NO).
- 大切なのは〜だ／〜のだ — claim flags in opinion snippets.
Summary & Key Takeaways
- N3 短文 = 4 texts × 150-200 chars (business e-mails, notices, opinion snippets), 1 precision question each.
- Business kit: request after お手数ですが; rules in 〜ことになりました; catches after なお／ただし; deadlines with 〜までに.
- Opinion architecture: common belief → しかし → writer's claim (〜のだ). Never answer with the rejected setup.
- Method: type-spot → classify question → full read flagging turn/exception words → evidence → exact elimination.
- Reading operators (までに, 必ず, 当日/前日, ご遠慮ください) carry the logic — they are vocabulary and strategy at once.