ZeroDelay Academy · Follow-up and handoff worksheet
Landscaping weather rescheduling: triage a recurring backlog
When weather postpones recurring visits, the backlog lands on days that already have work. A bounded triage compares the person-hours needed with the person-hours actually free, decides which visits to recover first, and tells the remaining customers honestly when they can expect service.
By ZeroDelay.ai · An educational framework, not a customer case study
A question to start with
After a weather disruption, how many postponed visits can realistically be recovered on the next usable day, and how will you communicate the rest?
Step 1
List the postponed visits
Record each postponed visit with its usual duration in person-hours, any agreed service window and a priority note. Decisions about whether conditions are workable stay with your crew lead and normal safety practice; this worksheet does not decide that.
Step 2
Find genuinely free person-hours
Take the crew's usable person-hours for the next workable day and subtract the hours already committed to that day's scheduled visits. Only the remainder is available for recovery, without assuming overtime.
Step 3
Recover, then coordinate the rest
Fill the free hours with the highest-priority postponed visits. For the remaining visits, contact customers with a realistic new date rather than an open promise, and record what was agreed.
Records to gather first
- List of postponed visits and their usual person-hours.
- Next workable day's existing schedule and committed hours.
- Crew availability for that day.
- Customer agreements about service windows.
- Notes of rescheduling communications sent.
Copy or print this blank worksheet
Copy the table into your own document or use your browser's Print command, then fill it in there or on paper. There are no entry fields here, nothing is saved, and numbers you write do not transfer into the diagnostic.
| Visit / reference | Usual person-hours | Priority note | Recover on (date) | Customer contacted | New agreed date |
|---|---|---|---|---|---|
| Visit 1 | ______ | ______ | ______ | ______ | ______ |
| Visit 2 | ______ | ______ | ______ | ______ | ______ |
| Visit 3 | ______ | ______ | ______ | ______ | ______ |
| Visit 4 | ______ | ______ | ______ | ______ | ______ |
| Visit 5 | ______ | ______ | ______ | ______ | ______ |
| Visit 6 | ______ | ______ | ______ | ______ | ______ |
| Total | ______ | ______ | ______ | ______ | ______ |
Fictional worked example
All figures are made-up assumptions to show the arithmetic. They are not industry benchmarks, customer data, achieved outcomes or a forecast for your business.
Assumptions
- Fictional: 6 recurring visits postponed by weather, each usually taking 2 person-hours.
- The next usable day has 16 crew person-hours, of which 10 are already committed to scheduled visits.
- No overtime is planned.
Simple math
- Backlog: 6 visits × 2 person-hours = 12 person-hours.
- Free capacity: 16 − 10 = 6 person-hours.
- Visits recoverable: 6 ÷ 2 = 3 visits, not 6.
- Remaining: 3 visits (6 person-hours) need coordinated new dates.
What this suggests checking: Recover 3 and coordinate the other 3 with realistic dates. Promising all 6 would rely on overtime or displacing already scheduled customers.
Review the usable-hours ledger before promising recovery dates
The worked example above recovers 3 of 6 visits. A ledger makes the same decision auditable: start from crew person-hours, subtract work already committed and setup or travel once each, and only then fill recovery visits. Qualified staff decide whether conditions are safe; the ledger only counts hours.
Separate fictional scenario for teaching only. It does not change the worked example above and is not a benchmark, customer result or forecast.
| Ledger line | Person-hours | Note |
|---|---|---|
| Crew available (2 people × 8 clock-hours) | 16 | Team clock-hours are 8; person-hours are 16 |
| Already committed scheduled visits, including their setup and travel | −10 | Counted once here, not again below |
| Free for recovery | 6 | No overtime assumed |
| Recovered postponed visits (3 × 2) | −6 | Highest priority first |
| Remaining backlog (3 visits) | 6 | Owner: office coordinator; contact each customer |
Check the arithmetic
- 2 people × 8 clock-hours = 16 person-hours. 16 − 10 = 6 person-hours free for recovery.
- 6 free person-hours ÷ 2 person-hours per visit = 3 recoverable visits. The 2 hours include the recovery visit's travel and setup.
- If recovery visits need extra travel not already in their 2 hours, subtract it before filling the day, so fewer visits fit.
- Remaining backlog: 12 − 6 = 6 person-hours across 3 visits, each with a named owner for customer communication.
Investigate when
- Any ledger where setup or travel appears both in committed hours and in visit hours.
- Remaining visits without a contacted date or an owner.
- Recovery plans that only work if overtime or displaced customers are assumed.
Next actions
- The coordinator contacts each remaining customer with a specific new date and records the agreement.
- Workability on the day stays with the crew lead and normal safety practice, not with this ledger.
If recovery days keep adding drive time, review route time and contribution.
What this cannot tell you
- Not safety or weather guidance; workability decisions belong with qualified crew leads.
- Fictional figures; not landscaping benchmarks.
- Route economics are covered in the separate recurring route profitability guide.
Choose a next step from your worksheet
After recording the weather disruption, review drive time and paid person-hours rather than counting rescheduled visits as completed work. Review landscaping route time and contribution.
If this worksheet raises a wider business question, the diagnostic below uses the answers you provide about your business; it does not import this worksheet or calculate its results. View the fictional sample 90-Day Plan to see an illustrative complete paid report, not your free results or a promised outcome. Available market research varies.