Vacation coverage for a one-rep function

Your only SDR asks for two weeks in August. The answer is yes; a rested rep in September is worth more than a resentful one in August. But in a one-rep function, a vacation is also a system test. We wrote in January that one rep is a single point of failure and that coverage has to be designed before it is needed. A planned absence is the friendly version of that failure, the one that ships with a start date, an end date, and two weeks of notice. Teams that improvise it anyway get the outage they planned for, which is to say none.

The four-part cover

The return-week list, built before departure. The rep's last two days include building the list they will dial on their first Monday back. Momentum dies when the first day back is spent rebuilding context instead of calling. The list waits; the warm-up does not need to be rediscovered.

Scheduled sends. Accounts mid-cadence keep getting their touches on schedule, queued before the rep leaves. A cadence that pauses for two weeks is not a pause, it is a restart: the familiarity that touches were compounding decays, and the account re-enters cold.

The manager's dial hour. Not full coverage, and not pretending to be. Forty-five minutes a day, on the five hottest accounts only: the buyer with a named deadline, the reply threads that cannot age, the meeting that needs confirming. A manager who tries to replace the rep's whole day fails at two jobs at once. One protected hour on the accounts that cannot wait keeps the live threads alive, and it has a side benefit: two weeks on the phone is the best calibration a manager's coaching gets all year.

An honest out-of-office. Named backup, direct contact, real return date. We spent a post in early June reading other people's OOO replies as routing instructions. Yours should pass the same test. A reply that reaches the backup should be answered fast and answered with a proposed time, because a prospect's reply is perishable whether your rep is at their desk or on a lake.

What not to attempt

Do not try to replace the missing activity. Two quiet weeks of dials will show up as a soft patch in meetings about a month later, because conversations lead meetings by a few weeks, and no amount of manager heroics changes that physics. The plan's job is to protect what exists, not to fake what does not. Forecast the soft patch, tell your AEs it is coming, and let it arrive on schedule instead of as a mystery. All of this assumes the function is documented, which is the quiet payoff of the playbook discipline we described last week in documentation as a management tool: a written track, objection map, and list rules are what make a backup possible at all.

This is also a fair question to put to any outsourced provider this month: what happens to your account in vacation season. At CommandVA the coverage plan is part of the engagement, built on the same documented playbook, so a rep's earned time off never becomes the client's pipeline gap. If your entire outbound motion currently boards a plane in August, book a strategy call before it does, and we will help you design the cover, whether or not we are part of it.