How to Document Contractor Deficiencies in Ontario Before You Sue

If a renovation or new build hasn't turned out the way your contract promised, your first instinct might be to call a lawyer or head straight to court. Before you do either, spend time building a solid record of what went wrong. A civil claim over defective work is often won or lost on the strength of the evidence you can put in front of a judge — and much of that evidence disappears once floors are covered, walls are closed up, or a contractor stops returning your calls.

Documenting contractor deficiencies properly, before you escalate, makes every later step easier: negotiating a settlement, sending a demand letter, or filing a court claim. This guide sets out what to gather and how to organize it.

Why the Documentation Stage Matters

In a civil claim, the person bringing it has to prove their case — including what was promised, what was actually delivered, and how the gap between the two should be measured. A judge or an opposing lawyer will want to see more than your account of events. Records created at the time, rather than reconstructed from memory months later, carry far more weight.

Good documentation also pays off before any lawsuit: contractors and their insurers often move faster toward a settlement when they can see a homeowner has a well-organized, credible file.

Step 1 — Pull Together the Paper Trail You Already Have

Start with what already exists in your inbox and filing cabinet:

• The signed contract, including any schedules, specifications, or product lists
• All quotes, invoices, and proof of payments made
• Any change orders or written variations to the original scope
• Permit documents and approved drawings, if applicable
• Written warranty language, whether in the contract or a separate document

Compare what these documents promised against what was actually built. A mismatch between the specification sheet and the finished product is often the clearest evidence of a deficiency.

Step 2 — Photograph and Film the Problem Thoroughly

Photos and video are usually the most persuasive evidence in a deficiency dispute, because they let a judge see the problem directly instead of relying on a written description.

• [ ] Take wide shots showing location and context, plus close-ups of the specific defect
• [ ] Date-stamp images where possible, or note the date separately in your log
• [ ] Record a video walk-through describing what you're looking at as you film
• [ ] Photograph the same problem again over time if it changes (spreading staining, widening cracks, recurring leaks)
• [ ] Keep the original, unedited files rather than cropped or filtered versions

Step 3 — Keep a Written Log as Things Happen

A simple dated log is one of the most underused tools in a dispute like this. Note the date you first noticed each issue, every conversation with the contractor (who said what, and when), and any promises made to return and fix something. Save text messages and emails rather than deleting them, even ones that seem unimportant at the time — tone and timing can matter later.

Step 4 — Bring In a Professional Opinion for Technical Issues

Some deficiencies are obvious to anyone: a crooked cabinet, mismatched flooring. Others — structural concerns, water infiltration, electrical work, HVAC sizing — need a qualified opinion to explain what's wrong, why it happened, and what it will cost to correct. A written report from a home inspector, engineer, or another qualified tradesperson gives you an independent, credible assessment, and often sets out a repair estimate you can use later to value your claim.

Step 5 — Organize the File Before You Escalate

Once you've gathered everything, put it in order — chronologically, and ideally with a short summary sheet linking each deficiency to the relevant contract clause or specification and the evidence that supports it. This is the file you'll hand to a lawyer, use to support a demand letter, or eventually file with a court claim. Ontario law also limits how long you have to start a legal claim over a problem like this, and that clock can begin running once you knew, or reasonably should have known, about the issue — so don't sit on a well-documented deficiency indefinitely.

Frequently asked questions