How to Review Workload Handoffs for Psychosocial Risk in 14 Days

A workload handoff can look orderly while leaving one person with the unresolved pressure, interruptions, and decisions that the previous shift could not finish. When the next team receives only a task list, it inherits the work without inheriting the context needed to judge what can safely wait.

A workload handoff is psychosocially controlled when the receiving team understands the unfinished demand, the decision limits, the support available, and the recovery time that protects people from carrying hidden overload into the next shift.

This guide gives supervisors, HR partners, and EHS leaders a fourteen-day method for reviewing that handoff. The aim is not to diagnose a person or turn a routine transfer into a clinical assessment. The aim is to find work-design conditions that make overload predictable, then change the handoff before strain becomes an absence, a mistake, or a safety exposure.

Across more than 250 cultural transformation projects, Andreza Araujo has seen that culture is revealed by repeated decisions under pressure. Her book Safety Culture: From Theory to Practice makes the same distinction that this review depends on, because a process is not controlled merely because every box in the form is complete.

What you need before starting

Choose one handoff that occurs often enough to show a pattern. It might be the transfer between a night and day maintenance team, the point at which a customer-service queue changes ownership, or the moment a production supervisor passes unresolved work to the next shift. Keep the first review narrow so the team can examine the real sequence instead of collecting broad opinions about workload.

Step 1: Define the handoff boundary

Write down when the outgoing team considers the work transferred and when the receiving team considers itself responsible. Those moments are often different. One group may send a message at the end of the shift, while the other does not read it until the next meeting or after the first operational interruption.

Map the boundary using observable events rather than job descriptions. Record when the queue closes, when the supervisor signs the transfer, when the receiving person first touches the work, and when an unresolved issue is escalated. Verification is complete when two people can point to the same start and end of the handoff.

A common error is treating the scheduled shift change as the whole boundary. The psychosocial exposure often sits in the gap between nominal transfer and practical ownership, where people remain available to the previous team while already being judged by the next one.

Step 2: Separate demand from urgency

Ask the outgoing team to classify each unfinished item as urgent, important but deferrable, waiting for information, or ready for closure. The purpose is not to create a perfect ranking. It is to prevent every unfinished task from arriving with the same emotional weight.

Compare the classification with what the receiving team actually did. If most items are labeled urgent but only a few require immediate action, the handoff is transmitting alarm rather than useful priority. If the receiving team repeatedly rechecks the same item, the original priority is not clear enough to support a calm decision.

Review the rule with the person who owns the operation. A workload review cannot ask employees to solve a priority conflict that the organization has left undefined. The control is the decision rule, not the employee's ability to absorb more work.

Step 3: Capture hidden work

List the work that does not appear in the official queue. This may include answering follow-up messages, waiting for approvals, explaining the history of a problem, checking whether a colleague has acted, or staying reachable after the shift has ended. Hidden work is still demand, even when no system records it.

Ask each side of the handoff to describe what they do before they can begin the visible task. Compare the answers. The difference is useful because it reveals coordination effort that the process owner may not see.

Do not label hidden work as poor organization before checking the design. People often create informal tracking because the formal handoff omits a decision, an owner, or a time boundary. The right correction may be a better field, a clearer escalation route, or a staffing decision rather than a reminder to be more resilient.

Step 4: Test decision authority

For each transferred item, ask what the receiving person may decide without approval, what must be escalated, and how quickly an answer should arrive. Record the answer in plain language. Vague authority creates a double demand because the person must keep the work moving while also protecting against a decision that might later be challenged.

Use one recent example to test the rule. If the receiver had to contact several people before acting, the authority boundary is not operational. If the receiver acted without knowing whether the decision was theirs, the boundary is also unsafe.

Psychosocial risk grows when accountability is clear but authority is not. A handoff that names the person responsible without giving that person a usable decision path transfers exposure, not control.

Step 5: Check interruption load

Observe one complete handoff and count interruptions by type, not only by volume. Separate requests that clarify the transferred work from unrelated demands that arrive because the receiving person is now visible or available. This distinction matters because the same number of interruptions can have very different effects on concentration and recovery.

Ask which interruptions can wait, which can be routed elsewhere, and which are caused by missing information in the handoff. Then change one point in the flow. A shared status field, a protected first work period, or a named escalation channel can reduce avoidable switching without slowing the operation.

Verify the change with the receiving team. If the new arrangement only moves interruptions to another person, the review has shifted the burden rather than reducing it.

Step 6: Review recovery and availability

Ask whether the outgoing worker can disconnect after the handoff and whether the receiving worker has enough protected time to understand the work. Do not assume that a message sent outside working hours is harmless because no reply is formally required. People read signals about what the organization expects, especially when the unresolved work has consequences for customers, production, or safety.

Define what counts as an after-hours exception, who can activate it, and what happens next. A rule that says everyone should use judgment is not enough when the consequences of waiting are unclear.

The review should also examine whether the first task of the new shift is immediate firefighting. When every handoff begins with emergency sorting, the operation may be using personal recovery time to compensate for a weak workload design.

Step 7: Run a receiving-team reality check

Give the receiving team the revised handoff without coaching them toward the preferred answer. Ask them to explain what they believe is urgent, what they can defer, who owns each decision, and what support they can request. Their explanation is the verification test.

Look for three kinds of mismatch. The written handoff may omit a demand that workers know from experience. The written priority may conflict with the manager's actual expectation. The written owner may not be the person who has the time or authority to act.

When a mismatch appears, fix the process rather than asking the team to compensate with memory. In The Illusion of Compliance, Andreza Araujo's central warning is that a completed record can coexist with weak control. The reality check makes that warning practical because it tests whether the handoff can guide action.

Step 8: Set the fourteen-day control and review it

Choose one change that the operation can sustain for the next fourteen days. State the owner, the start date, the conditions that require escalation, and the evidence that will show whether the handoff improved. Keep the measure close to the work, such as fewer repeated clarifications, fewer unplanned after-hours contacts, clearer ownership, or a shorter delay before a decision is made.

Do not use the review to create a target for people to appear calm. The point is to reduce avoidable ambiguity and demand, not to make strain less visible. A worker who reports that the new handoff still creates overload is providing control evidence, not failing the program.

On day fourteen, compare the original map with the observed handoff. Keep what made the work clearer, remove what added paperwork without reducing demand, and escalate any issue that requires staffing, role redesign, or a change in service expectations. Andreza Araujo's experience across 25+ years in executive EHS supports this practical standard, because a useful control must survive contact with the next shift.

FAQ

What is a workload handoff?

It is the transfer of unfinished or continuing work from one person or team to another. The transfer includes more than a task list because it also needs priority, decision authority, context, support, and a clear boundary for responsibility.

Why can a handoff create psychosocial risk?

A handoff can create risk when it transfers demand without transferring time, authority, information, or support. The receiving person then carries uncertainty and accountability at the same time, which can increase interruptions, hidden work, and difficulty recovering after the shift.

Should HR or EHS own the review?

The operational owner should lead the change because the risk sits in the workflow. HR and EHS can support the review with work-design, health, and safety expertise, while the supervisor team verifies whether the revised handoff works in practice.

What if workers do not want to discuss overload?

Start with the work sequence rather than asking people to disclose personal health information. Ask what is unclear, repeated, interrupted, delayed, or carried outside the shift. A process-based conversation can reveal design problems without requiring a diagnosis.

Which Andreza Araujo book fits this topic?

Safety Culture: From Theory to Practice fits the leadership and operating-system side of the review. The Illusion of Compliance helps teams test whether a tidy handoff record reflects real control. Together, they connect work design with the decisions people make under pressure.

Conclusion

A workload handoff is controlled when the receiving team knows what matters, what can wait, what it may decide, and where support comes from. Review the boundary, hidden work, authority, interruptions, and recovery conditions, then verify the change in the next real shift. That is how a routine transfer becomes a protection against psychosocial strain rather than another source of it.