TOEIC Link Reading Document Function and Communicative Purpose Identification Under the Why-Was-This-Sent Set: The Whole-Text Intent Discipline That Keeps Candidates From Answering a Purpose Question With a Detail

A TOEIC Link Reading purpose question asks what an entire document is for: "Why was this notice posted?", "What is the purpose of the email?", "Why did the writer send this memo?" The answer is the document's communicative function — to announce, to request, to remind, to apologize, to invite — and that function lives at the level of the whole text, not in any single sentence. Yet the document is full of true sentences, and each one describes something real that happened or will happen. The trap of the purpose question is that the most attractive wrong answer is always one of those true details: a fact stated plainly in the text that simply is not why the text was sent.

The candidate who answers a purpose question by scanning for the sentence that matches an option will almost always find a match, because purpose-question distractors are built from real content. "Why was the email sent?" with an option "To confirm a shipment arrived" — and somewhere in the email, a shipment did arrive. But the email was sent to request a corrected invoice; the shipment arrival is the background that explains the request. The detail is true and present, which is exactly what makes it dangerous. Answering at the sentence level, the candidate finds true statements and mistakes presence for purpose.

This article is the whole-text intent discipline for TOEIC Link Reading document-function questions. The guide identifies the function categories that purpose answers fall into, the detail-as-purpose trap that defines the wrong answer, the structural reading that locates a document's function quickly, and the function test that separates why a document was sent from what it happens to say.

The function categories that purpose answers fall into

A document's communicative purpose almost always belongs to a small set of recognizable functions, and learning to read a text for its function — rather than its facts — turns the purpose question into a category match.

To inform or announce. The document exists to make new information known: a policy change, an event, a closure, a new hire, a price update. The whole text serves the single job of delivering the news; the details are the content of the announcement, not separate purposes.

To request or instruct. The document exists to get the reader to do something: supply a document, complete a form, attend a meeting, follow a procedure. The request may appear late in the text after context that justifies it, and the context — however detailed — is in service of the ask. This is the function candidates most often miss, because the justifying detail is longer than the request itself.

To remind or follow up. The document exists to re-raise something already known: an upcoming deadline, an unpaid invoice, a pending response. The presence of phrases that signal recurrence — "as mentioned," "following up on," "this is a reminder" — flags the reminder function even when the document also restates the original information.

To respond, confirm, or apologize. The document exists to react to a prior communication: to answer a question, acknowledge receipt, confirm an arrangement, or apologize for a problem. A response document often opens by referencing what it responds to, and that opening reference is the strongest signal of its function. Recognizing the document as reactive depends on the same between-the-lines reading that the inference and implicit information discipline trains — the prior message is rarely shown, and its existence must be inferred from the opening.

The detail-as-purpose trap that defines the wrong answer

The defining distractor of the document-function question is the true detail offered as the purpose: a fact genuinely present in the text that describes content rather than function. Recognizing this trap as a category is what lets the candidate refuse an option just because it is verifiable in the passage.

The background-as-purpose distractor. The document includes context that explains why the real action is being taken — a problem that occurred, a situation that developed — and the distractor names that background as the purpose. "Why was the memo sent?" / "To report that the printer broke" when the memo was sent to instruct staff to use the second-floor printer until repairs are done. The breakdown is real but it is the reason for the instruction, not the purpose of the memo.

The secondary-action distractor. A document with a primary purpose often mentions a secondary action in passing — "we will also be updating the directory next month" — and the distractor elevates that aside to the main purpose. The candidate who has not weighed which action the whole text is organized around takes the secondary mention as central.

The single-paragraph distractor. In a multi-paragraph document, one paragraph may have a local function — describing a benefit, listing a schedule — and the distractor names that paragraph's job as the document's job. The defense is to ask what all the paragraphs together accomplish, not what one of them does. This whole-versus-part discrimination is the same one the author purpose and tone identification discipline applies to attitude — purpose, like tone, is a property of the whole text, and reading it off one paragraph produces a confident wrong answer.

The structural reading that locates a document's function

The defense against the detail-as-purpose trap is a structural reading that finds the document's function from its shape rather than from a search for a matching sentence, because function is signaled by where things sit, not only by what they say.

Read the opening for the orientation. The first sentence or two of a business document usually orients the reader to why it exists — "I'm writing to request," "Please be advised that," "Thank you for your inquiry regarding," "This is to confirm." The opening orientation is the single most reliable function signal, and a candidate who reads it deliberately often has the purpose before reading the body.

Read the closing for the action. When the opening is purely contextual, the function often surfaces at the end, where request and instruction documents place the ask: "Please send the revised figures by Friday," "Kindly complete the attached form." A document whose body is all background and whose final line is an instruction is a request document, and its purpose is the instruction, not the background.

Locate the one action the whole text is organized around. Between opening and closing, the candidate identifies the single action that every other element supports — the announcement the details elaborate, the request the context justifies, the apology the explanation accompanies. That organizing action is the function. Details that do not feed it are content, not purpose.

The function test that separates why from what

Before committing to a purpose answer, the candidate runs a function test: frame the option as a completion of "The writer's main goal in sending this was to ___" and check whether the option states a goal the whole document serves or merely a fact the document contains.

An option survives the test if the entire text is organized to accomplish it — if removing that purpose would leave the document without a reason to exist. An option fails if it names something true but peripheral, something that could be deleted while the document still served its main job. "To request a corrected invoice" survives, because without the request the email has no reason to exist; "to confirm a shipment arrived" fails, because the shipment is background the request rests on, and the email would still need sending even if the shipment were never mentioned. The test converts the purpose question from a sentence hunt into a single judgment — does the whole text serve this, or does it just mention it — and that judgment is what keeps a true detail from being mistaken for the reason the document was sent.