Supervisor Communication: Briefings, Handovers, Reports and Escalation
A premium course for supervisors and team leaders in any sector on the communication that keeps work safe and on track: short start-of-shift briefings, structured handovers, SBAR for raising a concern, plain-language written reports, and knowing when and how to escalate. Built on AHRQ TeamSTEPPS, HSE guidance on shift handover and the U.S. plain language guidelines. Not an accredited qualification.
What you will learn
- Run a short, two-way start-of-shift or start-of-day briefing.
- Give and receive a structured handover that transfers risk, not just tasks.
- Raise a concern clearly with SBAR and use closed-loop communication.
- Write short factual reports in plain language.
- Decide when and how to escalate, and record it.
Modules
- Why supervisor communication fails
- The start-of-shift briefing
- Handover that transfers risk
- Speaking up with SBAR and closed loops
- Written reports and escalation
Course facts
- Estimated study time
- about 1.5 hours
- Final assessment
- 10 questions · Pass mark 80%
- Available in
- English, Français, العربية
- Price
- Free. Optional verifiable certificate: $12
- Last updated
- Published by
- AMAADOR ACADEMY
Who this course is for
New and experienced supervisors, shift leads, team leaders and charge staff in operations, healthcare, IT, finance, projects and services.
Prerequisites
No formal prerequisite.
Course content
1. Why supervisor communication fails
Supervisors sit at the point where plans meet real work. Most of what goes wrong at that point is not a lack of skill but a gap in information: the night shift did not know a pump was running on bypass, the new analyst did not know a client deadline had moved, the agency nurse did not know a patient had a new allergy. AHRQ’s TeamSTEPPS programme, developed with the U.S. Department of Defense from healthcare and aviation research, treats communication as a teachable team skill — alongside leadership, situation monitoring and mutual support — rather than a personality trait.
Three failure patterns recur. First, one-way communication: the supervisor talks, nobody asks, and the team leaves with different pictures. Second, assumed shared knowledge: ‘everyone knows that valve is sticky’ — except the person who started on Monday. Third, softened warnings: people hint at a problem instead of stating it, especially to someone more senior. Each pattern is fixed by structure, not by talking more: short agreed formats, a habit of checking understanding, and permission to speak up.
Communication also has a legal and system dimension. ISO 45001 (clause 7.4) asks organisations to decide what they will communicate, when, to whom and how, for health and safety; quality and information-security standards have similar clauses. The supervisor is usually the person who makes that real at team level. A useful test: if you were absent tomorrow, would your team and the next shift have the information they need to work safely and meet today’s commitments?
Key point: Most front-line failures are information gaps; fix them with short structures and a habit of checking understanding.
2. The start-of-shift briefing
A good briefing is short, standing, at the same time and place, and follows the same order every day so people know what is coming. TeamSTEPPS describes a ‘brief’ as a short planning discussion before work: who is on the team, what the goals are, what the roles are, what resources and risks exist, and what the plan is if things change. In an office or IT team the same structure works as a daily stand-up; on a ward it is the safety huddle; on a site it is the pre-start or toolbox briefing.
Put safety and abnormal conditions first, while attention is highest: today’s hazards, permits, isolations, changes since yesterday, near misses worth sharing. Then the plan: priorities in order, who does what, what is due and to whom, known constraints such as missing parts, absent staff or system outages. Keep detail for the people who need it; a briefing is not the place to solve a problem in front of ten people — note it and agree who will meet after.
End by checking, not by asking ‘any questions?’, which almost always gets silence. Ask one person to say back the top priority, ask another what could stop them, and invite anyone to raise a concern. Record the key points in the shift log in two or three lines. TeamSTEPPS pairs the brief with a ‘debrief’ at the end — three questions on what went well, what did not and what to change — which turns daily communication into learning.
Key point: Same time, same order, safety first, and finish by checking understanding — not by asking ‘any questions?’.
3. Handover that transfers risk
Handover is one of the highest-risk moments in any 24-hour operation. The UK HSE’s human factors guidance points to major accidents where poor shift handover was a contributory factor — including the Piper Alpha disaster in 1988, where information about a pump whose safety valve had been removed for maintenance did not reach the next shift. The same pattern appears in hospitals, data centres and control rooms: the outgoing person knows something important and the incoming person never hears it.
HSE describes effective handover as two-way, face to face where possible, supported by a written record, and given enough time — not squeezed into the last five minutes. The content should focus on what is abnormal or changing: equipment out of service, isolations and overrides, jobs half-finished, alarms that keep recurring, promises made to customers or other teams. A structured form helps the outgoing person remember and lets the incoming person ask for what is missing.
Make the receiver active. Ask them to read back the key risks in their own words and to check the record before signing it. Handover also applies within a shift — when a task passes from one person to another, or when someone covers a break. For critical work, handover at the job location (looking at the plant, the screen or the patient together) is far more reliable than a conversation in the office. If the incoming person is not fit or not ready, the outgoing person should not leave.
Key point: Handover is two-way, written and verbal, focused on what is abnormal, and confirmed by the receiver’s read-back.
Case study: Piper Alpha (North Sea, 1988). A condensate pump’s pressure safety valve had been removed for maintenance during the day shift and the opening sealed with a temporary cover. The information did not pass effectively to the night shift, which restarted the pump when the second pump tripped. The leak and explosion that followed killed 167 people. The public inquiry identified failures in the permit-to-work system and in shift handover communication.
4. Speaking up with SBAR and closed loops
SBAR — Situation, Background, Assessment, Recommendation — was adapted from naval and aviation communication and is promoted by AHRQ as a TeamSTEPPS tool. It gives the speaker a fixed order so the listener gets the point in the first sentence. ‘Situation: line 3 is producing seals with a visible crease. Background: started after the 10:00 changeover, about 200 parts. Assessment: I think the new die is misaligned. Recommendation: I want to stop the line and quarantine this morning’s output; I need your approval in ten minutes.’ NHS England teaches a variant, SBARD, that adds a ‘decision’ step.
Closed-loop communication makes sure the message was received. The sender gives a clear message, the receiver repeats it back, and the sender confirms or corrects. It is used for instructions with consequences: isolating equipment, changing a dose, approving a payment, rolling back a release. TeamSTEPPS also teaches ‘check-back’ and a ‘call-out’ for critical information that everyone in the area needs to hear at once.
Speaking up across a hierarchy is hard. TeamSTEPPS uses the ‘two-challenge rule’ — if a concern is ignored, say it a second time; if it is still ignored, take it to the next level — and the CUS words: ‘I am Concerned, I am Uncomfortable, this is a Safety issue’. As a supervisor, model it: thank people who raise concerns even when they are wrong, and never punish someone for stopping work in good faith.
Key point: Lead with the situation, end with a clear request and a time, and close the loop with a read-back.
5. Written reports and escalation
Supervisors write every day: shift reports, incident notes, e-mails to other teams, justifications for overtime. The U.S. federal plain language guidelines give rules that work in any language: write for your reader, put the main point first, use short sentences and common words, use active voice (‘the night shift did not test the alarm’, not ‘the alarm was not tested’), and use lists and headings. Facts, times and numbers beat adjectives: ‘three of eight orders shipped late, by an average of two hours’ tells the reader more than ‘significant delays’.
Keep fact, opinion and request separate. In an incident note, record what was seen and done, with times, before any view of the cause; do not guess at blame. Write as though the report may be read later by an investigator, an auditor or a court — because it may. Avoid abbreviations your reader may not know, and re-read before sending: could the next shift act on this without calling you?
Escalation is a planned communication, not a failure. Agree triggers in advance with your manager: any injury or near miss with serious potential; a customer commitment that will be missed; a cost or time overrun above a set amount; a possible legal, data-protection or regulatory breach; a team conflict you cannot resolve. When a trigger is met, escalate early, using SBAR, to the person who can decide — and record when, to whom and what was agreed. Escalating with a proposed solution is welcome; sitting on bad news is not.
Key point: Main point first, facts before opinions, and escalate early against agreed triggers — then record it.
The full lesson, case studies, scenarios and templates continue in the interactive course on this page.
Sources and references
- TeamSTEPPS — team strategies and tools to enhance performance and patient safety
- TeamSTEPPS tool: SBAR (Situation, Background, Assessment, Recommendation)
- Human factors: safety-critical communication at shift handover
- Plain language guide
- Federal plain language guidelines
- ISO 45001:2018 Occupational health and safety management systems (catalogue) — clause 7.4 communication
Professional education only, not an accredited qualification. Follow your organisation’s procedures for handover, incident reporting and escalation; in an emergency, use your emergency procedure first. ISO content is paraphrased from public catalogue pages.