Holiday coverage starts with the promises due while people are away

Everyone has an out-of-office message. Every account has a backup. Yet the same two people are listed for most of the book, and one of them is already carrying a difficult implementation. The coverage sheet looks complete because it counts names instead of the work those names have accepted.

Plan temporary coverage around the customer decisions and promises that fall inside the absence window. Check available time and relevant skills across the substitute’s whole workload, then agree what will continue, move or require extra cover. Account ownership can remain unchanged while specific obligations transfer for a defined period.

Build the list from commitments, not account value

Start with promised responses, scheduled conversations, active recovery work, buying milestones and delivery dependencies. Include a customer whose account looks quiet but is waiting for a decision on a precise date. A high-value account without time-sensitive work may need less immediate cover than a smaller one with an unresolved commitment.

For each obligation, establish the next useful action, the customer’s timing, the expected effort and the knowledge needed. “Cover the account” is too broad. “Join Tuesday’s scope review with the current proposal and confirm the unresolved implementation dependency” gives the substitute a job they can accept or challenge.

Check the customer’s availability as well. Do not assume a local holiday closes a global customer’s operation, or that every customer wants a meeting moved earlier. Ask about timing through the normal relationship. The plan should reflect actual commitments and time zones, not a generic seasonal slowdown.

Test the substitute’s calendar as one portfolio

Combine inherited work with the substitute’s own commitments. Reserve a deliberate allowance for new requests and unexpected issues. Base estimates on the actual tasks; do not borrow a universal account-per-person ratio. A short executive conversation can require substantial preparation, while a standard status update may be straightforward.

Skill is a separate constraint. Someone with three spare hours may be unable to explain an implementation choice without a specialist. Someone who knows the customer well may lack access to the necessary records. Resolve these dependencies before the primary owner leaves rather than assuming a warm introduction is sufficient.

Keep approval authority separate from customer coverage. This plan determines who prepares, attends, follows through and escalates. It does not grant pricing, contractual or other approval rights. The substitute should know the existing decision route without becoming an improvised approver.

A fictional week has two more hours of work than cover

In a fictional team, Noor covers three colleagues during overlapping leave. After her own customer commitments and an allowance for unplanned work, she has six hours available for inherited tasks. The initial coverage list contains eight hours. All estimates are illustrative.

The manager cannot solve the shortfall by giving Noor three account names instead of eight hours. The team offers the routine check-ins a later date, subject to each customer’s agreement, and finds a qualified specialist to join Tuesday’s discussion. Noor accepts the remaining six hours only after the specialist confirms availability.

If one routine check-in cannot move, the plan needs another adjustment. If the specialist cannot attend, Noor’s spare calendar space does not make Tuesday deliverable. The manager must secure different qualified cover or discuss a revised commitment with the customer. A complete spreadsheet cannot substitute for either decision.

The primary owners prepare concise context before leaving. Each packet contains the customer’s objective, what was promised, the current source documents, open questions and the next escalation route. Noor confirms that she can explain the immediate situation. She is not expected to reconstruct the full relationship from a transcript archive.

Agree what happens when new work arrives

Temporary cover will encounter something outside the prepared list. Define where incoming requests are observed, who checks them and which consequences require escalation. A new question that can wait for the owner differs from a missed commitment or an issue that changes the customer’s immediate decision.

Give the substitute a way to ask for help when the agreed workload is exceeded. The escalation should name the conflict: two customer obligations need the same specialist in the same window, or an urgent issue consumes the time reserved for a renewal conversation. The leader chooses coverage or revised timing with that consequence visible.

Make the relevant temporary contact understandable to the customer where continuity requires it. Explain the dates, what the substitute can help with and how the next promised step will happen. Avoid broad promises of instant availability or a service level the team has not agreed to provide.

Close temporary coverage deliberately

Set an end date, but do not treat the owner’s return as automatic acceptance of everything that happened. Hand back completed decisions, open commitments, new customer context and unresolved issues. Identify who owns the next action while that brief is being reviewed.

An unfinished task may sensibly stay with the substitute for one final conversation, particularly if switching again would confuse the customer. Agree that exception explicitly and give it a completion point. Otherwise temporary cover can turn into indefinite shared responsibility without either person choosing it.

RevTech’s Customer Context connects account history and activity for prepared work; its customer-success offering brings available customer context into human review. An agreed preparation task can help assemble the relevant background. Those descriptions do not establish an automated holiday roster, extra staffing or a response guarantee. People accept the work and keep the customer commitments.

Sources and scope

Original temporary-coverage method and fictional workload example, reviewed November 6, 2026. RevTech’s Customer Context and Customer Success pages were checked that day. Permanent reassignment, approval delegation and changes to commercial terms are separate decisions. The practical test is whether each promised next step has a capable person with time to carry it.