TOEIC Link Reading — Entire-Agreement And Parol-Evidence Decoding Under The Integration Notice: How To Read Whether A Prior Promise Still Counts, And Stop Treating Every Earlier Assurance As Part Of The Deal

The TOEIC Link reading section builds a recurring passage type around integration clauses — the entire-agreement statement, the merger provision, the no-oral-modification term, the assurance exchanged in negotiation measured against the term written into the signed document — and constructs its high-discrimination questions around whether the written contract was meant to be the complete and final expression of the deal rather than whether an earlier promise was ever spoken. The band-ceiling candidate reads that a salesperson promised a discount, that an email guaranteed a delivery date, or that a manager assured a feature would ship, sees that the final contract says nothing about it, and concludes the earlier promise still binds, because the assurance was clearly made and clearly relied on. The candidate is scored wrong because an integrated agreement — one the parties declared to be the entire agreement — supersedes prior statements the parties chose not to carry into the writing; the earlier promise was real, but the integration clause is the instruction that it no longer counts. The spoken assurance happened, but an entire-agreement clause measures the deal by the writing, not by the negotiation that preceded it.

The scoring consequence is that the prior promise functions as an attractor. The passage narrates an assurance given before signing, the final contract omits it, the question asks whether the party can enforce it, and the answer choice that treats the earlier promise as still binding is offered as the trap. The candidate who reads the assurance as part of the deal rewards the vivid earlier promise and selects the trap; the candidate who reads for integration checks whether the contract declared itself complete and, finding it did, treats the omitted promise as superseded, selecting the answer the integration clause actually supports. This guide formalizes the written-versus-prior reading model that reframes an earlier assurance from a binding promise into a superseded statement, the integration protocol for clauses where an earlier promise was real but no longer part of the deal, and the four-week drill that installs the discipline of checking whether the document is complete before treating an earlier assurance as enforceable. For the related discipline of reading how a change to the contract must itself be made, see the reading amendment and no-oral-modification decoding under the writing-required notice guide, and for reading which document controls when two conflict, see the reading order-of-precedence and conflicting-terms decoding under the priority notice guide.

Why the prior promise reads as binding and functions as superseded

The integration notice presents a surface that invites the binding reading. It narrates an assurance exchanged in negotiation — a discount offered, a timeline promised, a capability guaranteed — in language vivid enough to feel like a commitment, and then buries the entire-agreement clause in the boilerplate at the end of the document, in wording that reads like a formality rather than the instruction that governs which promises survived. The candidate who reads the notice for the assurance forms the impression that the earlier promise is a live obligation, and then answers the enforceability question as though the negotiation, not the writing, defined the deal. The prior promise is the wrong anchor. The notice is not recording the assurance as a surviving term; it is recording that the parties agreed the writing is the whole deal, and whether the earlier promise counts turns on the integration clause, not on how real the assurance felt.

The gap between the binding reading and the superseded reading is where the discrimination lives. A buyer who was verbally promised free installation but signed a contract stating it is the entire agreement, with no installation term, cannot enforce the promise; a vendor who assured a longer warranty in an email but delivered a signed agreement declaring itself the complete and final expression of the parties' understanding is bound by the shorter written warranty. The question is constructed to describe exactly this kind of situation: a vivid earlier assurance competing with a final writing that declared itself complete, so that the reader who fixes on the promise treats a superseded statement as an enforceable term. The candidate who reads the assurance as binding enforces the earlier promise; the candidate who reads for integration checks whether the writing was meant to be the whole deal and, finding it was, treats the omitted promise as gone.

The reframe from prior-promise-as-binding to prior-promise-as-superseded is the central correction. The integration notice is a statement about the completeness of the writing — the assurance that preceded it, the clause that declares the document whole, the gap between what was negotiated and what was written, the promises the parties chose not to carry forward — and no prior statement survives an integration clause merely because it was made. The candidate must read the integration clause and check whether the writing was meant to be complete before treating an earlier assurance as enforceable. The reframe is installable, and the integration protocol below operationalizes it for the common case where the earlier promise was real but the writing, not the negotiation, decides.

The integration protocol

The passage whose earlier promise and written term point the same way is common enough to be plausible, but the test constructs its hardest items around passages where a vivid assurance was given and then omitted from a writing that declared itself complete, because that gap between a real earlier promise and a superseding integration clause is where the discrimination the protocol exists to navigate is built. The integration protocol has three steps.

The first step is to locate the integration clause and read whether the writing claims to be complete. The candidate reads the passage and identifies the entire-agreement, merger, or complete-and-final language, and registers that it declares the document the whole deal. The most common extraction failure is fixing on the vivid earlier assurance while skimming past the integration clause in the boilerplate, which leaves the reader with a promise and no instruction about whether it survived. The integration clause must be read because the question will turn on whether the writing was meant to be complete, not on how compelling the earlier promise was.

The second step is to test the earlier promise against the writing, not against the negotiation. The candidate isolates the prior assurance and checks whether it appears in the final document, setting aside how firmly it was made. The most common outcome failure is letting the vividness of the earlier promise stand in for its survival, when an integrated writing supersedes exactly the promises the parties left out. The earlier promise must be tested against the writing because the question will turn on whether it was carried into the document, not on whether it was once spoken.

The third step is to answer for the integrated writing, not the prior assurance. The candidate selects the answer consistent with the complete-and-final document, treating an omitted earlier promise as unenforceable when the writing declared itself whole. The most common selection failure is choosing the option that enforces the earlier assurance, because that reading rewards the vivid promise the notice foregrounded. The answer must follow the integrated writing because the passage rewards the reader who checked whether the document was complete, not the reader who enforced a superseded promise.

The four-week drill

The drill installs the completeness check as an automatic reading habit, so the candidate tests an earlier promise against the writing before the answer choices are read. Each week isolates one failure point in the protocol and trains it to automaticity.

Week one trains integration-clause extraction. The candidate reads integration passages and, for each, marks the entire-agreement or merger language and states whether the writing claims to be complete, without yet answering the question. The goal is to make the integration clause visible on first read, so it is never lost in the boilerplate. For the parallel skill of reading how the contract itself must be changed, the amendment and no-oral-modification guide drills the change-must-be-written distinction alongside this one.

Week two trains promise-versus-writing testing. The candidate takes each earlier assurance and checks whether it survived into the final document, deliberately bracketing how firmly the promise was made. The goal is to stop the vividness of the assurance from being read as its survival.

Week three trains integration-based answering under time pressure. The candidate works full passages and commits to the answer the complete-and-final writing supports, deliberately rejecting the option that enforces an omitted earlier promise. The goal is to make the integration reading the default under the clock, when the pull toward the vivid assurance is strongest.

Week four trains mixed discrimination. The candidate works a set in which some items turn on an integrated writing that superseded an earlier promise, others on a writing that expressly preserved a prior term, and others on two documents whose conflict is resolved by an order-of-precedence clause, so the habit generalizes beyond a single clause type. The goal is a reader who checks whether the writing is complete before judging whether an earlier promise counts, and who is no longer captured by the vivid assurance the notice foregrounds. For the related case of deciding which document controls when two disagree, the order-of-precedence and conflicting-terms guide trains the which-controls distinction that completes this cluster.

The candidate who finishes the drill reads the integration notice as a statement about the completeness of the writing rather than a record of every promise ever made. The integration clause declares the document whole, the earlier promise survived into it or did not, and the reader who checks the writing before enforcing an assurance answers what the passage supports instead of what the vivid earlier promise suggests.