TOEIC Link Reading Purpose and Audience Inference Under the Who-Is-This-For Set

A particular kind of TOEIC Link reading question never asks about a fact in the passage. It asks who the document is for, or why it was written: Who would most likely read this notice? For whom is this memo intended? What is the main purpose of this email? The answer is rarely stated outright. Instead, it has to be inferred from the way the document is written — its register, the channel it travels on, and the things it assumes the reader already knows. Candidates who hunt for a sentence that says "this is for warehouse staff" come up empty, because the document never says it. It shows it.

The skill these questions test is the one a competent reader uses without thinking: forming a quick, accurate picture of who a piece of writing is talking to and what it is trying to get them to do. A shift-change notice posted in a break room, an invoice sent to an accounts-payable department, a welcome email to a new subscriber — each carries unmistakable signals of its audience and purpose, even when neither is named. This article trains the inference: the cues that reveal the intended reader, the verbs that reveal the purpose, and the discipline of reading a document the way its real audience would.

Audience is encoded in register and assumed knowledge

The clearest signal of who a document is for is what it takes for granted. A writer pitches register and vocabulary to the reader they have in mind, and the gap between what is explained and what is assumed gives the audience away.

A document that explains basic terms is written for outsiders or newcomers. A memo that spells out "the CRM, the software we use to track customer contacts" is not written for the sales team that lives in the CRM all day — they would never need it defined. It is written for someone new, or someone in another department. Conversely, a notice that uses internal shorthand — "submit your TPS report to the Q3 folder" — assumes a reader already inside the system. Track what the document explains and what it assumes; the boundary is the edge of its intended audience.

Register places the reader on the formality scale. A breezy email opening with "Hey team — quick one" is internal, peer-to-peer, low-stakes. A letter opening with "Dear Valued Customer" is external, one-to-many, transactional. A notice headed "ATTENTION: ALL PERSONNEL" is top-down and mandatory. The tone is not decoration; it is the writer's read on their relationship to the reader, and it tells you which side of that relationship the audience sits on. For more on how register and tone steer interpretation, see our guide to register and formality-level decoding.

The channel narrows the audience further. A poster on a wall reaches whoever walks past — usually staff in a shared space. An email reaches a named list. An invoice reaches a billing contact. When the question asks who would "most likely" read something, the physical or digital channel is doing half the work: a break-room poster is for on-site staff, not remote clients; an invoice is for the people who pay it, not the people who ordered the service.

Purpose is encoded in the document's central verb

Once you know who a document is for, its purpose is usually carried by one dominant action it is trying to produce. TOEIC Link purpose questions reward readers who can name that action in a word.

To inform documents deliver information and ask for nothing back: announcements, policy updates, schedule changes. The giveaway is the absence of a request — the reader is meant to know something, not do something. Please note that the office will close early on Friday. Nothing is being asked of the reader except awareness.

To request documents are built around an ask: a form to complete, a confirmation to send, a payment to make, an action to take by a deadline. The verbs cluster at the end — "please submit," "kindly confirm," "we ask that you." If the document is steering the reader toward a specific action, its purpose is the request, not the background that sets it up. This is the same forward-leaning structure that drives persuasive and call-to-action document decoding, where the entire text exists to produce one response.

To persuade documents argue for a position or a choice: a recommendation, a proposal, a marketing message. They marshal reasons and benefits and try to move the reader toward agreement or purchase. To apologize or to reassure documents manage a relationship after something went wrong — they acknowledge a problem and offer a remedy. Naming the dominant verb — inform, request, persuade, apologize — answers the purpose question directly, and it keeps you from mistaking the document's setup for its point.

The trap: mistaking topic for purpose, and content for audience

The most common error on these questions is answering with what the document is about instead of what it is for. An email about a software outage is not "to describe a software outage" — it is, most likely, to apologize for it and tell affected users what to do. The topic is the outage; the purpose is the reassurance and the instruction. Always push past the subject matter to the action the writer wants.

The parallel trap on audience questions is choosing the people mentioned in the document over the people addressed by it. A notice that discusses a new policy for handling customer complaints is not necessarily written for customers — it is far more likely written for the staff who will handle the complaints. The customers are the topic; the staff are the audience. Ask not "who is this about" but "who is meant to read this and act on it." The reader the document is steering — through its register, its assumed knowledge, and its central request — is the audience, regardless of who else gets named along the way.

Training the who-is-this-for read

Build the habit on every business document you encounter. Before reading for detail, take three seconds to answer two questions: Who is this for? — judged from register, assumed knowledge, and channel — and What does the writer want them to do? — judged from the dominant verb. A purchase order is for a supplier, and it wants them to ship and bill. An onboarding email is for a new hire, and it wants them to complete setup steps. A recall notice is for owners of a product, and it wants them to stop using it and seek a remedy.

On the test, when a question asks about audience or purpose, resist the pull toward the most prominent fact in the passage and return to these two reads. The right answer almost always restates the document's register-and-channel audience or its central-verb purpose — not its topic. Reading a document the way its intended reader would, rather than the way a fact-hunter does, is the entire skill, and it is the same skill that makes you fast and accurate across the whole reading section. For the companion skill of pinning down why a document was sent in the first place, work through our document function and communicative purpose set alongside this one.