The client who negotiates before day one will dispute your invoice after

A contractor quoted $12,000. The homeowner kept adding work until the real scope hit $17,500. Two days before the start date, the homeowner said another contractor would do it for $11,000 and asked him to match it. The contractor said take the other guy. The homeowner came back the next day, then signed at $15,000, with a term requiring change orders in writing.

Day one on site, the homeowner was already pushing for work outside that signed scope, and hinting he would not pay extra for it.

The contractor asked a trade forum when to pack up and walk. Five hundred and thirty people answered, most of them contractors with their own version of the same story. The top reply did not tell him how to handle day one. It told him the mistake happened two days earlier: he should have walked the moment the homeowner asked him to drop his price.

The pattern: price-testing before the contract predicts disputes after

A client who tests whether your price is negotiable before a single tool comes off the truck is establishing something for later, whether they mean to or not: that the number is soft. Concede once at that stage and every later conversation, every change order, every "can you just" starts from the same premise. This is the core of construction change order scope creep, and it starts well before the actual creep does.

That does not mean walking away from every client who negotiates. Most clients negotiate a price at least once, and most of those relationships go fine. The signal worth reading is not that they negotiated, it is what they negotiated on. Asking about the payment schedule, or whether a specific line item can be substituted, is normal buyer behavior. Asking a contractor two days before start to simply drop the number, with no change in scope to justify it, is asking whether the number ever meant anything at all. It means recognizing what a negotiated concession before signing predicts about the conversations to come, and holding the contract terms firmly from the first day on site, not the third.

Why the small requests are the real danger, not the big ones

Nobody gets burned by one obvious, expensive scope change. Those get noticed and priced. The danger is the first informal add, the one that feels too small to bother invoicing separately. Maybe it costs $200. The second one costs $400, and by the third, the client genuinely believes extras are just part of what they are paying for. Nobody told them otherwise, because nobody sent a change order for the first one.

Resetting that expectation once it is set is far harder than preventing it. The contractor is now the one arguing that the "always been part of it" work was actually extra, against a client who has stopped expecting to pay for it. By the fourth or fifth unbilled add, the contractor is also the one who has to remember exactly what was added, when, and what it cost, usually from memory, weeks after the fact, against a client who remembers none of it the same way.

The one sentence that fixes it

"Happy to do that. Let me send you a quick change order to approve."

It is a short sentence, and it does three things at once. It says yes, so the client does not feel like they are being told no. It sets an expectation that added work has a price, without naming a number on the spot and getting it wrong. And it creates a paper trail the moment the client agrees, which is the part that actually protects the contractor later.

Say it on the first informal request, not the third. It costs nothing, it does not sound confrontational, and it puts the added work back on paper before the client's mental model of the project settles into "extras are included."

If the client pushes back with something like "I thought that was included," the answer is not to argue about what was said. It is to point at the document: "The signed scope covers X. This is additional to that, which is exactly why we agreed changes get a written order, so neither of us has to rely on memory." That sentence does the work the contract's change order clause was written to do. Most clients back off once the conversation moves from opinion to the document they signed.

What makes a change order actually enforceable

A change order that will hold up needs five things in writing:

• Description of the added work, specific enough to distinguish it from the original scope. "Extra electrical work" is not specific. "Add two additional outlets in the garage, per the client's request on-site" is.
• Price, stated as a number, not "we'll figure it out." An open-ended promise to bill later is exactly the ambiguity a dispute grows in.
• Schedule impact, since added scope usually moves the completion date, and a client who is not told that upfront will treat the delay as a separate grievance later.
• Signature from whoever actually has authority to bind the client, not just whoever happened to ask for the change. On a residential job that is usually the homeowner on the contract, not a spouse, a property manager, or a site visitor who mentioned it in passing.
• Date, so there is a clear record of when the request and the approval happened, which matters if a dispute later turns on whether the change was approved before or after the work was done.

Missing any one of these turns the change order into the same weak, verbal-adjacent document it was trying to replace. A description with no price is a request, not an agreement. A price with no signature from the right person is not enforceable against the client at all.

Payment structure as protection

Tie every payment to a completed, verifiable milestone, not to a date on the calendar. On the $15,000 job from the story, that could look like 30% at signing, 30% at rough-in complete, 30% at final inspection, 10% at walkthrough sign-off, each one tied to a stage anyone can look at and confirm rather than a date that arrives whether the work is done or not. Never let the work get more than one phase ahead of the money you have actually received. If a scheduled draw is missed, stop work until it is resolved. A contractor who keeps working two phases past the last payment is financing the client's project with their own labor and materials, and that gap only ever gets wider under pressure to "just finish it."

When the client stops paying

If a client stops paying and the informal fixes above have not resolved it, the mechanics lien is the real remaining leverage, and it runs on a state-specific clock. LienDone's lien deadline calculator covers the filing window by state. As a rule, finishing the work to the contract's specification and then filing tends to put a contractor in a stronger position than stopping mid-job, but this depends heavily on your state's lien statute and the termination language in your own contract, so confirm both before deciding either way.

Stopping work outright is sometimes the right call, particularly when a client has made clear they do not intend to pay for approved change orders already performed. But walking off mid-job without following the contract's own termination clause can hand the client a breach-of-contract argument of their own, on top of whatever nonpayment dispute already exists. Read that clause before the conversation gets heated, not during it.

This is general information, not legal advice. Change order enforceability, lien rights, and contract termination remedies vary by state. Talk to a construction attorney about your specific contract before you decide to stop work or walk off a job.

---

Scope creep and material markup disputes both show up on the same jobs, often from the same client. Why clients dispute your material markup covers the other half of that pattern, and the retainage carveout your lien waiver might be missing covers what protects you once payment starts moving again. LienDone sends state-compliant lien waivers your subs and clients sign from their phone, no account required. Start a 14-day free trial, no credit card required.