You said shift handovers were uneven. Here is what we did.

As of 15 June 2026. This sample page follows Northstar Services, a fictional organization, after its March listening exercise. 412 colleagues at all 9 sites took part, in the survey and in 14 site sessions, not only at head office.

Below: what we heard, the actions taken, what still needs more work, and when to expect the next update (14 September 2026). Each entry is marked Done, In progress or Not yet resolved.

An operations floor mid-shift

From feedback to action

  1. You said: handovers depend on who you follow

    Colleagues described notes that arrive in different formats, in different places, and sometimes not at all. One night-shift comment: "We find out about a stuck dock door at 10 pm, after the day team has gone home." The survey and 14 site sessions closed on 27 March.

  2. Done: themes shared back with site leads

    Employee Experience grouped the comments into three themes: handover gaps, late schedule-change notices, and unclear local decision-makers. Site leads chose handovers as the first priority, since it was the most common theme.

  3. Done: shared handover note started in two teams

    Dispatch Planning and Customer Support Tier 1 began using one handover note with four fields: open issues, commitments due next shift, equipment status, and who to contact. The outgoing lead completes it before the last 15 minutes of the shift. The incoming lead replies "received" in the team channel.

  4. Done: schedule changes posted with a reason

    Team leaders now post each approved schedule change in the team channel on the day it is approved, with a one-line reason. This answers the second theme in part. It does not set a minimum notice period.

  5. In progress: site discussions on local routines

    Three sites with short or no shift overlap are discussing how the note could work for them. Sessions run 22 June to 17 July. No decision has been made about extending the note to other teams.

  6. Next update

    We will report what the two pilot teams found, what the three sites decided, and whether the decision-maker question (the third theme) has a first action.

What we heard, in sample numbers

Illustrative sample figures written for this example, not live results. Collection period: 2–27 March 2026. 1,180 colleagues invited. A response could name more than one theme, so the theme counts do not add up to 412.

412
Responses received
35% of the 1,180 colleagues invited, across 9 sites
169
Mentioned handover gaps
41% of the 412 responses
111
Mentioned late schedule-change notices
27% of the 412 responses
74
Mentioned unclear local decision-makers
18% of the 412 responses

What changed, and what is still open

Take the stuck dock door. The new note gives it a place in the "equipment status" field. The shift that sees the problem can pass it on without relying on a phone call.

What changed

In the two pilot teams, shift-to-shift information now follows one format.

  • The handover note has four fields: open issues, commitments due next shift, equipment status and who to contact.
  • The outgoing lead completes the note before the last 15 minutes of the shift.
  • The incoming lead replies "received" in the team channel, so the sender knows it was read.
  • Schedule changes are posted in the team channel the day they are approved, with a reason.

What still needs work, and why

One format does not fit every site yet, so the note has not been extended beyond the two pilot teams.

  • Three sites have little or no overlap between shifts, so there is no time to hand over in person or read a note together.
  • Some sites keep their own paper logs. Whether the note replaces, adds to or links to them is undecided.
  • Schedule changes are posted with a reason, but no minimum notice period has been agreed.
  • The decision-maker theme has no action yet. Site discussions run 22 June to 17 July.

Why we are testing before standardizing

A good handover should not depend on which colleague you happen to follow. Two teams are trying one note format first. We would rather get it right at each site than announce a standard that does not fit your shift.

Fictional example: Vice President, Operations
Illustrative statement written for this sample page, not a real quotation

Who owns this, and where corrections go

Employee Experience team
Owns this page and the response. Send corrections or missing context here; the team reviews the page before each update date and whenever an action changes status.
Employee Experience
Site listening contributor
Each site has one. They bring local routines to the site discussions, so ask yours to raise anything this page misses about your shift or location.
Local site
Your team leader
For day-to-day questions about the handover note or posted schedule changes in your own team.
Operations