Forum Discussion

GreatRaven's avatar
GreatRaven
Contributor 2
9 days ago

$100K lesson - What contract language protects contractors when hidden conditions change the scope of a renovation job?

Hey all, first post.

I'm Chad, founder of Great Raven Renovations Ltd. We're based on Salt Spring Island, BC, and run renovation, roofing, decks, and structural work across Salt Spring, the Cowichan Valley, and South Nanaimo. Started the company in January 2022 after walking away from a stable off-island job rather than compromise how I wanted to work. Almost four years in now. Has been a hard, useful run.

The reason I'm here: most of what I've learned came the expensive way. Over those years I've put well over $140,000 into building this business — and lost more than $100,000 of it. Failed hires who couldn't hold a craftsmanship standard. Clients who exploited weak contract language to underpay or walk on finished work. Each one left a mark.

What changed isn't that we got smarter on people — it's that we built a system around the kinds of losses that almost killed the company.

A few of the pieces that came directly out of disputes:

Hidden-conditions clause in the master contract. Written after a project where opening a wall doubled the real scope and the client refused to acknowledge it.

Signed change orders with price and schedule impact before work happens. Written after a job where verbal "just add this" requests turned into three weeks of unpaid labour.

Before/during/after photo record on every job, including substrate conditions. Written after a homeowner claimed two months post-completion that something was never done — when in fact it was, and we had nothing to prove it.

Completion walkthrough before the final draw is invoiced. Written after a final-payment dispute that should have been a 10-minute conversation on site.

One accountable point of contact (me) instead of a rotating dispatcher. Written after we tried it the other way and watched communication fail in real time.

None of that came from a course. It came from losses. The process exists because of disputes, not in spite of them.

Curious how others here handle this — specifically the hidden-conditions problem. On older island homes we open walls and find things nobody could have priced. What language are you using in your contracts to protect both you and the homeowner when the unknown shows up? Anyone landed on wording that actually holds when a client pushes back?

Appreciate the community. Looking forward to learning from you.

— Chad

Great Raven Renovations Ltd.

Salt Spring Island, BC

3 Replies

  • I have a clause for lack of a better term lol that states that ; “ This agreement and pricing herein are based solely on the visible conditions at the time of inspection.” Then I go into my actions if I find something that will change the work and pricing . There are a lot of ways to say it but it’s important that you say it and in a professional manner so you don’t come off like you are out to get them. 

  • HUGEHomePros's avatar
    HUGEHomePros
    Jobber Ambassador

    Obviously having it in a contract is super important. I think also having a conversation about it, in some cases multiple times, and give tell them what your process is when you discover those things. Look at it from their perspective, they areinvesting tens of thousands of dollars and once you demo, they are in a vulnerable position. If you already described what will happen ahead of time, then back it up with evidence that makes sense to them, and also give them options, it will be a much easier pill to swallow. I like to give them other examples of times when that happened, what the cost was, and how we handled it. 

    If they are super concerned about it, they can pay you to do exploratory work. if that isn't an option, refer to the process above. 

  • Welcome, Chad. You have clearly built some useful processes out of some expensive lessons.

    My experience has been that there is a balance with contract language. The more legalistic and disclaimer-heavy an agreement becomes, the more it can invite scrutiny from a good client. At some point they start wondering, “Why does this contractor need protection from every conceivable scenario, and what are they expecting to go wrong?”

    I absolutely document hidden conditions, assumptions, exclusions, and change-order requirements, but I try to keep the agreement readable and make the real protection come from the conversation before signing. The client should understand that renovation pricing is based on what can reasonably be observed, and that opening a wall can reveal work neither party could responsibly price in advance.

    When something unexpected appears, I stop, document it, explain the options and impact, and let the client make an informed decision. By that point, the change-order language should confirm what everyone already understood rather than introduce a surprise.

    I have also been fortunate to build primarily through referrals, which creates a different starting point. There is already some transferred trust and accountability before I walk through the door. Over the past year, I have had only one return visit for a correction, and it was minor. I do not think that comes from having the most protective contract. It comes from careful client selection, detailed preparation, realistic expectations, communication, and attention to the work itself.

    The recurring pattern in your post makes me wonder whether the contract is only one piece of the issue. If hidden conditions, unpaid additions, failed hires, and completion disputes are all causing major losses, there may be a broader disconnect between estimating, client expectations, supervision, and the amount of risk the company is carrying at one time.

    A contract should be the guardrail, not the steering wheel.

    Chris
    helixcraftworks.com