FirmFooting / Briefs / Systems & SOPs
Systems & SOPs · Published Jun 29, 2026
Holiday Coverage Protocol: The Build
We wrote about the Thanksgiving Test, whether your firm can close for a week without a deadline slipping. This is the build: how to turn the pre-closure sweep from a good idea you do once into a documented, recurring protocol your firm runs the same way before every closure. It is a small SOP with a trigger, owners, a checklist, an escalation reroute, and a sign-off, and once it exists you never have to reinvent holiday coverage again.
Jareer Ali·
Field notes·
11 min read
A holiday coverage protocol is the pre-closure sweep turned into a documented, recurring SOP. It has five parts: a trigger (about two weeks before any closure, as a standing calendar entry), named owners, a checklist artifact that lists every deadline in and just after the window, an escalation reroute so alerts never go to someone who is away, and a pre-close sign-off confirming nothing is left waiting. You build it once and run it before every closure, so holiday coverage stops being a scramble someone has to remember and becomes a system that runs the same way every time. It supplements, never replaces, official docketing.
Key takeaways
- A protocol is the documented, recurring version of the sweep, so it survives turnover and no one has to reinvent it.
- Trigger about two weeks out, as a standing calendar entry tied to each known closure, not a decision made in the moment.
- The checklist artifact captures every deadline in the window and the first days back, with a decision for each.
- The escalation reroute is the step firms forget: alerts must never route to whoever is away.
- A pre-close sign-off confirms nothing is left waiting before the door locks.
- Whether a deadline extends over a holiday stays the attorney's call; the protocol never assumes it.
Companion video: VID-044 walks through running this protocol before a closure. (Embedded on publish.)
A sweep you do once is a favor you did your firm; a protocol you build once is a system your firm has. The difference matters more than it sounds. Last time we described the pre-closure sweep as four moves, identify, decide, assign, verify, and that is exactly right as an activity. But an activity that depends on someone remembering to do it, knowing how to do it, and having time to do it is fragile in precisely the way the holidays expose, because the person who knows the sweep is often the person who is leaving on vacation. The fix is to document the sweep as a protocol: give it a trigger so it starts on its own, an owner so someone is responsible, a checklist so it is done the same way every time, and a sign-off so its completion is verified. That is this build, and it is small enough to finish this week and durable enough to serve every closure from now on.
Why a protocol, not just a sweep
The case for turning the sweep into a documented protocol is the same case we make for documenting any recurring process, and the holidays are a nearly perfect illustration of it. A closure is foreseeable, repeats predictably, and carries real risk, which is the exact profile of work that should never live in someone's head. When holiday coverage is an informal habit, it degrades in all the usual ways: it depends on one person, it varies in quality depending on who does it and how busy they are, and it disappears entirely the year that person is out or gone. When it is a protocol, it runs the same way every time regardless of who is holding it, which is the whole point of documentation, covered more generally in the process documentation guide.
There is also a quieter benefit: a documented protocol removes the decision fatigue and low-grade dread that surround closures at firms without one. Instead of someone realizing in mid-December that the holidays are coming and nobody has thought about deadlines, the protocol has already triggered, the checklist is already being worked, and the owner already knows their job. The firm closes on a completed protocol rather than on a hopeful feeling, and the person who used to check email from the dinner table gets to actually stop. This is the build companion to the Thanksgiving Test, which makes the case for why; here we make the thing.
The five parts of the protocol
The protocol has five components, and each one closes a specific way the informal version fails. Together they form a small SOP you can write on a single page and store with your other operating procedures.
| Component | What it is | The failure it closes |
|---|---|---|
| Trigger | A standing calendar entry ~2 weeks before each closure that starts the protocol | Nobody remembers until it is too late |
| Owner | A named person responsible for running it (with a named backup) | "Someone" doing it means no one does |
| Checklist artifact | The list of every deadline in and just after the window, with a decision each | A deadline nobody surfaced |
| Escalation reroute | A temporary change so alerts route to a present person | Escalation firing to an empty desk |
| Pre-close sign-off | A final confirmation that nothing is left waiting before closing | Closing on a hope, not a check |
The handoff checklist that keeps deadlines covered when the firm is short-staffed over the holidays.
Get the free coverage checklistBuilding the checklist artifact
The heart of the protocol is the checklist artifact, the actual document the owner works through each time, and it is worth building carefully because it is what makes the protocol repeatable rather than improvised. The artifact is a simple table with one row per deadline in the window and a fixed set of columns: the matter number, the deadline type and date, whether it falls during the closure or in the first days back, the decision (handle ahead or cover), the assigned owner if covered, and a done checkbox. Because the columns are fixed, anyone can run the protocol correctly, and because it is filled in fresh each closure, it is always current. Keep it to matter numbers and deadline metadata; the artifact never needs the substance of any matter, which keeps it firmly on the operational side of the confidentiality line.
The one column people underuse is the "during or just after" flag, and it is the one that prevents the most common holiday miss. Firms reliably remember the deadlines that fall during the closed days and reliably forget the ones due in the first two or three days after reopening, which needed work done before the break. Making that a required field forces the owner to look at the tail of the window, not just the middle. The artifact draws directly on the deadline data your system already holds, so if you run the standing weekly review, filling the artifact is mostly a matter of filtering to the window and copying across. Store the blank template with your other SOPs, using the naming convention from the SOP library guide, so the next person who runs it does not have to rebuild it.
Making it recurring
The final step, and the one that converts this from a document into a system, is to make the protocol trigger itself without anyone deciding to start it. The mechanism is boring and reliable: for every closure your firm reasonably knows about, the major holidays, the firm's traditional year-end break, any planned all-hands absence, put a standing calendar entry about two weeks ahead that says, in effect, run the holiday coverage protocol, with the owner assigned. Because the trigger is on the calendar rather than in someone's intentions, it survives busy seasons and staff changes; the protocol runs whether or not anyone remembers it exists, which is exactly the property that informal holiday coverage lacks.
That is the whole build. A trigger, an owner, a checklist artifact, an escalation reroute, and a sign-off, documented as a one-page SOP and scheduled to recur, and your firm never again approaches a closure wondering whether a deadline is about to slip through it. It pairs with the year-round version of the same discipline in the vacation coverage guide and the escalation mechanics in the escalation ladder. The reason to build it now, in November, is obvious: the first closure it protects is a few weeks away, and the second is the long year-end stretch right behind it. Build it once this week, and both are handled.
Where to go next
- The Thanksgiving Test
The case for why, before the build.
- Law Firm Vacation Coverage
The year-round version of the protocol.
- The SOP Template
The format to document the protocol in.
- The Escalation Ladder
What the reroute step temporarily changes.
A diagnosis, not a pitch
See where your firm would slip first.
Take the free Footing Assessment for a read on where your systems have no second observer, or book the thirty-minute Risk Audit. One page, inside 24 hours, whether you hire us or not.
Frequently asked questions
What is a holiday coverage protocol?
A documented, repeatable SOP that a firm runs before every planned closure so no deadline slips while the office is closed. It has a trigger (a fixed number of days before the closure), named owners, a checklist artifact that captures every deadline in the window, an escalation reroute so alerts do not go to someone who is away, and a pre-close sign-off confirming nothing is left waiting. You build it once and run it before each closure.
How is the protocol different from just doing a sweep?
A sweep is the activity; the protocol is the documented, owned, recurring version of it. Doing a sweep once relies on someone remembering to do it and knowing how; a protocol assigns the trigger, the owner, and the steps so it happens the same way every time, even if the person who invented it is gone. The protocol turns a good habit into a durable system that survives staff turnover.
When should the protocol trigger?
About two weeks before the closure, so there is time to handle deadlines ahead rather than scramble. The trigger should be a standing calendar entry tied to each known closure, not a decision someone makes in the moment, because the whole point is that it runs automatically. Two weeks gives room to complete or advance anything due in the window and to arrange coverage for anything that cannot be handled ahead.
Does the protocol decide whether deadlines extend over holidays?
No. Whether any deadline extends, rolls, or is tolled because of a holiday is a legal determination the attorney owns; the protocol never assumes an extension. It surfaces every deadline in the window for the attorney to handle and treats each as live unless the attorney determines otherwise. The protocol supplements, never replaces, official docketing, and uses matter numbers and metadata only.
- FirmFooting operational method for a recurring holiday coverage protocol. Internal practice standard, 2026.