Managing Scope Changes in a Garden Care Agreement
A garden care agreement sets out what is done on each visit. Over time, though, requests pile up: a resident wants a hedge cut lower, a trustee asks for a back section to be cleared, someone wants leaves swept off a roof. Some of these are routine. Some aren’t. Handling them clearly protects the scheme’s budget and keeps the relationship with your provider straightforward.
What counts as a scope change
A scope change is any request for work that isn’t covered by the agreement, or a permanent change to what is covered. Common examples:
- Adding an area that wasn’t included, such as a new verge or a neglected corner
- Removing an area, for example after paving over a lawn
- More frequent attention to a particular area
- Specialist work, such as tree felling or irrigation repairs
New planting, landscaping and redesigns are different from caring for existing gardens. Do not treat a request for them as automatically available or included; agree the appropriate specialist and scope first.
Why it matters
Unmanaged scope changes cause the same problems in most schemes:
- The team spends time on extra jobs and routine work slips
- Residents get different answers depending on who they asked
- Disputes arise about what was agreed
- The committee loses track of what it is paying for
A simple process
1. Requests go through one person. The managing agent or a named trustee receives all requests. Residents should not instruct the team on site. See reporting garden problems.
2. Check the agreement. Is the work already included? Often it is, and the request just needs to be passed on as a normal issue.
3. If it isn’t included, ask for a written quote or proposal. Describe the work clearly: where, what, and how often it is needed.
4. Get it approved. Follow your scheme’s rules on who can approve spending. Larger items may need a trustee resolution.
5. Confirm in writing. Record what was approved, who authorised it and when it will be done, using the form required by the agreement and the scheme’s rules. Do not assume an informal message satisfies every approval requirement. Ongoing changes should be reflected in the written scope.
6. Record it. Keep the quote, the approval and the confirmation together. This helps future trustees understand why the scope looks the way it does. See handover records for trustees.
Grey areas to settle early
Some tasks cause repeated confusion. It is worth agreeing in advance how these are handled:
- Gardens belonging to individual units
- Hedges on boundaries shared with neighbours
- Leaves in gutters and on roofs
- Weeds in paving cracks and parking areas
- Storm damage
- Irrigation faults
Our guide on where routine hedge, bed and paving care starts and stops goes through several of these.
Reviewing the scope
Once a year, or when trustees change, it helps to walk the property and compare it with the agreed scope. Gardens change: trees grow, areas are paved, new units are added. The scope should reflect the property as it is now. Use the actual agreement’s review and renewal dates rather than assuming changes can only be discussed once a year.
Checklist: scope changes
- All requests go through one nominated person
- Agreement checked before treating a request as extra
- Extra work described clearly in writing
- Quote or proposal obtained
- Approval given according to scheme rules
- Confirmation in writing
- Ongoing changes added to the agreement
- Records kept together
- Scope reviewed yearly
Discuss your site
For an enquiry about common-area garden care, use our contact page. Include the suburb and the main issue you want to discuss. The work, timing and responsibilities need to match the agreement for your property.
