Workload Management:
The Competency Nobody
Thinks They Need

When I was teaching MCC and APS courses, my job was to take pilots who had spent their initial training flying alone and help them become functional crew members. The Core Competency framework was the structure we used. And of all nine competencies, Workload Management was consistently the one that new crew members found hardest to recognise in themselves — not because they lacked the capacity to manage workload, but because they had spent their foundation training developing solo habits that looked like workload management but were something quite different.

Single-pilot operation rewards a particular kind of mental agility — the ability to absorb demand, context-switch rapidly, and keep everything in your own head. That is a genuine skill. But it is not crew workload management. Crew workload management is a shared, organised, continuously monitored distribution of task demand between two people — and it requires habits of communication, delegation, and mutual awareness that solo flying never builds.

What those courses made clear to me was that the same gap appears, in subtler form, in experienced crew members too. The habits that allowed a pilot to cope with high workload early in a commercial career do not automatically mature into the disciplined workload architecture the competency actually describes. The same patterns show up on line training: arriving at demanding phases of flight carrying work that could have been done earlier, reluctance to delegate, automation used to defer demand rather than manage it. Getting through something and managing it well are not the same thing.

What Workload Management Actually Means

The competency is not a measure of how much a crew can absorb. It is a measure of how deliberately they organise, distribute, and monitor task demand — and how much capacity they preserve in the process. That preserved capacity is what the framework calls spare capacity, and spare capacity is the whole point.

Spare capacity is not idleness. It is the margin that allows a crew to detect a developing threat, absorb an unexpected instruction, support each other when one is under pressure, or simply think clearly. A crew operating at full capacity has none of that. They are current — but they are brittle. One additional input and something gets dropped.

The behaviours within Workload Management describe a crew that plans task distribution before pressure arrives, schedules work into the right phases of flight, recognises when capacity is approaching its limit, delegates and accepts help without ego, manages time and interruptions with discipline, and uses automation as a deliberate tool. Together they describe a crew that is never entirely surprised by their own workload — because they have been managing it continuously, not reacting to it periodically.

The Planning Habit Most Crews Skip

The most common workload management failure I encounter on line training is not people losing control under pressure. It is people arriving at a demanding phase of flight carrying work they could have completed earlier. The approach brief that should have been done during the cruise. The weather reassessment deferred to the top of descent. The fuel check squeezed around a frequency change and the first STAR constraint.

None of this is carelessness. It is the absence of a planning habit — the deliberate practice of looking ahead at the shape of the flight and asking: what needs to happen, when does it need to happen, and what is the right phase of flight in which to do it? That question, asked routinely, restructures a sector from a sequence of reactions into a managed programme of work.

The Transition That Reveals Everything

Teaching MCC courses gave me a specific view of Workload Management that line flying alone does not provide. When a pilot transitions from single-crew to two-crew operation for the first time, every workload habit they have built is suddenly visible — because those habits either translate into crew behaviour or they collide with it.

The most instructive pattern was delegation. Pilots who had learned to manage high workload by internalising everything — holding every task, every system state, every contingency in their own heads — found genuine delegation uncomfortable at first. Passing a task to another crew member felt like losing control of it. The instinct was to retain everything, monitor everything, confirm everything personally.

That instinct produces a crew where one person is overloaded and the other is underutilised. It also produces a crew where the shared mental model is fragile, because it lives in one person's head rather than being built and maintained between both. Teaching crews to distribute work, verbalise their intentions, and trust the structure of their crew roles took time — but when it clicked, the spare capacity it created was immediately and obviously different from what they had managed before.

Automation: Tool or Displacement?

Modern flight deck automation is the most powerful workload management resource available to a crew — and one of the most easily misused. The issue is not whether crews use automation. They do, routinely and correctly. The issue is whether they use it deliberately, in service of a workload strategy, or reflexively, as a way of reducing immediate demand without considering the downstream consequences.

Automation engaged without a clear shared understanding of what it is doing — without both crew members maintaining a mental model of the modes selected and the flight path being managed — creates a different kind of workload problem. It defers demand rather than eliminating it, and tends to concentrate that demand at exactly the wrong moment: when an unexpected mode transition or a disconnect forces a crew that has been passively monitoring to suddenly become the primary workload managers, often with less situational awareness than they needed.

The crew that manages workload well uses automation to create spare capacity — not to fill that capacity with something else, and not as a substitute for understanding what the aircraft is doing. Selecting an appropriate level of automation for the phase of flight, and briefing that selection explicitly, is itself a Workload Management behaviour.

The Social Side of a Shared Workload

Workload Management is not an individual competency. On a two-crew flight deck the total task demand is shared, and how it is shared matters as much as how much there is. Crews that manage workload well have a continuous, largely implicit conversation about who is carrying what and whether the distribution still makes sense. Crews that manage it poorly tend to either silo — each pilot absorbed in their own tasks, unaware of the other's state — or to double up, both attending to the same thing while something else goes unmonitored.

Offering help when a colleague is approaching saturation is a Workload Management behaviour. Accepting help when you are saturating is equally so — and in some ways harder, because it requires an honest, real-time assessment of your own capacity. Professional pride can make that genuinely difficult. The crew member who says "I've got this" when they don't is not demonstrating competence. They are demonstrating a gap in it.

This is something line training surfaces clearly. A First Officer who will not ask for help, or a Captain who will not give a First Officer the space to carry their share of the work, both represent Workload Management failures — but they tend to feel, in the moment, like something else entirely: thoroughness, experience, professionalism. The framework is useful precisely because it names the behaviour rather than the intention behind it.

The Competency Under Pressure

Everything above is relatively manageable in a normal sector. The real test of Workload Management is what happens when something unplanned enters the flight. A non-normal procedure. A late runway change in deteriorating weather. A cabin event. Each adds task demand at a point the plan was not expecting — and how a crew responds reveals whether Workload Management is a genuine habit or something that only functions in the absence of pressure.

The structured response is well established: aviate, navigate, communicate. The triage hierarchy reasserts itself. Tasks are explicitly reprioritised. Help is requested if available. The immediate demand is contained before the situation is assessed and a revised plan is formed. This is not instinctive under genuine pressure — it is a trained discipline, only accessible when it has been practised enough that the workload itself cannot consume it.

Thirty years in two-crew commercial aviation has reinforced one thing consistently: the crews who manage well under pressure are not the ones who are best at handling high workload when it arrives. They are the ones who arrive at the demanding phase with the most margin — because they planned, distributed, and protected their capacity throughout the flight. Workload Management, at its best, is not visible. It is the quality of the space around everything else.