There is a version of SOP compliance that treats it as a regulatory obligation — a set of requirements to be satisfied, documented, and signed off. That version misses almost everything that makes SOP compliance operationally important. Standard operating procedures are not principally about compliance. They are about the conditions they create: for communication, for workload distribution, for shared understanding, and above all, for the ability to detect that something has gone wrong before its consequences arrive.
A short sentence sits inside the Core Competency framework: follows SOPs unless safety dictates a deviation is necessary. It is easy to pass over. It contains, in compact form, two distinct and equally important ideas — the discipline of compliance, and the judgement required when compliance is not possible. Understanding both, and the relationship between them, is what this behaviour actually asks of a crew member.
What SOPs Actually Do
An SOP creates a shared expectation. When both crew members know what should happen at each phase of flight — what callouts will be made, what checks will be completed, what responses will follow what triggers — they are operating from the same picture. Neither person needs to explain, negotiate, or confirm the routine elements of the operation. The shared mental model is built into the procedure. The cognitive load of routine coordination is eliminated before it arises.
This is the Communication connection. SOPs are a communication infrastructure — a pre-agreed language for the operation that means both crew members can transmit and receive critical information without ambiguity. The callout that confirms a configuration change, the response that acknowledges a threat, the checklist item that closes a loop — each of these is a communication act whose meaning is pre-defined and mutually understood. Without the SOP, each of these exchanges requires active construction. With it, they are automatic.
The Workload Management connection is equally direct. An SOP distributes workload before the workload arrives. It defines who does what, when, and in what sequence — decisions that have already been made and do not need to be made again under pressure. The crew that is following a well-designed procedure is operating within a workload budget that has been established in advance. The crew improvising its way through the same situation is spending cognitive resource on decisions that should have been already settled.
SOPs create the conditions for every other competency to function. They are not the ceiling of professional performance — they are its floor.
The Early Warning System
There is a less obvious function of SOP compliance that may be its most important: it is the mechanism by which the crew detects that something has gone wrong before anything has visibly gone wrong.
When a procedure is being followed, each step creates an expectation of what should happen next. When what actually happens does not match that expectation — when the callout doesn't come, when the checklist item produces an unexpected response, when the confirmation that should have arrived hasn't — there is a signal. Something is not right. The crew does not know what yet. But they know that the expected sequence has been broken, and that knowledge arrives early, when there is still time to investigate and recover.
This is the Situational Awareness connection. The crew that is following the SOP is continuously generating a picture of what the correct state should be and comparing it against the actual state. Every step completed correctly narrows the uncertainty. Every step that produces an unexpected result is a flag — not an alarm, not a warning system activation, just the recognition that the expected and actual states have diverged. That recognition is only available to the crew that had an expectation to begin with. The crew that was not following a procedure had no expected state against which to measure the actual one.
Experienced pilots describe a feeling — a sense that something is not right that precedes any specific identification of what it is. That feeling is not mystical. It is the cognitive result of a discrepancy between expectation and observation. The expectation exists because a procedure was being followed. The observation was that the expected thing did not happen, or happened differently than expected.
The crew that does not follow the SOP does not have the expectation. They cannot have the feeling. They will discover the problem later — when it has had time to develop, when it has produced consequences, when the workload of managing it has arrived alongside everything else the flight is generating.
When the Safety Net Earns Its Value
In normal operations, SOP compliance feels routine — because it is. The checklist is completed. The callouts are made. The procedure follows its familiar sequence. None of this feels like safety. It feels like administration.
The value of that habit is not visible until the operation is no longer normal. Under distraction, under workload saturation, in a non-normal situation that has elevated the crew's cognitive load and narrowed their available capacity — this is when the SOP becomes the thing that holds the operation together. Not because the crew is thinking carefully about following it. Because they are not thinking about it at all. The habit runs automatically, freeing the available cognitive resource for the problem that actually requires it.
The crew that built the SOP habit in normal operations has a safety net available when they need it. The crew that treated normal operations as an opportunity to abbreviate, to skip the parts that feel unnecessary, to operate from memory rather than discipline — that crew has no net. At precisely the moment when the structure of the procedure would have caught what the conscious mind missed, there is nothing there.
The habit is built in the periods between structured training — on the line, sector by sector, in the routine operations that do not feel like development but are the only place where the behaviour can be consolidated to the point where it holds under pressure. This is the gap that High Performance Pilot is designed to fill. The sim teaches the procedure. The line is where the discipline that makes the procedure reliable is built.
The Deviation and What It Requires
The behaviour names an exception: unless safety dictates a deviation is necessary. This is not a loophole. It is a recognition that procedures are written for foreseeable situations, and that not every situation that arises in line operations was foreseeable when the procedure was written. Manufacturers and operators acknowledge this in their manuals — the caveat that covers the situation the procedure did not anticipate.
What the deviation requires is not the absence of the SOP — it is the full deployment of every competency that the SOP normally supports. If the situation allows time, the deviation is managed through Leadership and Teamwork, Communication, and Problem Solving and Decision Making: the crew identifies what the procedure cannot accommodate, agrees on the departure and its rationale, assesses the risk, and manages the deviation as a deliberate and shared decision. The SOP is not abandoned. It is adapted, consciously and collaboratively, with both crew members holding the same picture of what has changed and why.
If the situation does not allow time, if the deviation must happen faster than structured management permits, the crew is drawing on experience. On pattern recognition built through exposure to similar situations. On the internalised understanding of why the procedure exists and what it is protecting, which allows a departure from the procedure while still protecting the thing it was designed to protect.
The shortcut to that experience are the behaviours contained within the Core Competency Matrix. Not because the matrix replaces line experience, but because it provides a structured framework for understanding what each procedure protects, why each behaviour matters, and how the competencies connect, so that when a situation falls outside the SOP, the crew is not improvising from nothing. They are drawing on a developed understanding of the principles that the SOP embodies.
Training Events
High Performance Pilot structures your development of Follows SOPs Unless Safety Dictates a Deviation across three levels — Foundation, Proficient, and Mastery. The sim teaches the procedure. HPP builds the discipline that makes it reliable on the line. Free to start.
Start Free — highperformancepilot.com