Signing a contract with a landscaping or garden contractor is not the end of the work — it is the beginning of a project management phase that lasts until the final walkthrough and payment. Property owners who are actively engaged, organized, and communicative consistently get better outcomes than those who sign the contract and step away. The contractor is responsible for the work; the property owner is responsible for ensuring the work matches what was agreed.
This guide covers the practical mechanics of managing a garden construction project: what to track, how to communicate, when to intervene, and how to handle the inevitable complications.
Before Work Begins
Pre-Construction Checklist
Before the first crew member sets foot on the property, confirm the following in writing with the contractor: start date and expected daily schedule, permit status (confirm it has been issued, not just applied for), utility locates (required by law before any excavation), access arrangements (key code, gate access, parking), and material delivery schedule if materials are arriving before labor begins.
Photograph the existing property thoroughly — every bed, lawn area, path, structure, and plant that will be near the work zone. Time-stamp the photos. This record protects against disputes about damage caused by the contractor during work.
Establish Communication Protocols
Agree with the contractor on a communication method and cadence. Email is preferable to phone calls for anything significant — it creates a written record. Text works for quick operational questions. Ask for a daily or every-other-day update during active construction phases. Identify who the primary contact is on the contractor's team (the project manager or crew lead) and confirm their direct number.
During Construction
Daily Site Checks
A brief daily check of the work site takes 10–15 minutes and provides valuable information. Look for: progress consistent with the schedule, materials on-site matching the contract specification, no damage to existing plants or structures, and the work area being secured at the end of each day (tools stored, hazards marked). Take photos at each visit, organized by date.
The daily check is also an opportunity to notice issues before they become expensive corrections. Concrete footings poured at the wrong depth, lumber cut to wrong dimensions, or plants installed in the wrong location are far easier to fix before the surrounding work is complete.
Tracking the Schedule
Compare actual progress against the project schedule weekly. Construction projects commonly slip — weather delays are legitimate, but pattern delays (crew not showing up, materials not ordered on time, key decisions not made) indicate project management problems. Raise schedule concerns in writing when the project falls more than a few days behind, and ask for a revised schedule that shows how the original completion date will be met.
Material Verification
When materials arrive, verify them against the contract specifications before they are installed. Check lumber species and grade, hardware type (galvanized vs. stainless), soil or mulch product against the specification, and plant species and sizes against the plant list. If substituted materials arrive, reject them in writing and confirm the correct materials will be ordered before work continues. Once materials are installed, rejecting them becomes complicated and expensive.
Handling Change Orders
A change order is any modification to the original contract scope — additional work, deleted work, or work that is different from what was specified. Every change order, no matter how small, should be documented in writing and signed by both parties before the work is done. Verbal agreements to change scope are the most common source of contractor disputes.
A change order document should include: description of the change, reason for the change, additional cost or credit, impact on project timeline, and signatures of both parties. Maintain a log of all change orders throughout the project.
When Problems Arise
Quality Issues
Raise quality concerns in writing as soon as they are identified. Describe the specific issue clearly and reference the contract specification that is not being met. Ask the contractor to confirm in writing how and when the issue will be corrected. If the response is unsatisfactory, refer to the dispute resolution process in the contract.
Schedule Failures
Repeated missed schedule commitments without communication are grounds for contract remedies. Most contracts include provisions for schedule failures — review the contract language and follow the specified process, which typically involves written notice and a cure period before any withholding of payment is appropriate.
Safety Concerns
Any observed safety violation — workers without appropriate protection near power equipment, trenches without shoring, unsafe electrical work — should be raised immediately with the contractor's project manager. If the concern is not addressed promptly, contact the relevant oversight authority. Safety issues are the one area where immediate action is appropriate without waiting for written procedures.
Inspections and Milestones
For projects that require permits, inspections are scheduled by the contractor at defined stages — typically foundation/footing before concrete pour, framing before cover, and final on completion. Attend these inspections or ask the contractor to provide the inspector's written sign-off documentation. A failed inspection that is not documented leaves the property owner unaware of code issues until a future sale or renovation reveals them.
For planting projects, a mid-project walkthrough at the point when the first wave of plants is installed allows any placement adjustments before the remaining plants go in. Relocating a plant while the root ball is still in its nursery container is trivial; moving it after four weeks of establishment disrupts the root system.
Understanding plant establishment needs — when to water, when to fertilize, what to mulch — from the soil amendments guide and composting basics helps set expectations with the contractor about what the handoff care instructions should include at project completion.
Final Walkthrough and Payment
Never release the final payment before a complete walkthrough. Walk every element of the project against the contract specification. Create a punch list — a written list of items not yet complete or not meeting specification — and agree with the contractor on a timeline for addressing each item before final payment is released. A holdback equal to the value of the punch list items is standard practice until all items are resolved.
Frequently Asked Questions
How much should be withheld until final walkthrough?
Withholding 10–15% of the contract total until project completion and satisfactory punch list resolution is standard. This should be specified in the contract payment schedule before work begins, not imposed unilaterally at the end.
What is a punch list and how is it used?
A punch list is a written record of incomplete or non-conforming items identified during the final walkthrough. Each item should include a description, location, and agreed completion date. When all items are resolved, the punch list is signed off by both parties and final payment is released.
Who is responsible for obtaining inspections?
The contractor (as permit holder) is typically responsible for scheduling inspections and ensuring work is ready for inspection at the appropriate stages. The property owner should confirm inspection status and ask for copies of inspection sign-offs.
How should disputes be escalated if the contractor is unresponsive?
Start with written notice via email citing the specific contract provision. If unresolved, follow the dispute resolution process specified in the contract (often mediation before litigation). File a complaint with the state contractor licensing board, which can investigate and apply license sanctions. Small claims court is an option for disputes within the dollar limit (typically $5,000–$10,000 depending on state).
Is it appropriate to leave a review during the project?
Generally, wait until project completion before posting any public review. An in-progress review based on one phase does not reflect the full project outcome. A review posted in frustration over a mid-project issue that is later resolved is difficult to update fairly.