EnglishBlitz

TOEIC Link Reading — Reading Email Headers and Subject Lines for Fast Context in Part 7: How to Extract the Situation Before the Body

Many Part 7 passages are emails, and every email arrives with a header — sender, recipient, date, subject line — that compresses the whole situation into four lines. Fast readers mine that header before touching the body, so they read the message already knowing who is writing to whom, about what, and when. This guide explains how to read a header for context, what each field tells you, and how the subject line often points straight at the main-idea question.

EnglishBlitz Editorial Team·

TOEIC Link Reading — Reading Email Headers and Subject Lines for Fast Context in Part 7

A large share of Part 7 passages are emails, letters, and memos, and every one of them opens with a header before the body begins: a From line, a To line, a date, and — for emails — a subject line. Inexperienced readers treat the header as decoration and skip straight to the first paragraph, then spend the first three sentences of the body reconstructing what the header already told them: who is writing, to whom, and why. Fast readers do the opposite. They read the four header lines first, extract the situation from them, and start the body already knowing the frame. The header is not preamble to be skimmed past; it is a four-line summary of the message's context, and reading it well means the body arrives pre-interpreted rather than cold.

The reason the header repays close reading is that TOEIC's business emails are situational — they exist because one person needs something from another — and the header names both parties and, in the subject, the thing needed. A message from a supplier to a purchasing manager about a delayed shipment reads very differently from a message from a manager to a new hire about orientation, and the header tells you which you are holding before you read a word of the body. That framing shapes what every ambiguous pronoun and vague reference in the body means, and it is the same orientation-first habit developed in document structure and section orientation mapping.

What each header field tells you

Read the header top to bottom and lift a specific inference from each line rather than glancing at it. The From and To lines establish the relationship and its direction — supplier to client, manager to subordinate, colleague to colleague — and that relationship predicts the message's register and purpose. A junior writing to a senior is likely requesting or reporting; a company writing to a customer is likely informing or apologising. The date matters more than it looks: Part 7 questions frequently hinge on sequence — what was true before an event, what deadline follows a message — and the header date is the anchor the body's "next week" and "by Friday" are measured from. Reading the direction and timing of a message before its content is the groundwork that makes the body's references resolve cleanly, much as tracking who refers to whom is handled in referent tracking and pronoun-antecedent resolution.

Pay attention to CC lines and job titles when they appear. A message copied to a manager signals escalation or the need for a record; a signature block naming a department tells you which function the writer speaks for. These small fields are exactly the kind of concrete, distinctive detail that answers a "who" or "which department" question without any hunting through the body.

The subject line often names the main idea

An email's subject line is the writer's own one-line summary of why the message exists, which makes it the single most useful field for the main-idea and purpose questions that open most email passages. "Subject: Rescheduling of the March 12 vendor meeting" tells you the purpose is to change a meeting time before you read any body text; a purpose question can often be answered from the subject line alone, confirmed by a glance at the first body sentence. Treat the subject as a hypothesis about the main idea and read the opening of the body to confirm it. This turns the most common email question — "What is the purpose of the email?" — from a passage-reading task into a header-reading task, the same collapse from whole-passage to targeted search practised in scanning for answer-bearing sentences via question-word anchoring.

Be alert, though, to messages where the subject is generic — "Update," "Following up," "Quick question" — because those subjects summarise nothing and force you back into the body for the purpose. Recognising a contentful subject from an empty one in a glance saves you from either over-trusting a vague subject or ignoring a rich one.

Use the header to disambiguate the body

The header's real payoff comes when the body turns vague. Business emails are full of unnamed references — "as we discussed," "the attached," "your team," "the earlier issue" — that would be ambiguous read cold but resolve instantly against a header you have already absorbed. If the header established that a supplier is writing to a client about an invoice, then "the outstanding amount" in the body needs no puzzling out. Reading the header first means the body's shorthand lands on a frame that is already built, rather than sending you back up the page to construct one. When a body reference still will not resolve, the header's fields — who, to whom, when — are the first place to check, and this pairing of frame and detail is the two-level reading described in the two-pass gist-then-detail reading protocol.

In multiple-passage sets, headers are the map

Double and triple passages often include two or more emails, and their headers are how you keep the correspondence straight. Reading each header tells you the order of the exchange — who wrote first, who replied, what date each message carries — so that a cross-reference question ("What does Ms. Tanaka's reply agree to?") sends you to the right message immediately rather than to a hunt through undifferentiated text. Skipping the headers in a multi-email set is how readers confuse who said what and pick a distractor built from the wrong message. Letting the headers organise a set before you read its bodies is part of the cross-text discipline in Part 7 multiple-passage cross-reference strategies.

A four-week protocol

Week one — read the header aloud. For every email passage, state in one sentence who is writing to whom, when, and about what, using only the header, before reading the body. Check afterward whether your one-sentence frame held up.

Week two — subject as hypothesis. For each purpose or main-idea question, write your answer from the subject line first, then confirm or correct it from the opening body sentence. Log how often the subject alone was enough.

Week three — disambiguate deliberately. Each time the body uses a vague reference, resolve it against the header rather than by re-reading up the page. Note the time saved.

Week four — at pace, and in sets. Under TOEIC timing, read every header first, and in multi-passage sets use the headers to order the messages before reading any body. Sort email questions into header-answerable and body-required on sight.

The habit worth keeping

The lasting shift is to stop skipping the header and start mining it. Four lines of From, To, date, and subject compress the whole situation of a business email, and reading them first means you enter the body already knowing the frame that its pronouns, deadlines, and vague references depend on. The purpose question is often answered before the body begins; the "when" and "who" questions are often answered by the header alone; and the body's shorthand resolves cleanly against a context you built before you reached it. Reading the body cold to reconstruct what the header already stated is the tax the exam collects from readers who skip the top four lines. Read the header first, and every email passage starts with the situation already in hand.