Handover Without the Drop: When Someone Leaves

Summary

"Do you have time for a quick chat?"

Every principal knows that sentence. You also know, from the way a valued staff member says it, roughly what's coming before they've finished closing the door.

It's a Friday afternoon. A senior lawyer gives notice. They're professional about it, they'll work out their four weeks, and there's no ill feeling anywhere.

You still have a problem, and it's roughly sixty matters large.

Handover is only painful when the work wasn't written down as it happened. If it was, handover is a readout: someone reads what's already there. If it wasn't, handover is a memory exercise performed under time pressure by someone who is also still doing their job, and it will be incomplete no matter how conscientious they are.

This guide covers what actually gets lost when someone leaves (it isn't the files), why the reconstruction is so brutal, and how firms make handover something that happens continuously in the background rather than in a fortnight of panic. It also covers the risk nobody names out loud: what it means when your practice depends on a few people carrying it in their heads.

Contents

• The Friday resignation
• What actually gets lost isn't the files
• Why reconstructing it is so brutal
• The version where handover is already written
• Work should travel up the chain, not into a void
• The dependency nobody names
• Anyone should be able to give the client an update
• Onboarding whoever comes next
• The planned version: leave, illness, secondments
• Key takeaways
• Frequently asked questions

The Friday resignation

Nobody plans for this well, because it always arrives as a surprise even though it's statistically inevitable.

The four weeks that follow tend to go the same way in most firms. The first is spent absorbing it. The second is spent on the most urgent matters. Somewhere in the third, someone asks for handover notes, and the departing lawyer starts writing, in the evenings, between actual work, from memory. The fourth week is a farewell lunch and a document that covers perhaps the top fifteen files properly.

Then they're gone, and for the next six months the firm discovers what wasn't in the document. Usually at the worst possible moment, on a matter nobody had thought about since March.

This isn't a story about a bad employee. It's what happens when the only copy of the plan is inside a person and that person walks out the door.

What actually gets lost isn't the files

Worth being precise about this, because firms often reassure themselves with the wrong evidence.

The documents are fine. They're in your practice management system, where they've always been. The correspondence is fine. The ledger is fine. Nothing that a compliance audit would look for has gone anywhere.

What leaves is everything that was about to happen:

• The next three steps on each matter, and the order they need to go in
• Which files are quietly at risk, and why
• The conversation with the client in June where expectations were reset
• The half-made decision about whether to brief counsel
• The thing they were going to chase on Thursday
• Which of the other side's people actually returns calls

None of that is a document. It's the working state of sixty live matters, and it existed in exactly one place.

Figure 1 — The files are never the part at risk.

Key point: Your PMS holds what has happened. What walks out the door is what was going to happen next, and that's the part the matter actually runs on.

Why reconstructing it is so brutal

Firms underestimate this task badly, and it's worth being fair about how hard it is.

"If the work isn't documented as you go, handover means sitting down and recalling the state of sixty matters from memory: progress, risks, next actions, deadlines, all of it. Under time pressure, while still doing the job."

— Ashley Kelso, Hivelight

Consider what's actually being asked. Reconstruct, from memory, the current position of sixty active files. For each: where it's up to, what's next, what's at risk, what's been promised to whom, and when things fall due. Write it down clearly enough for a stranger. Do it in the evenings, over about a fortnight, while still running those same sixty matters.

Nobody does that well. Not because they don't care. The good ones care enormously and stay late trying. It's because it's a memory task at a scale memory doesn't handle. Recall is reconstructive: you rebuild the picture from fragments, and the fragments you happen not to reach for are simply gone. The gaps aren't in the notes. They're in what got remembered.

Which is why the handover document always covers the busiest matters and misses the quiet ones. The quiet ones are where the limitation dates hide.

The version where handover is already written

Now the alternative, and the contrast is stark.

If the work on each matter is captured as it goes (tasks with owners, milestones with dates, notes recorded against the matter as things develop) then at the moment someone resigns, the handover already exists. It was written continuously by the act of doing the work.

The departing lawyer's job changes completely. They're not reconstructing sixty matters from memory. They're walking someone through a structure that's already there, adding the colour that isn't obvious from the record. That's a conversation of a few hours, not a fortnight of evenings.

And it's complete, because it never depended on anyone remembering the quiet files. The matter nobody has touched since March has its next task sitting on it with a due date, exactly like every other matter.

Key point: Handover isn't a task you do at the end. It's either a by-product of how you worked all along, or it's a reconstruction, and reconstructions have holes.

Work should travel up the chain, not into a void

There's a mechanical question underneath all this: when someone is removed from a matter, where does their work go?

In most systems the honest answer is nowhere. The tasks stay assigned to a person who has left, or drop into an unassigned state that nobody has a reason to look at. The work is still recorded; it's just no longer anyone's.

The safer design routes it automatically. When someone comes off a matter, or a task has no assignee, the work travels up to the next appropriate person by role: Paralegal or Law Clerk to Junior Lawyer, to Senior Lawyer, to Matter Lead, to Matter Owner. Administrative roles escalate through their own chain and then cross into the legal one. Nothing needs to be noticed by a human first.

That's how it works in Hivelight, and it's genuinely uncommon in legal software. Most tools will leave a task assigned to a departed staff member indefinitely and consider that correct behaviour.

The practical effect is that the four weeks of notice stop being a race. Work reallocates as people come off matters, rather than waiting for someone to conduct an audit of what the leaver was holding.

(The full chain is set out in legal team roles and responsibilities.)

The dependency nobody names

There's an uncomfortable second-order effect, and it's worth saying plainly because most firms feel it long before they articulate it.

"A firm that doesn't document its work ends up depending on a few people who carry it in their heads. Everyone knows it, including them. And if one of them leaves, it blows a hole in the practice."

— Ashley Kelso, Hivelight

This isn't about anybody behaving badly. It's a structural position that emerges on its own: if the knowledge of how matters run lives in three senior people, then those three people are the firm's continuity plan. That shapes conversations about pay, about workload, about what can be asked of them and what can't, and it does so quietly, without anyone ever needing to say it out loud.

It also caps growth, because the firm cannot expand faster than those individuals can personally absorb.

Documenting the work changes the position for everyone, and it's worth noting it's better for the individuals too. Being the only person who can do something sounds like security, but in practice it means you can't take leave properly, can't move to more interesting work, and can't be promoted out of it. Nobody actually enjoys being indispensable in that particular way.

Anyone should be able to give the client an update

Here's a smaller test that reveals the same thing.

A client rings on a Tuesday and wants to know where things are at. Who in your firm can answer?

If the honest answer is "only the lawyer with carriage", then you don't just have a handover risk. You have a daily capacity problem. Every client update has to be done by the most expensive, most constrained person on the file, because they're the only one who knows.

When the state of the matter is written down rather than remembered, that changes. Anyone with access can give a competent update, which means you get to choose who spends time on client communication and who keeps producing work. During a handover period that's precisely the flexibility you need most: the departing lawyer's remaining hours can go into the work rather than into the phone.

Key point: If only one person can update the client, you're rationing your scarcest resource on your most delegable task.

Onboarding whoever comes next

The other half of a handover is the arrival, and documented work shortens it dramatically.

When instructions travel on the tasks themselves, a new starter doesn't need the process explained before they can begin. They pick up a task, and the task tells them what's required and what good looks like here. They're trained while working rather than in an induction week they'll have forgotten by the time it's relevant.

The compounding effect matters more than the first few weeks. Every time a process gets refined, that refinement is captured in the workflow and reaches everyone using it, including people who haven't joined yet. Knowledge accumulates in the practice rather than in individuals, which is the only version that survives turnover.

(This is the wider theme of legal matter management, on running the firm so it doesn't depend on who happens to be in the building.)

The planned version: leave, illness, secondments

Handover isn't only about resignations, and treating it that way misses most of the value.

The same structure means a fortnight of annual leave doesn't stall six matters. It means someone off sick on Monday doesn't create a scramble. It means parental leave can be planned as a transition rather than survived as a gap. In each case the question, what was this person about to do, and who does it now?, has an answer that already exists.

There's a planning dimension too. If you can see workload distribution across the year, you can schedule leave so the firm is never skeleton-staffed during a heavy period, and you can arrange cover before the absence rather than during it. Hivelight's demand-forecasting view exists for exactly this: a heatmap of when work is due, by person and across the team.

The firms that handle resignations calmly are almost always the ones that already handle annual leave well. It's the same capability, tested at a different scale.

Key takeaways

• The files aren't what's lost. What leaves is the working state of every live matter: next steps, risks, promises, half-made decisions.
• Reconstructing sixty matters from memory is a task nobody does well, and the gaps land on the quiet files where the risk hides.
• If work is captured as it happens, the handover already exists. It becomes a few hours of colour, not a fortnight of archaeology.
• Work should escalate automatically when someone comes off a matter, not sit assigned to a person who has left.
• Undocumented firms depend on a handful of people carrying it in their heads. That caps growth, and it isn't good for those individuals either.
• If only one person can update the client, you're spending your scarcest hours on your most delegable task.
• Handover capability is the same capability as handling annual leave. If leave is smooth, resignations will be too.

Want to see how Hivelight keeps matters moving when your team changes? Book a demo →

Frequently asked questions

What happens to matters when a lawyer leaves a law firm?

The files stay where they are: documents, correspondence and ledgers are all in your practice management system. What leaves is the working state of every live matter, which is the part the matter actually runs on. The next three steps, which files are quietly at risk, what was promised to the client in June, the half-made decision about counsel. If that lived only in one person's head, it goes with them.

How do I get proper handover notes from someone who's resigning?

Recognise what you're asking for. Reconstructing sixty matters from memory, under time pressure, in the evenings, while still running those same matters, is a task nobody does well no matter how conscientious they are. You'll reliably get the busiest fifteen files in good shape and the quiet ones missed, which is where limitation dates hide. Ask for a walkthrough of what's already recorded rather than a document written from scratch, and accept that the completeness was decided months ago by how the work was captured.

How long should a handover take?

If the work was captured as it happened, a few hours of conversation adding the colour that isn't obvious from the record. If it wasn't, a fortnight of evenings that still won't be complete. The difference isn't effort or goodwill. It's whether the handover was being written continuously all along.

What if the person leaving is the only one who knows how things are done?

That's the more serious problem, and it's structural rather than personal. A firm that doesn't document its work ends up depending on a few people who carry it in their heads, which caps growth and quietly shapes every conversation about pay and workload. It isn't good for those individuals either: being indispensable in that particular way means you can't take proper leave, move to more interesting work, or be promoted out of it.

How do we cover annual leave without stalling matters?

The same capability, tested at smaller scale. If the state of each matter is recorded and work routes by role rather than by name, a fortnight away doesn't stall six files, because the question of what happens next already has an answer. Firms that handle resignations calmly are almost always the ones that already handle leave well.