Engineering Contracts in Ontario: 6 Clauses That Can Void Your E&O

A mechanical engineer signs a developer's services agreement to get a project moving. Buried on page nine: a clause promising to "defend and indemnify" the developer, and another holding the engineer to the "highest standard of care." Two years later a mechanical system underperforms, the developer's lawyer fires off a demand, and the engineer's E&O insurer pays for the negligence claim. The contractual promise to fund the developer's defence? That part comes out of the firm's own account.

I see versions of this play out with engineering firms across Ontario. The work was fine. The insurance was in place. The contract was the problem. Your client's professional services agreement can quietly create liability that your errors and omissions (E&O) policy will never pay, and most engineers sign it without a second look.

This is the companion piece to our Ultimate Guide to Engineering Insurance in Ontario, which covers how E&O actually works: limits, claims-made, tail coverage. Here we're looking at the other side of the same coin, the contract. Here's what's inside:

• The 60-second triage before you read a single clause
• The six clauses that can void your E&O coverage
• The clauses you actually want working in your favour
• How long you're really on the hook in Ontario
• A practical pre-signing checklist

One principle ties all of it together. Professional liability insurance covers your negligence. Specifically, it covers the liability you would have had even if there were no contract. Every clause below pushes you past that line, into territory your insurer never agreed to cover.

The 60-Second Triage Before You Read a Single Clause

Before you get into the substance, spend a minute on the basics. They catch more problems than people expect.

• Get it in writing. A handshake with a repeat client feels efficient until there's a dispute and it's your word against theirs. A signed agreement is your first line of defence in a claim.
• Check what the contract calls you. You should be the "Consultant" or "Engineer," not the "Contractor." If a client's template labels you a contractor, the whole document was probably written for a builder, and it will hold you to a builder's standard.
• Find out what it incorporates by reference. Plenty of consultant agreements quietly absorb the prime contract between the owner and the general, or the owner's full spec. You can be bound by onerous terms in a document you've never read. Ask for every document the contract references, and confirm your agreement governs if there's a conflict.
• Start from a known-good base. The ACEC standard agreements (Document 31, the prime agreement between client and engineer) and CCDC 31 were written to allocate risk fairly. Negotiating up from a balanced Canadian form beats negotiating down from a client's home-brew contract.

The Six Clauses That Can Void Your E&O Coverage

Your E&O policy answers for your professional negligence. The clauses below each add a duty beyond negligence, and that's the part your policy won't follow.

1. An Elevated Standard of Care

Watch for "best," "highest," "first-class," "state of the art," or "to the Client's satisfaction." In Ontario, an engineer's standard of care is negligence-based: the skill and care a reasonable engineer would exercise on similar work under similar conditions. That's exactly what your E&O policy is built around. The moment you promise perfection (or anything above the ordinary standard), you've created a contractual duty that sits outside your coverage. If you fall short of "highest" but still met the reasonable standard, you weren't negligent, so your policy has nothing to respond to, yet you're contractually on the hook.

The fix is to tie the standard of care to that ordinary, reasonable standard and strike the superlatives. It's one of the most common edits I see, and one of the most important.

2. Broad-Form (One-Sided) Indemnity

Indemnity clauses are where contracts do the most damage. A reasonable one says you'll make the client whole for losses caused by your negligence. A dangerous one asks you to indemnify against "any and all claims," or for the client's own negligence, or for breach of contract generally. Your policy covers liability arising from your negligent acts, errors, or omissions, not liabilities you volunteer to assume on someone else's behalf. Sign a broad indemnity and you've contracted for exposure no E&O policy in the country will pick up.

Keep indemnity reciprocal where possible, and limit your obligation to damages "to the extent caused by the Engineer's negligence." Delete language that sweeps in the client's fault or other parties' actions.

3. A Duty to Defend

If I could get engineers to delete one word, it would be "defend." A duty to indemnify is triggered once your negligence is established. A duty to defend kicks in the moment an allegation is made, before anyone knows whether you did anything wrong. And here's the part that surprises people: your E&O policy defends you, the named insured. It has no mechanism to defend a third party. Unlike a commercial general liability (CGL) policy, a professional liability policy can't add your client as an additional insured. So when you promise to defend a client, you're promising to pay their legal bills personally, from the first invoice.

Strike "defend" (and its cousins, like "hold harmless" used as a defence obligation) and keep your commitment to indemnifying for damages your negligence actually caused.

4. Guarantees, Warranties, and Certifications

Engineers provide a service, not a product. But clients, used to suppliers warranting their goods, often slip in "guarantee," "warrant," "ensure," or "certify." Each one quietly raises your duty to a standard of perfection. Certifying that a contractor built "in strict compliance with the drawings," or guaranteeing a building will achieve a particular energy or LEED target, turns your professional judgment into a product warranty. Warranties aren't negligence, so they aren't covered.

You can still sign reasonable certifications. Just qualify them: "to the best of the Engineer's knowledge, information, and belief," and "in general conformance with" rather than "in strict accordance with," keep you tied to the standard of care instead of a guarantee.

5. "Comply With All Laws and Codes" or Fitness for Purpose

There's a meaningful difference between agreeing to comply with "applicable" codes and agreeing to comply with "all" laws, codes, and regulations. Codes conflict, change, and get interpreted differently by different authorities. Promising to satisfy all of them is an absolute obligation no one can actually meet. The same goes for "fitness for purpose" language, which guarantees an outcome rather than competent effort. Both exceed the standard of care, and a breach of an absolute obligation isn't negligence, so once again your E&O sits it out.

Swap "all" for "applicable," tie the obligation to the standard of care, and delete fitness-for-purpose warranties.

6. Taking On the Contractor's Job: Site Safety, Means and Methods, and Schedule Guarantees

This one creates two problems at once. Ontario's Occupational Health and Safety Act puts overall jobsite safety on the "constructor," the party with control of the project. An engineer who contracts into responsibility for construction means, methods, sequences, or site safety has stepped into a role the law never intended for the designer, and has created bodily-injury exposure that E&O excludes and that belongs in the CGL world. The same logic applies to "time is of the essence" plus liquidated damages: you've guaranteed a schedule you don't fully control.

Keep your site role as review and observation, not inspection or supervision. Don't accept authority to stop work (you can reject non-conforming work, or recommend the owner reject it). And resist liquidated-damages and "time is of the essence" clauses. Agree instead to perform as expeditiously as is consistent with the standard of care.

The Clauses You Actually Want Working in Your Favour

Reviewing a contract isn't only about deleting bad clauses. It's also about negotiating in the protections that keep a manageable claim from becoming a firm-ending one.

• Limitation of liability. A limitation of liability clause caps your total liability (to your fee, the available insurance, or an agreed amount) and is one of the strongest protections you can have, especially when your fee is small relative to the project. Good news for Ontario firms: our courts generally enforce clearly drafted limitation clauses between commercial parties, provided they're unambiguous and don't try to exclude fraud or wilful misconduct.
• Mutual waiver of consequential damages. This takes lost profits, lost revenue, and loss of use off the table for both sides. On projects that live and die by an opening date (retail, hospitality, anything revenue-driven), consequential damages can dwarf your fee many times over.
• A defined, negligence-based standard of care. State it affirmatively (the fix from clause #1), so there's no argument later about what standard applies.
• Ownership of your instruments of service. Your drawings, models, and reports are yours. Under the Copyright Act you generally own copyright in your work by default, so license it to the client for this project, make any reuse on other projects their risk, and don't hand over editable electronic files as "contract documents" without protective language.
• A sensible insurance clause. Confirm you'll carry the limits the contract requires (and that you actually can, so check before you sign). Provide a certificate of insurance as evidence. Offer a mutual waiver of subrogation. But don't agree to name the client as an additional insured on your E&O. It isn't possible, and a clause demanding it is a sign the contract was drafted by someone who doesn't understand professional liability.

How Long Are You Actually on the Hook in Ontario?

Engineers consistently underestimate this. Under Ontario's Limitations Act, 2002, there are two clocks: a basic two-year limitation that runs from when the claim is discovered, and an ultimate 15-year limitation that runs from the act or omission and isn't subject to discoverability.

Fifteen years is a long tail. There's an Ontario case involving a hog barn built in 2002 where a beam failed and the structure partially collapsed in 2017, and the engineering firm that provided structural advice was named in the action a decade and a half later. That's not an outlier. It's how long-tail design risk works.

This is where contract review and insurance meet. E&O is claims-made, meaning the policy that responds is the one in force when the claim is filed, not when you did the work. If you retire, merge, or let coverage lapse without buying tail coverage (an extended reporting period), a claim that surfaces years later has nothing to respond to. We walk through that timing in detail in the pillar guide. It's the reason we tell every engineer near retirement to price tail coverage early. One smaller point while you're reviewing: avoid signing "under seal" where you can, since it can extend the limitation periods that would otherwise protect you.

What This Means for Your Firm

Five things to do before you sign your next agreement:

1. Run every contract past two reviewers. A construction lawyer for the legal wording, and your E&O broker for what your policy will and won't back. They answer different questions, and skipping the second one is guessing.
2. Start from a Canadian standard form. Negotiate up from ACEC Document 31 or CCDC 31, not down from the client's template.
3. Red-flag the trigger words. "Defend," "guarantee," "warrant," "ensure," "certify," "highest," "best," "all laws," and "any and all claims" are your cue to slow down.
4. Match your limits to the contract. If the agreement requires $2M and your professional liability policy carries $1M, you have a compliance problem and a coverage gap. Size your engineering E&O to the projects you're actually bidding.
5. Price tail coverage before you need it. If retirement or a merger is on the horizon, get the number now and build it into your planning.

A contract is the cheapest risk-management tool you'll ever use, or the most expensive thing you'll ever sign without reading. Every firm's situation is different, and a solo geotechnical consultant faces a different contract risk than a structural firm stamping high-rise towers. If you want a second set of eyes on the insurance side before you sign, reach out for a tailored review. We do this all day.