CheckoryCheckory
Clause 18 entire-agreement box, unnamed side letter outside the packet, no face

How to Review an Entire-Agreement and No-Reliance Clause

Review entire-agreement and no-reliance: list bought promises, name every artefact, lock this subject matter, then move the missing side letter in or walk.

9 min readArticle
💡

Key takeaway in 30 seconds

Knowing how to review an entire agreement merger and no-reliance clause is a keep / narrow / walk log, not a back-page heading. List every promise the business thinks it bought. Name the master contract, order form, schedules, and any side letter on the face of the clause. Lock this subject matter. Check no-reliance and a fraud carve-out. Then move the missing promise in or walk.

An ops lead is about to accept a vendor MSA — master services agreement, the umbrella the vendor hangs the order form on — that “just has standard boilerplate at the back.” Buried in Miscellaneous sits entire-agreement plus no-reliance. Fill a keep / narrow / walk log: list the bought promises, name every artefact, lock this subject matter, then move a missing letter in or walk.

On 5 September 2026, Tess — Ops at a 23-person UK marketplace — has Finance’s yes on a fulfilment SaaS. Sales emailed last Tuesday: a full CSV export within 30 days of exit, side letter attached. Clause 18 says the Agreement plus the Order Form is the entire agreement and she has not relied on any statement not set out in it. The letter is not in the zip or any schedule. The AE says “standard — everyone has entire agreement.” Go-live is Monday. Typical mistake: treating the heading as harmless integration.

Disclaimer: Checkory provides AI support, not legal advice. Consult a qualified lawyer for binding decisions.

How do you list every promise the business thinks it bought?

Write the bought list before you open Clause 18. Seats, price, uptime, CSV export on exit, anything sales said in the demo or the deck. Search entire agreement, merger, integration, supersedes, no-reliance, “not relied.” That sentence decides what counts as the deal.

Freeze the packet — the signed file set — first. The packet freeze walk is one folder. Which named document wins a fight inside that folder is the order-of-precedence walk. Entire agreement is not a spare parachute for an unnamed letter. Under England and Wales paper, a merger sentence alone usually does not kill a misrepresentation claim — GC.AI on Inntrepreneur: denying contractual force is not the same as killing reliance. Do: write the bought list first. Don’t: skip Clause 18 as boilerplate.

Typical mistake

Tess treats “standard entire agreement” as harmless. The hidden risk is an unnamed export letter sitting next to no-reliance.

Entire-agreement box naming MSA and order form, one side letter sitting outside, no face
Entire-agreement box naming MSA and order form, one side letter sitting outside, no face

Which papers must the entire-agreement sentence name?

A High sentence — a high-severity line a human must verify — reads “this Agreement constitutes the entire agreement” with no list. Buyer colour names the MSA, Order Form, SOW, DPA — data processing agreement — exhibits — attached schedules — and the side letter by date and parties. Unnamed sits outside.

For example, Forms Legal is blunt: if the main clause is not carved out for the side letter, the letter may be treated as superseded. Name it by date and parties; say it is supplemental and does not merge. ContractKen lists “together with Exhibits A–D…”. CSV format, days, and fees are the export-rights walk once the letter is named — this H2 is only whether it is named. Do: title plus date on the face. Don’t: assume “everyone knows Exhibit B is in.”

What to lock: this subject matter — not every deal you have?

A High sentence supersedes all agreements between the parties with no “relating to the subject matter” limit. Buyer paper says “with respect to the subject matter of this Agreement” and lists surviving papers: an existing NDA — non-disclosure agreement — a different SOW. This clause is not a wipe of every live contract.

Typical wording on UKLegalGuides already uses “subject matter.” The opposite High: Tess wants a prior formal paper dead and the clause only says “supersedes.” Buckles on Capgemini: “supersedes … relating to its subject matter” does not automatically extinguish a separate formal contract; silence is not a repeal. If a prior paper must end, name it and say so. Do: lock this subject matter. Don’t: treat “all agreements” as a tidy broom.

Subject-matter limit circled next to an all-agreements wipe, no face
Subject-matter limit circled next to an all-agreements wipe, no face

How do you read no-reliance against a fraud carve-out?

Three parts sit in one Miscellaneous block: the entire-agreement statement; a no-reliance limb (“has not relied on any representation not set out in this Agreement”); and a fraud carve-out. Entire agreement alone is not no-reliance. The second limb is the lock.

In practice, no-reliance is an exclusion in substance. Misrepresentation Act 1967 s.3 (England and Wales) sends it through the UCTA 1977 s.11 reasonableness test. A&O on First Tower is structure-only: you cannot draft around s.3 by calling it a “basis clause.” Do not write that UCTA will save Tess. Thomas Witter colour: a clause that also tries to exclude fraud can fail as a whole — carve fraud out. Helix is blunt: this is not a licence to lie, and proving fraud is a high bar. Do: keep mutual no-reliance plus an express fraud carve-out. Don’t: accept a Tess-only limb that also waives negligent misrepresentation on standard terms without counsel — a qualified lawyer.

Not a wipe and not a green light

Do not write that no-reliance is void, or that fraud is easy to prove. Name the limb, carve fraud out, and still move the missing promise in.

When to send future changes to a variation clause, not here?

Entire agreement looks backward. Slack, email, or “the AE said we can add export later” is a variation fight. Merger is not a no-oral-modification clause. Tess’s pre-sign side letter is this review; a post-sign Slack yes is not.

Pactlio splits the jobs: merger looks back; a signed-writing variation clause looks forward. If the paper already requires signed writing, an informal yes may not vary it — Pactlio’s review steps plus the Rock Advertising [2018] UKSC 24 fence. Do: park future changes on the variation path. Don’t: leave export to a Monday Slack thread.

What to do with a missing promise — move it in or walk?

Tess’s draft is the walk trigger: Clause 18 entire-agreement plus no-reliance, export side letter not named. Buyer ask: schedule the letter (date, parties, “supplemental, does not merge”) or lift the export sentence into the order form before anyone signs. Sales calling it “standard” is not the test.

You are done when the one-page log is filled and you can point to one sentence that would pause signature. That is the success bar: bought-promise list → name every artefact → this subject matter only → no-reliance + fraud carve-out → variation is not this clause → missing promise in or walk.

Escalate a Delaware SPA or a live fraud allegation to counsel. After the log, upload the same PDF to Checkory document analysis for a first-pass — a first machine scan that highlights entire agreement, merger, no-reliance, and side letter on that file. A human still opens every High flag — a high-severity item a human must verify.

Keep, narrow, or walk board: named side letter versus walk, no face
Keep, narrow, or walk board: named side letter versus walk, no face

Keep, narrow, or walk

GateKeepNarrowWalk
What is the dealBought list matches named papersAdd the letter or lift the sentenceExport stays unnamed next to no-reliance
Which papersMSA, order form, SOW, DPA, exhibits, letters named by dateSchedule the letter; supplemental, does not merge“This Agreement” only, no list
ScopeThis subject matter; surviving papers listedCut “all agreements”; name a paper to end itSilent supersedes used as a wipe
No-relianceMutual + express fraud carve-outAdd the fraud sentence; strike a Tess-only limbThey refuse the letter and keep no-reliance

Six steps before go-live

1

Write the bought list

Seats, price, uptime, CSV export, deck promises. Then search merger / no-reliance.

2

Name every artefact

MSA, order form, SOW, DPA, exhibits, side letters — title and date on the face.

3

Lock this subject matter

Not every deal. List surviving papers. If a prior paper must die, name it and say so.

4

Read no-reliance + fraud

EA alone is not the lock. Keep mutual no-reliance and an express fraud carve-out.

5

Park future changes

Slack after go-live is a variation fight, not this clause.

6

Move it in or walk

Schedule the letter or lift the sentence. Walk if they refuse and keep no-reliance.

Frequently asked questions

Does a pitch deck survive an entire-agreement clause?
Not as a term once the clause is live, unless you schedule the deck. Put the slide on the bought list first.
What if an exhibit is not named in the entire-agreement sentence?
Treat it as outside until it is scheduled by title and date. Do not assume “everyone knows Exhibit B is in.”
Is a no-reliance clause a licence to lie?
No. Fraud cannot be excluded. Proving it is a high bar. Name the side letter or walk — do not plan a fraud claim.
Does “supersedes all agreements” wipe every other contract with this vendor?
Not automatically. Lock “this subject matter.” If a prior formal paper must end, name it. Silence is not a repeal.
Does an entire-agreement sentence alone bar a misrepresentation claim?
Usually not under England and Wales paper. You need a separate no-reliance limb, still facing Misrepresentation Act 1967 s.3. Do not write that the limb is void.
Can a later Slack “yes” add the export after go-live?
That is a variation fight, not this clause. If the paper requires signed writing, an informal yes may not vary it.

Highlight entire-agreement on this file

Upload the same PDF. A human still opens every High sentence.

Start document analysis

What to do next

Sources

Read also

Related guides

Updated: September 5, 2026