Jump to section
Here is the test of a well run firm: someone takes two weeks off, turns their phone all the way off, and nothing catches fire. No frantic texts on day three. No limitation period discovered on day nine. No pile of untouched files waiting on their desk when they walk back in. Most small firms fail that test, not because the people are careless, but because the firm never planned for absence. Coverage is not a personality trait. It is a system, and you can build it in an afternoon or two.
What follows is a checklist. Work through it once for your firm, write down the answers, and you will have turned "hope nothing goes wrong" into an actual plan. The goal is simple: anyone can be away for a real stretch, and the work keeps moving.
Map the tasks only one person can do
Start by finding the single points of failure. In most small firms there are a handful of tasks that live entirely in one person's head or one person's login, and everyone else quietly assumes they will always be there. Those are the tasks that stall a firm the moment that person is gone.
Walk through a normal month and list the jobs that only one person actually knows how to do. Common ones:
- Running payroll and remitting source deductions on time.
- Approving trust transfers and reconciling the trust account.
- Posting to the general ledger or closing the books each month.
- Filing at a particular registry or e-filing portal with the right credentials.
- Answering the main line and triaging new client calls.
- Sending invoices and chasing receivables.
Write each one down with the name of the only person who can do it. That list is your risk map. Everything on it needs a backup before that person can safely disappear for a week.
Note. Trust accounting deserves its own line. Law society rules on who can authorize trust transactions and how often reconciliations happen do not pause for vacation. Make sure your coverage plan keeps you compliant, not just functional.
Build a backup for every critical role
For each task on your risk map, name a second person who can do it, and then actually let them do it while the primary is still around to answer questions. A backup who has read a document but never touched the live system is not a backup. They are a guess.
The fastest way to build real backups is to cross train in normal weeks, not crisis weeks:
- Pick one critical task and one backup person.
- Have the backup do it once, start to finish, while the expert watches.
- Write down the ten things that tripped them up. That becomes the procedure.
- Repeat until every task on your risk map has a trained second.
This is where documented procedures earn their keep. If your team already writes down how things get done, coverage is mostly a matter of pointing the backup at the right page. If it does not, this is a good reason to start, and we have written about procedures people actually use rather than binders nobody opens. A shared knowledge base beats tribal memory every time someone is out.
A backup who has never touched the live system is not a backup. They are a guess. Firm Operations at A1 CMS
A handoff sheet that fits on one page
Before anyone leaves, they fill out a handoff sheet. One page. If it runs longer than a page, it will not get read, and half of it will be out of date anyway. Keep it tight and current.
A good handoff sheet covers exactly this:
| Section | What goes in it |
|---|---|
| Live files needing attention | Matter name, what is due, who is covering, any deadline dates. |
| Deadlines during the absence | Every date that lands while you are gone, with the owner beside it. |
| Waiting on a reply | Emails or calls that may land and who should handle them. |
| Do not touch | Matters that can safely wait, so nobody starts unnecessary work. |
| Contacts | The covering lawyer, the client for anything urgent, opposing counsel if relevant. |
Store the sheet where the whole team can find it, not in the vacationer's inbox. If your files, deadlines, and contacts already live in one place, such as your matter and calendar system, the sheet is easier to complete because the covering person can look up the rest. This also means keeping your coverage plan tied to the same tools you use every day, rather than a separate document nobody remembers to update.
Protecting deadlines while someone is away
Deadlines are the part of this that can actually hurt a client. A stalled invoice is annoying. A missed limitation period is a claim. So this section gets its own rules, and they are non negotiable.
- No single owner for a deadline during an absence. Every date that falls while someone is away gets reassigned to a named covering person before the vacation starts, not "the team."
- Calendar the reassignment, not just the deadline. The covering person should get their own reminder, in their own view, well ahead of the date.
- Build in slack. Where you can, do the filing or the reply before the vacation rather than leaving it for the covering person on the actual due date.
- Confirm receipt. The covering person acknowledges each deadline they are taking on, so nothing falls into the gap between "I assumed you had it" and "I thought you had it."
Warn. The most dangerous deadlines are the ones nobody has entered yet. If a new limitation period or filing date could arise from mail or a call during the absence, make sure the covering person knows to diarize it the moment it appears, not when the primary returns.
A firm that runs a simple shared dashboard has a real edge here, because upcoming dates are visible to everyone rather than trapped in one person's calendar.
Making the return smooth, not a pileup
Coverage is only half done if the returning person walks into two weeks of chaos. If coming back is punishing, people stop taking real time off, and you are back where you started. Plan the re-entry as deliberately as the departure.
- Keep a running log of what the covering person handled and what decisions they made. The returner reads it once and is caught up.
- Flag anything held for the returner specifically, so they know what genuinely waited for them versus what is already resolved.
- Block the first morning back for catch up, not client meetings. No new deadlines land on day one.
- Debrief for five minutes. What broke, what was missing from the handoff sheet, what to fix before the next person leaves.
That last step is what turns a single vacation into a durable system. Each time someone is away, the plan gets a little better and the next absence runs more smoothly.
None of this requires a big firm or a fancy budget. It requires deciding, once, that time off is normal and that the firm will be built to handle it. Map the tasks only one person can do, give every one of them a trained backup, keep a one page handoff sheet, guard the deadlines with named owners, and plan a calm return. Do that, and vacations stop being a risk you dread and become ordinary scheduled absences the firm handles without incident. If you want more on running the operational side of a small practice, the operations archive and the rest of our writing are good places to keep going.
