Operational Planning and Monitoring
What the domain covers
Operational planning converts a contract or service requirement into a workable schedule of people, time, equipment, and materials. Candidates should understand scope (what is in and out of the service), workload estimation (task time × frequency × area), staffing calculations (productive hours versus paid hours, allowing for breaks, travel, training, and absence), and resource allocation (equipment, consumables, budget). Know the difference between a plan (intended sequence and targets) and monitoring (comparing actual against planned and acting on variance).
Key concepts include key performance indicators (KPIs) and service-level targets, rostering and shift coverage, contingency and business continuity planning (covering absence, equipment breakdown, peak demand), and change control when scope shifts. Understand why plans fail: unrealistic task times, no allowance for absence, unclear responsibilities, and no feedback loop. Monitoring tools include inspection schedules, time and attendance records, completion logs, and short interval control (checking progress during the shift, not only at the end).
Traps to watch for
Questions often tempt candidates to accept a plan that looks efficient but ignores breaks, travel, or absence - the correct answer builds in contingency. Another trap is treating monitoring as paperwork only; effective monitoring leads to corrective action. Watch for answers that respond to a missed KPI by simply adding pressure, rather than diagnosing the cause (understaffing, poor sequencing, equipment fault). Also beware of confusing frequency of a task with the time it takes.
Worked example / rule of thumb
A site needs 40 washroom cleans per day at 12 minutes each: 480 minutes, or 8 labour hours. With a 7.5-hour productive shift, that is roughly 1.1 staff - but add absence and contingency cover. Rule of thumb: plan the work, then plan the risk; always state the assumption behind a staffing figure.