It’s December 24.
A client’s server backup fails.
The alert goes to the tech who’s already on vacation.
Who picks it up?
If a small team supports several businesses, agree on holiday coverage before clients start closing for the year. One sheet per client is enough to spell out what you cover, who responds, and when to call.
Use the checklist at the end of this article to review each client’s coverage before the holidays.
1. Agree on what the shift covers
Start with each client’s actual schedule. One office might close for the week while a branch keeps taking payments through the afternoon of December 24. Write down the dates, time zone, services that need to stay available, and agreed first-response time.
Name a primary technician, a backup, and a client contact authorized to make decisions. If you work solo, arrange any outside support in advance and agree on the coverage you can offer. Send the plan with the emergency contact channel and ask the client to confirm receipt. Guide to writing an MSP service-level agreement
Practical tip. Try a test call. If the primary technician misses the agreed acknowledgment window, the plan should tell you how to reach the backup.
2. Decide which alerts warrant a call
A billing server going down during month-end close might warrant a call right away. A powered-off laptop in a closed office can wait for the next shift. Use the impact and the client’s operating hours to make the call.
If a backup fails, check the last usable copy and how much data the client can afford to lose. If the failure puts them outside that limit, escalate as agreed. If the last copy still meets the recovery target and a retry is scheduled, assign the ticket and set a time to verify the result.
NIST recommends documenting who can act, how to assess an incident’s severity, and when to escalate. Use those criteria to draft a short list of events that warrant calling the on-call tech, such as a critical outage or a high-severity security alert. NIST incident response guidance
Practical tip. Send a test alert. Ask the primary and backup technicians where they received it and how they’d record their response.
3. Test access and recovery
Before the holidays, have the backup technician sign in with their own account and MFA, confirm they can see the right client, and find the recovery procedure. Check that they can contact the relevant vendor if they need help.
For the most critical service, run a test restore in an isolated environment. Record what you recovered, how long it took, and who verified that it worked. CISA and the FBI documented ransomware incidents over holidays and recommended keeping offline backups as part of preparation. CISA and FBI advisory · How to test a database backup
Practical tip. Put the ticket or runbook reference on the checklist. Keep credentials in the approved password manager.
4. Agree on which changes can wait
Review work that’s already scheduled. If an update requires a server reboot and nobody at the client can test the app afterward, consider moving it to January. For urgent changes, agree on who approves, how to roll back, and who verifies the service. MSP maintenance window guide and template
Practical tip. Check recurring jobs that trigger a reboot or can interrupt service. Confirm who can validate the results during the shift.
5. Give the next shift a clear action
Back to the December 24 backup. The on-call tech opens a ticket, checks the last usable copy, and assesses the impact against the client agreement. If a retry is still running, the next shift gets the ticket with a verification time, an owner, and a record of what the client already knows.
Practical tip. For each open item, write down what happened, what comes next, who owns it, and when they should check.
6. On-call checklist for each client
- Coverage. Record the dates, hours, time zone, critical services, and first-response target.
- Contacts. Confirm the primary tech, backup, and client contact who can approve changes. Test the emergency channel and agree on when to escalate.
- Alerts. Decide which alerts warrant a call and which can wait. Send a test alert and verify that the backup tech has access with their own account and MFA.
- Backups. Test a restore for the critical service. Record the result and runbook reference in the ticket.
- Changes. Review scheduled patching, reboots, and jobs. For urgent changes, confirm who approves, how to roll back, and who validates.
- Handoff. Record what the client was told and give each open item an owner, next action, and check-in time.
Keep these details where the on-call team can find them. Use Lunixar RMM to check the status and alerts of managed devices when you investigate an issue. Lunixar RMM for MSPs












