Landscape Maintenance Checklist
A landscape maintenance checklist template for a commercial site, built on two seasons rather than four. Growing season means high frequency and short visits; dormant season is when the structural work happens. Thirty-six tasks across ten zones, plus the two things that are liabilities rather than gardening: tree safety inspections with a countdown, and irrigation coverage checked while the system is actually running.
- Two seasons, not twelve equal months
- A different standard for the entrance than the perimeter
- Tree survey dates counting down as a duty of care
- Irrigation coverage checked while the system is running
Landscape Maintenance Checklist
Growing season, then dormant
| # | GROWING SEASON | DONE | SEASON | ZONE |
|---|---|---|---|---|
| 1 | Grass and lawns, ten tasks | |||
| 2 | Beds, shrubs and hedges, eight tasks | |||
| 3 | Irrigation and water, eight tasks |
The document you will get. Download for the full, editable file.
Who this landscape maintenance checklist is for
One site, and three people who want completely different things from the grounds.
The facilities or estates manager
The zones and their standards. What you are buying is a presentation standard at the entrance and a containment standard at the perimeter, and pricing them the same wastes most of the budget.
The grounds contractor
The seasonal split and the visit frequencies. A contract written as twelve equal months cannot deliver a growing season properly, and both sides know it by July.
Whoever carries the liability
Tree surveys and the chemical record. Trees near paths, car parks and boundaries carry a duty of care, and every application is evidence you may be asked for.
Whoever signs off the cost
Visit compliance against season, and cost per unit of area. Visits delivered in the dormant season instead of the growing one is the commonest way a contract underperforms quietly.
Where grounds carry more than appearance
The structure suits any commercial site with external space. What changes is who uses the grounds and what a failure costs. If you run one of these, the sector page goes further than the template does.
- Commercial real estate
Office parks and business estates, where the approach and entrance are part of how the asset is presented to a prospective tenant.
Portfolio maintenance software - Corporate facilities
Corporate campuses, where external space is amenity as well as approach and gets used rather than only looked at.
Corporate facilities software - Retail and malls
Retail parks, where car park perimeters, planting and gritting routes matter more than ornamental planting.
Retail maintenance software - Healthcare
Hospital and clinic sites, where access routes must stay clear and gritting is a patient safety matter rather than a convenience.
Healthcare maintenance software - Education
Campuses and school grounds, with sports and amenity grass on their own regime and tree surveys near play areas.
Campus maintenance software - FM service providers
Contracted grounds maintenance, where visit compliance by season is the measure a client should be asking for.
FM service provider software
What a commercial landscape maintenance checklist should contain
A landscape maintenance checklist is the annual grounds program for a commercial site, organized by growing and dormant season rather than by calendar month. It sets a standard and visit frequency per zone, lists the seasonal tasks, tracks tree safety surveys to their next due date, records every chemical application, and audits delivery by zone.
A. Organized by season, then by zone
| Field | What goes in it | Why it earns its place |
|---|---|---|
| Site details | Grounds and hard landscaping area, site type, contract, and the growing season months | The growing season months are recorded once and everything below flexes with them. A site in a long season and one in a short season cannot share a frequency table. |
| Zones on this site | Ten zones, each with area, standard expected, visit frequency and owner | The owner column matters where some zones are the tenant's and some the landlord's. Unowned zones are the ones that look neglected for years. |
| Standard per zone | Presentation at the entrance, containment at the perimeter | The decision that saves the most money. Spreading one specification evenly across a site spends the most where nobody looks and the least where everybody does. |
| Grass and lawns | Ten tasks from mowing height through aeration to overseeding | Mowing height is specified rather than assumed. Cutting too short in a dry spell is the commonest way a contractor damages a lawn while apparently doing the job. |
| Beds, shrubs and hedges | Eight tasks including mulch depth and recorded plant losses | Plant losses recorded and replacement agreed is the line that prevents a slow decline nobody formally notices until a bed is half empty. |
| Irrigation and water | Eight tasks from startup and pressure test to winterizing | Every head checked for coverage, damage and blockage, and checked during operation. A blocked head looks identical to a working one when the system is off. |
| Backflow prevention | Tested and certified as part of the irrigation section | A compliance item sitting inside what looks like a gardening list, which is exactly why it gets missed on a grounds contract. |
| Autumn and winter | Ten structural tasks including drainage, hard pruning and the gritting plan | The dormant season is when the work that cannot be done around growth happens, and it is the half a twelve-equal-months contract quietly drops. |
| Tree safety inspections | Tree or group, location, last survey, next due, days, condition and action | Days to next counts down on its own. Trees near buildings, paths, car parks and boundaries carry a duty of care that the rest of this document does not. |
| Chemical application record | Date, product, registration number, target, area, amount and operator license | Every application including fertilizer. This is the evidence you will be asked for after a complaint about an adjacent property or a watercourse. |
| Standards audit by zone | Eight zones scored one to five against a weight | Weighted because the entrance and the perimeter are not equally important, and an unweighted average will tell you a site is fine while its approach looks neglected. |
| Result | Audit score, visit compliance, tree surveys overdue and cost per unit of area | Visit compliance by season is the number a client should ask for. Visits delivered in the dormant season instead of the growing one is how a contract underperforms without missing a visit. |
The single structural decision here is refusing to price twelve equal months, and it is the one most grounds contracts get wrong. Landscape work does not distribute evenly through the year. In the growing season a site needs frequent short visits: mowing, edging, weeding, dead-heading and irrigation, all of it driven by growth that does not pause because a visit is scheduled fortnightly. In the dormant season it needs fewer, longer visits for the structural work that cannot be done around active growth: hard pruning, tree work, drainage, turf repair, planting and preparing for winter. A contract written as twelve equal monthly visits produces exactly the wrong distribution. It under-delivers in summer, when the site is busiest and most visible and growth is fastest, and it over-delivers in midwinter, when there is genuinely less to do. Both parties usually know this by July, and the conversation that follows is about whether the contractor is underperforming when the real problem is that the specification was written against a calendar rather than a season. The second thing worth copying is the tree survey countdown. Trees near buildings, paths, car parks and boundaries carry a duty of care that is entirely separate from how the grounds look, and after a limb comes down the question is when the tree was last inspected, by whom, and what the recommendation was. A date in a column with days counting down against it answers that. A general sense that a tree surgeon came a couple of years ago does not.
B. What it looks like filled in
One visit in the growing season, and the two liabilities that were being tracked alongside it.
| Line | Value |
|---|---|
| Site and visit | Northgate Park, 12 May 2027, growing season |
| Zones done, hours | 8 zones, 6.5 hours, audit 88 |
| Chemical applied | Selective herbicide, 4.0 L on 400 square meters |
| Recorded against | Product registration and operator license |
| Tree survey | Lime avenue, 6 trees, main drive |
| Next survey, condition | 518 days, Fair, crown lift over footpath |
An ordinary growing-season visit, and the two entries on the page that have nothing to do with how the site looks. Eight zones in six and a half hours with an audit score of eighty-eight is a normal, competent visit, and most grounds records would stop there. The chemical line is the first of the two that matter later. Four liters of a selective herbicide went onto four hundred square meters of front lawn, and the record carries the product registration number and the operator's license alongside the amount. None of that is interesting until somebody in an adjacent property complains, or a watercourse is involved, at which point it is the only thing that is interesting, and reconstructing it from memory is not an option. The tree line is the second. A lime avenue on the main drive is precisely the situation the duty of care is about: mature trees over a route people walk and park under every day. Five hundred and eighteen days to the next survey is comfortable, the condition is recorded as fair, and there is a specific recommendation to lift the crown over the footpath. If a limb comes down in two years, that row is what the conversation turns on, and it exists because the file counts down rather than waiting for somebody to wonder.
Word for the version that goes into a grounds tender, Excel for the one that counts tree surveys down and calculates visit compliance and cost per unit of area, and PDF for the copy that gets signed at the annual review. Free, and yours to rebrand.
How do you build a landscape maintenance schedule?
Record the growing season first, because every frequency in the document flexes with it. Six steps.
Record the growing season for this location
Not a generic table. A long-season site and a short-season site need different visit distributions, and this is the field everything else in the document answers to.
Divide the site into zones and set a standard for each
Ten zones from the main entrance to the bin store. The entrance gets a presentation standard; the perimeter gets containment. Pricing both the same wastes most of the budget.
Weight the visits toward the growing season
High frequency and short visits while things are growing, fewer and longer ones when they are not. Twelve equal months under-delivers in summer and over-delivers in midwinter.
Put the structural work in the dormant season
Hard pruning, tree work from the survey, drainage, turf repair and planting. This is work that cannot be done around active growth and is the first thing a flat contract drops.
Check irrigation while it is running
Every head for coverage, damage and blockage, with the controller programmed for the season and the rain sensor tested. A blocked head is invisible when the system is off.
Track tree surveys and record every application
Days to the next survey counting down per tree or group, and every chemical including fertilizer recorded with product, amount and operator license.
Growing season versus dormant season
The same site needs two completely different services depending on whether things are growing, and a contract that does not distinguish them delivers the wrong one at the wrong time.
| Aspect | Growing season | Dormant season |
|---|---|---|
| Visit pattern | Frequent and short | Infrequent and long |
| What drives it | Growth rate and rainfall | The work that needs no growth |
| Typical work | Mowing, edging, weeding, irrigation | Pruning, tree work, drainage, planting |
| What fails | Visits too far apart | Structural work never scheduled |
| Who notices | Everybody, immediately | Nobody, for a year |
| The contract risk | Under-delivery when it shows | Paid-for visits with little to do |
This is the annual program, not the record of a visit. When a crew attends and you need what was done that day, with hours, materials and a signature, that is a landscape work order, and the two documents work together: the program says what should happen across the year and the work order records each attendance against it. Keeping them separate matters because they answer to different people. A client reviewing a grounds contract wants visit compliance by season and cost per unit of area, which only the program can produce. A supervisor checking yesterday wants hours and tasks on one site, which only the work order has. Worth being explicit about one more thing: this is a commercial grounds document throughout. The zones are entrances, car park perimeters, hard landscaping and bin stores; the liabilities are tree surveys, backflow prevention and chemical records; and the audit measures a contract rather than a hobby. A domestic yard maintenance checklist covers none of that and does not need to.
When the template starts to feel limiting
The file is built for one site and one annual program, kept on paper. Four things start to hurt as soon as that is not the shape of the problem.
The survey countdown only runs when the file is open
Days to the next tree survey recalculates when somebody opens the workbook. A survey that lapsed four months ago waits to be noticed.
Irrigation faults are invisible between visits
Coverage is checked when somebody is standing there during operation. Between visits a blocked head or a leak runs unseen, which is where the money goes.
Visit compliance is counted by hand
Visits due against visits completed, split by season, means somebody totaling a log. Most contracts never do it, which is why under-delivery in summer survives.
Applications sit in a folder
The chemical record is evidence, and it is only as retrievable as the folder it is in on the day somebody asks for it.
What running this in Facilio looks like
The program does not change. What changes is that the dates carrying liability are watched rather than recalculated.
Work Order Intelligence
Seasonal visits raise themselves
The program's frequencies become scheduled work weighted to the growing season, so visit compliance is counted rather than reconstructed at a review.
Audit Report Intelligence
Applications become a retrievable record
Product, amount, area and operator license sit against the visit, which is the form the question takes when a neighbor or a regulator asks.
Asset Intelligence
Trees and irrigation are assets with histories
A tree group carries its survey dates and recommendations, and an irrigation controller carries its faults, so a recurring problem reads as one.
Ops Performance Intelligence
Survey dates are watched, not remembered
A tree survey approaching its due date surfaces before it lapses, which is the only version of that countdown that protects anybody.
Hallucination-free by design. Atom AI answers from the records in your tenant rather than generating plausible text, so an empty field reads as empty rather than filled in for you.
Frequently asked questions
What is a landscape maintenance checklist?
It is the annual grounds program for a commercial site, organized by growing and dormant season rather than by calendar month. This one carries ten zones, each with its own standard and visit frequency, and 36 seasonal tasks.
It also carries the parts that are liabilities rather than gardening: tree safety surveys with a countdown, backflow prevention testing, and a chemical application record.
Why organize grounds work by season rather than by month?
Because landscape work does not distribute evenly. Growing season needs frequent short visits driven by growth that does not pause for a schedule; dormant season needs fewer, longer visits for work that cannot be done around active growth.
Twelve equal monthly visits under-deliver in summer when the site is busiest and most visible, and over-deliver in midwinter. Both parties usually know it by July.
What should a commercial landscape maintenance checklist include?
Zones with a standard and frequency each, grass and lawn work including specified mowing height, beds and hedges with recorded plant losses, irrigation with coverage checked during operation, and the dormant season structural work.
Then the compliance items: tree safety surveys, backflow prevention testing, and a chemical application record with product, amount and operator license.
Why do tree surveys matter so much?
Because trees near buildings, paths, car parks and boundaries carry a duty of care that is entirely separate from how the grounds look. After a limb comes down, the question is when the tree was last inspected, by whom, and what was recommended.
A row with a next-due date counting down answers that. A general sense that a tree surgeon attended a couple of years ago does not.
How should irrigation be checked?
While the system is running. Every head for coverage, damage and blockage, plus the controller programmed for the season, the rain sensor tested, and leaks or pooling investigated.
A blocked head looks identical to a working one when the system is off, and faults that run unseen waste more money than the whole grounds contract.
Should the whole site be maintained to the same standard?
No, and doing so is the commonest way a grounds budget is wasted. The main entrance and visitor approach need a presentation standard; a car park perimeter needs containment.
Setting one specification evenly across every zone spends the most money where nobody looks and the least where everybody does.
Does this work as a yard or lawn maintenance checklist?
For a commercial site, yes, and the grass and lawn section covers mowing height and frequency, edging, fertilizing, weed control, aeration and overseeding across amenity and sports grass.
It is written for office parks, campuses and retail sites rather than for a private garden, so it carries zones, contracts, audits and liability records that a domestic list would have no use for.
Does this cover a single grounds visit?
No. This is the annual program. Recording one attendance with its hours, materials and signature is a landscape work order and belongs on its own document.
The two work together: the program says what should happen across the year, and the work order records each visit against it.
In one paragraph
A landscape maintenance checklist works when it is built on two seasons rather than twelve equal months. Weight the visits toward the growing season, when growth does not pause for a schedule, and put the structural work in the dormant season, when it can actually be done. Set a different standard for the entrance than for the perimeter. Track tree surveys as a duty of care with the days counting down, check irrigation coverage while the system is running, and record every chemical application including fertilizer.
Two of these lines are not about how the site looks
Record the growing season, zone the site, weight the visits to the season that needs them and keep the tree surveys and applications current. Once a survey countdown only runs when somebody opens the file, or irrigation faults run unseen between visits, the paper version has reached its limit.
