Shift handover notes: a simple template for the next person

“Printer still broken” tells the next person there is a problem. “Printer offline. IT ticket sent. Use reception printer until fixed” gives them a starting point. A useful handover note makes the next action clear without asking someone to reconstruct your whole shift.

This guide covers everyday operational tasks such as room preparation, equipment returns and maintenance follow-ups. Clinical handovers and other required records belong in your organization’s approved systems and procedures.

What a handover needs to answer

The next person needs to know what is happening now, what you have already done and what still needs attention. A chronological work log is useful source material, but a handover is a selected summary of the items that matter next.

Start with unresolved items. Include a completed task when it changes what the next person should do, such as a room being ready again. Routine details that no longer affect the next shift can stay in the underlying log.

A shift handover template to copy

• Shift or date:
• Area, room or task:
• Current status:
• Action already taken:
• Next step:
• Owner or team to contact:
• Next check or agreed deadline:
• Confirmation still needed:

Use the names and location labels your team recognizes. If nobody has accepted an action, write “owner to confirm” rather than assigning responsibility by assumption. A named person in a note is not proof that they have received it.

Filled example: clinic administration

These events and times are fictional. The example concerns clinic administration, with no patient information.

• 13:40, Room 2: restocked and ready for afternoon clinic. No further supply top-up needed before opening.
• 13:45, office printer: still offline. IT ticket sent. Reception printer available as a temporary alternative.
• Next step: afternoon coordinator to check the IT response at 15:00; acceptance of this task still to confirm.
• Equipment: spare cuff returned to the cupboard in Room 2.

The printer entry distinguishes the status from the action. “Ticket sent” does not mean “printer fixed.” The final line gives the next person a location instead of another search.

Keep observation, action and uncertainty separate

Write what you know, then what you did. “No reply received by 13:45” is more precise than “IT is ignoring this.” If you did not check something, say that instead of describing it as complete.

When writing after an event, include the event time in the note if it matters. The time a note was saved and the time something happened can be different. A timestamp supports the sequence; it does not confirm that a task was completed or a handover was received.

Prepare the summary from short Lognote entries

Keep brief operational notes together in a group, for example “Clinic shift.” Classic view places the date and time beside your entries. A consistent hashtag such as #followup can mark items you want to return to; avoid creating a new tag for every small variation.

At the end of the shift, read the relevant entries and write a short handover summary. Check whether open items have changed since the original note. Share the necessary information through the process your organization uses, and confirm receipt where required. Writing a personal note does not notify the next shift automatically.

For the capture routine, see how to organize notes with hashtags. For a specific event, use the incident log template.

Before you finish the handover

• Can the next person identify the location or task?
• Is the current status different from the action already taken?
• Is the next step specific enough to carry out?
• Are the owner and next check agreed, or clearly marked as unconfirmed?
• Does the recipient know where the handover is and what needs a response?

Start small: one clear update for the next person is more useful than a long list of unexplained fragments. Get Lognote to try a dated group of operational notes and build your summary from what you recorded.