
Guides
Window cleaning scheduling delays: windows and the call
Window cleaning delays handled with arrival windows you can hold, built-in slack, a call sequence for late days and a stated fee for wasted visits.
- Agree a weekday and frequency for recurring work, and promise a service window rather than an exact arrival time.
- Plan the route by on-site hours, allow for overruns, and reserve daily and weekly slack.
- Find the reason for a delay, call the next customer with a revised window, and record the cause.
- Confirm entry arrangements, permissions, the work method, and any wasted-visit fee before booking.
- Set weather rules and a morning decision process in writing, and use qualified training and advice for each method.
- Review the scheduling measures each week and investigate recurring patterns.
- Check that equipment, the daily routine, and urgent requests fit the capacity already promised.
Make the arrival promise workable
Use a service window rather than an exact arrival time because jobs vary and a small shift can trigger complaints. For recurring work, agree a weekday and frequency, then repeat the pattern on a rolling cycle instead of fixing every visit to a calendar date.
Build recovery time into the route
Build the route around on-site hours rather than stop count, and reserve capacity for a job that runs long. The route should begin near the first stop and finish toward home, with the next day locked at the prior close.
Put the first stop near the route start because it is more likely to overrun, and aim the final stop toward home. Lock tomorrow's schedule at the prior close so later changes do not quietly crowd the route after dispatch or consume the time reserved for recovery.
Keep a flexible afternoon opening for overruns, callbacks, or same-day requests. If it stays unused, it can become an early finish rather than wasted capacity. Put later changes into that opening or into the next visit to the same zone once the day's schedule is set.
Packed vs slack schedule
Packed schedule
- Overrun effect
- All later jobs late
- Crew afternoon
- Apologizing
- Callback work
- Done at night, unpaid
Schedule with slack
- Overrun effect
- Absorbed by flexible slot
- Crew afternoon
- Cleaning
- Callback work
- Done in lighter day
Diagnose the slip and call ahead
Identify the reason for a delay before choosing a correction. Entry, travel, unexpected scope, cascading overruns, and weather each call for a different response, so treating every late finish as a crew-speed problem can leave the actual cause untouched.
Match the scheduling fix to the source. The table distinguishes access failure, travel gaps, scope surprises, a chain of overruns, and weather decisions, with a practical response for each. A repeated pattern of delays can point to a process problem rather than pace.
The five causes of delay
| Cause | What it looks like | Scheduling fix |
|---|---|---|
| Access failure | Locked gate, no key, wrong contact, nobody home | Written access arrangement per account, confirmed the day before |
| Travel | Long unpaid gaps between jobs | Zone days, and a stated service radius |
| Scope surprise | The job is bigger or dirtier than quoted | Survey before quoting, and a variation rule the crew can use |
| Overrun cascade | One late job makes four jobs late | Deliberate slack, and an early call to the next customer |
| Weather | Crew waiting for a decision | A written policy and a decision time each morning |
Five delay causes and fixes
Cause
- Access failure
- Written access arrangement
- Travel
- Zone days, service radius
- Scope surprise
- Survey, variation rule
- Overrun cascade
- Deliberate slack, early call
- Weather
- Written policy, decision time
Scheduling fix
- Access failure
- Travel
- Scope surprise
- Overrun cascade
- Weather
Two-minute delay call
- Call next customer as soon as you know
- Give a revised window, not an apology
- Offer the option to reschedule
- Record what caused the delay
Call the next customer as soon as a delay is predictable, not after the promised window has passed. Give a revised window and offer the choice to reschedule. Record what caused the change; customers are more likely to accept a shifted arrival when they hear in advance than when a visit passes without notice.
Remove entry uncertainty before dispatch
Settle access arrangements before the first appointment, since entry failure is a major source of wasted visits. Keep account-specific instructions in both the written agreement and the scheduling record, then send a short confirmation the day before recurring work.
Access details per account
- Who provides access
- Key or code arrangement
- On-site contact and backup
- Parking notes
- Gate and pet notes
- Cost of a wasted visit
Calculate a wasted-visit fee from crew hours lost multiplied by loaded labor cost per hour, plus unrecovered travel expense and other direct costs. Put the amount, trigger conditions, and exceptions under payment terms in the agreement before service, then apply the rule consistently.
At the survey, agree the method for each building and save it in the job record before work starts. Confirm who can authorize entry and record that approval before scheduling, so a crew already behind schedule does not have to choose a method on the spot.
Set the weather call and method in advance
Write the weather policy into the agreement. List conditions that stop work, name the decision-maker, set the morning decision time, and state how a missed visit will be rescheduled. A process agreed ahead of time keeps the crew from waiting at the site for an answer.
Freezing conditions matter most for pure-water systems, while high wind is a key hazard for work at height. Height work and access equipment carry serious risk, so use qualified training and technical advice for each method in use. A compressed schedule is no reason to take shortcuts.
For applicable general-industry work, OSHA's fall protection guidance includes 29 CFR 1910.27, Scaffolds and rope descent systems, and 29 CFR 1910.28, Duty to have fall protection and falling object protection. Record the agreed method for each building before work begins.
OSHA's cleaning industry hazard material discusses wider cleaning industry hazards. Recordkeeping for the weather decision and rescheduling route keeps the morning call from becoming a new dispute at the site. Name the responsible person in the agreement, and use the written process to manage risk rather than debate it after arrival.
Use weekly measures to find repeat causes
Review four measures each week: on-site hours compared with paid hours, wasted visits, jobs completed within their promised window, and callbacks. Together, they help show whether the schedule is being lost to travel, access, overload, or repeated corrections rather than guesswork.
- On-site hours compared with paid hours
- Wasted visits
- Jobs completed within the promised window
- Callbacks
A falling ratio of on-site hours to paid hours points to travel or slack that needs review. More wasted visits suggest access details have aged, while callbacks clustered on one day can indicate an overloaded route. Use service quality checks to interpret a callback pattern.
The IRS's Publication 583, Starting a Business and Keeping Records, explains recordkeeping for business income and expenses. Capture each measure in the job record when work happens; the same per-job record supports all four measures and avoids rebuilding the week's account from memory.
Match daily support to promised capacity
The crew's ability to finish within its promised window depends partly on the equipment and setup taken to each job. A badly loaded van loses minutes on every stop, so operations and workflow should support the schedule rather than rely on slack to conceal poor setup.
Book recurring visits far enough ahead for customers to plan, but use a weekday-and-frequency cycle to avoid the rearrangement burden of fixed dates. Reserve the flexible opening for urgent requests, price urgency honestly, and decline work if accepting it would make scheduled customers late. An existing customer made late costs more than a new one gained.







