TOEIC Link Reading — Meeting Minutes and Action-Item Attribution: Reading Who Owns What After the Meeting

Meeting minutes are a ledger of obligations. A discussion is over; the minutes record what was decided and, crucially, who now has to do something about it and by when. The document is dense with names, tasks, and dates, and its whole reading value lies in binding the three together correctly — this person, this task, this deadline. TOEIC Link reading writers build questions on exactly the seams between them. A candidate who reads "the team discussed the launch" has skimmed the surface; the minutes exist to assign the launch tasks to named owners with due dates. Follow-up emails compound the challenge by revising the ledger: a deadline slips, a task is reassigned, an item is deferred. The vocabulary of action-item tracking is small, but each phrase pins a responsibility, and misreading one attaches a task to the wrong person.

This guide maps the phrase families of minutes and post-meeting follow-up correspondence, the ownership-and-deadline traps they carry, and a reading protocol for pinning down each action item. Because this genre threads named people through tasks and revisions, pair it with the invoice discrepancy and billing-adjustment language guide and the conditional clause scope and hypothetical consequence tracking framework, which train the same discipline of holding attributions and conditions precisely.

Why attribution is the whole question

An action item without an owner is not an action item; it is a wish. Minutes are written to prevent that ambiguity, and questions are written to test whether the reader preserved it. The typical stem asks Who is responsible for X?, By when must Y be completed?, or What is Z expected to do before the next meeting? Each of these demands that the reader hold a name, a task, and a date as one bound unit. The trap is that minutes list many names and many tasks in close proximity, so a reader who tracks the tasks but loses the owners can attach the right task to the wrong person. Reading minutes is an exercise in keeping the bindings intact through a crowded field.

The four phrase families of minutes and follow-up

Minutes and follow-up emails run on four recurring phrase families, each carrying a signature function.

• Assignment: X will take the lead on, assigned to, X is responsible for, action: X to, owner: X. These bind a task to a named person.
• Deadline: due by, to be completed before, target date, no later than, by end of week. These attach a time to the task.
• Status and carryover: pending, in progress, on hold, deferred to the next meeting, carried over, outstanding from last session. These describe where an item stands.
• Revision: reassigned to, the deadline has been moved, now owned by, rescheduled to, superseding the previous assignment. These overwrite an earlier attribution.

The revision family produces the sharpest traps, because it silently voids an assignment the reader may have already fixed in mind.

The ownership-transfer trap

The core trap presents an original assignment and later reassigns it, offering the original owner as a distractor. The minutes read Chen will prepare the budget draft, and a follow-up email states Since Chen is out next week, Alvarez will take over the budget draft. A distractor names Chen as responsible. The task is unchanged; the owner is not. Read take over, reassigned, now owned by as overwrites, and always let the latest attribution win. When a question asks who is responsible, trace the task to its most recent owner, not the first one mentioned — the earlier name is bait left in place precisely because it was stated first and most memorably.

The deadline-revision trap

Deadlines move, and questions target whether the reader tracked the move. The minutes set the report is due the 15th, and a later note says the deadline has been pushed to the 22nd to allow for review. A distractor offers the 15th. The task and owner are stable; only the date changed. Track moved, pushed, rescheduled, extended, and carry the revised date. A correct-sounding task attached to the superseded deadline is the trap, and the original date lingers in memory exactly because it was the first one read.

The deferred-versus-completed trap

Status language separates what is done from what is still open, and questions probe the difference. The vendor contract was signed; the venue booking is still pending. A question asking what remains to be done is answered by the pending item, not the completed one, but a distractor offers the signed contract as an outstanding task. Sort every item into done, in progress, or pending before answering, and match a "what is still outstanding" question to the open items only. The completed item is present precisely to tempt a reader who conflates "mentioned in the minutes" with "still to do."

The collective-versus-individual trap

Minutes mix tasks owned by one person with tasks owned by the group, and questions test which is which. The whole team will review the proposal; Nakamura will circulate the final version. A distractor assigns the circulation to the team, or the review to Nakamura alone. Distinguish the team will, all members, jointly from a named individual owner, and attach each task to exactly the scope stated. Blurring collective and individual responsibility is a frequent slip when several attributions sit in one sentence.

The reading protocol for minutes and follow-up

1. Bind name, task, and date as one unit: for every action item, hold the owner, the task, and the deadline together — never track the task alone.
2. Let the latest attribution win: on any reassignment or reschedule, discard the original owner or date and carry only the revised one.
3. Sort by status before answering: classify each item as done, in progress, or pending, and answer "what remains" questions from the open set only.
4. Separate collective from individual ownership: attach group tasks to the team and individual tasks to the named person, without blurring.
5. Trace to the most recent mention: when a name or date appears more than once, follow the item to its last update, treating earlier mentions as superseded.

Minutes and follow-up correspondence reward the reader who treats attribution as a live ledger, not a static list. Every follow-up email is an edit to the ledger, and the question almost always lives on the line that was edited — a reassigned owner, a moved deadline, an item quietly carried over. Hold the bindings, honor the revisions, and each action item resolves to exactly one person, one task, and one date, which is all the question ever asks for.