Two hours can be enough. Four hours can be enough. The right answer depends on the facility. The variable that actually moves outcomes is whether the visit leaves any observation headroom past the reactive work, because that is the only space in which lead indicators of future conditions get noticed.
Why block length is the wrong question
Operators frequently ask: how long should the visit be? The question is a proxy for a different question: how much maintenance will get done? The proxy works at the extremes (a 30-minute visit is clearly too short; a 12-hour visit is clearly over-provisioned) but it fails in the middle, where most real decisions live.
The actual question is operational: does the block clear the active ticket queue and leave time for forward-looking observation, on this facility, at this cadence? Two hours produces a good outcome on a small, low-ticket property. Four hours can produce the same outcome on a larger property. The same four hours can be too short on a high-density, deferred- maintenance-heavy property. Block length follows the facility, not the other way around.
Lead indicators and lag indicators
Two categories of facility condition matter for maintenance programs. Each shows up at a different stage in the life of a problem.
Two condition categories
Lag indicators
Conditions that have already failed. The door that no longer latches, the faucet that is leaking, the bulb that is out. Lag indicators surface as tickets because someone on-site noticed something broken. Reactive maintenance is the work of resolving lag indicators.
Lead indicators
Early signs that point to a future condition. The hinge starting to sag before the door fails. The dripping connection before the leak. The bulb dimming before it burns out. The cracked caulk line before the sealant fails. Lead indicators are visible to someone walking the property with attention to spare, but invisible to someone working the ticket queue.
Both categories need to be addressed for the facility to stay in good condition over time. Reactive-only programs catch lag indicators and miss lead indicators by definition. Programs with observation headroom catch both.
If you are always doing something, you stop looking
The phenomenon is observable in any operating environment. When attention is fully committed to the active task, peripheral awareness drops. A technician working a ticket queue with no slack is working the queue. The wall behind the fixture, the corner of the ceiling, the seam in the parking surface: these do not get noticed because there is no attention left over to notice them.
The fix is not to work harder. The fix is to build the program so that observation capacity exists in every visit. That means sizing the block to include time past the reactive work, and spending that time deliberately on forward-looking observation rather than additional reactive work.
This is why two technicians can perform the same scope on the same property and produce materially different condition trajectories. The one with observation headroom catches lead indicators and addresses them when they cost minutes. The one without observation headroom catches the same conditions later, as lag indicators, when they cost much more.
The sweet spot
A right-sized maintenance program produces three outcomes inside every visit:
- ◆Active ticket burn-down. The known issues that surfaced between visits are addressed and closed out.
- ◆Lead-indicator observation. Areas not currently generating tickets are walked with attention. Early-stage wear, conditions trending toward failure, and quick fixes that prevent next month's ticket get noticed and addressed.
- ◆Documented record. Work completed and conditions observed are captured in a format ownership can review.
The third outcome is what makes the program legible over time. The first two are what keep the facility moving toward good condition rather than away from it. All three need to fit inside the block.
What changes the right size
Five facility-side inputs change the right answer for block sizing. There is no universal number.
- ◆Property size. Larger square footage requires more time to walk, period. A 2,000 SF medical suite and a 25,000 SF office park cannot share the same block size.
- ◆Operating function. Facilities with constrained operating windows (daycare, medical, school) compress the available work time, which affects both visit frequency and block length. Daycare maintenance happens before children arrive or after they leave; medical work happens around patient schedules.
- ◆Current condition. A property with significant deferred maintenance carries a larger active ticket queue than a property that has been maintained continuously. The first six months of a new engagement on a deferred property may require longer blocks until the backlog is brought current.
- ◆Cadence. Higher-frequency cadences (weekly, bi-weekly) can support shorter blocks because the ticket queue accumulates less between visits. Lower-frequency cadences (monthly, quarterly) require longer blocks to absorb the full between-visit accumulation.
- ◆Ticket volume. The actual rate at which the facility generates active maintenance items. A high-traffic retail property generates more tickets per square foot than a light-industrial property. Block size has to fit the rate.
How to tell whether the program is right-sized
Three signals tell an operator their maintenance program is under-covered for the facility.
- ◆The ticket queue grows between visits. Each visit clears only the most urgent items. The remaining items push into next month, and the next month generates more. The backlog compounds.
- ◆The same conditions resurface as tickets. An item that would have been a five-minute lead-indicator fix returns later as a lag-indicator ticket. Multiply across the property and the program is producing the work it is trying to prevent.
- ◆Untracked areas drift. Zones of the facility that do not generate active tickets (storage rooms, mechanical rooms, exterior perimeter, walls behind furniture) decline because they never receive attention. The drift becomes visible months or years later, when one of those zones produces a major condition.
If any two of the three are present, the program is under-covered for the facility. The corrective action is to right-size the block, not to push the technician to work faster inside the same block.
Right-sizing in practice
Proportional FM sizes Scheduled Recurring General Maintenance blocks to the facility, not to a default. The initial sizing looks at property size, operating function, current condition, cadence options, and ticket history. The early visits validate the sizing: if the ticket queue is clearing and lead-indicator work is fitting into the block, the size is right. If either is suffering, the block adjusts.
Over time, the right block size for a given facility often shrinks. A property that started with a heavy backlog moves into steady state once the deferred conditions are addressed, at which point the same observation headroom is available in less time. The reverse can also happen: properties that grow in tenant count, complexity, or condition load may need a larger block than they did at engagement start.
The program is calibrated by the result, not by the calendar.