How do you hand over event control between shifts?

Your replacement has arrived, the radio is on the desk, and you're already thinking about getting home. Then someone asks whether the second entrance can reopen. You remember discussing it with the venue, but the answer never reached the log. Your replacement has the keys and none of the conversation that explains what to do with them.

A good event control handover transfers the current situation and the responsibility for coordinating what happens next. Prepare the open issues, check them together, record who accepts which duties and when, then tell the teams whose contact has changed. Keep restrictions and unfinished decisions visible until the people authorised to resolve them actually do so.

That applies whether you have a festival control room or two producers sharing a desk at a paid conference. The scale changes the people and systems you need. The basic question stays the same: can the incoming person explain what needs attention now, what they're allowed to decide, and who they need to contact?

This guide walks through the preparation, a copyable handover record, a worked live-event example and the awkward cases when the replacement is late or an incident interrupts the conversation. It focuses on changing the person coordinating an event that's still operating. Your venue, specialist providers and emergency arrangements determine the responsibilities for your actual event.

Agree exactly what is being handed over

Start with the job. "Taking over control" can mean running the organiser's coordination desk, supervising a security team, calling the stage programme or acting as the venue duty manager. Those are different responsibilities. A single announcement shouldn't leave everyone assuming that one person now holds all of them.

For this guide, event control means the organiser's agreed point for receiving operational information, coordinating decisions and tracking follow-up. Some events combine that with the event director's role. Others have a separate controller, log keeper and representatives from different teams. Choose the arrangement your event requires rather than borrowing a large festival's job titles.

Write the transfer in ordinary language. For example, the incoming duty producer will coordinate the organiser's live operations, receive department updates and refer specified commercial decisions to the event director. The stage manager still calls the show. The venue retains its agreed responsibilities. Security and medical providers continue managing their own professional work.

Great Britain's Health and Safety Executive distinguishes coordinating event work from doing every contractor's technical job. Its guidance calls for suitable management arrangements through each event phase. Use the handover to keep those boundaries understandable. Receiving a report about an electrical fault doesn't qualify the duty producer to approve electrical work.

Confirm the period and area covered too. Are you handing over the whole event, one venue or a particular work phase? If public admission continues while a separate team prepares another space, say who coordinates the connection. A person receiving the daytime show operation may have no authority to release equipment for overnight removal.

A change of shift also differs from handing a retained site to an overnight provider. Our guide to overnight festival site handover covers retained equipment, continuing services and the morning return. Here, the immediate concern is an operation that keeps receiving reports and making decisions while its coordinating lead changes.

Get the authority agreed before writing the form. If the outgoing producer can approve a programme change but the replacement cannot, that difference must be explicit. The team needs a working decision route for the incoming shift, not a document that promises powers the replacement doesn't hold.

Build the overlap into the booking

A handover is work. Schedule and pay for the time needed to prepare, discuss and check it, including any agreed overlap between suppliers or staff. If one person's booking ends exactly when the other person's starts, you've left the actual exchange dependent on someone staying beyond the arrangement.

There isn't a universal handover length. A quiet indoor event with no open problems differs from a festival changing shifts during a delayed programme and several supplier movements. Decide what the people need to examine and which departments must contribute. Use that workload to plan the exchange, then reassess it when the operation changes.

Choose a point that avoids predictable pressure where possible. Don't deliberately place the lead change at public opening, a major audience movement or the programme's most demanding transition merely because the roster is easier to draw. Sometimes that timing is unavoidable. Arrange enough competent cover and preparation for the actual conditions.

Keep somebody handling incoming reports while the outgoing and incoming leads talk. Depending on the event, that may be another authorised controller or an agreed temporary arrangement with the relevant leads. People reporting urgent problems must still reach the event's response route. A sign saying "handover in progress" doesn't make those problems wait.

HSE's guidance on fatigue explains that tiredness can affect memory, attention and information processing. It also says working patterns need assessment for their actual demands. Don't build your continuity plan around an exhausted producer repeatedly extending their shift whenever relief goes wrong.

Before the event, agree who arranges replacement cover, who can authorise an extension and what happens to affected operations if suitable cover isn't available. Check the employment, supplier and venue arrangements that apply. Booking more hours is only useful if the person can still perform the job and the resulting arrangement is acceptable.

For a small event business, this can be a practical conversation with your co-producer and venue contact. You still need a real person covering the work and a clear transfer. A shorter document may suit the event; an imaginary backup who never agreed to be available does not.

Prepare the current position before the replacement arrives

The outgoing lead should prepare throughout the shift, rather than trying to remember everything in the last few minutes. Keep significant decisions, unfinished actions and changed conditions in the agreed working record as they happen. That gives the next person something better than a hurried reconstruction of your day.

Before the exchange, ask department leads for changes that affect the next shift. What remains unresolved? Has an expected person arrived? Is a restriction still active? Has a supplier accepted the changed instruction? You're collecting current information for the transfer, not asking every department to write an account of everything it did.

Record the time and source of important reports. "Venue checked the entrance" is incomplete if nobody knows which entrance, what was checked or whether the report preceded a later fault. A useful entry names the condition, the person reporting it and when they last confirmed it.

Mark uncertainty honestly. An expected arrival isn't an actual arrival. A proposal awaiting agreement isn't an instruction. A message sent to a department isn't confirmation that the department received and applied it. These distinctions help the incoming lead avoid turning your hopeful shorthand into an operating decision.

Use the current versions of the site plan, roster, running order and relevant procedures. Your handover can reference those documents and call out changes rather than copying them in full. Keep superseded versions distinguishable so the replacement doesn't use an old screenshot because it was easier to find.

Separate the short summary from the supporting history. The summary should show what needs attention on the incoming shift. The detailed log explains how decisions developed and where to find supporting records. Both matter, but making someone read every closed ticket query before discovering an active restriction is poor preparation.

If you're still investigating an important issue, say what is known, what isn't known and who is checking. You can hand over an unresolved problem with a clear owner and restriction. You can't honestly describe it as resolved because the next shift has arrived.

Put open issues ahead of the finished work

The most useful starting point is what could require the incoming lead's attention before their next planned review. That may be an active incident, a restricted area, an unanswered decision request, a missing team member or an attendee update already promised. Let the current conditions determine the order.

For each open item, write the observed situation, the action already taken, the current owner and the next required action. Add the relevant deadline or review condition and explain what remains restricted. A colour or priority label can help people scan, but it doesn't explain the issue on its own.

Compare "Entrance B sorted" with "Entrance B remains unavailable; venue duty manager is arranging a check of the reported door fault; admission lead keeps the existing instruction; control needs the venue's confirmation before considering any changed use." The second takes longer to write, but the incoming person can actually use it.

The person coordinating follow-up isn't necessarily the person repairing the fault or authorising release. Record those jobs separately where they differ. Otherwise, the next controller may keep calling the organiser for a technical conclusion that only the contractor or venue can provide.

Carry forward conditions that still apply even when no new action is due immediately. A room can remain unavailable while its specialist assessment is scheduled for later. If it disappears from the handover because there's no imminent task, the next shift may assume it has reopened.

You also need to know what is already committed. A replacement delivery may be approved and awaiting arrival. A discretionary payment may already have used part of the event's allowance. The change of controller doesn't reset money, permissions, promised updates or supplier instructions.

Close an item only when the defined completion has been confirmed and recorded. If one action finishes but another remains, update the entry instead of removing the whole issue. Receiving a technician's arrival message may complete the arrival check while leaving the fault and restriction open.

Copy this event control handover record

Use this as a starting structure, then adapt it with the people responsible for your event. It records a shift transfer, rather than supplying a suitable emergency plan or technical procedure. Some entries can reference your controlled documents; others need the current facts written out.

Keep the form readable at the place people work. If you use a shared system, confirm that incoming staff have the right access. If paper supports the operation, identify the current copy and how later updates are reconciled. Don't create several equally plausible versions of the open-issues list.

Event and transfer details

• Event, date, venue and operating areas: identify the operation covered.

• Outgoing lead and incoming lead: record names, organisations, roles and contact routes.

• Planned overlap and responsibility period: distinguish the discussion from the intended transfer.

• Actual acceptance time: record the full date, time and relevant time zone.

• Scope accepted: state the coordinating duties and any exclusions or continuing specialist responsibilities.

• Current supporting documents: identify the site plan, roster, running order and emergency arrangements by version.

Current situation and restrictions

• Event phase and immediate milestones: state what's operating now and what's due next.

• Significant changes since the incoming lead last worked: explain the changed instruction and affected teams.

• Active incidents and open issues: reference each record and describe its current operational consequence.

• Restricted areas, equipment or activities: name the restriction and the authorised release route.

• Information awaiting verification: state the source, last confirmation time and person checking it.

• External organisations involved: identify the working contact and any agreed limits on the organiser's role.

Decisions, actions and communications

• Decision required: say what needs deciding, by whom and before which actual deadline.

• Action owner and backup: name the people who have accepted the task or follow-up.

• Current action and completion condition: distinguish a request, an instruction and confirmed completion.

• Approved commitments: include relevant supplier changes and the current spending position by reference.

• Messages outstanding: record what's drafted, approved, sent or still awaiting acknowledgment.

• Next review: state the time or observed condition that requires another check.

People and working equipment

• Department leads currently on duty: include the agreed contact route and relevant upcoming changes.

• Missing cover or changed assignments: record the actual arrangement and unresolved gap.

• Communication equipment and access: confirm the working radio, phone and authorised system access.

• Important items transferred: use the controlled key, device or document record where appropriate.

• Restricted records: identify where authorised recipients can find the information they need.

• Communication failure or absent replacement: reference the agreed fallback and the person arranging it.

Acceptance and notification

• Incoming cross-checks: record the important facts checked and any discrepancy found.

• Outstanding conditions at acceptance: state what remains open and the duties accepted around it.

• Outgoing confirmation and incoming acceptance: name both people and record the actual transfer.

• Teams notified: identify who received the change of contact and which acknowledgment is required.

• Outstanding notifications: assign an owner and keep them visible until confirmed.

• Next handover or return: identify the planned recipient and the fallback if they aren't available.

The form should make an uncomfortable truth easy to record. If a required contact isn't reachable, write that down and use the agreed escalation. A complete-looking set of ticks doesn't help the incoming lead decide what can proceed.

Check the handover together before accepting it

HSE's shift handover guidance describes outgoing preparation, an exchange of relevant information and incoming cross-checking. It recommends spoken and written communication, preferably face to face, with enough time for the job. Its examples include other industries; the event process here applies those communication principles to live coordination.

Start with current conditions, then work through the open issues and the incoming person's authority. Let the incoming lead ask questions while you can still identify the source of an answer. The outgoing person's familiarity with the event can hide how much context their shorthand assumes.

Check the facts that could change the next decision. Contact the relevant lead, inspect the current approved record or arrange an appropriate joint check. The incoming controller doesn't need to repeat every specialist inspection. They do need to establish which confirmation exists and what it actually permits.

Ask for the next action in the incoming person's own words. "What will you do if the supplier hasn't provided the promised arrival update?" is more useful than "All clear?" You're checking whether the action, owner and consequence transferred successfully, rather than testing someone's confidence in a room full of colleagues.

Try the working equipment and access as well. Can the replacement reach the department leads from the control position? Can they open the current log and add an entry? Does the duty phone receive the expected calls? A successful login yesterday doesn't settle whether today's shift has usable access.

If the incoming lead finds a discrepancy, resolve the immediate instruction before recording acceptance. You may need a department to correct its report or a senior lead to arrange cover. Where an open condition can legitimately continue, record who owns it and what remains restricted. Don't use an unconditional signature to hide a conditional situation.

The outgoing lead should also explain changes that aren't obvious from the latest schedule. A delayed session might affect a sponsor appearance, catering release and the next audience movement. Keep the discussion focused on those dependencies instead of retelling every conversation that produced the delay.

A worked handover during a paid festival

Let's use a fictional paid event called Riverside Makers Festival on Saturday 14 November 2026. All names, times, records and USD figures in this example are invented to show the method. They aren't staffing recommendations, safe operating intervals or actual customer results. The venue and providers have their separate agreed plans.

Amira coordinates the organiser's live operation until the shift transfer. Ben is the incoming duty producer. Both producers can coordinate the approved programme and request department action within it. Leila, the event director, retains approval of additional spending and changes to the advertised programme, including cancellation. Jo leads admission, Pat is the venue duty manager, Maya coordinates production and Nia handles approved attendee messages. Their teams and specialist providers have responsibilities beyond the selected issues shown here.

The planned overlap runs from 16:30 to 17:00, with transfer before its end if the necessary checks are complete. All example times are local venue time, UTC+0. Those times come from this fictional roster. The event continues operating throughout, with an authorised controller covering incoming reports while Amira and Ben conduct the discussion.

At 16:20, Amira prepares the current summary. It identifies three open items. Entrance B remains unavailable after a reported door fault. A replacement production delivery is approved but hasn't arrived. An update about a revised workshop start has been approved internally, but Nia hasn't yet confirmed sending it.

Entrance B stays unavailable

Entry E17 records that Pat is coordinating the venue's check. Jo has confirmed that her team is following the existing admission instruction and is not directing attendees to Entrance B. Ben needs to follow up with Pat at 17:05, the review time agreed for this fictional issue, or sooner if conditions require attention under the agreed plan.

The handover doesn't declare that the wider admission arrangement is suitable merely because Entrance B is closed. That depends on the event's actual assessments and responsible decisions. If the restriction makes the current operation unacceptable, the authorised people must change or pause the affected activity under those arrangements.

During the joint check at 16:40, Ben finds a message describing the venue visit as complete. He asks Pat what that means. Pat confirms that a representative has attended, but no release for the entrance has been given. Amira corrects the summary to preserve the distinction. E17 remains open and Entrance B remains unavailable.

The delivery is approved, not received

Entry P08 concerns a replacement production delivery. Leila approved the complete additional cost of $360 at 15:50, and Maya issued the instruction to the supplier. The supplier acknowledged it at 16:05. Arrival is still pending, with a supplier update agreed for 17:10.

The event's simplified additional-cost reserve was $2,000 before this commitment. Recording $360 leaves $1,640 available under the example's assumptions, with no other changes. Ben receives that same balance. He doesn't gain a fresh $2,000 because a new shift has started, and he doesn't deduct the same $360 again when the delivery arrives.

Maya still owns supplier coordination and the relevant production acceptance. Ben owns the control-room follow-up. If the supplier reports a different price or an unacceptable delivery change, Ben refers the new decision through the existing authority arrangement. The old approval doesn't cover whatever happens next.

The attendee message is still outstanding

Entry C04 records a workshop start change from 17:30 to 17:45. Leila approved the change and wording at 16:10 after the relevant programme and venue checks. Nia owns the send and confirmation to the affected front-of-house team. Amira's summary says "approved, send confirmation outstanding".

Ben asks Nia for the actual position. At 16:48 she confirms the update has been sent through the agreed attendee communication route, and Jo acknowledges the corresponding staff instruction at 16:52. Amira records both facts. A message being sent doesn't establish that every attendee has read it, so onsite communication continues under the event's arrangements.

C04 can now be marked complete for its defined send-and-staff-notification action. The new start remains in the current running order. Closing the communication task doesn't remove the changed programme instruction from the incoming shift's information.

Ben accepts the coordinating role

At 16:55, Ben confirms the current documents, his authority, E17's restriction and P08's next update. He can access the log and working contact routes. The acceptance record states that he takes the organiser's defined live-coordination duties at 16:55, with E17 and P08 still open. Leila's retained powers and provider responsibilities continue unchanged.

Amira records her confirmation at the same time. The teams requiring the change of contact are notified and acknowledge it by 16:58. Amira remains for the rest of the booked overlap as support, but Ben is now the coordinating lead. They don't both issue independent instructions because both are still in the room.

At 17:05, Ben contacts Pat about E17. Pat confirms that the entrance remains unavailable and agrees to report the next position at 17:35, with any urgent change reported immediately. Ben records that follow-up. The review appointment does not authorise waiting if conditions require earlier action.

At 17:10, Maya reports that the supplier has confirmed arrival for 17:20. Ben updates P08 as an expected arrival, not a received delivery. When Maya confirms arrival and the required acceptance at 17:25, Ben records that confirmation and closes P08's defined delivery action. The $360 remains an existing commitment for financial reconciliation.

Ben knows what continues after Amira leaves. At acceptance, he has an open entrance issue, a delivery follow-up, the revised workshop instruction and a current record of who can decide each matter. He doesn't need to reconstruct those facts from Amira's private messages.

Connect department handovers to the current control lead

Your departments may change shifts at different times. The admission supervisor can finish before the production lead, while the organiser's duty producer continues across both changes. Record those changes as they happen rather than treating the main control handover as the only transfer worth tracking.

Each department needs its own exchange appropriate to the work. Control needs the current lead, their contact route and any change affecting shared operations. Receiving a new name at the coordination desk doesn't establish that the department has completed its specialist handover. Ask the provider or responsible lead to confirm their arrangement where the event depends on it.

For example, an incoming stage manager may receive unfinished work and programme changes through the stage team's process. The control lead needs to know who now handles the relevant stage decisions and whether a shared milestone has changed. They shouldn't try to conduct the technical handover themselves from a short summary.

Keep the current run of show with the people operating the programme. If a department change reveals that the stage team is using a different confirmed start time from front of house, resolve the instruction with the responsible leads. Updating the contact list alone leaves that disagreement intact.

Avoid moving every open task automatically to the replacement's name. A contractor who agreed to investigate a fault may still own that action after their department supervisor changes. Check which responsibilities actually transfer and which continue with the existing person. The incoming supervisor can own follow-up without becoming the specialist performing the work.

Tell the current control lead about an incomplete department transfer. Perhaps the incoming supervisor hasn't received the current restriction or cannot reach their own backup. That gap can affect other teams even while the department appears staffed. Record the consequence, the person resolving it and the agreed conditions for affected work.

At the next control handover, the incoming producer should see the department leads who are on duty now, along with any imminent change requiring follow-up. They shouldn't have to guess which person on yesterday's supplier list still answers the radio. Maintaining that current position is part of running the shift, rather than a task saved for its final minutes.

Announce the change to the people relying on it

Recording acceptance at the desk doesn't tell admission, production or the venue who now receives their reports. Agree which contacts need the change and how they'll acknowledge it. For an event with several organisations, the right recipients may include their supervisors rather than every individual worker.

Keep the announcement short and concrete. Identify the outgoing and incoming lead, the effective time, the duties transferred and the working contact route. Mention any temporary limit that changes who decides a matter. Don't broadcast sensitive incident details as part of a general change-of-shift message.

HSE's safety communication guidance recommends choosing methods, language and timing for the people receiving important information. It also discusses reinforcing important messages through more than one method. For your event, make the announcement understandable to the actual teams and keep the written contact information current.

Check acknowledgment where the operation requires it. A new controller posting in a large chat may miss the supervisor who is already working away from their phone. If a required team hasn't received the change, assign someone to contact it through the agreed alternative and keep the notification open.

Update the duty contact in the place later arrivals will consult. Your event team briefing should explain how that information changes during the day. Otherwise, a late supplier can follow the original briefing perfectly and still call the person who has gone off duty.

The outgoing lead needs to respect the transfer too. If someone contacts Amira after 16:55, she should connect the report to Ben through the agreed route. Quietly resolving it without updating him can recreate the split responsibility the handover was meant to prevent. Immediate emergencies still follow the event's emergency procedures.

Keep access and attendee messages usable on the next shift

Check software access before the incoming shift needs it. The person can be fully briefed and still unable to perform their job if the current log or ticket tools belong to an account only the outgoing organiser can open. Use individual authorised access and the appropriate process for changing it when assignments end.

For ticket operations, Loopyah lets you add event admins and door staff without sharing your login. Door staff can receive check-in-only access and scan QR tickets from their phones. Confirm the access assigned to the incoming team, then brief the separate decisions they must refer, such as an unresolved ticket exception.

Don't paste a full attendee or order export into the control log simply because someone may ask a ticket question. Give authorised staff access to the relevant working record and record the operational follow-up needed at control. The replacement needs to know who is handling the case and what remains outstanding.

Attendee communications deserve their own status. A proposed change, approved wording, completed send and recipient acknowledgment are different facts. Record the ones your event actually requires and avoid marking the entire issue complete while an important action remains unconfirmed.

Loopyah's attendee email tools support event updates and sending yourself a test before the audience receives the message. That helps the team check the actual message. Your event still needs a named person approving a consequential change, someone responsible for the send and an appropriate onsite route for people who haven't read email.

For Nia's fictional workshop update, the useful handover entry records the approved 17:45 start, who approved it and the actual send confirmation. It also points Ben to Jo's staff acknowledgment. The handover doesn't need another manually maintained copy of every recipient's contact details.

Keep restricted incident details with the right people

An operational handover may need to say that a welfare matter remains active and identify the responsible provider. It doesn't follow that every controller, supplier and group-chat member needs the person's medical history. Decide the access arrangement with the organisations responsible for those records.

The UK Information Commissioner's Office describes data minimisation as keeping personal information sufficient, relevant and limited to its purpose. Its guidance is under review following UK legislative changes. Check the requirements applying to your event and the information involved, especially where specialist providers hold their own records.

In the general handover, reference the restricted record and say what the coordinating lead needs to do. That might be maintaining contact with the medical lead or preserving an agreed operational restriction. Share the necessary details through the authorised route with people who need them to carry out their role.

Our event incident report guide covers recording the incident itself. The shift summary should reference that record and show the unfinished coordination work. Rewriting the incident into several separate summaries makes corrections harder and can circulate personal information beyond its intended recipients.

Use the same care with staff contact details, access credentials and sensitive site information. Don't put passwords into the handover form or announce private details over an open channel. Confirm the incoming person can use the authorised route instead of copying everything into whatever chat happens to be convenient.

Agree retention and access changes through your normal record process. Keep information required for legitimate follow-up, applicable duties or a relevant preservation requirement, and remove unnecessary copies through that process. An outgoing worker shouldn't have to keep a private archive on their phone so the business can reconstruct its own operation.

Handle a late replacement without inventing acceptance

If the replacement is late, activate the arrangement you agreed before the event. Name the person arranging competent cover and confirm what happens to the affected work. The schedule's transfer time is an intention. It doesn't establish that someone who hasn't arrived has accepted responsibility.

Record the actual position. The outgoing lead may continue temporarily only where that is an agreed, suitable arrangement. Alternatively, another authorised person may accept specified duties after the necessary briefing. If the required coverage cannot be provided, the responsible people must decide what can continue under the event's plans and duties.

A remote exchange may sometimes be part of your agreed arrangement, but assess what the replacement can actually do from that position. Can they reach the teams, access the current information and carry out the assigned role? A phone call doesn't compensate for a responsibility that requires competent presence at the venue.

When a substitute arrives, give them the current handover and the event-specific preparation they need. Having worked at last year's festival doesn't establish that they know today's restrictions, contacts or authority. Adjust the exchange to their actual knowledge rather than rushing them through the same words you prepared for someone else.

Also plan the return from short cover. If Ben temporarily hands coordination to a deputy during a break, the record and affected teams need to know when the deputy accepts and when Ben takes the duties back. Two names on the roster don't explain which one is coordinating a decision right now.

If an incident interrupts the handover, keep the response clear

A serious developing situation takes priority over finishing a routine form. Staff must follow the agreed emergency arrangements, including raising the alarm and summoning urgent help where appropriate. Nobody should wait for a handover signature before taking those actions.

HSE's event emergency guidance calls for clear responsibilities, staff understanding of emergency instructions and tested communications. It also discusses coordination with responding services. Have the people responsible for your event define how routine control, specialist responsibilities and incident authority relate, including any required transfer to emergency responders.

During an interrupted shift change, make the current arrangement explicit through that plan. Is the outgoing lead continuing the coordinating role while the replacement supports? Has an authorised deputy accepted it? Has incident authority changed under the emergency arrangements? Record the actual facts when practicable without delaying the response.

Don't improvise a second command structure because a more senior person has entered the room. A founder can contribute information and still need to work through the agreed coordination. Likewise, an incoming producer's routine commercial permission doesn't give them authority over professional decisions belonging to responders or specialist providers.

When a transfer can proceed, brief the current incident position with the relevant leads. Include actions underway, restrictions, outstanding requests and the next decisions. Preserve relevant records and identify what remains uncertain. The incoming person needs the situation as it now stands, including changes made after the first draft handover.

Afterwards, reconcile any notes made during the interruption into the controlled record without rewriting the history. Distinguish when an event happened from when someone entered it into the log. If an earlier entry was wrong, correct it transparently through the system's process rather than making the original uncertainty disappear.

Test the awkward parts before the event

Run a practice handover with the people who will use it. Give the outgoing lead a realistic open issue, a message awaiting confirmation and a report that conflicts with the summary. Ask the incoming lead to explain their next action and the limits of what they can decide.

The contradiction is useful. Perhaps the supplier says "delivered" while production says the equipment hasn't been accepted. Can the team keep the item open and find the right confirmation? If everyone is satisfied with a tick beside the word delivery, revise the entry before the actual event relies on it.

Test a missing person and a failed communication route too. Follow the agreed fallback far enough to establish that the backup is available and has the necessary access. You don't need to create a real disruption. You do need more evidence than the outgoing lead saying they can probably be reached if something happens.

After the event, review specific handovers against what the next shift encountered. Look for repeated calls to off-duty staff, instructions that weren't acknowledged, restrictions mistakenly treated as cleared and commitments counted twice. Ask the people receiving the handover which missing fact delayed their first useful decision.

Change the record and preparation around those findings. An extra signature won't fix a missing contact route. A longer log won't fix contradictory authority. Sometimes the necessary change is more overlap, a different transfer time or a properly available relief person, and that needs to be reflected in the next booking.

Before the next live shift, ask the incoming lead to find the current restriction, the next outstanding decision and the person responsible for it. Then confirm how they accept the coordinating duties and how affected teams hear about the change. Resolve any disagreement while both leads and the relevant departments are still available.