Before your vacation, appoint someone to read website notifications and start investigating issues. Give them the URLs of important pages, the contacts for service providers, and the limits of what they can decide on their own. An active subscription does not replace this arrangement.
Pay special attention to the dates you’ll be away: the developer, owner, and support team may have different days off. If everyone expects to contact one person who will be offline, there will be no one to pass the problem on to.
Prepare a checklist for specific dates
Below is a sample for a service-booking website. Replace the names and URLs with real ones; keep the contact details somewhere the team can access.
| What the backup needs | Details |
|---|---|
| Period | 31 December — 8 January |
| Who starts investigating | Igor, working hours 10:00–18:00 |
| If Igor is unavailable | The owner, via the agreed communication channel |
| What to open if there’s a problem | Home page, /appointment, /contacts |
| Technical contact | Developer; save the ticket number in the shared task |
| Who approves an urgent publication | The owner, or a process agreed in advance with the developer |
The subscription does not create an on-call schedule based on this table. This is an arrangement you make yourselves. If there is no response at night, say so explicitly so everyone has the same understanding of working hours.
Confirm the business’s holiday schedule. The form may accept requests while the office is closed, and a staff member can process them later. State the actual response times on the website. This is a content change, not a reason to disable technical monitoring.
Check contacts and access to information
Ask the backup to find the hosting provider’s or developer’s contact details and understand how to open a ticket. “Message the usual programmer” won’t help someone who doesn’t know who that is.
Specify who has the access they need. The backup does not necessarily need full server permissions: they may only need to check the URL and pass on the facts. But the service provider should be able to start work without waiting for you to return.
Check whether the backup can view the data or get the necessary report from the account owner. Do not assume that reChecker automatically creates a separate team role for them. You do not need to publish a private report for everyone just to include it in a vacation checklist.
Confirm notifications and walk through the first investigation
In the Website Monitoring dashboard, open the website, then “Settings” and “Where to send notifications.” Check Telegram or Email and the recipients’ addresses. After changing the channel, ask the backup to confirm receipt of a specific new message.
If no relevant event has occurred yet, note that delivery has not been tested and agree to check the dashboard directly. The Telegram setup process is described in the setup instructions. There is no need to take the website offline to test it.
Show them one saved event. Have the backup find the URL and time, open the page, and name the service provider. This will show whether the checklist is clear. For an outage, use the owner’s first-response steps; a new audit finding can be added to the next plan if it is not affecting visitors right now.
Agree on how to record actions and hand over after the holidays
In the shared task, record the time, the observed response, the service provider’s name, and the next response deadline. If someone is already investigating the problem, the backup should be able to see that before making parallel changes.
Example entry: “03.01 at 11:20 /appointment did not open; the home page works. The developer has accepted the ticket; a response is expected at 12:00. No changes were made independently.” After the issue is resolved, add who checked the original URL and how.
When you return, review the open items. If the website has been restored but the cause is still being investigated, hand the task back to the usual person responsible. Update the checklist if a contact was unavailable or a step was unclear. Before your next vacation, you only need to verify any changes to the dates, people, and channels—not write everything again.