Ledge

Included vs. Not Included: How to Write Proposal Exclusions That Protect Your Margins

EG
Edgar Galindo
April 14, 2026· 8 min readProposals
Proposal inclusions and exclusions — what to list as not included to prevent scope creep and disputes

The client asked about the irrigation head near the patio. You assumed it was obvious it was not in scope. They assumed it was. Three days later that argument cost you $400 and a review.

Scope creep is the silent margin killer. It does not usually start with a client asking for something unreasonable — it starts with a proposal that was vague enough to make something reasonable feel included when it was not. Exclusions fix this before the job starts.

A well-written exclusions section is not about being difficult with clients. It is about giving everyone the same understanding of what was priced. That prevents the job-site argument — and the argument-review that follows.

Where to Put Exclusions in a Proposal

After the scope and before the signature line. Not buried in fine print at the bottom. Not in a separate document that only gets referenced. In the proposal itself, clearly labeled "Not Included" or "Exclusions," written in plain language.

Clients who sign a proposal with a visible exclusions section have no leg to stand on when they ask for something on that list at no charge. The expectation was set in writing before work started. That is where the protection lives.

Landscape proposal exclusions section showing permit fees, irrigation, lighting, and utility locates not included

The Standard Exclusions List for Landscape Proposals

Every landscape proposal should include these by default — add job-specific items on top:

  • Permit fees: "Permit applications and fees are not included. If required, they will be billed at cost."
  • Irrigation adjustments: "Adjustments to existing irrigation heads or zones are not included unless noted in scope above."
  • Existing concrete or structure demolition: "Removal of existing concrete pads, retaining structures, or landscaping beyond what is listed in scope is not included."
  • Utility repairs: "Any damage to unmarked utilities discovered during excavation is not the responsibility of [Company Name]. Client is responsible for utility locate (811) prior to project start."
  • Grading outside project footprint: "Grading or drainage work beyond the immediate project area is not included."
  • Tree removal or stump grinding: "Tree removal, trimming, or stump grinding is not included unless specifically listed."
  • Pre-existing debris hauling: "Removal of debris, materials, or equipment existing on site prior to project start is not included."
  • Sealer: "Sealer application is not included in the base scope — available as an add-on. See optional line items."

Job-Specific Exclusions You Should Add

Walk the property at the site visit and note anything adjacent to the work area that could be misunderstood as in scope. Flower bed near the patio? Exclude it explicitly if it is not being touched. Gate near the access point? Exclude any repairs. Existing landscape lighting? If you are not adjusting it, say so.

The more specific the exclusion, the more protection it provides. "Existing landscaping" is vague. "Existing jasmine groundcover in the 4-foot bed adjacent to the south patio edge" is specific and leaves no room for interpretation.

"An exclusion clause does not signal distrust. It signals professionalism. Good clients appreciate the clarity."

How to Handle Change Requests Mid-Job

When a client requests something not in scope, refer to the proposal and offer a change order. "That's not included in the original scope — I can price it out as an add-on and get you a number before we start on it." That is not a confrontation. It is a professional response backed by a signed document.

Clients who pushed back on change orders after seeing a clear exclusion section are rare. Most accept the process once they see it was documented upfront. The ones who fight it regardless were going to be difficult regardless — the exclusion just gives you a reference point for that conversation.

Close more jobs

Ledge proposals get signed 3× faster than PDF quotes.

Good/Better/Best options, digital e-signature, job photos built in, and automatic follow-up reminders. Built for landscape contractors.

Book a Demo →

Frequently Asked Questions

Will exclusions scare clients away from signing?

Rarely. Most clients read exclusions as evidence that you have done this before and know where jobs go sideways. The clients who are scared away by a professional exclusions section are often the clients who would have caused a scope dispute later. Losing them at proposal stage costs you nothing.

How do I handle an item that was excluded but the client still expects it?

Reference the signed proposal. "I can see why you assumed that — but you will see it is listed in the exclusions on page two of the proposal you signed. I can price it out as an add-on right now if you'd like." Stay calm and refer to the document. You do not need to argue — the document does that for you.

Should I use legal language in exclusions?

No. Plain language is more readable, more enforceable in a dispute, and less likely to confuse or alarm a client. "Irrigation adjustments are not included" works better than "Client agrees that contractor bears no obligation for existing irrigation infrastructure modifications unless otherwise stipulated herein." Write it the way you would say it.

What is the difference between an exclusion and a change order?

An exclusion is work that was not priced and will not be performed unless a change order is signed. A change order is the document that adds excluded work back into scope at an agreed price. Exclusion protects you from doing work for free. A change order is how you do that extra work for fair compensation. Both are necessary parts of running a clean job.

EG

Edgar Galindo

Co-founder, Ledge

Edgar built Ledge while running a landscape design-build company in Central Texas. He added a standard exclusions section to every proposal after one too many scope disputes that started with a vague proposal.