Skip to content
Interface language: English
Imperium / Signal

The shift ends, but the case does not: how the next person takes over

Pass an open case to the next shift with its current state, next action and deadline, without making the customer repeat the story.

Article language: English

A woman in a red apron beside a round glass lens in a gold-coloured housing.
In this article

At 16:58 a customer sends the missing attachment. At 17:00 the person who has worked on the case since morning finishes their shift. At 17:12 the next shift asks the customer for the same file. The attachment exists. What has been lost is its purpose: why it was needed, who was supposed to check it, and what was promised after that check.

That is a poor handover of a case in progress. The message history may be complete, yet the next person still has to reconstruct it from the beginning. A change of staff requires a state that allows someone to act. This applies to a service desk, event support or an office receiving requests over extended hours. “I'm keeping an eye on it” has a surprisingly short life after its author logs out.

The incoming person needs to know what they are taking over

Consider a fictional company that rents conference equipment. A customer reports a missing item from a set. The first shift checks the list, asks for a photograph and agrees to contact the customer before the event begins. The next person does not need the entire negotiation history. They do need to know what is missing, what is confirmed and which deadline matters to the customer.

HSE describes shift handover as preparation by the outgoing person, an exchange of information and checking by the incoming person. The material concerns human factors in settings with particular safety requirements. An ordinary service team can use that distinction while adapting the form to its work.

Preparation without acceptance can end in a polished note nobody reads. Acceptance without checking may only confirm that a file exists. In this example, the incoming person should be able to say: we are waiting for the photograph; once it arrives I will check completeness; the customer needs an answer before a specified time. That makes a misunderstanding visible.

A project handover between teams (in Polish) often transfers responsibility for a larger phase. A shift has a shorter rhythm: the same case stays open while the person handling it changes. A daily handover should therefore preserve what enables the next action, without requiring a miniature final report.

The latest message does not always describe the current state

The 16:58 attachment may be called “photograph”, but its title does not say whether it satisfies the earlier request. Add a short account after the last significant change. “Photograph received, not yet checked” is different from “photograph confirms the missing item”. The distinction prevents a customer from receiving a conclusion nobody has reached.

Separate facts, things being awaited and future commitments. Receiving the material is a fact. A supplier's reply may be awaited. The next contact with the customer is a commitment. If all three become “in progress”, the next person cannot tell whether to act, wait or remind someone of a deadline.

Four questions help describe an active case:

  • What is confirmed, and where is the supporting information?
  • What can be done next?
  • If the step is blocked, whose answer are we waiting for?
  • When should the state be checked or the customer contacted again?

The answers can be short. Two sentences and a reference to the material may suffice for the conference set. An elaborate template does not help if completed once in the morning and left behind as events change. Update the record after an event changes the possible action, rather than adding ever more mandatory fields.

Include arrangements that have ceased to apply. If a customer was to send a photograph but the business later obtained the information another way, the next person needs the current condition. Otherwise they may repeat an unnecessary request because it was prominent early in the history. A well-written old point can obscure a brief later correction.

Check events from the last minutes before the changeover. A new response may arrive after the note was prepared. Both people should know up to what point the state was checked and where later messages appear. The aim is not to copy a timestamp into every sentence. It is to avoid a gap in which each person assumes the other checked the new material. If automated events update the status, see late information and the order of status changes (in Polish), so an older record does not overwrite the current state.

Acceptance of the case should be visible

In Google SRE's chapter on managing incidents, transferring the incident commander role calls for an explicit handoff, firm acknowledgement from the successor and informing the participants. This is an example from technical incident response. Its useful feature is removing doubt about whether the next person actually accepted the lead.

Our office can use a simpler equivalent: the person starting the shift confirms the open cases they have taken over and raises questions. Sending a group message alone does not prove someone has accepted the work. In a group of six, name a lead so everyone is not waiting for everyone else.

Confirmation belongs where both shifts actually look. If cases are managed in a shared application, a private chat can make the handover harder to reconstruct. If the team uses a simple list, it need not buy a platform just for an “I accept” button. First agree who confirms understanding of the next action and when.

Allow a short conversation when something is unclear. Writing carries decisions well, but another comment is not always the fastest way to resolve a discrepancy. Decide in advance which situations require a joint check before the shift ends: conflicting information, an important deadline or a contact that cannot be reconstructed from the record.

Aeneia conceptual photography

If shifts do not overlap, choose an acknowledgement that can be made after the incoming person starts work. They can mark the cases reviewed and report anything that prevents progress. The business should decide beforehand where they can get help. Requiring a live conversation will not work when the previous person is already unavailable; the handover method must fit the actual rota.

When several people are involved, record who contacts the customer. Two people may help internally, but sending conflicting updates five minutes apart creates a new problem. The lead should see the result of a consultation before updating the customer. If the lead changes again, that new assignment also needs acceptance.

Open cases need an order of attention

With ten cases, the incoming person needs to see which requires the earliest response. The order of the latest messages may not be the right work order. A case with no new comment may have a deadline in twenty minutes. Another with five new attachments may safely wait until tomorrow if no earlier answer was promised.

Do not confuse a customer's urgency with readiness to act. Chasing a supplier does not replace checking material that has already arrived. The incoming person needs to know what they can influence now. This relates to a team status that helps action (in Polish): the state should reveal where intervention is needed, not merely show that a case exists.

Mark what can wait until a particular time. If an answer is expected tomorrow, the next shift should not send the same request every hour. The handover should preserve the meaning of the existing arrangement. The customer should not have to renegotiate the contact rhythm at every change of staff.

Work waiting for the customer (in Polish) needs particular attention. “Waiting” is not enough. State what is missing, whether the request was sent and what happens when the material arrives. Only then can a new attachment trigger the right step instead of entering a file store called “to review”.

Pass on a significant unsuccessful attempt too. If a team checked and ruled out an option on a specific basis, the next shift need not start there again. In the rental example, one warehouse may have confirmed it lacks the item. That matters to the next action, although it does not yet resolve the customer's case. Recording the basis also helps reveal if the condition has since changed.

The first message after takeover can refer to the present need: we received the photograph, the item is being checked and we will return to you as agreed. The new person need not introduce themselves as if the whole service process were starting again. If the contact or handling changes, however, give the customer the information they need. Continuity is about delivering the service, not knowing the internal rota.

An automated summary needs review too

An AI tool can draft the state from a conversation history. A person should check that it distinguishes fact from intention and preserves the current deadline. An old promise can appear more definite in a summary than a later correction. No answer in one channel can become “no contact” across the whole case.

For a trial, choose several real cases appropriately available for that purpose and compare the summary with the source. Look for differences that affect the next action. Attractive prose is not enough. In the conference set, “the customer confirmed the set is complete” differs from “the customer is to confirm the set is complete”. One word changes what the team does next.

Aeneia Audit may help examine AI use in such a workflow: what data reaches the tool, how the summary is produced and who checks it. Begin with one handover the team can reconstruct from its sources. That evaluates the actual path of information, not just the impression left by a demonstration.

Preserving the basis of a summary does not mean copying all data into every record. The guide to AI logs without excess data (in Polish) is relevant. The incoming person needs access to the right source within the appropriate scope. Copying customer data into several tools can make control harder rather than easier.

Record omissions when comparing a tool's output with its sources. A summary may contain no false sentence yet omit the next contact deadline. The reader then gets an accurate account of the past without the information needed to work. Review should cover both the accuracy of recorded facts and the presence of what the next person needs.

Check one handover from the outcome backwards

Choose a completed case and ask the next shift what their first step was based on. Did they find the current state? Did they have to call the previous person? Did the customer repeat something already known? These questions reveal reconstruction work that the number of closed cases does not show.

If the predecessor's help is regularly needed, check whether the issue is the record, access or ability to perform the task. A shift can reveal dependence on one person (in Polish), which a more detailed summary alone will not fix. An internal services catalogue (in Polish) can indicate where to consult when a case exceeds the current team's competence.

At the next trial, check only the selected improvement. Perhaps it is enough to add that material received still needs verification. Perhaps acceptance of a case with a running deadline needs to be explicit. The result should be a way to continue service without guessing. At 17:12 the customer should receive a response to the 16:58 attachment, not a ceremonial request to send it again.

Aeneia / Aeneia editorial

Editorial article. Source links are included in the text.

About Aeneia

Brands we have worked with

  • L’Oréal
  • Garnier
  • Netflix
  • Carrefour
  • Warner Bros. Discovery
  • Biedronka
  • HBO Max
  • Wolt
  • Żabka
  • COSRX
  • Embassy of China in Poland
  • Mixa
Aeneia / Initium

From knowledge to a decision

Tell us what you want to put in order. We will agree on where to start.

Contact Aeneia

We partner with and use solutions from:

  • Google
  • OpenAI
  • Microsoft
  • Stripe
  • Anthropic
  • Linear