The missing hour
Consider a fleet workshop that starts each morning with an apparently complete schedule. The vehicles are assigned, the technicians are present and the parts list has been checked. By noon, one diagnosis has changed, an urgent vehicle has arrived and a planned repair has revealed another fault. The schedule is now inaccurate, but nobody has stopped working. The missing capacity sits between tasks: a decision waiting for approval, a vehicle occupying a bay, a technician searching for a substitute part. This is an operating example, not a claim about a measured portfolio result.
A useful capacity discussion begins with those intervals. Counting available technicians tells us little if the constrained resource is diagnostic equipment, a supervisor's approval or the space required to keep an unfinished job open. The first task is to identify what actually limits completion. That answer can vary during the day. A plan built around one average productivity rate risks concealing the moments when a different constraint takes over. More urgency then produces more movement without necessarily producing another completed vehicle.
Promise less work in progress
For a fleet-service operation, the relevant promise is a credible return-to-service time. Accepting every job immediately may make the intake queue appear efficient while making that promise harder to keep. A vehicle that enters the workshop without the required part or decision consumes space and attention. A bounded intake rule would ask whether the next stage is ready before admitting another job. The operation can still prioritise a genuinely urgent case, but it should record which existing commitment moves and who has approved the change.
This suggests a different daily meeting. Start with the unfinished jobs that cannot advance and the decision needed for each one. Then review which new jobs can enter with a reasonable path to closure. Finish by naming the capacity deliberately kept available for uncertainty. That reserve should not be hidden as underperformance. It is an explicit operating choice with a cost and a purpose. If it is repeatedly exhausted, the review should examine the kinds of work arriving, not simply instruct the team to preserve more capacity next time.
Three clocks, three responsibilities
A job has at least three clocks worth separating. The first runs from request to acceptance. The second covers active work. The third runs from technical completion to release. They belong to different parts of the organisation and respond to different interventions. Faster intake will not resolve a final sign-off queue. Additional technicians will not correct an ambiguous permission rule. Combining all three into one average can be useful for a customer promise, but it is insufficient for deciding what to change inside the operation.
The review should therefore follow a small sample of jobs through their full path. For each pause, record the condition that prevented progress, the person able to resolve it and the next action. Avoid turning this into minute-by-minute surveillance. The objective is to find recurring dependencies, not to classify every human movement as productive or unproductive. A short, reliable description of a blocked state is more useful than an elaborate time record that staff reconstruct after the event. The record should help the next decision arrive sooner.
The next operating review
The review also needs a record of cancelled work. A cancelled appointment may release apparent capacity while leaving the original service need unresolved. Closure reasons should therefore remain visible beside completion counts.
For Relay Fleet Services, the proposed review question is whether intake, diagnosis, parts readiness and release can be discussed as one sequence. For Meridian Road Services, the equivalent question concerns the relationship between inspection, intervention planning, access and closure evidence. The operating details differ, so a common template must not imply identical targets. What can be shared is the discipline of naming the current constraint and distinguishing scheduled work from work that is actually ready to proceed. Any reported improvement needs a stable definition and a dated comparison.
A credible review would include examples of a commitment kept, a commitment revised and a job held back because its dependencies were incomplete. It would state what the team learned from each case and what changed in the following schedule. It would also retain unresolved problems. Capacity planning becomes valuable when it gives the organisation a way to absorb ordinary uncertainty without converting every exception into a crisis. The desired result is not a permanently full timetable. It is a service whose promises remain usable when the timetable changes.
Sources and data notes
- PTD Capital LLC — Relay Fleet Services — current operating file2026 · Primary project record for workshop reporting, repeat-service review and the paused service-zone proposal. The workshop scenario in this article is analytical, not a measured outcome.