Treadstone Associates
Article · 6 min read

The limits of an as-is clause

“As-is” is a real, legally meaningful clause — and it protects far less than most sellers assume it does. Knowing exactly where it stops working is what keeps you from telling a client something that isn’t true.

Treadstone Associates · Updated 2026

Key takeaways

  • • An as-is clause protects a seller against patent defects — the kind a reasonable inspection would have caught. It was never designed to cover what it doesn’t.
  • • “A seller who knows about a serious latent defect and stays silent isn’t protected just because the agreement says ‘as is.’”
  • • As-is language gives a seller zero cover for a false answer to a direct question — that exception overrides the clause completely.
  • • Caveat emptor already does most of the work an as-is clause is often assumed to add — the clause makes the default explicit, it does not create new protection.

Sellers — and sometimes agents — treat an as-is clause as a kind of shield: put it in the agreement, and whatever is wrong with the house becomes the buyer’s problem. That is true for exactly one category of problem, and false for two others that matter more.

What the clause actually protects against

An as-is clause protects against patent defects: it “reinforces that the buyer took the property as they found it and generally can’t come back later complaining about something they could have caught with reasonable diligence.” (Treadstone Law) This is largely the same ground caveat emptor already covers on its own — a seller has “no general legal duty to volunteer everything they know about a property,” and the risk of a visible or discoverable condition already sits with the buyer by default. (Treadstone Law) The clause is confirmation of the existing rule more than a new layer of protection — useful for clarity and for setting buyer expectations, but not a separate legal shield stacked on top of caveat emptor.

What it does not touch: a known, dangerous latent defect

The clause has no effect on the caveat emptor exceptions. Stated directly: “a seller who knows about a serious latent defect and stays silent isn’t protected just because the agreement says ‘as is.’” (Treadstone Law) A material latent defect — one that makes a property dangerous or uninhabitable and is not discoverable on a reasonable inspection — still has to be disclosed if the seller actually knows about it, as-is language or not. (Treadstone Law)

What it does not touch: a direct lie

This is the harder line for sellers to accept, and the one worth stating plainly to a client considering it: as-is language “doesn’t give a seller cover to make false statements” in answer to a direct question. (Treadstone Law) A buyer who asks “has the basement ever flooded” and gets a false “no” has a claim regardless of what the agreement says about the property’s condition generally. The clause governs silence about undiscovered conditions — it does nothing at all once a direct, dishonest answer has been given.

Active concealment defeats it too

The same active-concealment principle that overrides plain caveat emptor overrides an as-is clause for the identical reason — a clause about the property’s condition cannot cover deliberate steps taken to hide that condition from view. Painting over water staining before a showing, or otherwise disguising a defect the seller knows about, is active concealment whether or not the agreement says as-is. (Treadstone Law)

Where RECO’s material facts guidance fits in

RECO names specific facts sellers have a legal obligation to disclose regardless of any as-is language — including history of flooding, and material facts more broadly like zoning by-law status and open permits. (RECO Bulletin 7.3) A companion bulletin addresses the seller’s own legal disclosure obligation directly. (RECO Bulletin 7.4) An as-is clause in the agreement of purchase and sale does not override an obligation that sits on the seller independently of the contract’s terms.

The clause and the doctrine are the same test, worded differently

It is worth being precise with a client about what an as-is clause changes and what it does not: caveat emptor already puts the risk of patent, discoverable conditions on the buyer by default, with no clause required. What an explicit as-is clause adds is clarity and a documented expectation — useful where a property has visible, known wear the seller wants the buyer to accept without negotiation, and useful as evidence later that the condition was flagged rather than hidden. What it cannot do is convert a hidden, dangerous, actually-known condition into something the clause’s wording waives. The legal test underneath both is identical — discoverability and the seller’s actual knowledge — the clause does not change the test, it only makes the buyer’s acceptance of the discoverable half of it explicit in writing.

A worked example

A seller lists a house “as is” because the furnace is old and the roof is near end-of-life — both visible, inspectable conditions the buyer’s own inspector would reasonably be expected to flag. That is exactly what the clause is for, and it works as intended. If the same seller also knows the basement has an active, unresolved leak that was never actually fixed — just cosmetically covered — the as-is clause does nothing to protect them on that specific issue, because it is a known, latent, dangerous-to-property-value condition the seller is aware of and did not disclose. The clause covers the furnace and roof. It does not extend to cover the leak, no matter how broadly the seller assumed “as is” would apply.

What this means for how you advise a seller

An as-is clause is a legitimate tool for setting expectations on a property with known, visible wear — an older mechanical system, cosmetic issues, deferred maintenance the seller is not planning to address before closing. It is not a substitute for an honest conversation with the seller about what they actually know and whether any of it crosses into the three exceptions above. Advising a seller that “as-is protects you either way” is the kind of advice that creates exactly the disclosure-failure exposure described elsewhere in this hub — the clause was never designed to do that work.

Related: this sits inside the same doctrine covered in the disclosure decisions that end careers, and a false statement made under an as-is clause’s false sense of cover is exactly the kind of matter that reaches a discipline hearing.

The moment an SPIS gets signed, the calculus changes

Ontario’s Court of Appeal has ruled on what happens once a seller volunteers answers on a Seller Property Information Statement: “although the completion of an SPIS is not mandatory, once a seller decides to fill one out, he or she must do so honestly and accurately and the purchaser is entitled to rely on the representations” (Krawchuk v. Scherbak, 2011 ONCA 352), endorsing the trial finding that once a vendor answers, caveat emptor “falls away as a defence mechanism”.

Common questions

Does an as-is clause remove the need for a home inspection?

No — if anything it makes one more important, since the clause’s protection is specifically tied to what a reasonable inspection would catch. A buyer who skips the inspection on an as-is property has given up the diligence step the clause’s protection assumes they will take.

Can a seller use as-is language instead of completing an SPIS?

The SPIS is optional in Ontario regardless of whether the listing is marketed as-is. The two are not substitutes for each other — an as-is clause addresses the property’s condition generally; an SPIS, if completed, is a set of specific factual representations, and each carries its own separate risk if handled carelessly.

Is “as is, where is” different from a plain “as is” clause?

The added “where is” language is common in practice and generally understood to reinforce the same idea — the buyer accepts the property in its current physical location and condition. It does not expand the clause’s effect beyond patent defects any further than a plain as-is clause already does.

Want your listing agreements to say what they actually protect?

A short conversation is enough to map how your current as-is language holds up against the exceptions that actually override it.