Table of Contents

• Start with the boundary, not the entire shift
• Give slippery words a local definition
• Agree what the receiver needs to accept
• Rewrite a handover that sounds finished
• Make “not accepted yet” an ordinary answer
• Try it on one transfer and inspect the result
• Frequently Asked Questions

Last Updated: November 3, 2026

The order is ready. Excellent. Ready to pack, ready to collect, ready for someone to approve, or ready in the optimistic sense that it will probably be ready soon?

A cross-department handover can contain perfectly ordinary words and still leave two teams with different instructions. The awkward bit is often the boundary between their jobs: one department has finished its part, while the next cannot yet begin.

This is a practical way to agree what must be true before work passes across that boundary. It suits early, late, rotating and night shifts wherever different functions need to work together. Use it alongside your organisation’s procedures, especially where safety, permits or formal authorisation are involved.

Start with the boundary, not the entire shift

Choose one recurring transfer: an approved design going to production, a prepared order going to dispatch, or a maintenance job being returned to operations. Trying to redesign every handover in the organisation before breakfast is an ambitious hobby.

Write two sentences: “Our part ends when…” and “Your part can start when…”. Compare the answers. The gap between them is the useful finding.

The Health and Safety Executive’s handover guidance explicitly includes transfers between different functions during a shift, such as operations and maintenance. It recommends an exchange that allows the receiving team to check the information. A message arriving in an inbox is not, by itself, that check.

For this exercise, ask people who actually receive the work to describe what prevents them starting. Their answer may be a missing attachment, a physical access condition or an unresolved decision rather than a longer report.

Give slippery words a local definition

Make a short shared vocabulary for the transfer you have chosen. Three troublesome terms are enough to begin. These illustrative definitions are prompts for a conversation, not universal operating rules:

• Prepared: the sender has assembled the required material; the receiver has not accepted it yet.
• Accepted: the receiving function has checked that the agreed starting conditions are met.
• Complete: the named task has finished, with any remaining work stated separately.

Then test the definitions against a real-looking example. If a design is approved but its attachment is the wrong revision, is it ready for production? If a parcel is packed but its collection is unbooked, what exactly has finished?

Do not force every department to abandon useful specialist language. Translate the few terms that cross the boundary. A small glossary people use beats a magnificent dictionary nobody opens.

Agree what the receiver needs to accept

Build a tiny acceptance list around the next action. For a fictional design-to-production transfer, it might be: correct job reference, current approved drawing, required quantity and a named route for resolving discrepancies. Other workplaces will need different conditions.

The list should make a decision possible: can this work enter our process, or is something missing? Avoid requirements such as “all information included”, which merely move the argument into a larger phrase.

Separate a request from an authority. “Please proceed” does not replace a required sign-off, permit or release procedure. Where your workplace already defines the transfer, use that definition rather than inventing a convenient alternative.

Also distinguish acceptance from completion. The next department can acknowledge that it has what it needs without promising that its own work is already done.

Rewrite a handover that sounds finished

Here is a fictional, low-stakes office example. The original message says: “Print pack ready. Sent over.” The recipient finds three attachments, two versions and no quantity.

A more useful transfer might read: “Print pack for Tuesday meeting: approved PDF revision 4 is attached. Please print 12 copies. Revision 3 is superseded. Can your team confirm acceptance by 10:00? If the file will not open, contact the document owner through our usual channel.”

The improvement is not extra ceremony. It identifies the object, the version, the requested action and the condition that needs checking. The time is an example of an agreed response point, not a rule for every workplace.

For a late-to-early transfer, include the relevant date wherever “tomorrow” might be read after midnight. Keep sensitive information in the approved system, with the message pointing to it as appropriate.

Make “not accepted yet” an ordinary answer

A receiving team needs a way to return incomplete work without starting a departmental feud. Agree a factual response: “We cannot start because X is missing; the next decision belongs to Y.” That is more actionable than “Your handovers are always bad.”

Decide how genuinely urgent exceptions are escalated through existing procedures. Do not create a quiet workaround in which the receiver guesses the missing detail and the sender assumes everything went well.

If the sender has gone off shift, the record should identify the agreed contact route or responsible function. It should not depend on one person answering their personal phone while asleep.

Keep track of repeated rejection reasons. If the same attachment is missing every time, repair the transfer process rather than treating each incident as a fresh surprise.

Try it on one transfer and inspect the result

For the next few handovers of that type, ask the receiver one question: “Could you begin the intended next step without chasing an explanation?” Record what had to be clarified.

Change one definition or acceptance condition in response. Remove fields that do not help a decision. Keep those that prevent a specific misunderstanding.

The aim is not a longer handover. It is a shared answer to a very small question: when you say the work is ready, what can I now do with it?