Change Order Pricing and Documentation on Hardscaping Jobs
Protect yourself by getting three things in writing before any change order work begins.
A change order missing any of its required elements isn't a change order. It's a conversation that someone will remember differently in six months, and they will remember it in whatever way costs you money.
Every enforceable change order needs three things: a description of the scope change specific enough that someone who was never on the job could understand exactly what was added, deleted, or modified; the exact dollar adjustment to the contract sum; and the modification to the project timeline, whether that's additional calendar days, a revised completion date, or both. All three. Signed by both parties before any work on the change begins.
That last part is where most contractors get hurt. They do the work, then try to get the change order signed after the fact. At that point, the client has already received the benefit of the labor. Your negotiating leverage is gone. The conversation shifts from "do we proceed?" to "was this really necessary?" A signed document before work begins forecloses that argument entirely. Once you've handed over the value, you've handed over the leverage.
There's also a legal distinction worth knowing because it changes your posture on a job. A change order is a mutual agreement, signed by both parties at an agreed price. A change directive is issued unilaterally by an owner when the parties can't agree on price but the owner wants the work to proceed anyway. Different documents, different legal implications. Know which one you're dealing with before you pick up a shovel.
Notice requirements are the piece contractors are most likely to skip, and that skip is expensive. Most well-drafted contracts specify that you must notify the owner within a defined window after identifying a potential scope change. Miss that window and you forfeit the right to compensation entirely, even when the work was clearly outside the original scope and completely legitimate. Read that language before the job starts, not after the dispute.
The Potential Change Order, a PCO, functions as an interim step that protects you before pricing is finalized. The moment a possible scope change surfaces, issue a written PCO to the owner. It documents that a change has been identified, starts the notice clock, and creates a timestamped record without committing to a price you haven't had time to calculate. It's not the change order itself; it's the flag in the ground that says this conversation is happening on the record.
Finally, every original contract should contain explicit language stating that no additional work will be compensated without a written, signed change order. Courts in most jurisdictions enforce that language. Include it, and every change order conversation that follows has a contractual foundation under it.
How to Calculate the True Cost of a Scope Change Before You Quote It
The most common pricing error on change orders isn't dishonesty. It's underestimation born from the instinct to be accommodating. A crew is already on site, materials are close, and adding a course of block to a retaining wall feels like a small thing. It isn't. I've watched contractors quote change orders off the top of their heads on a job site, being generous because the client seemed reasonable, and then spend the next two weeks quietly absorbing the difference.
Your crew cost is your crew cost. That rate applies to change order labor the same way it applies to original contract labor. There is no "we're already here" discount. If anything, change order work carries additional cost because it disrupts sequencing you already had dialed in.
The full cost stack for any change order should include every item below, and each should appear as its own line in your estimate. Direct labor hours, calculated realistically, including demolition, rework, or repositioning the change requires, not just the additive work. Materials at actual cost plus a consistent markup for sourcing, purchasing, and transportation; apply that markup every time, not selectively based on how you feel about the client that week. Equipment time if additional machine hours are required. Subcontractor costs as a separate line, never buried in general labor, because lumping them obscures your actual cost structure and creates confusion when the client wants to understand the bill. And overhead allocation, because a change order consumes project management time, scheduling coordination, and administrative effort whether you account for it or not.
The change order should carry the same target margin as the original contract. It is not a favor. It is a mini-contract with its own cost and its own required return.
Two pricing structures apply depending on what you know at the time. Time-and-materials pricing fits situations where the scope can't be fully defined before work begins: unknown subsurface conditions, concealed work that excavation has to reveal. For T&M, hourly rates and markup percentages must be agreed to in writing before work starts, not after. Fixed-price change orders fit situations where the scope is clear and bounded, as when an owner adds a defined square footage of pavers to an area that's already been excavated and prepared.
The disruption cost is where most estimates fall short. Adding a 200-square-foot patio extension isn't just 200 square feet of incremental paver work. It requires moving a material staging area, resequencing the crew's afternoon, extending site time, and coordinating a second delivery. Price the real impact, not just the addition.
The Documentation Workflow That Prevents Disputes From Forming
Scope creep doesn't usually blow up a job in one dramatic moment. It compounds. One undocumented change becomes the precedent for the next one, and by the time the final invoice arrives, the client is comparing a number they don't recognize to a contract they half-remember. The documentation workflow isn't bureaucratic overhead; it's what catches the problem at the first step before it gets a chance to cascade.
The sequence works like this, and every step matters.
The crew lead or project manager identifies a potential scope change on site. Work on that element stops. Nothing proceeds until the process runs its course. A PCO goes to the owner in writing immediately, even before pricing is ready, creating a timestamped record and triggering any notice requirements in the contract.
Then pricing is prepared using the full cost stack, reviewed internally before it goes to the client. The written change order, containing all three required elements, is presented to the client in person when possible; a phone call or email is a last resort. Both parties sign and date before any work on the change begins. No exceptions, not even for small dollar amounts. The exception you make today sets the expectation for every change order that follows.
The change order gets logged with the date, description, dollar amount, and confirmation of signature. A running log lets the project manager track the cumulative impact on contract value and timeline throughout the job, which prevents the end-of-project moment where a client sees a final number significantly higher than the original contract and experiences it as a surprise rather than a documented progression. That moment, when it happens, is almost impossible to recover from gracefully.
Photo documentation reinforces everything. Photograph existing conditions before any change order work begins, then photograph the completed work. Visual evidence that the triggering condition actually existed is invaluable when a dispute surfaces later, particularly with differing site conditions like unexpected rock or unsuitable soils discovered after excavation.
Any verbal conversation with a client about a potential scope change should be followed immediately by a written summary. It doesn't have to be formal; it just has to exist. "Per our conversation this afternoon, we identified that the excavation revealed..." That message, with its timestamp, is part of the paper trail even before the formal change order is issued.
How Detailed Scope Definition in the Original Contract Reduces Change Order Friction Later
Most change order disputes aren't really disputes about the change. They're disputes about what the original contract included. A client who signed a one-paragraph scope description for "patio installation" will genuinely not understand that a step-down landing, a grade transition, or a drainage channel along the foundation is additional work. The friction isn't bad faith. It's ambiguity that was avoidable, and it was avoidable at the contract stage.
A hardscaping contract scope section should specify the exact square footage and layout of all hardscape elements; material specifications including product name, manufacturer, color, and thickness, not just the word "pavers"; base preparation depth and materials; what drainage provisions are included and explicitly what is not included; cleanup and haul-off scope; and what happens if subsurface conditions differ from the assumptions the bid was built on.
That last item is the one most contracts skip, and it's critical. Every hardscaping bid makes assumptions about what's in the ground. Those assumptions should be stated in writing. When the excavator hits unexpected rock or unsuitable expansive soil, the contract language that said "bid assumes uniform sandy loam to 18 inches, consistent with visible surface conditions" becomes the foundation of your differing site condition claim. Without it, you're having a conversation instead of citing a document.
The contract should also define the change order process itself: how changes are initiated, the written sign-off requirement, and the T&M rates that apply when scope can't be fully defined upfront. Clients who read and sign that language before the job starts don't experience the first PCO as an ambush. It's consistent with what they already agreed to.
A pre-construction site walkthrough, documented in writing, establishes the evidentiary baseline for every assumption in the bid. Note visible conditions, access constraints, existing utilities, and anything the pricing depends on. If something changes between that walkthrough and execution, you have a dated record of what conditions looked like when the number was built.
One more thing that gets overlooked: inconsistent pricing in the original bid creates downstream problems. If the original estimate doesn't reflect true costs and a realistic margin, change order pricing will look arbitrary or inflated by comparison. A standardized, defensible pricing methodology in original contracts gives every change order a coherent baseline to stand on.
How a Consistent Change Order Process Protects Margins Across a Full Season of Jobs
Do the math once. A contractor running twenty hardscaping jobs at an average contract value of $35,000 who absorbs one unpriced scope change per job at five percent of contract value leaves $35,000 on the table annually. That's a piece of equipment. That's several months of a crew member's salary. That's the cash reserve that keeps a business liquid through a slow spring. Most of it is invisible because it never appears as a line item anywhere; it just shows up as a margin that's thinner than it should be, every single year.
NALP's 2025 benchmark data identifies maintaining profit levels as the second-highest concern for landscaping firms, cited by 44 percent of respondents. Change order leakage is one of the controllable contributors to that margin compression. It's not a market condition or a labor cost problem. It's a process problem, and process problems can be solved.
Standardization is what makes a change order process scalable across a season. When the workflow is written down and the pricing methodology is consistent, an office manager or project coordinator can prepare change orders without the owner needing to personally catch and price every scope change in the field. That's a meaningful operational shift for a growing company: a bottleneck removed, accountability distributed. Businesses that depend on one person's intuition about how things get priced hit a ceiling that a documented process removes.
The end-of-season review of the change order log becomes genuinely useful at that point. It shows you which job types generate the most scope changes, which client segments push back hardest, and which original scope descriptions consistently prove inadequate. That data makes next year's bids more accurate and next year's contracts more specific before a single shovel goes in the ground.
There's also a relationship dimension worth naming plainly. Clients who experience a professional, calm, well-documented change order process are more likely to approve the extra work without friction, sometimes without hesitation. A contractor who shows up with a clear written description, a defensible price, and a simple signature request communicates competence. Clients read that signal. They understand they're dealing with someone who runs a real business, and that understanding makes the approval easier every time it comes up.
