Task Criticality vs Risk-Based Maintenance vs Inspection Strategy: Which Decision Should Govern Overdue Work?

A maintenance planner opens the backlog and sees three overdue jobs. One is older by six weeks. Another protects a pump that keeps a containment system available. The third concerns a degraded guard whose condition is changing faster than the work-order age suggests. If the oldest item automatically wins, the queue has become the decision maker.

Task criticality, risk-based maintenance, and inspection strategy answer different questions. The first tells leaders what matters if a function fails. The second helps them decide how much attention the exposure deserves now. The third tells them what evidence can support continued operation. Confusing the three creates a backlog that looks orderly while high-consequence exposure remains unresolved.

On a Headline Podcast conversation, Michael Emery and Cam Stevens connected meaningful safety measures to maintenance histories and better work by design rather than to month-end interaction counts. That principle matters here because an overdue work order is not only a maintenance statistic. It is a signal that a risk decision may be aging without a fresh review.

Andreza Araujo makes a related point in A Ilusão da Conformidade, translated as The Illusion of Compliance. A recorded process does not prove that the operational control is working. For overdue work, the practical question is not whether the order exists, but whether the organization can show why the exposure remains controlled while the order waits.

What should leaders compare before choosing a maintenance priority?

The comparison should begin with five dimensions. First, identify the function that may be lost. Second, define the credible consequence if it is lost. Third, examine the likelihood of failure and the conditions that can accelerate degradation. Fourth, test the interim controls that are supposed to protect people while the work is deferred. Fifth, record the uncertainty, because incomplete evidence is itself a reason to shorten the review interval.

This is different from ranking work orders by age, cost, or the visibility of the requesting department. Those factors may affect scheduling, yet they cannot replace an exposure decision. James Reason's work on latent failures is useful here because the visible defect is often the final sign of earlier decisions about design, inspection, staffing, procurement, and supervision.

Leaders can also use the risk register aging review to test whether assumptions behind the priority are still current. If the risk picture has changed, the maintenance priority should change with it.

When does task criticality provide the right first screen?

Task criticality is the best first screen when a large backlog needs a fast, consistent triage. It asks which equipment, barrier, or work function would matter most if it failed. A criticality screen can separate a cosmetic defect from a degraded emergency isolation function without requiring a full risk study for every line item.

The strength of this method is speed and comparability. A planner can group work by consequence class, affected population, safety function, environmental release potential, production dependency, and legal or standard-based obligation. That creates a common language for the maintenance and operations teams, which is especially valuable when different departments use different coding habits.

Its weakness is that criticality can become a permanent label. An asset marked critical may receive attention forever, even when its condition is stable and the available controls are strong. Another asset marked routine may become urgent after a failed inspection, a process change, or a change in operating conditions.

Use task criticality to answer, “Which failures deserve the strongest initial attention?” Do not use it alone to answer, “Can this work wait another month?” That second question requires current evidence.

When should risk-based maintenance govern the priority?

Risk-based maintenance should govern when leaders need to choose among competing tasks and the consequence is only one part of the decision. The priority should reflect the credible failure mode, the chance of failure in the current operating context, the people or environment exposed, the performance of existing barriers, and the quality of available evidence.

This approach prevents a common distortion. A low-frequency failure can still deserve immediate action when the consequence is severe and the interim control is weak. Conversely, an old work order may be safely resequenced when the failure mode is well understood, degradation is stable, and a verified temporary control prevents exposure.

Risk-based maintenance also makes uncertainty visible. If the team cannot establish whether a guard, interlock, relief device, or detection function is still reliable, the uncertainty should increase the priority rather than disappear inside a generic “monitor” note. A signed risk decision that does not name the missing evidence is only a record of discomfort.

The risk acceptance tests provide a useful companion because they force the approver to distinguish a temporary, bounded decision from an indefinite transfer of exposure.

When should inspection strategy govern the decision?

Inspection strategy should govern when the central issue is condition. Leaders may know that an asset is important, yet still lack evidence about its current state. In that situation, the immediate decision may not be “repair or defer.” It may be “what inspection can reduce the uncertainty before the next operating window?”

A useful inspection strategy names the degradation mechanism, the measurement method, the competence required, the access conditions, the acceptance criteria, and the consequence of a missed indication. It also explains what happens when the inspection cannot be completed as planned. An inspection that produces a checkbox without reliable evidence does not lower risk.

Inspection strategy is especially important for equipment whose condition changes with vibration, corrosion, fatigue, temperature, contamination, loading, or repeated intervention. The interval should follow the mechanism and the evidence, not a convenient calendar date.

Leaders should connect inspection findings to the conditions for credible safety assurance. If an inspection result cannot be traced to a decision, an owner, and a follow-up date, the organization has collected information without converting it into control.

How do the three methods differ in practice?

The methods work best as a sequence rather than as rival departments. Criticality narrows the queue. Risk-based maintenance sets the decision priority. Inspection strategy tests the condition that supports the decision. When the three disagree, the disagreement deserves escalation because it usually reveals a missing assumption.

What should a maintenance backlog review look for?

A weekly backlog review should not ask only how many orders closed. It should ask which safety functions are overdue, how long each decision has remained open, whether interim controls are verified in the field, and whether the operating context has changed since the original due date.

The review should also examine work that was repeatedly rescheduled. Repetition may indicate a capacity problem, but it may also show that the organization has accepted the exposure without naming it. The maintenance backlog case is a useful internal reference for turning overdue work into explicit risk decisions rather than hiding it inside completion percentages.

For each high-consequence item, the meeting should leave with one clear outcome. The work is completed by a named date, the temporary control is strengthened and verified, the inspection is performed to answer a defined question, or the risk is escalated to the level with authority to change resources and operating conditions.

Which method should govern overdue work in different contexts?

Task criticality should govern the first pass in a large, immature backlog where the organization lacks a consistent way to distinguish safety functions from routine tasks. It creates a shared screen, but the labels must have review dates so that criticality does not become administrative wallpaper.

Risk-based maintenance should govern a constrained shutdown, a production conflict, or a situation where several important tasks compete for the same people and time. It makes the operational compromise explicit and gives the accountable manager a basis for explaining why one exposure moves first.

Inspection strategy should govern when the condition of the asset is the main unknown, when a defect is progressing, or when continued operation depends on proving that a barrier still performs its intended function. In that context, delaying the inspection can be more dangerous than delaying the repair because the organization is operating without knowing what has changed.

The control-owner review before a critical maintenance window shows how to connect the technical decision to the person who can change the work plan. That connection is what prevents a maintenance priority from becoming nobody's responsibility.

What evidence makes a deferral defensible?

A deferral is defensible only when the organization can state what is being deferred, why the exposure is bounded, who owns the decision, which temporary control is active, how that control is verified, and when the decision expires. The record should also state the condition that ends the deferral, such as a failed inspection, a change in loading, a change in staffing, or a deterioration observed in the field.

Do not treat a risk score as evidence by itself. Scores summarize an argument, but they do not prove that the barrier works. The strongest record links the score to a physical condition, an operating assumption, a verification result, and a scheduled action.

That discipline reflects Andreza Araujo's distinction between compliance that is recorded and safety that is operated. A signed form can show that someone approved the delay. It cannot show that the exposure stayed within the accepted boundary unless the organization verifies the condition that made the approval reasonable.

What decision should leaders make next?

Start with task criticality if the queue is unstructured. Move to risk-based maintenance when competing exposures need a priority decision. Use inspection strategy when condition evidence is the uncertainty that keeps the decision open. The methods are complementary, yet they should not be collapsed into one score that hides the reasoning.

The next backlog review should select one overdue safety-related task and trace its full decision chain. Identify the failed function, test the current risk, verify the interim control, and confirm the owner and expiry date. If the chain cannot be reconstructed, the work is not merely late. The decision system is incomplete.

For more Headline conversations on practical safety decisions, visit Headline Podcast. Andreza's book Safety Culture: From Theory to Practice offers a broader route from declared systems to working practices, while the comparison above gives the maintenance team a concrete decision to make this week.