Skip to content

On-call handover

Hand the pager over cleanly: open incidents, recent changes, noisy alerts and what to watch.

Fill it in and preview

On-call handover

Service: Payments platform
Handing over: Sam Okafor
Taking over: Hamza Idrissi
Handover time: Monday 14 January 2030, 09:00 UTC
Period covered: 7 to 14 January

1. Open incidents

Incident What State Next step
INC-2041 Slow card checks in the evening Mitigated, cause not found Next step: trace on Tuesday 18:00

2. Incidents closed this period

Incident What Fix Follow-up
INC-2037 Email provider timeout Fixed by a longer retry Follow-up ticket DEV-512

3. Changes

When Change
Wed Database upgrade to the new minor version, watch query times
Thu Rollout of new fraud rules at 10 percent
Sat 02:00 Planned maintenance on the queue

4. Alerts

Disk warning on batch-3 fires at night during backups. It clears by itself within 20 minutes.

5. What to watch

Checkout error rate (normal under 0.3 percent)
Queue delay (normal under 5 seconds)
Partner API status page, they have had two short outages

6. Follow-ups

Check the trace for INC-2041 after the evening peak.
Confirm the backup alert fix is merged.

7. Contacts

For Who to call
Database help Anna Berg, +44 7700 900123
Partner contact Maria Costa
Escalation Engineering manager on call

8. Useful links

Dashboards, runbooks and the incident channel.

Confirmation

The person taking over confirms they have read this note and can be reached for questions.

______________________ Hamza Idrissi

Templates are a careful starting point, not legal advice. Where the law matters, check what applies where you are.

IT and projects

What this template is for

An on-call handover note for engineers changing shift. Record open incidents, risky changes, alerts, follow-ups and contacts so nothing is lost. Word or PDF.

It is free to fill in online, needs no account, and downloads as a Word document or a PDF. See all IT and projects templates

IT and projects

What you fill in

The form asks for 13 details. The document fills itself in as you type.

  • Service or team

    For example: Payments platform

  • Handing over

    For example: Sam Okafor

  • Taking over

    For example: Hamza Idrissi

  • Handover date and time

    For example: Monday 14 January 2030, 09:00 UTC

  • Period this note covers

    For example: 7 to 14 January

  • Open incidents

    Write none if there are none. One row for each incident.

    For example: INC-2041 | Slow card checks in the evening | Mitigated, cause not found | Next step: trace on Tuesday 18:00

  • Incidents closed this week (optional)optional

    One row for each incident.

    For example: INC-2037 | Email provider timeout | Fixed by a longer retry | Follow-up ticket DEV-512

  • Recent and upcoming changes

    One row for each change.

    For example: Wed | Database upgrade to the new minor version, watch query times Thu | Rollout of new fraud rules at 10 percent Sat 02:00 | Planned maintenance on the queue

  • Alerts that are noisy or can be ignored (optional)optional

    For example: Disk warning on batch-3 fires at night during backups. It clears by itself within 20 minutes.

  • What to watch

    For example: Checkout error rate (normal under 0.3 percent) Queue delay (normal under 5 seconds) Partner API status page, they have had two short outages

  • Follow-ups left for you (optional)optional

    For example: Check the trace for INC-2041 after the evening peak. Confirm the backup alert fix is merged.

  • Who to call

    One row for each contact.

    For example: Database help | Anna Berg, +44 7700 900123 Partner contact | Maria Costa Escalation | Engineering manager on call

  • Useful links (optional)optional

    For example: Dashboards, runbooks and the incident channel.

IT and projects

What is inside

The parts of this document, in order.

  1. 11. Open incidents
  2. 22. Incidents closed this period
  3. 33. Changes
  4. 44. Alerts
  5. 55. What to watch
  6. 66. Follow-ups
  7. 77. Contacts
  8. 88. Useful links
  9. 9Confirmation

Templates

How it works

  1. 01

    Fill in

    Type your details in the form. The document fills itself in as you type; click any gap to jump to its field.

  2. 02

    Check

    Read it through. Gaps you have not filled stay marked, so nothing goes out half done.

  3. 03

    Download

    Save it as a Word document to edit further, or as a PDF to send or print.

Make it yours with AI

Open it in the chat and ask for changes: shorter, firmer, another situation, another language.

Adapt it with nerix

IT and projects

Questions people ask

What details does this template ask for?

The form asks for 13 details, starting with Service or team, Handing over, Taking over, Handover date and time, Period this note covers. 4 more are optional.

Can I download this template as Word or PDF?

Yes. When you have filled in the form, save it as a Word document to keep editing, or as a PDF to send or print. It is free and needs no account.

Is what I type sent anywhere?

No. What you type stays in your browser while you fill in the document. It only goes to nerix if you choose to open the template in the chat.

Are these IT and project templates free?

Most are. Fill in and download them for free as Word or PDF, with no account. A few longer documents are premium: free to fill in, paid once to download, and marked with their price.

Does a security policy make us secure?

No document does that alone. A policy helps when it matches what people really do, so keep it short, explain it to your team and review it every year.

Is a project charter only for large projects?

No. A small project benefits too, because one page that names the goal, the limits and the decision maker prevents most arguments later.