How to Review Workload Before a Seasonal Production Peak

F2 practical guide

A seasonal production peak can look like a commercial success on the planning board while creating a very different experience at the point of work. Output rises, schedules tighten, support functions become harder to reach, and supervisors spend more time moving people between priorities. The psychosocial risk often appears before overtime becomes visible in a monthly report.

Review workload before the peak by comparing demand with real capacity, then test whether staffing, recovery, role clarity, supervision, and escalation routes can absorb the change without relying on silent overextension.

This guide is for plant managers, EHS leaders, HR partners, and frontline supervisors who need a practical review before a predictable demand increase. It does not diagnose an individual medical condition, and it does not replace professional occupational health advice or legal requirements that apply to the workplace.

ISO 45003:2021 treats psychosocial risk as part of the occupational health and safety management system, which means workload should be examined as a feature of work organization rather than as a personal weakness. Andreza Araujo’s *Safety Culture: From Theory to Practice* makes a related leadership point. What leaders plan, protect, and review tells employees which risks can be raised without penalty.

What you need before starting

Collect the production forecast, staffing plan, shift pattern, absence coverage, overtime rules, maintenance calendar, contractor schedule, recent concerns, and the decisions that supervisors currently struggle to make.

Use at least one source from planning and one source from the field. The plan shows intended capacity. The field shows where the plan already depends on workarounds, informal coverage, delayed maintenance, or a supervisor who is carrying several decisions at once.

Do not begin by asking whether people feel resilient enough for the peak. Begin by asking which work conditions are changing, who absorbs the change, and what evidence would show that the plan is no longer safe to continue.

Step 1: Define the peak and the decision window

Write down when demand rises, what work changes, which teams are affected, and the date on which leaders can still alter the plan.

A review without a decision window becomes a discussion that ends when the schedule is already committed. Identify the first week of increased demand, the expected duration, and the latest point for changing staffing, sequencing, service levels, or delivery commitments.

Include non-production teams whose capacity protects safe work, such as maintenance, logistics, quality, occupational health, and training. A peak that looks manageable in production can still create exposure when support decisions arrive late.

Step 2: Map demand by task, shift, and critical role

Translate the forecast into tasks and decisions, then show where volume or complexity concentrates by shift and role.

Units produced are not enough. A small increase in output can create a large increase in changeovers, troubleshooting, cleaning, dispatch, quality checks, or supervisor interventions. Map the work that requires judgment, coordination, or recovery after an interruption.

Mark the roles that cannot be left uncovered. If one person is the only competent decision-maker for a safety-critical process, the plan has a resilience gap even when the headcount appears adequate.

Step 3: Test real capacity instead of planned capacity

Compare rostered capacity with the capacity that remains after leave, absence, training, meetings, travel, maintenance, and normal interruptions.

Planned hours are not the same as usable capacity. A supervisor who is scheduled for a full shift may also be expected to complete investigations, coach new workers, approve permits, respond to alarms, and cover an absent colleague.

Use a simple capacity ledger for each shift. Record what is fixed, what is flexible, and what is already being postponed. The purpose is not to create a perfect forecast. It is to expose the assumptions that make the peak appear manageable.

Step 4: Review recovery time and shift transitions

Check whether people can recover between shifts and whether handovers preserve the information needed for safe decisions.

Recovery is part of work design. Examine consecutive shifts, short turnarounds, night work, travel time, break access, call-in expectations, and the way work is handed over when production continues across teams.

Connect this review with the site’s workload risk review before overtime, but keep the seasonal question distinct. The issue here is not only whether overtime exists. It is whether the demand pattern removes the recovery and information conditions that keep decisions reliable.

Step 5: Identify role conflict and priority collisions

List the situations in which production, quality, maintenance, customer delivery, and safety instructions compete for the same person’s attention.

Role conflict becomes dangerous when people are told to meet every priority at once. Ask supervisors to describe the decision they would make when a delivery commitment conflicts with a maintenance hold, when quality requires rework, or when a control needs verification before restart.

Write the priority rule in plain language. A rule that exists only in a presentation will not resolve a collision at 2 a.m. The escalation route must identify who can pause work, who can change sequence, and who must be informed.

Step 6: Check supervision and contractor interfaces

Verify that every shift has access to a supervisor who can make decisions and that contractors know how workload changes affect their work.

Seasonal peaks often increase contractor activity at the same time that internal supervisors have less time to coordinate it. Review induction, language needs, simultaneous operations, permit ownership, communication channels, and the point at which a contractor can escalate an unmanageable condition.

A supervisor who cannot reach the right technical or occupational health support is not fully supported by the organization. The gap belongs in the risk register rather than in a note about individual performance. Use the contractor integration guide to test whether the same interface remains reliable during the peak.

Step 7: Set escalation triggers before pressure rises

Define the conditions that require a plan change, a leadership review, or a temporary reduction in work rather than a request for extra effort.

Triggers can include uncovered critical roles, repeated missed breaks, consecutive short turnarounds, unresolved control defects, rising error corrections, delayed maintenance, loss of competent supervision, or reports that people cannot complete the task within the available time.

Do not wait for one metric to prove the situation is serious. A combination of small signals can show that the operating margin is narrowing, especially when workers have stopped raising concerns because earlier concerns changed nothing.

Step 8: Rehearse the review with the people doing the work

Run the proposed peak plan through a short, cross-functional conversation and record which assumptions the field rejects.

Ask what will be different on the busiest shift, which task will become the bottleneck, what information will arrive late, and what a supervisor will do when the plan stops matching the work. Invite disagreement before the schedule is locked.

This is a practical application of psychological safety, not a request for agreement. People need to see that raising a concern can change a decision. The final plan should show what was changed, what remains uncertain, and who will review the conditions after the first operating week.

What should the final workload review contain?

The final review should connect the peak forecast to capacity, recovery, role clarity, supervision, contractor coordination, escalation triggers, and a named owner for each action.

Keep the record short enough to use and specific enough to govern. A useful review states the operating assumptions, the evidence behind them, the conditions that would invalidate them, and the person who can change the plan.

Link each material concern to one decision. For example, a shortage of competent night supervision may require a staffing change, a sequence change, or a reduced production window. It should not end as a general reminder to “stay alert.”

For a related leadership application, compare the review with the psychosocial review used before a shift-schedule change and the fatigue-risk review for night-shift teams. The seasonal peak adds a demand and capacity lens to those controls.

How can leaders verify the plan after the peak starts?

Review the first operating week against the assumptions, then change the plan when field evidence shows that capacity or recovery is weaker than expected.

Use a short review with supervisors, workers, maintenance, HR, and EHS. Ask which workload assumptions held, which failed, which concerns were raised, and whether the escalation route produced a decision. Avoid treating the meeting as a search for individual fault.

Andreza Araujo’s work across multinational safety programs emphasizes that culture becomes visible in the decisions leaders make under pressure. A seasonal peak is therefore a useful test. If the organization protects recovery, hears concerns, and changes the plan when evidence requires it, the review has done more than document psychosocial risk. It has improved the operating conditions that shape safe behavior.

• The peak has a defined start, duration, and decision window.
• Demand is mapped by task, shift, and critical role.
• Capacity includes absence, training, maintenance, meetings, and interruptions.
• Recovery time and handover quality are checked across the actual schedule.
• Priority collisions have an explicit decision rule.
• Supervision and contractor interfaces are covered on every affected shift.
• Escalation triggers are defined before pressure rises.
• The plan is rehearsed with the people doing the work and reviewed after launch.

A seasonal peak is controlled when leaders can show how demand will be absorbed without hiding the conditions that make work harder to perform safely. If the plan depends on silence, skipped recovery, or permanent supervisor improvisation, the workload review has already found a material risk.

For more work on safety culture, leadership, and risk decisions, explore Headline Podcast’s workplace safety and leadership articles and Andreza Araujo’s perspective on making prevention visible in everyday management.

Related reading: Work intensification explained through four design pressures shows how workload changes can weaken safety controls before a visible incident.