Back to Glossary

Entry · Business

Shift Handover

Shift handover is the deliberate transfer of current work status, risks and pending actions from outgoing staff to the incoming team. It includes a chance to ask questions and verify critical facts, not just a document left at a workstation.

From the Money Master HQ dictionary, founded by Shihan Sheriff (FCMA, VP of Finance at Nomod, CFO at Esanjo Ventures). How these definitions are written.

What it means

Work often continues after one person's shift ends, so the next team needs to know what is running, what changed and what requires action, and an incomplete handover can cause missed service or unsafe decisions. A fictional factory operator tells the next shift that one machine is stopped for maintenance and its lockout remains active, and the incoming operator checks the status before restarting anything.

Prepare before shift change by updating the log, identifying exceptions and distinguishing finished work from work in progress, because a rushed memory dump can miss the most important fact. The UK Health and Safety Executive describes preparation, an information exchange and incoming cross-checking as elements of effective handover, and its safety guidance favours two-way verbal and written communication while warning that missing or inaccurate information can undermine the process.

It recommends clarification and enough time, though specific workplace procedures should fit the risk and local operating rules still apply. Support discussion with a durable log, since spoken details may be forgotten while a written record may not reveal misunderstandings, as when a fictional hospital team records a pending test and discusses its urgency at the bedside under the applicable clinical protocol.

State current equipment or service condition, not only what happened earlier, because "pump inspected" does not say whether it is safe to operate now; a fictional technician reports that a valve was tested but remains isolated pending a second reading. Assign owners to pending tasks, since a note saying "check tomorrow" without a person or deadline can be ignored, as when a fictional customer complaint needs a callback by noon and the incoming support lead accepts ownership and sees the case reference.

Use timestamps and identifiers so a pending shipment, case or machine is traceable to the right record, because a vague "the big order" can point to the wrong customer. Highlight safety-critical deviations, temporary workarounds and permits, because a normal-looking display may hide an overridden alarm or out-of-service guard, as when a fictional plant has a temporary bypass approved for maintenance and the next shift receives the permit status and checks the physical controls.

Avoid flooding the handover with irrelevant detail, focusing on changes, exceptions and decisions while keeping full records available, because too much text can bury a critical warning. Do not mark work complete to make the outgoing shift look good: a fictional operator reports a test as pending rather than ticked off, and the incoming technician finishes it and records the result.

Incoming staff should verify critical status instead of assuming the log is current, since conditions can change during the overlap, and a fictional outgoing worker who says "the job is fine" should be asked whether testing and customer approval are complete. Escalation should be explicit: if the next team lacks skills or authority to handle a risk, name the person to contact, because a handover is not a way to transfer responsibility into a void, as when a fictional night shift lacks a qualified electrician and the outgoing lead contacts the on-call specialist about an unresolved electrical fault.

Plan enough overlap for complex handovers so that staff have time for the exchange and the checks. Digital tools can help, but version control matters, because a stale dashboard or unsynced note may be worse than a clear paper log, so show who updated the record and when.

Handover should include customer commitments such as a callback or promised delivery, with the exact deadline and owner, and recurring handover failures can point to a badly designed form or unclear process rather than individual carelessness, so ask incoming users what they need. For regulated and safety-critical work, follow the specific mandated handover protocol, because a generic checklist cannot replace specialised training or legal duties, and a shift handover succeeds when the next team knows what remains, what is risky and who is responsible.

In practice

Real-world examples.

1

Example

A maintenance lockout is verified at shift change in a factory. The outgoing technician names the machine, the permit and the isolation point, and the incoming technician checks the lock in person before signing the log. The machine stays stopped until the second reading is complete.

2

Example

A customer callback in a support centre receives a named owner and a noon deadline. The incoming lead accepts it, sees the case reference and records the outcome after the call. Nothing depends on someone remembering a verbal remark.

3

Example

An incoming operator at a utility cross-checks a stale outage status on the live system rather than trusting the earlier log entry. The check shows that supply has been restored on one feeder. The operator updates the log with the time and source.

Case study

Seen in the real world.

In this fictional case, the day team at Ridge Works leaves a pump isolated after a failed test. Its handover names the asset, permit and pending second reading. The night lead reviews the log face-to-face and verifies the isolation before assigning the test.

The pump is not restarted merely because the shift changed. Afterwards the supervisors add a short overlap and a field for the next action and owner, so that every open item on the log names a person. They review a sample of handovers each month and record missed actions separately from routine omissions.

Watch out

Common mistakes.

  • Leaving a long log without discussing the critical exception.
  • Writing a pending task with no owner.
  • Assuming a prior status remains true without checking.

Questions

People also ask.

Is a written log enough?

For consequential work, two-way discussion and verification often matter too.

Who owns an unfinished task?

Name the incoming owner and escalation route clearly.

What should be prioritised?

Current risks, changes, pending decisions and customer commitments.

Was this explanation helpful?

From the founder's library

Accounting Fundamentals: A Non-Finance Manager's Guide to Finance and Accounting, by Shihan Sheriff

Take it further with the book.

Build your financial confidence beyond this definition. Shihan's full-length guide, Accounting Fundamentals, takes the same plain-English approach and turns it into a complete, practical playbook for non-finance managers, business owners and students - with chapter-end quiz answers and presentation slides included.

US$2.24US$2.99

25% off with code MMHQ25, applied at checkout. Priced in USD - checkout may show the equivalent in your local currency.

View the book and save 25%
Last updated · October 8, 2026
Browse all terms →

Disclaimer

The information provided in this finance dictionary is for educational and informational purposes only. It should not be construed as financial, investment, legal, or tax advice. Always consult with a qualified professional before making any financial decisions. Money Master HQ makes no representations or warranties about the accuracy, completeness, or suitability of this information. Use of this content is at your own risk.