The Competencies
Behind the Brief

Most crews brief. Fewer crews brief well. And very few crews, if asked to explain why a particular briefing was effective, could articulate the answer with any precision. They might say it felt thorough, or that the captain was clear, or that everything important got covered. What they would rarely say — because the language doesn't come naturally — is that the briefing worked because the Core Competency framework was visibly operating throughout it.

It was, though. It always is. The question is whether that operation was deliberate and skilled, or incidental and inconsistent.

The nine ICAO/EASA Core Competencies are not a post-flight evaluation tool. They are a description of what effective professional pilots actually do — and they are doing it continuously, from the moment the crew first sits down together to the moment the aircraft is safely chocked. The pre-flight brief is the opening act. It is where the competency framework either establishes itself or fails to, and where the character of the entire operation is set.

Workload Management — Structuring What Comes Next

Before anything else, the brief is an exercise in workload management. Not the workload of the brief itself — though that is real — but the workload of everything that follows it. A well-constructed briefing anticipates demand, sequences tasks, assigns responsibilities, and builds a shared mental model of the operation ahead. Done properly, it compresses the cognitive load of the flight by resolving complexity in advance, at a time when the crew has the capacity to think clearly.

The observable behaviours under Workload Management make this explicit. Manages own and crew workload effectively is not just about managing tasks in real time — it is about anticipating them. Plans and prepares appropriately for the expected and unexpected is, in large part, a description of what a good brief accomplishes. The brief is where the unexpected is given a name, a plan, and a decision trigger before it has happened.

Crews that brief poorly — that race through performance figures without discussion, that skip the contingency plan because the weather looks fine, that never explicitly assign monitoring responsibilities — are not just producing a thin briefing. They are carrying unnecessary cognitive load into the flight that a proper brief would have discharged. The cost of that shortfall is paid in the cruise, in the approach, and sometimes in the event itself.

Situational Awareness — Building the Picture Before Departure

Situational awareness has three levels: perceiving the elements in the environment, comprehending what they mean, and projecting what they will mean in the future. The brief should be doing all three, for both crew members, simultaneously.

The WANT phase of a well-structured brief — weather, aircraft state, threats — is a systematic effort to build Level 1 SA before the aircraft moves. The discussion that follows is where Level 2 SA is established: what does this weather mean for the approach? What does that MEL item mean for our fuel plan? What does the forecast wind at destination mean for the alternate selection? And the contingency discussion — what will we do if the destination goes below minima — is Level 3 SA: projection of a future state and pre-planning the response.

• Monitors and assesses the state of the aircraft, operational environment and crew
• Identifies and assesses threats, errors and undesired aircraft states
• Anticipates likely threats and events — plans and mitigates appropriately
• Aware of aircraft trajectory, terrain and the operational environment

Each of these behaviours has a pre-flight expression. The brief is the moment when the crew formally constructs the situational picture that will sustain them through the operation. A brief that is rushed, incomplete, or not genuinely shared between crew members does not just produce a thin briefing — it produces degraded SA at the point of departure, before the flight has even begun.

Communication — The Open Cockpit Begins Here

An effective briefing is, among other things, a communication event. But the most important thing it communicates is not the weather or the performance figures. It is the crew's disposition towards each other: that information will flow freely, that both voices carry equal weight when it matters, and that neither crew member is operating in isolation.

The Communication competency describes the condition that the brief must establish and sustain. Conveys messages clearly, accurately and in a timely manner. Listens actively and demonstrates understanding. Asks and responds to questions appropriately. These behaviours are not just operational communication standards — they are descriptions of the psychological contract between two professional crew members that an effective brief makes explicit.

The brief is the crew's first opportunity to calibrate their communication style with each other. Is this captain comfortable with questions? Does this first officer volunteer information or wait to be asked? The answers to those questions are established early — often in the brief — and they set the tone for the entire operation. A brief that models open, bidirectional communication signals clearly that the cockpit is a safe environment for information exchange. A brief that doesn't sends a different signal — one that is much harder to correct once airborne.

Leadership & Teamwork — The Environment That Makes the Brief Work

A brief does not happen in a vacuum. It happens in a crew dynamic, and the quality of the brief is partly a function of that dynamic. The captain who creates the conditions for a genuine crew briefing — who invites contribution, who makes it safe for the first officer to raise a concern, who positions the brief as a joint construction rather than a captain's monologue — is demonstrating Leadership and Teamwork competency whether they use that language or not.

The behaviour creates and maintains a safe and open atmosphere is particularly significant here. Psychologically safe crew environments produce better briefings: first officers contribute observations, raise concerns, and surface threats that a more inhibited environment would leave unspoken. The captain's role in the brief is not just to deliver information accurately — it is to create the conditions under which both crew members can contribute what they know.

• Creates and maintains conditions for open exchange of information
• Demonstrates empathy and respect in crew interactions
• Accepts and acknowledges the contribution of others
• Assumes the appropriate role within the crew structure

This applies to the first officer as much as the captain. The experienced first officer who arrives at the brief having already reviewed the weather, who raises the MEL item before it's asked for, who offers a view on the threat picture — that is also a Leadership and Teamwork behaviour. The brief is a joint product, and both crew members share responsibility for its quality.

Application of Knowledge — The Foundation Everything Else Sits On

A briefing can only be as good as the knowledge that informs it. Threat identification is hollow if the crew cannot recognise what constitutes a genuine threat. Contingency planning is limited if the crew's understanding of the regulation, the aircraft system, or the aerodrome environment is shallow. The Performance Cross-Check only works if the crew understands what the numbers mean and what happens if they are wrong.

Application of Knowledge — specifically the behaviours around demonstrating knowledge of relevant procedures, regulations and aircraft systems and applying knowledge effectively in normal and non-normal situations — underpins the entire brief. It is the substrate on which every other competency operates during the briefing. Without it, the brief becomes a recitation without understanding: the right words spoken without the comprehension that gives them operational value.

Threat Identification — The Brief's Core Operational Purpose

If the brief has one non-negotiable purpose, it is this: to identify the threats that the operation will face and to establish a plan for each of them before they become active. Everything else the brief does — building SA, aligning workload, confirming knowledge, opening the cockpit — is in service of this central function.

Threats are not hypothetical during the brief. They are real, identified, named, and given a response. The weather threat has a decision trigger: if destination goes below X, we divert to Y, and we have the fuel to do so. The aircraft threat has a response: the deferred item affects this system, which means we will manage the operation this way. The environmental threat — the terrain, the airspace, the unfamiliar aerodrome — is acknowledged and given an action.

The Situational Awareness behaviour anticipates likely threats and events — plans and mitigates appropriately is the competency framework's description of exactly this process. Threat identification in the brief is Level 3 SA: projection, anticipation, and pre-planned response. It is the highest and most operationally valuable form of situational awareness, and it requires the brief to be genuinely engaged rather than merely completed.

What effective threat identification looks like

In practice, effective threat identification in the brief has three stages. First, the crew identifies the threats that are present — weather, aircraft state, environmental factors, crew factors. Second, they assess each threat: how likely, how consequential, how manageable? Third, they establish a response: what is the trigger, what is the action, who is responsible?

The difference between a crew that does this well and a crew that doesn't is not intelligence or experience alone. It is the habit of structured thinking that the Core Competency framework, when genuinely applied, produces. The brief is where that habit is most visible — and most consequential.

The Brief as a Competency System

The point of this article is not that the brief is important — most professional pilots already believe that. The point is that the brief is important for specific, articulable reasons that map directly onto the observable behaviours the competency framework describes. When you understand which competency is doing which work during the brief, two things happen.

First, you can diagnose a brief that isn't working. If the threat picture was thin, that is an SA behaviour gap. If the first officer didn't contribute, that is a Leadership and Teamwork environment problem. If the contingency plan was vague, that is a Workload Management failure. The framework gives you the precision to identify where the degradation occurred and to address it specifically — not just to note that the briefing felt flat.

Second, you can develop deliberately. The crew member who understands that their brief communication style reflects a specific observable behaviour can work on that behaviour with intention. They are not trying to be "better at briefing" in some vague sense — they are developing a specific, measurable competency against a defined standard. That is a fundamentally different kind of professional development, and it is a more effective one.

The brief is not the beginning of the flight. It is the beginning of the crew. And the crew begins with the competency framework — whether the crew knows it or not.