The distribution of service request types is one of the earliest leading indicators of a maintenance program deteriorating or an asset fleet aging past its reliable service life. When the proportion of planned maintenance requests is stable or growing, the operation is executing its preventive program and demand is predictable. When the proportion of emergency and unplanned repair requests begins increasing even while total request volume stays constant the operation is absorbing more reactive work, which is inherently less efficient, less predictable, and more disruptive to planned workloads than the preventive work it is displacing.

The risk in a shifting request type distribution is that it is gradual and invisible unless tracked. A team that handled 15% emergency requests in January and is handling 24% in April has experienced a significant shift in the character of its demand. That shift may indicate deferred PM work returning as failures, a specific asset class aging out of reliable service, or a change in how requests are being classified. Each explanation has a different response, but all of them require knowing that the shift has occurred and that knowledge comes from tracking the distribution over time rather than from looking at total request volume alone.

The two metrics identify risk from complementary directions. Service Type Request looks at demand what the operation is being asked to do and whether that composition is shifting toward types of work that are more expensive, less predictable, and harder to staff for than the planned work they are displacing. Technician Workload looks at capacity whether the people responsible for meeting that demand are carrying loads that are sustainable and distributed equitably across the team.

The risk scenario that both metrics together can surface is one that neither alone would catch: an operation where total work volume appears normal but where emergency request proportion is rising and two specific technicians are absorbing most of that reactive work because they are the ones with the relevant skills. Total request volume looks fine. Technician average workload looks acceptable. But the request type shift is heading toward a structural imbalance and the two technicians carrying the reactive load are approaching the point where their individual sustainability becomes the constraint on the operation's ability to respond. Both signals are visible in this dashboard. Neither is visible in a total volume count.

Service Type Request supports demand-side decisions. When emergency request proportion is rising, the immediate response is to investigate which assets or service areas are generating the increase. The longer-term response may be adjusting the PM schedule, adding resources for reactive response capacity, or beginning an asset replacement analysis for the equipment class driving the failures. None of those responses can be initiated without the data showing that the shift has occurred and which service types are driving it.

Technician Workload supports capacity-side decisions. When the workload distribution is uneven, the immediate response is reassignment redistributing open work orders from over-assigned technicians to those with available capacity. The longer-term response may involve cross-training, hiring, or schedule restructuring if the imbalance is structural rather than situational. Both the immediate and the longer-term response require knowing which technicians are over-assigned and by how much information the metric provides from real work order data rather than from a calendar review that reflects scheduled rather than actual load.