An engagement manager wakes up on the Tuesday of a steering committee week to a message from her only analyst. He has a fever and will not be at the client site. The model sits on his laptop. The weekly status deck is half built. The client's finance head expects the pack at nine on Thursday. Nobody else on the team has opened the data room folder. This is what absence costs in a consulting firm, and it is rarely about the person who is missing.
Owners ask how to cover absence. Ask instead what must already exist on the day someone drops out. A consulting firm sells days of named people. When a name drops out, the statement of work, the staffing grid and the client's trust all move at once. Below: the cover tiers, a handover template, leave rules tied to SteerCo dates, and a bench routine, all aimed at keeping Thursday's pack on Thursday.
Start with the staffing grid, not the leave register
A leave register tells you who is away. A staffing grid tells you what breaks. Most small firms keep the first and improvise the second. The grid is a simple sheet: one row per engagement, one column per week, and in each cell the people billed that week against each workstream. Add two more columns. One for the named second person on every workstream. One for the next client milestone, whether that is a kick-off, a steering committee, a partner review or a final readout.
Read the grid against leave every Monday. A planned week off for an associate in a quiet fortnight is nothing. The same week off the fortnight before a readout needs a decision. Keeping this view is the core of attendance, shift and leave process design for a firm whose busy weeks are set by clients.
Types of absence and the cover each one needs
- Planned leave of a week or more: agree it at engagement kick-off, block it on the grid, brief the second person in the week before.
- Short planned absence, such as a wedding or a visa appointment: swap the client-site days, keep remote deliverables with the same person.
- Sudden sickness on a deadline day: the second person takes the live deliverable, the partner calls the client the same morning.
- Long absence, such as surgery or maternity: staff a replacement from the bench with a full week of overlap, and tell the client early.
- Resignation with a notice period: treat the notice weeks as a handover sprint, with the client-side counterpart introduced to the successor.
The one-page handover note
ENGAGEMENT client code, workstream, partner, engagement manager.
NEXT DATES next steering committee, partner review, data request due.
WHERE THINGS data room folder, model version, deck master, shared drive path.
LIVE ASKS open client requests, who asked, promised date.
KNOWN TRAPS sheet with manual overrides, source with late refresh, client contact who replies only on WhatsApp.
NEXT 3 ACTIONS what the cover person does first, in order.
WHO TO CALL engagement manager first, partner second, client counterpart third.
FILED BY name and date; reviewed by second person.The note is filed weekly by the person on the workstream, not written in panic. It takes ten minutes. It is also the quickest way to see which analysts are carrying a model that nobody else understands.
Run the bench like a real resource
Firms that keep a bench of one or two people between assignments cover absence without drama. Firms that bill everyone at full utilisation cannot, because every absence is a missed deliverable. The bench should be visible: who is free next week, which skills they carry, such as modelling, survey design, process mapping or interview synthesis. Note which data-room permissions they already hold, and whether an NDA sits with the client. A weekly twenty-minute resourcing call between the partners and engagement managers fills it in. If you want the cost of a bench set against billed days, HR reporting from timesheets and the grid gives you that.
- 1
Name a second for every workstream
At kick-off, the engagement manager writes a second person beside each workstream. A second is someone who has seen the model and the deck, not someone who has heard of them.
- 2
Rotate the second into one review a month
A ten-minute walkthrough of the live file keeps the second honest and spots a model that only one head can read.
- 3
Mark client-site weeks and milestones on the grid
Leave requests landing on those weeks get a conversation, not an automatic yes or no.
- 4
Agree who calls the client
For a sudden absence, the engagement manager or partner calls before nine. Clients forgive absence and do not forgive silence.
- 5
Close the loop on return
The returning person reads the note the cover wrote, and the grid is corrected so billing matches who actually worked.
Leave rules that survive a client week
Write the rules around work, not around calendars. Many firms use a short list. One leave approval per workstream in a milestone week. Leave beyond three days needs the engagement manager's sign-off at least two weeks ahead. Travel days for client-site weeks are logged, so Monday and Thursday flights are not mistaken for office days. Public-holiday weeks and festival periods are mapped on the grid at the start of each quarter so clients are warned in the kick-off, not at the last minute.
Offer something back when the rule bites. Compensatory time after a hard readout, or a flexible Friday after a client-site week, makes the rule feel fair. Link this to how performance management credits the extra effort, so cover work is visible at appraisal time and not taken for granted.
Where this fits the rest of the firm
Cover planning is one thread among several. Strategy, quality and finance advisory desks each staff differently. Read the pages on management consulting and operations consulting, and the wider consulting firms hub. To have a staffing grid and handover note drafted around your own practice mix, tell us about it through the requirements wizard.
