A clear shift handover

A handover is a snapshot of what the next person needs to know, not a history of everything that happened. Begin with the service, project or location and the time covered. Include the time zone when people work in different places. State who is receiving the handover through an appropriate internal channel, rather than adding unnecessary contact details to a shared paste. List current problems in order of urgency. For each one, record the observed behavior, the latest action and the next check. Distinguish something you verified from something another person reported. If a system is working normally, a short confirmation is enough; do not hide important unresolved work in a long list of routine checks. Record any upcoming deadline or scheduled change that may affect the next shift. Include a ticket reference where your team already has a secure system of record. Do not copy passwords, session cookies, access tokens or full customer records into the handover. Replace them with a reference to the approved internal location. Before finishing, review whether the receiving person can identify the first task without calling you. Make each action specific and include a checkpoint. When a shared link is no longer needed, delete the account-owned paste or let its chosen expiration take effect. Keep permanent operational records in the system your organization uses for that purpose.

Handover: [service or project]
Period: [start - end, time zone]

Current status
[short summary]

Priority items
1. [issue]
   Last action: [what was done]
   Next check: [action and time]
   Reference: [ticket ID]

Upcoming changes
- [change and owner]

Routine checks completed
- [check and outcome]