The Trough Is the Resource.
The Peak Is the Test.

For professional flight crew, the planned workload peaks are not hard to identify. The departure, the arrival, the non-normal that arrives mid-cruise — the phases of flight that carry the highest demand are known, anticipated and prepared for. This is the function of effective planning and prioritisation: to map the peaks in advance, understand when and why they will arrive, and structure the operation to meet them with the resources they require.

But identifies and responds to workload peaks is not primarily about the planned ones. Identifying a peak that has been anticipated and briefed is not a demanding behaviour — it is the confirmation of something already known. The behaviour becomes genuinely demanding when the peak is unplanned: when it arrives unexpectedly, when it compounds on top of an already-demanding situation, and when the crew is already inside it before they have had the opportunity to identify it.

The Trough Is Not Idle Time

Before the unplanned peak, there is the trough. And the trough is the resource that determines how the peak is managed.

Low-workload periods are not gaps in the operation. They are the opportunity to prepare for what comes next — to brief contingencies, complete tasks that would consume capacity later, build the shared understanding that makes high-workload operation more reliable. A crew that uses the trough actively is a crew that arrives at the peak already partially resourced for it. Tasks are complete. The picture is current. Options have been considered. The peak lands on top of a crew with margin.

A crew that treats the trough as genuinely idle — that defers preparatory tasks, that allows the shared picture to drift, that does not use quiet periods to get ahead — arrives at the peak having spent no capacity on preparation. Whatever the peak demands has to come entirely from what the crew can generate in the moment, under conditions that are exactly wrong for generating it.

The planned peak and the trough that precedes it are therefore a single workload management unit. Identifying the peak in the plan is only part of the behaviour. Using the trough to reduce its demand is the other part — and the one more directly under the crew's control.

The Unplanned Peak and the Narrowing Horizon

The unplanned peak is the harder problem. It does not announce itself. It arrives — the system failure, the weather that developed faster than forecast, the ATC instruction that adds complexity to an already demanding phase — and the crew is inside it before the identification has been made.

This is what makes unplanned peaks so hard to catch. The capacity to step back and assess — to recognise that the current demand has exceeded the available resource, to name it and respond to it — is exactly the capacity the peak is consuming. SA has narrowed. The horizon has shortened. The crew is absorbed in the immediate. The very awareness that would allow the recognition is the awareness that is being depleted.

This is where habitual discipline becomes operationally critical. A crew whose baseline behaviours are consistent — whose SOPs are precise, whose communication is clear and efficient, whose actions are not wasting resource — starts every unplanned peak from a lower baseline of consumed capacity. The behavioural discipline built in normal operations has already compressed the demand. The peak lands on top of a crew with margin. The same event landing on a crew whose baseline discipline is inconsistent lands on a crew that is already stretched — and what might have been a challenging period becomes a stress point, a reduction in safety margin, and in the worst case a failure point.

Responding: The Sequence That Matters

Identifying the peak is the first step. The response is everything that follows — and the sequence matters.

Prioritise. Not all tasks in a high-workload environment are equal. The most consequential require immediate attention. Others can be deferred. Identifying which is which — quickly, under conditions that are exactly wrong for deliberate assessment — is the first response action. The crew that can triage rapidly under pressure preserves the capacity that a more reactive response would consume.

Delegate. Workload peaks are the environment in which delegation has the most value. Tasks that would normally be performed by the captain or the pilot monitoring can be transferred — to the other crew member, to the cabin crew, to ATC. Delegation is not relinquishment of responsibility. It is the intelligent distribution of demand to preserve the capacity of the person who most needs to think clearly.

Create time. The hold. The extended routing. The deliberate slowing of pace that buys the minutes needed to process, plan and communicate before committing. Time is not always available. When it is, using it is one of the most effective workload management responses available. The crew that creates time under pressure is the crew that makes the subsequent decisions from a position of greater capacity and awareness.

Stop non-essential progress. An approach that is becoming unstabilised. A descent that is developing too fast for the crew to process. The instinct is often to continue — to push through, to manage the increasing demand in the hope that it resolves. The discipline is to stop, to call a halt, to take the go-around or the missed approach or the level-off that resets the situation to one the crew can manage. That decision requires recognising that the current trajectory is not sustainable — and acting on that recognition before the consequences make the decision for you.

The Hardest Response of All

And then the hardest response of all: admitting that the workload has reached a point that is beyond what is safely manageable — in yourself, or in your colleague.

This is the behaviour that requires every other part of the competency framework to be working. The psychological safety to say it without fear of judgement. The leadership environment that meets the admission with support rather than criticism. The trust built across the crew relationship that makes stating it a professional act rather than a confession. The assertiveness to say it clearly even when the instinct — particularly strong in experienced, capable crew members — is to push through and manage.

Without those conditions, the admission does not happen. The crew member who recognises that their workload has exceeded safe limits but cannot say so is a crew member who will attempt to manage alone what should be managed together. The workload peak that should have been redistributed and contained instead compounds. And the situation that could have been recovered at the point of admission becomes the one that is recovered — if at all — much later and at much greater cost.

Identifying a workload peak is a situational awareness behaviour. Responding to it with prioritisation and delegation is a workload management behaviour. Admitting it openly and asking for support is a Leadership and Teamwork behaviour. This is the behaviour where all three competencies converge — and why it is among the most demanding in the framework.