Inspection scheduling
What is inspection scheduling: inspection scheduling explained
Inspection scheduling is the work of assigning every due inspection to a date, a competent inspector and a location, so that each asset is examined before its interval expires. Demand is fixed by the intervals and by regulation. Scheduling does not change how much work exists, only whether it gets done in time.
Planners also call it inspection planning, or examination planning where statutory duties dominate. Whatever the label, it is a matching problem: a demand set that somebody else decided, against a supply of inspector hours that moves every week with leave, sickness, travel and reactive work.
What does inspection scheduling actually involve?
Four things have to line up before an inspection can be booked at all, and a schedule that ignores any one of them produces bookings that quietly fail on the day.
- A due date per asset. Derived from the last completed inspection plus the inspection interval, not from the calendar quarter it happens to land in.
- A competent person. Competence is asset specific and legally loaded. A scheduler treating inspectors as interchangeable will book work that nobody on site is qualified to sign off.
- Access. The asset has to be available, isolated where required, and physically reachable. Equipment out on hire or running a shift pattern is the usual reason a booked inspection does not happen.
- Somewhere for the record to land. The report has to end up against the right entry in the asset register, not on an inspector's phone. An inspection that cannot be found later did not happen, as far as an auditor is concerned.
How do you calculate the inspector days you need?
One formula does most of the work here:
Productive inspector days required = (inspections due in the period x average hours per inspection, including travel and write up) / productive hours per inspector day.
The denominator is where schedules die. A working day is not a productive day. Once leave, training, site travel, reactive callouts and administration come out, most inspection teams sit near 60 percent productive time. Planning on headcount multiplied by working days overstates capacity by roughly a third before anything has gone wrong.
Inspection scheduling explained: a short staffed quarter
Take an estate of 480 inspectable assets on a six month interval. That is 960 inspections a year and 240 in any given quarter. At half a day each including travel and write up, the quarter needs 120 productive inspector days.
The team is three inspectors. Sixty working days each is 180 days gross, and at 60 percent productive time that is 108 days available. The plan was already 12 days short at full strength, a ceiling of about 90 percent before anyone called in sick. When one inspector was off for six weeks, roughly 24 productive days went with them. The remaining 84 days produced 168 inspections: 70 percent inspection coverage, and 72 items dropped into the inspection backlog.
Nothing unusual happened that quarter. One person was ill. The schedule was built on a capacity number that was never true, and the illness only revealed it.
Scheduling on the due date versus scheduling with float
A six monthly statutory examination booked for the day it falls due has no room in it. One access refusal, one breakdown, one inspector off, and the asset is in service past its due date. That is a legal position rather than a planning inconvenience.
Experienced planners book statutory items at around 80 to 85 percent of the interval. On a six month cycle that means month five, leaving four weeks of float to absorb a slip. It costs a little interval compression each year. It buys the difference between an inspection that ran late and an asset that ran overdue.
Seasonality is the other thing worth fixing early. If intervals were all set at commissioning, due dates cluster on the anniversary of installation and the schedule inherits a peak nobody chose. Deliberately staggering the first cycle across the year flattens it, and doing that once at the start is far easier than unpicking it three cycles in.
How it differs from scheduling ordinary work
Inspections and work orders get planned by the same people, often in the same system, and they behave differently. A work order exists because something needs doing, and moving it costs goodwill. An inspection exists because an interval says so, and moving it past the due date changes the compliance status of the asset.
The practical consequence: inspections go on the calendar first and reactive work fits around them. Most teams do the reverse, because reactive work arrives with somebody shouting about it, and an examination due in three weeks arrives with nothing.
It is also worth separating scheduling from routing. Scheduling optimisation is about squeezing travel and idle time out of a day's jobs, and it helps. What it cannot do is create capacity that was never there. If the arithmetic shows a 12 day gap, better routing recovers a slice of it. The rest has to come from changed intervals, extra resource, or a shortfall that somebody senior accepts in writing.
