SPECIALIST FIELD GUIDE / 6 MIN READ
Plan recurring landscape maintenance around visits and capacity
A practical record for service frequency, visit economics, seasonal tasks and customer communication.

View the planning illustration
Original Booked Work Pro business guidance · October 20, 2026. Examples are fictional. Technical site decisions and actual agreements require the appropriate review.
Define the service before counting the visits
Recurring maintenance needs a service map: named areas, included tasks, exclusions, frequency and the season or review period. Do not let a customer’s phrase “look after the garden” imply unlimited pruning, replacements, cleanup or specialist work. Record the actual agreed tasks and the review process for additions. Keep routine mowing distinct when it has a different scope or estimator. A recurring arrangement can include several task frequencies, but the schedule must make clear which tasks happen at every visit and which are separate events. Use the lawn-care tools for mowing-specific visit assumptions and this guide for the broader maintenance business record.
Count the real visits in the planning period
Use the actual proposed service dates or a clearly labeled planning count. Twelve months do not each contain four weeks, and a seasonal agreement is not automatically fifty-two weekly visits. Record how you handle a shifted window, an unsuitable site condition or missed access under your real arrangement. Distinguish the planned service count from guaranteed attendance on a specific day. The seasonal planner uses monthly days and person-hours to test capacity; it does not create customer appointments or optimize routes. Keep production scheduling with the system and people responsible for that work.
Separate crew time from person-hours
For a representative visit, record elapsed task time, crew size, loading and the travel or other time assigned to that service. Two people spending one and a half hours on site use three person-hours. If you already enter person-hours in a job model, do not multiply them by crew size again. Review actual records over several comparable visits and identify exceptions instead of treating a single best day as the normal production rate. A service that looks quick on site may use much more paid time after setup, material handling and transport are included.
Model usable capacity honestly
The seasonal planner starts with crew members multiplied by paid days and paid hours per day. The usable field-time percentage reduces that total for time you have not separately made available for productive tasks. Use your own records to set it and avoid deducting the same allowance twice. Compare planned total person-hours with the resulting capacity. A negative spare-hours figure identifies a planning conflict, not permission to overload the crew. Review workload, staffing, service scope or timing before promising another recurring commitment. Weather and absence assumptions should reflect your own operation rather than a universal utilization target.
Keep season-specific work visible
A recurring visit can be ordinary most of the year and substantially different around an agreed seasonal task. List those events separately with their scope, expected time and price treatment. Do not quietly include a major cleanup, replacement planting or irrigation work in a normal maintenance visit because it happens at the same property. Route technical suitability and timing questions to the qualified reviewer for the actual site and plants. The business calendar should record the decision and responsible person, not prescribe horticultural treatment. Review the event before it reaches the crew as an assumed standing instruction.
Distinguish cash timing from job profitability
A busy month can still have pressure on cash if payroll and suppliers are paid before customers pay. In the planner, enter expected actual receipts in the month received and cash outflows in the month paid. Include equipment cash expenses once in their own budget. Opening cash should reconcile with your records. A closing balance below your chosen buffer is a signal to review timing or commitments. A positive year-end balance cannot prove that every week is affordable; the monthly model can miss an intra-month shortage. It is also not a tax statement or a profit-and-loss calculation.
Communicate changed visits with one useful next step
When a planned visit changes, explain the reason you can substantiate, the next action and when the customer will receive an update. Do not promise an unconfirmed replacement window. Keep the actual service and billing treatment consistent with the agreement. If access repeatedly fails, review the arrangement with the customer rather than silently shortening every visit. Record recurring issues consistently so they become visible in the next service review. BWP can help organize inquiries and estimate appointments; production-route decisions and maintenance delivery remain with your team. Keep that boundary clear when discussing the software with a customer.
Review the service as a repeatable business decision
Compare estimated and actual visit time, assigned costs, extra requests and payment timing. Identify whether a recurring property fits the operation at its current scope and price. A change in area, access or task frequency may require a revised scope rather than a general price increase with no explanation. Record the current version, customer discussion and next review date through your normal process. Use the seasonal model to test capacity and cash after proposed changes. Save separate working copies for alternatives so the comparison remains inspectable. A better recurring service is one the customer understands and the business can consistently deliver.
Build a monthly milestone calendar
Alongside person-hours and cash, give each month one or two business checkpoints with a named owner. These might include a customer scope review, equipment service booking, supplier availability check or a review of actual visit times. Use actual operational needs, not a universal horticultural calendar. The planner has a milestone column precisely so a number can lead to an action. “Review recurring scope with customer / owner” is more useful than an unassigned note saying “busy season.” If a milestone depends on another person or provider, record the next contact rather than treating the date as confirmed. Review the calendar when work shifts between months. A moved project can change the equipment window and cash timing as well as the apparent workload.
Compare a lower-collections scenario
Save a copy of the base plan before changing assumptions. In the comparison file, move a realistic portion of expected receipts to the following month while keeping payroll and supplier payments in the months you expect to pay them. Recalculate the lowest modeled cash and the number of months below your chosen buffer. Do not change booked revenue and call that a collections test: this planner deals with cash timing. If borrowing is part of an actual reviewed plan, enter proceeds and repayments in the appropriate months without presenting them as operating profit. Include tax payments and owner cash withdrawals in the outflow assumptions where applicable to your records. Review the result with the person responsible for the business finances before committing to spending. The model cannot identify every weekly shortage.
Set a practical service-review threshold
Choose in advance what would trigger a review of a recurring property: repeated extra work, sustained actual visit time above the estimate, repeated access failure or a material change in the maintained area. Use evidence from comparable visits and separate unusual events. A review does not automatically mean a price increase; the appropriate response may be a clearer scope, different frequency, an access arrangement or declining an unsuitable addition. Prepare the customer discussion around the observed work and available choices. Update the current service record through the real approval process and tell the crew which version applies. Then test the changed workload in the capacity model. A recurring commitment should be evaluated as part of the whole operation rather than accepted solely because one individual visit appears affordable.
Take this checklist to the next job.
- Named areas, tasks, frequency and exclusions agreed
- Actual planned visit count recorded
- Elapsed time and person-hours kept distinct
- Seasonal events priced and scheduled separately
- Monthly planned work checked against usable capacity
- Cash receipts and outflows entered when expected
- Changed-visit process and next review recorded
CSV opens in spreadsheet software. Fill the blank project-record column and save your own copy. Your entries are not uploaded.
Turn the guidance into a working record.
Use your own scope and reviewed values. Keep the customer-facing estimate separate from internal cost and capacity assumptions.
Open the matching FREE tool →