
How to Review Knowledge Qualifiers on Representations and Warranties
Review knowledge qualifiers on warranties: split absolute vs knowledge, name officers plus enquiry, keep title and IP flat, then qualify, schedule, or escalate.
Key takeaway in 30 seconds
Knowing how to review knowledge qualifiers on representations and warranties is a qualify, schedule, or escalate log. Split every warranty into absolute or knowledge-qualified. Lock named officers plus a duty to enquire — or strip the qualifier. Keep title, authority, and IP ownership flat. Treat the numbered disclosure schedule as the only exception list. Then qualify, schedule, or escalate.
A founder at a 14-person UK SaaS is about to accept a vendor MSA — the umbrella later order forms sit under — whose IP and title warranties are true “to the best of Seller’s knowledge.” Sales calls it stationery. Knowing how to review knowledge qualifiers on representations and warranties means you split absolute from qualified, lock named officers plus enquiry, keep title and IP ownership flat, then qualify, schedule, or escalate.
On 8 September 2026, Ellis — Founder of a 14-person UK SaaS — has Finance’s yes on a US analytics vendor. Clause 8 warrants good title and non-infringement “to the best of Seller’s knowledge.” No Knowledge definition, no named officers, no due enquiry, no Schedule 8.1 for contractor assignments or open-source. AE Slack: “standard — we can’t warrant the whole internet.” Last year a contractor claimed a module. Go-live is Monday.
“To the best of Seller’s knowledge” is not a free pass — and in England and Wales it is not automatically a duty to look. LexisNexis UK (© 2026) says there is no statute; undefined wording generally implies no duty to investigate. Ellis names no officers and requires no enquiry, so an unknown IP or title gap can sit with him. Weagree calls “best” redundant.
Disclaimer: Checkory provides AI support, not legal advice. Consult a qualified lawyer for binding decisions.
How do you split absolute warranties from “to the knowledge of”?
A flat warranty makes the vendor the guarantor even if nobody knew. The same sentence plus “to the knowledge of” shifts unknown defects to you. Treat an unqualified sentence as the baseline and a knowledge limb as a risk shift, not stationery.
Freeze the packet — MSA plus warranty schedule plus any disclosure letter. See the packet freeze walk. Split every warranty into flat or qualified. High sentence = “to the best of Seller’s knowledge” with no definition. LegalClarity treats a flat IP or title sentence as a guarantor promise. Vaquill (20 June 2026) says the fight is the qualifiers, not the rep. For example, Ellis’s Clause 8 qualifies title and IP in one breath. Do: log each as absolute or qualified. Don’t: treat a to the best of knowledge warranty as stationery.
Typical mistake
Ellis hears “standard — we can’t warrant the whole internet” and files the qualifier as stationery. Undefined knowledge on title and IP is a costly risk shift.

What to lock if they name no officers — and no duty to enquire?
“Seller’s knowledge” with no names and no enquiry leaves nobody’s head in the box. Demand named roles plus “after due and careful enquiry,” or strip the qualifier. Without names you cannot point to a head; the vendor can point to nobody.
High sentence: “Seller’s knowledge” with no officers and no enquiry. Define Knowledge as the actual knowledge of named roles — CTO, head of legal, founder — after due and careful enquiry of the people who run IP and title. Lexana [2026] EWHC 611 (TCC) treats a deeming clause as objective — what those enquiries would have revealed. BCLP (3 June 2026) on Synthos [2026] EWHC 83 (Comm): a named enquiry group can have knowledge aggregated. In practice, Ellis cannot bank on a judge writing that sentence in. Do: names, roles, due enquiry. Don’t: accept a bare “Seller’s knowledge.”

What does “in all material respects” hide on the same sentence?
Stacked “to the best of Seller’s knowledge, in all material respects” is two doors on the face of the warranty. You must show they knew and that the gap was material. Circle every material word on the same sentence as knowledge.
High sentence: “to the best of Seller’s knowledge, in all material respects, the Services do not infringe.” Two hurdles. If the next sentence is an indemnity scrape that reads those words out when deciding who pays, that is the indemnity-clause review checklist. Do: strip materiality from title, authority, and IP ownership; if it stays on an operational warranty, demand a number (“in excess of £X”). Don’t: treat stacked words as comfort.
Which title, authority, and IP lines stay unqualified?
Organisation, authority, title, and IP ownership stay flat. Knowledge is a commercial ask on unknown third-party claims or threatened-not-filed litigation — not on “we own what we are selling.” A vendor that will not give flat title is telling you the stack may not be theirs.
Ellis’s live line puts knowledge on good title and on IP. Vaquill and Mayer Brown (October 2025) — structure, not his statute — keep ownership and title flatter; non-infringement is where sellers push knowledge. Split: “we own or are licensed to grant what we sell” stays absolute; knowledge after enquiry of [CTO] on non-infringement may survive. Contractor assignments and open-source licences are checkable facts, not “the whole internet.” Do: refuse knowledge on title, authority, and IP ownership. Don’t: accept “nobody can warrant IP.”
When to treat Slack as not a disclosure schedule?
Exceptions that are not on a numbered schedule do not qualify the warranty. A sales-call, Slack note, or “anything in the data room” is not disclosed. Demand Schedule 8.1 that matches the warranty — “except as set forth in Schedule 8.1.”
High sentence: “except as disclosed in the data room.” CT Acquisitions (27 April 2026) treats a scheduled item as accepted; omit it and the clean rep is false. If the ownership promise is only on a slide, that is the entire-agreement and no-reliance review. Do: demand section-referenced disclosure schedule exceptions. Don’t: treat Slack as the schedule.
Workflow
packet → absolute vs knowledge → named officers / enquiry → materiality stack → title / IP flat → schedule not Slack → qualify / schedule / escalate

How do you qualify, schedule, or escalate?
Qualify only on unknown third-party claims, with named roles plus due enquiry and title and IP ownership flat. Schedule known contractor, open-source, and claim letters on Schedule 8.1. Escalate knowledge on title or IP ownership, no names, stacked materiality, or a data-room catch-all.
Success bar before you sign: fill the checklist — which reps are qualified? whose roles? actual only or after due enquiry? materiality on the same sentence? title and IP still flat? exceptions only on a numbered schedule? qualify / schedule / escalate — and point to one sentence that pauses Monday.
Copy the live Knowledge definition, named roles, and schedule numbers onto the go-live note. Owner = Ellis or a deputy. Optional: a Checkory first-pass — a first machine pass before a human reads every page — on the same PDF, then a human opens every High flag — a high-severity hit a human must verify. No green light.
Qualify, schedule, or escalate
| Gate | Qualify | Schedule | Escalate |
|---|---|---|---|
| Knowledge limb | Unknown third-party claims | Known claim letters on 8.1 | Knowledge on title / IP ownership |
| Whose heads | Named roles + due enquiry | People who run IP and title | No names and no enquiry |
| Materiality | Off title / IP ownership | A number, not a vibe | Best-of + in all material respects |
| Exceptions | Except as set forth on 8.1 | Contractor / OSS / claim letters | Slack or data-room catch-all |
Six steps
Freeze the packet
MSA plus warranty schedule plus any disclosure letter. Search knowledge, aware, best of, title, IP.
Split absolute versus knowledge
Log each warranty as flat or qualified. Undefined “best of” is High.
Lock names plus enquiry
Roles that run IP and title, after due enquiry — or strip the qualifier.
Circle stacked materiality
Material words on the same sentence as knowledge. Indemnity scrape? Leave this page.
Keep title and IP ownership flat
Knowledge may survive only on unknown third-party claims after named enquiry.
Qualify, schedule, or escalate
Exceptions only on Schedule 8.1. Owner = Ellis or a deputy. No green light.
Frequently asked questions
Is “to the best of knowledge” a free pass?▼
Should title be qualified?▼
Do marketing claims become warranties?▼
Knowledge of which officers?▼
Does a Slack note count as a disclosure schedule exception?▼
Can a warranty also be a representation?▼
What to do next
Indemnity-clause review checklist
Who pays after a scrape.
RelatedEntire-agreement and no-reliance review
The promise is only on a slide.
RelatedMSA vs Order Form Precedence: How to Review Which Document Controls
Open the sibling checklist after this screen.
RelatedHow to Review a Survival List and Duration After Expiry
Open the sibling checklist after this screen.
Sources
Related guides


