TOEIC Link Reading — Author Purpose and Tone Inference Anchoring: Answering "Why Was This Written" From Textual Evidence

The TOEIC Link reading section asks why a message was written and how the writer feels toward the subject — questions with no single sentence stating the answer. Candidates guess from a general impression and fall for the confident-sounding wrong option. This guide shows how to anchor purpose and tone to specific evidence in the text: the document type, the action requested, and the evaluative words, so your inference is a reading of the page rather than a feeling about it.

EnglishBlitz Editorial Team·

TOEIC Link Reading — Author Purpose and Tone Inference Anchoring: Answering "Why Was This Written" From Textual Evidence

Two of the harder question types in the TOEIC Link reading section never point at a sentence you can highlight. Why did the writer send this email? and What is the writer's attitude toward the new policy? ask you to infer purpose and tone — the reason behind the text and the writer's stance inside it — and no line in the passage states either directly. Because there is nothing to underline, candidates fall back on a general impression: they read the passage, form a vague sense of what it "felt like," and pick the option that matches that feeling. The item writer builds the trap precisely there. Among the four options sits one that sounds confident and reasonable and describes a plausible purpose the passage does not actually support. Impression-based reading walks straight into it.

The correction is to treat purpose and tone as inferences that must be anchored to evidence, not feelings to be matched. A purpose you cannot tie to the document type and the action the writer requests is a guess. A tone you cannot tie to specific evaluative words is a projection. Anchoring means naming the textual features that force your answer, so that when two options both "sound right" you can eliminate the one with no anchor on the page.

Purpose is anchored by document type and requested action

The purpose of a business message is almost always visible in two features you can point to.

The document type sets the default purpose. An email confirming an appointment exists to confirm; a notice about a schedule change exists to inform; a follow-up after a complaint exists to apologize or resolve. Before inferring anything subtle, identify what kind of document this is, because the type already narrows purpose to a small set. An option describing a purpose that does not fit the document type — "to advertise a new product" on what is plainly a meeting-reschedule notice — is eliminated on the anchor alone.

The requested action names the real purpose. Most business writing exists to make something happen: reply by Friday, submit the form, attend the session, approve the budget. Find the sentence that asks the reader to do something — usually an imperative or a polite request near the end — and the purpose is whatever that action serves. If the writer asks the reader to confirm attendance, the purpose is to secure attendance, not merely "to provide information." The action sentence is the strongest purpose anchor because it states what the writer wants back, and reading it means reading past the surface topic to the transaction underneath — the same move behind reading answer options as paraphrases rather than keyword matches: the correct purpose option paraphrases the requested action, not the passage's headline subject.

When purpose and action seem to disagree — a message that describes a policy at length but ends by asking for feedback — the requested action wins. The description is context; the ask is the point.

Tone is anchored by evaluative words, not by topic

Tone is the writer's stance toward the subject, and it lives in a specific class of words: the evaluative ones. Unfortunately, we are pleased, regrettably, we appreciate, disappointing, a valued, we must insist — these carry the attitude. Topic words carry none. A message about a delayed shipment is not automatically "frustrated"; it is frustrated only if the writer chose frustrated-sounding words, and often the writer chose apologetic ones instead. Anchor tone by locating the evaluative words and reading the attitude off them, ignoring the subject matter, which tells you what the writer is talking about, not how they feel about it.

Two anchoring cautions:

  • Register is not tone. A formal, polite email can still carry a firm or dissatisfied stance under its courtesy. Do not read "polite" as "positive." Read the evaluative words beneath the politeness — we must insist is firm no matter how many _please_s surround it. Separating the stance from the surface courtesy is the same discipline as author purpose and tone identification, where the register and the attitude are tracked as different layers.
  • One strong word can be outweighed. A single negative word does not make the whole message negative if the surrounding evaluation is appreciative. Weigh the evaluative words together; the dominant stance, not the loudest single word, is the tone.

The anchoring routine

For every purpose or tone question, run the same evidence check before choosing:

  1. Name the document type. Email, notice, memo, review, advertisement — the type sets the default purpose and eliminates off-type options immediately.
  2. Find the requested action. Locate the imperative or polite request. The purpose is what that action serves. Hold that sentence as your purpose anchor.
  3. Collect the evaluative words. Underline every word carrying attitude. Their combined weight is the tone anchor. Ignore topic words entirely for this.
  4. Test each option against its anchor. A purpose option must match the requested action; a tone option must match the evaluative words. An option with no anchor on the page — however plausible it sounds — is the distractor.

The step that saves points is the last one, and it is the same confirm-before-committing discipline as answer choice comparison and elimination sequencing: the option that "sounds right" is exactly the trap unless it is anchored to a document-type, an action, or an evaluative word you can point to.

The confident-distractor trap

The wrong answer on these items is engineered to sound like a reasonable summary of the passage. On a purpose question it names a purpose the document could plausibly have but does not actually pursue — "to request a refund" on a message that only mentions a refund in passing while actually asking the reader to reschedule. On a tone question it names an attitude the topic might suggest but the words do not carry — "angry" on a complaint that is worded with cool professionalism. Both traps die the moment you demand an anchor: the plausible purpose has no requested action behind it, and the plausible tone has no evaluative words behind it. Impression says yes; the evidence check says no.

A four-week training protocol

Week one — type and action first. On each purpose item, before reading the options, write the document type and copy out the requested-action sentence. Choose only after both anchors are named. This breaks the habit of picking from a general sense of the passage.

Week two — evaluative-word hunts. On tone items, underline every evaluative word before looking at the options, then read the tone off them alone. Practice ignoring the subject matter so topic stops contaminating your read of attitude.

Week three — register-versus-tone drills. Work items where a polite surface hides a firm or dissatisfied stance. Confirm you can report the underlying attitude correctly despite the courtesy, since that gap is where tone questions are lost.

Week four — distractor autopsy. For every purpose or tone item you miss, write down what anchor the wrong option lacked — no requested action, no evaluative word. Naming the missing anchor each time trains you to demand one before committing, which is the entire defense against the confident distractor.

What these questions are really testing

Purpose and tone questions are not testing whether you got a feeling from the passage. They are testing whether you can convert a feeling into evidence — whether you can point to the document type and the requested action that fix the purpose, and to the evaluative words that fix the tone. Read the page for those anchors, and the plausible-sounding wrong option loses its footing: it describes a purpose with no action behind it and an attitude with no words behind it. Anchor the inference, and "why was this written" stops being a guess and becomes a reading.