Troubleshooting field aid

Troubleshooting Readiness Gate Checklist

A structured working check for the conditions, controls and evidence needed before diagnostic intervention, during testing and at close-out or transfer.

How to use the gates

Review the gates in order with the person who controls the work and the people competent in the affected systems. Tick an item only when it is confirmed, or when its non-applicability has been assessed and recorded under the project’s requirements.

PassThe applicable checks are satisfied and the authorised reviewer agrees that the work may move to the next gate.

HoldA correctable readiness gap or uncertainty remains. Pause at that gate, resolve or formally control the gap, then review it again.

StopControl has been lost or continued work could increase risk. Cease the activity and place or retain the system in the agreed safe state.

EscalateThe decision, risk or technical issue exceeds the available authority or competence. Transfer it with the evidence preserved.

Investigation details

Before diagnostic intervention

Gate 0 Problem definition and intent

Objective: Confirm the reported condition, expected behaviour and purpose of the investigation.

Gate 0 readiness checks
Gate 0 decision

Hold if the symptom, expected behaviour or investigation purpose remains unclear.

Before diagnostic intervention

Gate 1 Tooling and information readiness

Objective: Ensure observations can be obtained safely and with suitable confidence.

Gate 1 readiness checks
Gate 1 decision

Hold if a required measurement cannot be made safely, reliably or by an authorised competent person.

Before diagnostic intervention

Gate 2 System limits and boundaries

Objective: Define the investigation boundary, operating envelope and recoverable safe state.

Gate 2 readiness checks
Gate 2 decision

Hold if the boundary, applicable limit or method of returning the system to a safe known state is uncertain.

Before diagnostic intervention

Gate 3 Dependencies and interactions

Objective: Check that an upstream, supporting or shared service is not being mistaken for equipment failure.

Gate 3 readiness checks
Gate 3 decision

Hold if a dependency or connected-system condition could invalidate the proposed test or its interpretation.

Before diagnostic intervention

Gate 4 Preconditions, permissives and interlocks

Objective: Establish whether the system has failed or is being correctly prevented from operating.

Gate 4 readiness checks
Gate 4 decision

Hold if the reason for an inhibit or protective action is not understood, or if the proposed action could mask it.

Before diagnostic intervention

Gate 5 Environmental and site conditions

Objective: Identify external conditions that could affect the equipment, the measurement or safe access.

Gate 5 readiness checks
Gate 5 decision

Hold if environmental influence is unresolved or conditions prevent safe, representative observation.

Before diagnostic intervention

Gate 6 Access and inspection validity

Objective: Confirm that access and observation quality are sufficient for defensible conclusions.

Gate 6 readiness checks
Gate 6 decision

Hold if access is unsafe, the observation is inconclusive or intrusive work is not properly controlled.

Before diagnostic intervention

Gate 7 Safety and risk control

Objective: Confirm that the investigation can proceed without uncontrolled exposure or defeated safeguards.

Gate 7 readiness checks
Gate 7 decision

Hold if authority, isolation, safeguards, emergency arrangements or risk controls are incomplete.

During the investigation

Gate 8 Structured troubleshooting method

Objective: Keep each test evidence-led, controlled, reversible where practicable and capable of reducing uncertainty.

Gate 8 readiness checks
Gate 8 decision

Hold and re-plan if method discipline is lost, the evidence becomes unreliable or risk changes.

Close-out or transfer

Gate 9 Documentation and handover

Objective: Make the evidence, reasoning, restoration state and remaining limitations traceable.

Gate 9 readiness checks
Gate 9 decision

Hold close-out or transfer if another competent person could not understand what was done and why the system state is acceptable.

Close-out or transfer

Gate 10 Stop, escalation and ownership

Objective: Decide whether to accept, transfer, escalate or stop without uncontrolled persistence.

Gate 10 readiness checks
Gate 10 decision

Do not allow the investigation to continue by default when ownership, authority or the safe interim state is unclear.

Stop and escalation criteria

Apply the project’s more conservative requirement whenever it sets a lower threshold. The examples below are prompts, not an exhaustive risk assessment.

Stop and make safe when

  • The safe state, isolation boundary or restoration route is unclear or no longer effective.
  • An unexpected condition, limit exceedance, loss of containment or protection concern appears.
  • The proposed test would defeat a safeguard or introduce an uncontrolled temporary condition.
  • Required authority, competence, tools, access, communication or emergency support is absent.
  • Personnel, equipment, environment or essential operations could be exposed to unacceptable risk.
  • Changing conditions, poor evidence quality, fatigue or time pressure make the next action unreliable.

Escalate or transfer when

  • The issue exceeds the team’s technical competence, work authority or acceptance authority.
  • A safety-critical, protective, regulated or high-consequence function may be involved.
  • Evidence conflicts, the fault repeats, or the pattern may affect other systems or assets.
  • Further work requires design review, specialist testing, configuration or setting changes, or manufacturer input.
  • The system cannot be returned to a known acceptable state within the approved plan.
  • Operating restrictions, deferral or continued service require a decision by a higher authority.
Final decision record