Between the designers, the crew, the supplies, and theA strong landscape design can still turn into a difficult project when the client, estimator, project manager, and crew have different ideas about what’s included.
Maybe the client assumes irrigation changes are part of the job. The estimator priced the new planting but not the removal and disposal. Or the crew arrives expecting access that hasn’t been arranged.
Each assumption creates another opportunity for added costs, delays, and difficult conversations.
A clear landscape scope of work helps prevent those problems before construction begins. It defines the work, deliverables, responsibilities, boundaries, and other conditions that everyone is agreeing to. Just as importantly, it makes clear what the project doesn’t include.
That gives your client a clearer understanding of what they’re paying for. It also gives your team a shared reference point for estimating, approvals, production, and any later changes.
In this article, we’ll explain what to include in a landscape scope of work, how to clarify exclusions and assumptions, and how to manage changes without letting them expand the job.
Key Takeaways
A useful landscape scope of work defines what’s included, what’s excluded, and the assumptions behind the project. Design decisions, approvals, responsibilities, timing, and pricing need to align before work begins so the client and your team share the same expectations. Changes are normal in landscape design projects. But documenting their impact on scope, cost, and schedule helps prevent unpriced work and protect your margins.
What Is a Landscape Scope of Work?
A landscape scope of work defines the agreed-upon boundaries of a project. It explains:
- What work will be completed
- What will be delivered
- Who is responsible for key parts of the job
- Important exclusions and assumptions
For landscape design-build firms, that clarity is important because several teams rely on the same project scope. The designer needs to understand what the client approved. The estimator needs to price that same work. The project manager and crew need to know what they’re expected to deliver.
Just as important, the client needs to understand what they’ve agreed to.
That’s how Glenn Curtis, owner of Plantenance Landscape Group, approaches scoping. He uses the scope of work to set expectations from the start, so clients understand what they’re receiving and what they’re paying for.
“The last thing we want is a disappointed client at the end of the build,” Curtis says. “We push a lot about client experience, which is very big for us. A lot of clients come back because they’re not only very satisfied with the end result, but they’ve had a great client journey.”
Once those expectations are documented, everyone has something to refer back to as the project moves forward.
A scope of work is also related to several other project documents, but they don’t all serve the same purpose:
| Document | What it primarily establishes |
| Scope of work | What work and deliverables are included and excluded |
| Estimate | Expected costs or pricing for that work |
| Proposal | The recommended project and offer |
| Contract | The broader agreement governing the project |
Exactly how you structure these documents will depend on your company and the project. What matters is that they stay consistent.
The scope of work has one job: define the project everyone is agreeing to deliver.
RELATED ARTICLE: The Modern Landscape Design Workflow: From Site Visit to Signed Proposal
What Should a Landscape Scope of Work Include?
A good landscape scope of work should answer key questions before they become problems on the job.
It doesn’t need to cover every minor detail. But it should be specific enough that the client, estimator, project manager, and crew all understand what they’re working toward.
Use this landscape scope of work checklist as a starting point:
| What to define | What to clarify | Why it matters |
| Project objective and work areas | Which areas of the property are being changed and what the project should accomplish | Sets clear boundaries for the job |
| Site conditions and assumptions | Grades, access, existing features, utilities, drainage, or other relevant conditions | Prevents the estimate from relying on hidden assumptions |
| Specific deliverables | Planting, hardscape, grading, irrigation, lighting, structures, or other work being provided | Shows exactly what the project includes |
| Materials and quantities | Material types, specifications, quantities, or allowances where needed | Gives estimating and production clearer information |
| Responsibilities | Who handles permits, site access, utility coordination, or other requirements | Keeps important tasks from falling into a gray area |
| Approvals | Which designs, materials, selections, or other decisions need client approval | Creates clear decision points before work moves ahead |
| Timeline and milestones | Expected start and completion windows, major milestones, and schedule dependencies | Sets expectations for how the job will progress |
| Pricing and payment | Relevant allowances, payment milestones, or other pricing details | Keeps pricing connected to approved work |
| Inclusions, exclusions, and assumptions | What’s included, what isn’t, and what the scope assumes | Brings potential misunderstandings into the open before work begins |
Some of this information should start taking shape before you write the final scope. A consistent process for gathering client requirements helps establish priorities, budget, site concerns, and other decisions that eventually define the job.
The level of detail you need depends on the job. A planting renovation won’t need the same scope as a full backyard project with hardscape, drainage, lighting, and irrigation.
What matters is that the details tell the same story. If the scope calls for one thing, the approved design shows another, and the estimate prices something else, you’re starting the job with three different versions of what was sold.
After you create your scope of work, use one question to evaluate it: Could someone read the scope and still make an assumption that changes the work, price, or schedule?
If so, clarify it.
RELATED ARTICLE: How Much Should Landscaping Cost for High-End Projects?
Be Just as Clear About What’s Not Included
It’s easy to focus on what the project includes when creating a landscape scope of work. But some of the biggest scope problems come from work that was never discussed at all.
If something isn’t clearly included or excluded, the client may assume it’s part of the price. Your estimator may assume something different. Then by the time the question reaches the crew, the work may already be underway.
For example, imagine you’re replacing a planting bed next to an existing irrigation system. Does the project include modifying irrigation for the new layout? What about repairing irrigation components that are already damaged?
Leaving those details unstated creates a gray area. A clearer scope might specify that irrigation modifications within the new planting area are included, while repairs to existing damaged components are not.
Assumptions deserve the same attention. If your price assumes existing soil can be reused, equipment can access the work area, or excavated material can remain on-site, write that down.
Being specific isn’t about filling the scope with defensive fine print. It’s about making sure nobody has to guess where the agreed work begins and ends.
Align the Scope Before You Finalize the Estimate
Once the scope is clear, the next question is whether your estimate reflects it.
Every inclusion, exclusion, and assumption can affect what the job costs to deliver. If those details don’t carry into estimating, you can end up pricing a different project from the one the client approved.
That’s why design approval is so important. At Plantenance Landscape Group, Curtis’s team uses the approved drawing to calculate materials, get supplier pricing, and complete accurate takeoffs.
“We can’t produce a budget until the drawing is approved,” Curtis explains. “Once the drawing is approved, we can calculate how much material we need, get pricing from suppliers, and put together accurate takeoffs.”
Before finalizing your estimate, make sure it reflects the approved design, quantities, materials, responsibilities, and assumptions. If disposal is included, price it. If limited access adds labor or equipment needs, account for those costs too.
Tools can help keep that information connected. For example, DynaScape Design supports quantity takeoffs from the drawing, helping design-build teams carry approved design information into estimating.
The goal is to ensure the scope, approved design, and estimate describe the same job.
RELATED ARTICLE: How Growing Landscape Design Firms Build More Consistent Workflows
Control Changes Before They Become Scope Creep
Changes are normal once a landscape project gets underway. For example, a client may request an upgrade, or site conditions may require a different approach.
The problem starts when those changes become part of the job without anyone revisiting the price, schedule, or expectations.
That’s called scope creep—when work expands beyond the agreed scope without being properly accounted for.
A clear original scope gives you the baseline you need to recognize when something has changed. From there, use a consistent process to handle changes:
- Identify the change. Be clear about what’s different from the approved scope.
- Determine the impact. Look at additional labor, materials, cost, and schedule changes.
- Document it. Record the new work and its impact on the project.
- Get approval. Make sure the client agrees before the added work moves forward.
- Update the project record. Keep the change connected to the job so your office and field teams are working from the same information.
This is where a formal change order becomes useful. Manage360, for instance, lets landscape design-build firms manage change orders separately without altering the original contract. That preserves the original baseline while keeping added work and costs connected to the project.
Changes don’t have to put the project or your margins at risk. When you document and approve each change before the added work begins, everyone knows what changed, what it will cost, and how it affects the job.
A Clear Scope Makes the Whole Project Easier to Manage
Before you approve a scope of work, give it one final test:
Could the client, estimator, project manager, and crew read it and come away with the same understanding of what’s being delivered?
If not, look for the gaps:
- Clarify what’s included and excluded
- Check the assumptions behind the price
- Make sure the approved design and estimate describe the same job
- Establish how you’ll handle changes before construction begins
That clarity benefits everyone. Clients know what they’re paying for and what to expect. Your team also gets better information for estimating, handoffs, and production.
Then when something changes, you have an agreed starting point for deciding what happens next.
About the Author
Natalie is a Director of Product Development for DynaScape. She’s been working with spatial software applications for over 20 years. If she’s not solving problems, you can find her outside—running, working in the garden, or on a bike.