Vacation Coverage Without the Pile: Before, During and After

Monday, 08:30, at Redbrook Engineering. Jonas is back from two weeks away and the desk has kept his seat warm. Fourteen open tickets still have his name on them. Sixty-one notifications are waiting, and he reads the subject lines in the hope that most are nothing. Four tickets have replies from requesters that nobody answered; one of them has three, the last of which says "Hello? Is anyone there?" A supplier quote he was waiting for arrived on his second day away and expired on his ninth. One requester gave up and e-mailed the engineering director, which is why the director is standing at his desk at 08:35, before his coat is off. Femi had been asked to keep an eye on things. Femi kept an eye on things. Nobody had said what "things" were.

Vacation coverage is the arrangement by which a person's open tickets and standing duties are handled while they are away, so that nothing waits for them to come back. The pile is the set of things that waited anyway. It forms in the week before the leave, when the person going away decides what can wait. It is discovered on the first morning back, by the person least able to do anything about it. This article is part of our Handoffs & Coverage Transitions series. It is about leaving without a pile and coming back to none.

It covers why the pile forms, then the pre-leave sweep, a week out and on the last day. Next comes the decision for each ticket between reassigning it and watching it, with a table. Briefing the cover and the out-of-office that tells the truth follow. Next come the standing duties that are not tickets and get forgotten. Then come unplanned absence, where none of the preparation happened, and the first morning back. A short war story and the pre-leave checklist to copy follow, in that order.

Why the Pile Forms

The pile forms because the owner field does not know anyone is away. A ticket assigned to Jonas on the Friday before his leave is assigned to Jonas on the Monday of it, and on every day after. Every view on the desk that is filtered by owner shows it to one screen, which is switched off. The tool is not being unhelpful. It has been told who owns the ticket and it is telling everyone, accurately, for two weeks.

The pile also forms because of a judgement made by the wrong person. In the week before leave, the person going away looks at each open ticket and asks "can this wait until I'm back?" The person asking has an interest in the answer being yes, because every no is a handover to write. Most of the yeses are wrong. A ticket waiting on a requester will get its reply on day three. A ticket waiting on a supplier will get its quote on day two. A ticket that is "basically done" will turn out, on day six, to have a step left. The step will be the one only the absent person knew about.

Requesters make the pile bigger by doing exactly what they were asked to do. They reply. The reply lands on the ticket, and the ticket is Jonas's. In most tools a reply to an open ticket updates it and notifies the owner, and does nothing else. It does not reassign. It does not raise a flag anyone else can see. The requester has done their part and is now waiting on a man who is on a boat.

And the pile forms because "keep an eye on things" is not a handover. Femi was willing. Femi was not told which tickets, what had been promised on them, what to do if a reply came, or whether she was allowed to close anything. A cover who has been given a list and no authority will do the safe thing, which is nothing, until the owner is back. The pile is not Femi's fault. It is the predictable output of a cover who was named and not briefed.

The Pre-Leave Sweep

The sweep is a pass through your own open list, twice: once a week before you go, and once on the last afternoon. The first pass is for shrinking the list, the second is for emptying it. A week out, the list is at its longest and you have the most time to do something about each item. On the last day you have an hour and a coat on. The only decision left should be confirming that nothing active still carries your name.

A week out, open your list sorted by last update and work it from the top with one question per ticket. What would make this not need me while I am away? For many, the answer is "finish it". A week of knowing you are leaving is a remarkable cure for tickets that have been nearly done since March. For tickets waiting on a requester, chase now, so the reply comes while you are still in. For tickets waiting on a supplier, chase now, for the same reason. For the rest, decide between reassigning and watching, which the next section covers. On a desk of normal size this first pass turns a list of fifteen into a list of five or six that genuinely need a cover.

On the last afternoon, open the list again and read it as the lead will read it on Monday morning. Every ticket still assigned to you, active or waiting, is a ticket that will do nothing until you are back. The target is zero active tickets owned by you when you leave. Not "a few that can wait". Zero. Every one of the remainder has been reassigned to a named cover who has accepted it, or moved to the team queue with a note. Or, for a small and specific class, it has been left with you deliberately, with a date after your return and a note that says so.

Do the second pass before the farewell drinks, not after. I have done it after. The notes I wrote were cheerful and contained no information.

Reassign or Watch: Deciding for Each Ticket

Each ticket that survives the first pass gets one of two treatments. Reassign means the cover becomes the owner: the ticket is theirs, they take the next action, they answer the requester, and they may close it. Watch means the ticket stays with you, but the cover has it on a named list and checks it on a schedule. A written trigger says when watching turns into taking over. Reassigning is the default. Watching is for the few tickets where nothing should happen during the leave, and where the only risk is that something does.

The rule for deciding is the one that runs through this whole series. No ticket owned by an absent person should need anything before they are back. If a ticket could need anything, a reply, a chase, a decision, a part signed for, then it needs an owner who is in. That is a reassignment. If it truly cannot need anything, because it is waiting on a date that falls after the return and the requester knows it, then it can be watched. The honest test is to imagine the worst plausible reply arriving on day four and ask who answers it. If the answer is "nobody until I'm back", reassign.

Watch has a cost that is easy to miss. The watched ticket still shows your name, and every view filtered by owner still hides it from everyone but you. The cover's list is a workaround. Workarounds survive only if the cover's list is written down somewhere the lead can see, with the trigger beside each item. "Watch 5120, supplier due the Tuesday after I'm back, take over if the requester replies or the date moves." That line is the whole of a watched ticket's handover, and without it the ticket is not watched. It is merely still yours.

Where a tool lets a ticket sit unassigned in a team queue, there is a third option. Move it there with the note on it, so that whoever reads the unassigned view picks it up. This is right for a ticket whose next step anyone on the desk can do, and wrong for one that needs the cover's specific knowledge. That is because the team queue is read for "what shall I take" rather than "what was Jonas promising".

Briefing the Cover

The cover is briefed, not notified. Take fifteen minutes, on the last day, with the list in front of both of you, one line per ticket. Cover what it is, what has been done, what the requester has been told, and what the next step is. The cover says each one back and accepts it, in the tool, by taking ownership while you watch. A ticket is handed over when it has the cover's name on it and the cover has said what they will do first. The note format is the one the desk uses at a shift change, with a longer horizon; its headings are in The Shift Handover.

Tell the cover the three that worry you. Every list has two or three tickets where the requester is impatient, the fix is uncertain, or the history is long. Those are the ones the cover will be asked about in week one. Say which they are and why. "5103 is the broker portal certificate; it expires on the Thursday after I leave; the renewal is ordered and the reference is in the ticket; if it has not arrived by Tuesday ring the supplier, the number is in the note." A cover who knows which three to watch will watch them. A cover with fourteen tickets of equal weight will watch none in particular.

Say what the cover may decide. This is the part most briefings leave out and the part that makes the difference between a cover and a caretaker. May they close a ticket? May they tell a requester "no"? May they re-promise a date you gave? May they spend money, up to what? Without an answer the cover will wait for you on anything that feels like a decision, which is most things. The requester will wait with them. The answer that works is "decide as if I were not coming back", said out loud, and meant. Nothing you would do on your return is worth a requester waiting two weeks for it.

Pick the cover from the coverage matrix, not from who sits nearest. The person who can cover the broker portal is the person who knows the broker portal. If that person is also away, the gap should have shown up on the calendar when the leave was booked. Building that calendar is the subject of The Coverage Calendar and the Single Point of Failure. If the matrix says nobody else can do a thing, the pre-leave week is the week to write it down and walk someone through it. It is not the week to hope it does not come up.

The Out-of-Office That Tells the Truth

The out-of-office reply is read by every requester who writes to you. It should answer the only question they have: who is dealing with my problem now? Most out-of-office messages answer a different question, when you are back, and then promise something false: "I will respond to your message on my return." A requester who reads that will wait for your return, because you told them to. Two weeks of requesters doing what the message said is the pile.

The honest version says four things. The dates. That the desk is open and tickets are being worked. Who to contact and how, which is the desk's normal address or form, not the cover's personal address. And that anything already in a ticket is in hand. "I am away until the 14th. The support desk is open as usual: new requests go to helpdesk@example.com or the portal, and existing tickets are being handled by my colleagues. There is no need to wait for my return." Nothing about responding when you are back, because you will not; the ticket will have been closed by someone else, and that is the point.

Set it on your mailbox and check what it does to the ticketing tool. Most tools send notifications from an address that can receive replies. An out-of-office reply to a notification can land in the tool as a new ticket, or as an update on the ticket that triggered it. In some tools it can start a loop in which the tool replies to the reply. Test it the week before: have a colleague trigger a notification to you with the out-of-office on, and see what the tool does. Then exclude the tool's address from your auto-reply if the mail system allows it. (Most do. The option is usually three menus deep and labelled unhelpfully.)

Chat needs the same honesty. A status that says "On leave until the 14th, contact the help desk" costs ten seconds. It is read by exactly the colleagues who would otherwise message you first and raise a ticket never.

Standing Duties, Not Just Tickets

The tickets are the visible half of a person's work. The other half is the standing duties, the things they do on a schedule that no ticket records. Those include the daily unassigned sweep, the Monday backlog report, and the Wednesday supplier call. They include the backup check, the approvals for new accounts, and the weekly export that finance relies on. None of these have an owner field, so none of them show up in the pre-leave sweep. All of them stop on the first day of leave unless somebody has been told to do them.

Write them down, once, as a list with a day and a time against each, and give the list to the cover with the tickets. On a small desk the list runs to six or eight items and takes five minutes to make. The surprising thing is usually how many of them nobody else knew existed. That is because the person who does them has done them every Wednesday for three years and stopped mentioning it. A duty that stops silently for two weeks is noticed on the Thursday of week three, by the person who needed its output. By then the pile has a second storey.

Two duties need particular care. The first is anything with a deadline outside the desk: a certificate renewal, a licence that lapses, a report with a date. These go on the cover's calendar as appointments, not on a list. The second is the absence check itself, the morning look at tickets assigned to people who are not in, which is in Keeping Tickets From Hiding. If the person going on leave is the person who does that check, the cover inherits it on day one, and inherits with it the job of finding anything the sweep missed.

Unplanned Absence

Unplanned absence is the pre-leave sweep done by someone else, in a hurry, on the morning it is needed. Somebody is ill, or has a family emergency, and their open list is exactly as they left it the evening before: active tickets, promises, a reply due at 10:00. Nothing has been reassigned, because nothing was planned. The one preparation that helps is the one made every day for other reasons: last night's handover note. It lists what was promised and in flight, and it is the only context the desk will have.

The rule is that the lead opens the absent person's list by a fixed time each morning, and reassigns everything active. That means every ticket where a requester is waiting on the desk, plus every waiting ticket whose reply could arrive today. The fixed time is what makes it happen; "when I get a minute" is a time that does not occur on the morning somebody is off sick. By 09:30, for a desk that opens at 08:00, is about right. Each reassigned ticket gets a one-line note saying why it moved. Each requester with a promise due that day gets a message with a new time from the new owner.

The lead also sets the absent person's out-of-office, if the mail system allows it and the policy permits, with the same four truths as the planned version. If the absence runs past three days, treat it as leave. In that case, the cover gets a proper briefing from whoever knows the most. In that case, the standing-duties list is also found and handed over, even though the person who should have written it is at home with a temperature.

The Return

The first morning back is half an hour, and it is spent reading rather than doing. Read the cover's note first, before the notifications, because the note says what happened and the notifications say only that things did. A good cover leaves a note in the same four headings they received: what was promised in your name, what is in flight, what to watch, and what happened outside the queue. If there is no note, ask for a ten-minute conversation before touching anything.

Do not take everything back. The instinct on returning is to reclaim every ticket that was yours. The instinct is wrong, because the cover has been talking to those requesters for two weeks and knows where each one is. The cover finishes what they started. Tickets come back to you only when the cover offers them. A return that reassigns fourteen tickets at 08:40 produces fourteen requesters whose contact has changed twice in a fortnight. It also produces a cover whose two weeks of work is now invisible.

Skim the notifications for one thing only: replies from requesters that nobody answered. Sort the mailbox by sender and look for the names that are not colleagues. Anything found gets a reply within the hour, with an honest line and a time, from whoever now owns the ticket. Then archive the rest of the sixty-one. They were news a week ago. Now they are a diary, and nobody has ever caught up by reading a diary.

A Short War Story: The Certificate at Stonebridge Insurance

Helen ran the broker portal at Stonebridge Insurance, a four-person desk. She went on two weeks' leave with ticket 5103, the portal's certificate renewal, still assigned to her. That was because the new certificate was due on the Tuesday of her first week away and installing it was "a ten-minute job I'll do when I'm back". The certificate arrived on the Tuesday as an e-mail to Helen, which her out-of-office answered. The old one expired on the Thursday, at which point about forty brokers could no longer submit business through the portal. The underwriting team spent a morning taking submissions by phone. The cover, Dev, had been told to "keep an eye on 5103" and had, in the sense that he could see it. Nobody had told him the certificate was coming to Helen's inbox, or that he was allowed to install it. Helen's first morning back was a meeting with the head of underwriting, which took longer than the ten-minute job. Stonebridge now reassigns everything, puts anything with a date on the cover's calendar as an appointment, and uses the phrase "decide as if I'm not coming back" in every briefing. A ticket with a deadline inside the leave is never a watch. It is the first thing to hand over.

The Pre-Leave Checklist

The checklist is the sweep, the decision, the briefing, the out-of-office and the standing duties on one page, in the order they are done. Start it a week out and finish it on the last afternoon, before the drinks. The last block is for the cover to complete on the morning you return, so that the handover closes in writing in both directions.

PRE-LEAVE CHECKLIST — ONE PAGE
Name: ______________   Away from: ________  to: ________   Cover: ______________

ONE WEEK OUT
  [ ] Open list sorted by last update; every ticket given one of: finish, chase, reassign, watch
  [ ] Everything waiting on a requester chased now
  [ ] Everything waiting on a supplier chased now; promised dates written in the ticket
  [ ] Anything with a deadline inside the leave listed here:
      #______ __________________ due ______   #______ __________________ due ______
  [ ] Standing duties written down (day, time, what, where the instructions are):
      ______________________________   ______________________________
      ______________________________   ______________________________
  [ ] Cover confirmed on the coverage calendar; no duty drops to nobody

LAST AFTERNOON
  [ ] Active tickets still owned by me: ____  (must be 0)
  [ ] Reassigned to cover, each with a note: what done, next step, what requester was told
  [ ] Watched tickets listed for the cover with a trigger each:
      #______ trigger: __________________   #______ trigger: __________________
  [ ] Briefing done, 15 minutes, cover took ownership of each ticket while I watched
  [ ] The three that worry me, named to the cover: #______  #______  #______
  [ ] Cover told what they may decide: close [ ]  say no [ ]  re-promise dates [ ]  spend to ______ [ ]
  [ ] Out-of-office set: dates, desk is open, desk address, no "on my return"
  [ ] Out-of-office tested against a ticket notification; tool address excluded
  [ ] Chat status set
  [ ] Deadlines inside the leave are appointments on the cover's calendar

FIRST MORNING BACK (cover fills in, returning person reads)
  Promised in your name: __________________________________________
  In flight: ______________________________________________________
  Watch: __________________________________________________________
  Outside the queue: ______________________________________________
  Tickets I will keep: ____________   Tickets ready to hand back: ____________

Two lines on the sheet do most of the work. "Active tickets still owned by me: must be 0", because it turns a judgement into a count, and a count is harder to talk yourself out of. And "cover told what they may decide", because it is the line that turns a caretaker into a cover. Jonas filled it in for the first time before his next leave, a long weekend in the autumn. He came back to three notifications, none of them from the director.

Frequently Asked Questions