Opens in a new tab
Commentary

Make time away work before the specialist leaves

In brief

A backup needs access, knowledge, authority and room for the work. Rehearse the transfer before leave so the service has a dependable path.

4 min read

Is this the right starting point?
Before you read
Familiarity with the team’s work and coverage arrangements; no specialist technical or wellbeing expertise is required.
What you will take away
Plan dependable time away by transferring usable access, decisions and capacity rather than only assigning a backup name.
Sources
A desk after work in Brescia, Italy, photographed by Luca Bravo in 2017.
A desk after work in Brescia, Italy, photographed by Luca Bravo in 2017. Time away depends on coverage that can operate without its absent specialist. Luca Bravo · CC0 1.0. Resized; uncropped.
On this page3 sections

The specialist is on vacation. The backup receives the page, finds the runbook and reaches a step that needs a permission only the specialist has. In this hypothetical team, the name on the calendar changed before the ability to do the work did.

Dependable time away begins with transferring that ability. Before departure, let the backup rehearse the recovery with their own account in a safe exercise or representative test environment. Confirm the necessary production access through read-only checks. A missing permission is much easier to address while there is still time to transfer it, choose another backup or adjust the service commitment.

Show colleagues where each kind of work will go

An urgent service failure needs a route to the duty responder. An ordinary request may be able to wait for working hours. Write down the distinction and where each belongs, so colleagues have somewhere useful to take the question beyond the absent person's private messages.

Ongoing investigations need a little more than a folder of links. Give the backup the current state, unresolved risks, the next consequential decision and the person able to make it. A link helps them open the material. That context helps them take up the work without asking the person on leave to explain it again.

Move responsibility before time away begins
Identify incident, approval and routine duties. Assign backup or defer work, check access, knowledge and escalation, then protect time away without depending on the absent person.
A coverage transfer includes the work and the access needed to perform it. The substitute’s ability to recover the service determines whether the absent specialist can stay off duty.
Read diagram description

A coverage-planning sequence. Transfer or defer the work and check that the substitute can actually perform it. A name on the rota is not enough if essential access is missing. Diagram labels: Responsibilities during leave: Incidents, approvals and routine work; Transfer or defer: Identify backup coverage and work that can wait; Check the handoff: Access, knowledge and escalation path; Protected time away: The service plan no longer depends on the absent person.

The messages reveal what has not transferred

Read the recurring requests with that question in mind. Several people asking for the same privileged command point toward access. Questions about the same recovery step point toward knowledge others need a chance to practise. Unclear decision authority or design knowledge can leave the team dependent on one person too.

The rehearsal makes our vacation example concrete. Can the backup complete the recovery without calling the specialist? Moving responsibility includes the authority and capability needed to answer yes. If either is missing, the team can work on that specific gap.

Then look at the backup's calendar. They might know every step and still have no room for the added work. A pager transfers a workload along with a duty. Decide which existing commitment moves before leave begins, so protecting one person's time away does not quietly consume another person's evenings.

The on-call workload review and rotation design guide connect those hours and skills to the coverage plan. Some routine work may need to wait while urgent responsibilities are covered.

Let the plan reflect the people actually available

The same reasoning applies after a disrupted shift. A night spent responding leaves a different amount of capacity for the next day's assignments. If every deadline stays fixed, the person has to find the missing hours somewhere. Adjusting the work plan makes the recovery arrangement usable.

When interruptions keep returning, follow their source. The answer may be narrower service scope, a different support-intake route, funded automation or more trained coverage. Each changes the relationship between the work and the people available to do it. Better calendar habits alone cannot fill a persistent capacity gap.

These arrangements need to remain dependable when delivery pressure rises. Leaders who use the agreed channels and honour the recovery plan make it easier for the team to know what will happen. The conversation can stay focused on coverage and work. People do not need to share unrelated personal circumstances to explain why the schedule must be workable.

Exceptional emergencies can exceed normal coverage. Define that exception narrowly and account for the additional work afterward. If reaching the person on leave becomes routine, that is information about the coverage plan that needs repair.

Before our specialist leaves, the backup can now follow the recovery, reach the right help and make room for the responsibility. The next page has somewhere to go without making the person on vacation its final dependency. Both people can plan around that.

Source context

This article does not include external reference links. Read it as the author’s perspective and evaluate the guidance against your environment.

Report an error or outdated detail

Keep reading

Where to go next