Collaboration Between Lawyers and Support Staff

Summary

Your firm grows, and somehow everyone is busier while less seems to get done. Not because anybody slowed down. It's that the work of coordinating the work has quietly become a job of its own.

More people means more email, more meetings, more status-chasing, more admin. And that load doesn't grow in step with the firm. It grows faster.

Collaboration in a law firm is really a question of coordination cost: how much effort it takes to get work from one person to the next. Every growing firm eventually reaches the point where that cost becomes the constraint. From there it goes one of two ways. Either coordinating swallows the working day, or the firm under-coordinates and pays for it in misallocated work, progress nobody can see, and the exhausting sense that everything is always urgent.

This guide covers why coordination scales so badly, why hiring rarely fixes it, why your reporting gets less trustworthy as you grow, and the five things that genuinely help. Most of all it names the trap that undoes most attempts, and the reason a new tool so often changes nothing.

Contents

• Why coordination gets harder faster than the firm gets bigger
• The fork every growing firm reaches
• Why your reporting gets slower and less trusted as you grow
• Why throwing bodies at it makes the ratio worse
• Where the work actually stalls
• The holding pattern: what your team does while it waits
• What work standing still actually costs
• The trap: doing the work and documenting the work are two different jobs
• The five things that actually fix it
• What good collaboration looks like on a Tuesday
• How Hivelight approaches collaboration
• Key takeaways
• Frequently asked questions

Why coordination gets harder faster than the firm gets bigger

Most firms expect coordination to grow with headcount. It doesn't. It grows with the number of connections between people, and that's a much steeper curve.

Add one person to a team of five and you haven't added one working relationship. You've added five. Each of them generates its own email threads, its own handoffs, its own "where are we up to on this?" And every new matter multiplies that again, because the same people now coordinate across more files.

You feel it as a set of individually reasonable things that have collectively got out of hand:

• Email volume that no longer fits in the gaps between real work
• A standing meeting that exists so people can find out what's happening
• Status reports assembled by hand, for someone who needs to see across everything
• The general administrative sediment of keeping everyone pointed the same way

None of that is waste, exactly. It's all doing something necessary. But it's coordination overhead, and at some size it stops being a tax you barely notice and starts being a serious claim on the working day. The firm hasn't got worse at anything. It has simply grown past the size where coordination could happen informally, without anyone deciding it should.

Key point: Coordination cost doesn't scale with the number of people. It scales with the connections between them, which is why it seems fine right up until it doesn't.

The fork every growing firm reaches

Once coordinating has become a real cost, a firm ends up on one of two paths. Most oscillate between them.

Path one: pay the cost. Coordinate properly: the meetings, the updates, the reports, the chasing. The work gets coordinated, and coordination eats the day. Fee earners feel like administrators. The genuine complaint here isn't that coordination is pointless; it's that it has become a barrier to doing the actual work.

Path two: skip it. Coordinate less and hope the work sorts itself out. This feels more productive and costs more, in three ways that are all hard to see from the inside:

1. Work ends up at the wrong level. Without a shared view of what needs doing, tasks land wherever they happen to land, usually with whoever noticed. Professional staff pick up work support staff could have done, support staff sit on capacity nobody knew was free, and the firm's most expensive hours get spent on its least demanding work. (This is the subject of delegation in a law firm.)
2. Management can't see it, so can't fix it. Misallocation is invisible without reporting, and reporting is the first thing dropped when coordination gets skipped. So the problem persists. Not through indifference, but because nobody has the information that would let them act.
3. Everything becomes urgent. Work that isn't coordinated in advance surfaces late. It lands on support staff as an emergency, with a tight deadline, inadequate notice and no time for anyone to explain how it should be done. Do that a few times a week and you have built a genuinely stressful place to work, which is how firms lose good support staff. (More in reducing partner bottlenecks.)

Both paths are rational responses. Neither is a failure of effort. They're what's left when coordination is treated as something you do on top of the work, because then your only choices are to spend time on it or not.

The way out isn't picking a side. It's changing what coordination is.

Key point: Coordinate more and it eats the day. Coordinate less and you pay in misallocation, blind spots and manufactured urgency. The trap is the choice itself.

Why your reporting gets slower and less trusted as you grow

Path one has a failure mode of its own, and it's worth following closely because it's the reason so many firms end up with reporting nobody quite believes.

It turns on a single distinction: is your reporting information gathered, or is it aggregated?

Gathered means someone goes and collects it: emails the team, asks for updates, chases the three people who didn't reply, then assembles the result into a report. Aggregated means it accumulates on its own, because people ticking off their own work feeds the reporting system as a by-product.

Gathered reporting decays as you grow, in a loop that tightens on itself:

1. The collection task grows with the team and the caseload. More people to ask, more matters to ask about.
2. So the lag grows. The time between something happening and it appearing in a report gets longer. Days, then a week, then more.
3. So the data is old when it lands. By the time the report is in front of someone, it describes a firm that has already moved on.
4. So people quietly stop trusting it. Nobody announces this. They just start checking with the person directly instead, because they know the report is behind.
5. So it slips down everyone's priority list. The people doing the work are being asked for updates that feed a report they've noticed nobody acts on. Responding drifts to the bottom of the pile, entirely rationally.
6. So collection takes longer still, and the loop goes round again.

The result is the worst of both worlds: reporting that consumes an increasing amount of time while commanding a decreasing amount of confidence. And because it degrades gradually, there's rarely a moment where anyone decides to stop; it just becomes a thing the firm does that everyone privately works around.

The fix isn't chasing harder or building a better template. It's changing where the information comes from. If the record is produced by people completing their own work, it's current by definition, and steps two through six never start.

Key point: Gathered reporting gets slower and less trusted as the firm grows. Aggregated reporting gets more useful, because more work means more signal, not more collection.

Why throwing bodies at it makes the ratio worse

When coordination starts eating billable time, the standard response in legal is to hire. It is comfortably the most common tactic in the profession, and it's worth understanding why it disappoints.

Hiring adds gross capacity. What it doesn't do is make the existing capacity more productive. You've built a bigger engine, not a more efficient one. And since coordination cost rises with the connections between people, a bigger firm generates more of the very overhead you hired to relieve. The wage bill grows reliably; the proportion of it that's recoverable often doesn't. Your return per dollar of salary can quite easily go backwards while revenue goes up, which is one of the more disorienting experiences in running a practice.

There's a bind underneath it, and both ways out lead back in:

• Hire more operations staff (practice managers, assistant practice managers, coordinators) and you have added more people whose job is to ask other people for updates. The professional and support staff now field more requests, which is friction, and which they experience as being chased rather than supported.
• Hire more professional or support staff and you stretch your operations people further. More matters and more staff to keep track of, with the same collection effort spread thinner, so the reporting gets slower, which is exactly the spiral above.

Each hire is defensible in isolation. Together they describe a firm spending progressively more on coordination and getting progressively less from it.

None of which is an argument against hiring. It's an argument against hiring as a fix for this. Growth is worth having. But adding people to a coordination problem multiplies the problem you were trying to solve, and the only way out is to change what coordinating costs in the first place.

Key point: Adding people to a coordination problem adds coordination. Efficiency has to come from how the work is structured, not from how many people are handling it.

Where the work actually stalls

To see the way out, it helps to look at what all that coordination is really for.

A matter is a relay. A lawyer takes it a certain distance and hands it to a paralegal, who takes it further and hands it back. Multiply that by every matter and every person, and the firm's real output is decided by how cleanly those handoffs happen. Almost all your coordination cost (the emails, the check-ins, the status meetings) exists to service those handoff points.

Which means the handoff is where to look. A handoff needs remarkably little: the next person has to know the work is ready, what's required, and by when. When that information travels with the work, the handoff is free. When it doesn't, someone has to move it manually, and that manual movement is the overhead.

The gap never appears on anyone's timesheet. It shows up as a matter that took eleven weeks instead of seven.

Key point: Coordination overhead is just the cost of moving information that should have travelled with the work.

The holding pattern: what your team does while it waits

Here's the part most firms never see, because by definition it happens while nobody is looking.

When the work on a matter isn't written down anywhere, your support staff can't know what's next. They aren't being passive; they genuinely have no way of finding out. So they wait. And because nobody sits still gracefully, they fill the gap: tidying files, chasing something low-value, reorganising a folder, or wandering over to ask a colleague a question that interrupts their work too.

They're busy. They're just not moving anything forward.

Now picture the same team where the work is written down progressively. A paralegal finishing a task looks at the matter, sees what's coming up next, and starts on the item that actually advances it. No email required. They can also see where the pressure is across the team, which means support staff can support each other, not just the lawyer they report to.

That single change also flips the shape of the work.

Undocumented work runs in sequence. The lawyer does something, then tells someone what's next, then waits for it, then reviews it, then says what's next again. Every round trip passes through the same person.

Documented work runs in parallel. The lawyer works on the complex task that genuinely needs them, while support staff prepare the next set of outputs for review at the same time. Same people, same hours, dramatically different throughput, because you removed the queue, not because anyone worked harder.

Figure 1 — The same team and the same hours, in two different shapes. The waiting never appears on a timesheet.

Key point: If your team can only find out what's next by asking you, then everything in the firm runs at the speed of one person.

What work standing still actually costs

There's a line from an earlier Hivelight article that gets to it faster than any spreadsheet:

You're paying for their time but you are not getting a return on it while people are standing still.

That's the visible cost. The bigger one depends on how the matter is billed.

On non-speculative work, the cost is a ratio. Your wage bill doesn't change according to how your people spend their day. What changes is the share of it you can actually charge for. Every hour absorbed by coordination overhead (chasing an update, assembling a report by hand, sitting in a meeting held so people can find out what's happening) is an hour of salary you paid and can't bill.

So the gain from better coordination isn't that anyone works harder. It's that hours move out of internal administration and into billable work. Same people, same salaries, a higher proportion of them recoverable. That's the return on your wage bill improving without a single new hire.

On speculative or no-win-no-fee work, the cost compounds, and it's the one firms consistently underrate. Speed to the next cash-flow event is the return. The faster a matter reaches settlement, the faster you're paid, and the longer it runs, the longer you carry the costs of running it. A matter that drags doesn't just delay your money. It produces a bigger final bill, which raises the odds of a costs dispute with your client and with the other side. A stalled file is quietly building you an argument you'll have to have later.

None of that shows up as a line item. It shows up as a practice that feels flat out and isn't growing.

The trap: doing the work and documenting the work are two different jobs

This is the heart of it, and it's the reason most attempts to fix collaboration quietly fail.

Everything above points the same direction: if the information travelled with the work, the handoffs would be cheap and the coordination overhead would mostly disappear. So firms decide to write the work down. They buy something, or set up a shared spreadsheet, or agree on a process. And for about three weeks it works.

Then it stops, because documenting the work has been set up as a separate act from doing it. It's a second job, done after the first job, by people who are already out of time. When the week gets hard, the second job is the one that gets dropped. Always.

People do what they're measured on

It's worth being precise about why, because "people got slack about it" is the wrong explanation and leads to the wrong response.

Professional staff are measured on billable output. That's the number that shows up in reviews, in remuneration conversations, and in their own sense of whether they had a good week. Updating a report is not that. So when there's an hour left and a choice between one more billable task and bringing the reporting up to date, the billable task wins. Not out of indifference, but because it's the thing the firm has told them counts.

Any system that asks people to act against their own incentives is running on goodwill, and goodwill is a rechargeable battery that discharges on busy weeks.

The same logic reaches further up than most firms admit. Principals and partners routinely defer the business problems (coordination, systems, how the firm actually runs) in favour of one more piece of billable work. And the reason is entirely understandable: billable work feels certain and rewarding. You know what it's worth, you know when it's done, and it pays this month. Fixing coordination is diffuse, slow, and pays later in ways that are hard to attribute. Choosing the certain thing isn't a failure of discipline. It's what any sensible person does when one option has a defined payoff and the other doesn't.

Which is exactly why the answer can't be resolve. It has to be a change to the work itself, so that nobody is being asked to choose.

And once documentation stops, the whole chain unwinds. If the work isn't written down, nobody can pick up what's next. If nobody can pick up what's next, delegating means explaining. And explaining is where delegation dies:

"Nobody delegates because it's faster to do it yourself than to delegate it, explain it, track it and review it. And they're right. It is faster, today. It's also the single thing most likely to cap the size of the practice."

— Ashley Kelso, Hivelight

That's the trap in full. Doing it yourself is genuinely the rational choice for any one task. It's an irrational one across a hundred of them, because it caps the output of every person who could have helped.

The way out isn't discipline, and it certainly isn't nagging. It's collapsing the two jobs into one, by structuring work so that doing it and recording it are the same act. When a task list is the actual plan for the matter, ticking a task off isn't admin on top of the work. It's just what finishing looks like.

And this is what resolves the fork. The choice between paying for coordination and skipping it only exists while coordination is a separate activity. Make it a by-product of doing the work and the economics invert: coordination that used to grow with every new person and every new matter now costs roughly nothing to maintain, because nobody is maintaining it. They're just working, and the record is what working leaves behind.

Key point: If recording the work is a separate job from doing the work, it will not survive a busy week. It has to be the same act, which is also the only version that scales as the firm grows.

The five things that actually fix it

Once the work is captured as it happens, five things do the real work. Each has a guide of its own.

1. Clear roles. Not job titles, but responsibility for specific work on specific matters. The enemy here is dilution: "If a job is everyone's job, it's no one's job. That's how you end up with four people standing around a missed deadline, all saying the same thing: I thought you were doing that one." (Go deeper: legal team roles and responsibilities.)

2. Precedents for delegating, not just for drafting. This is the one firms miss, and it's the one that moves the needle most.

Your practice already accepts this logic everywhere else. Nobody drafts a lease from a blank page. You keep a precedent suite and a clause bank, because composing the same document from scratch every time is obviously wasteful. Delegation is composition in exactly the same sense. Every time you hand work over, you're assembling a scope, an instruction, a standard and a deadline. And most firms assemble it fresh, every single time, from memory, usually while busy.

A workflow template is a precedent for delegating: the set of tasks a matter type needs, with the instructions already attached, ready to be applied rather than written. That removes the single largest cost of delegating, which is the explaining, and the explaining is precisely what made "faster to do it myself" true in the first place. Do it once for a matter type and you've done it for every matter of that type you'll ever run.

The flip side matters just as much, and it's where most template programmes die. A precedent you can't adapt is a precedent nobody uses. No one sends a template lease unamended; they apply it and then adjust it to the deal in front of them. Workflow templates need exactly the same latitude: apply, then adapt to this matter, this client, this fee earner's way of running things. A template that must be followed to the letter gets abandoned the first time it doesn't fit, and abandoned work goes undocumented, which is where we came in. (Go deeper: how to enforce matter templates firm-wide.)

3. Delegation that survives contact with a busy week. Which means a clear task, an instruction attached to it, and a way to see it's been done, so that handing work over doesn't mean losing sight of it. (Go deeper: delegation in a law firm.)

4. Queues you can see. Work piles up at the top of every firm, and the pile is usually invisible, including to the person holding it. A visible queue can be triaged. An invisible one is just stress. (Go deeper: reducing partner bottlenecks.)

5. Work that doesn't live in one person's head. So that leave, illness and resignations are inconveniences rather than emergencies. (Go deeper: handover without the drop.)

Together they produce something firms rarely get to have: a practice where the plan for the work is common property rather than private knowledge.

"The best practitioners I know treat their support staff as the hands and feet through which the work gets done. The ones who don't end up doing all of it themselves, and wondering why the firm won't grow."

— Ashley Kelso, Hivelight

What good collaboration looks like on a Tuesday

Not in theory. On an ordinary Tuesday in an ordinary week:

• A paralegal finishes a task at 10am and starts the next one without asking anybody, because the matter tells them what's next and which items matter most.
• A lawyer spends the morning on the one task that genuinely required a lawyer, while two other matters progress in parallel.
• A client rings for an update, and whoever picks up the phone can give them one, because the state of the matter is written down, not remembered. You get to choose who spends their time on client communication instead of being forced to use the person who happens to hold it all in their head.
• Someone is off sick, and their work routes to the next appropriate person instead of sitting untouched until Thursday.
• Nobody asks "where is this up to?", because everybody can already see.

That last point is the real test. In a firm that collaborates well, the status meeting has nothing to report. The reporting already happened, as a by-product of people doing their jobs.

How Hivelight approaches collaboration

Hivelight is built around exactly the problem this guide describes: making the work visible so it can move between people without a conversation each time.

It sits on top of the practice management system you already use (Clio, Actionstep or Smokeball) rather than replacing it. Your PMS stays the system of record for billing, documents and accounts. Hivelight is where the firm sees and coordinates the work itself: what needs doing on each Matter, who's doing it, and where it's up to.

The design answers the trap directly. Work is broken into Tasks grouped under Milestones, and a Roadmap template lays that structure onto a matter from the start, with instructions travelling on the tasks themselves. Because the task list is the plan, ticking things off isn't a documentation chore performed afterwards; it's just how work gets marked done. The documentation is a by-product, which is the only version that survives a busy fortnight.

Two things follow from that. Everyone can see what's next without asking, so the team stops running in sequence. And when people change (leave, illness, resignation) Tasks route automatically to the next appropriate person by role, so work doesn't sit in a vacated seat.

See how Hivelight approaches collaboration →

Key takeaways

• Coordination cost scales with connections, not headcount, which is why it feels manageable right up until it doesn't.
• The fork is the trap. Coordinate more and it eats the working day; coordinate less and you pay in misallocated work, blind spots, and manufactured urgency.
• Look at the handoffs. Nearly all coordination overhead is the cost of manually moving information that should have travelled with the work.
• Undocumented work forces everything into single file. Documented work lets professional and support staff run in parallel: more output from the same hours.
• Gathered reporting decays as you grow. Longer to collect, older when it lands, trusted less, deprioritised further. A loop that tightens on itself. Aggregated reporting gets better with scale instead.
• Hiring adds gross capacity, not efficiency. More operations staff means more people chasing updates; more fee earners means thinner reporting. Both routes raise the wage bill and lower the share of it you can bill.
• On non-speculative work the cost is a ratio. Coordination overhead is salary you paid and can't charge for. On speculative work it's slower cash flow plus costs-dispute risk.
• The trap is separation. If recording the work is a second job, it won't get done, because people do what they're measured on, and nobody is measured on reporting.
• Fix it structurally: clear roles, precedents for delegating, delegation with visibility, queues you can see, and work that doesn't live in one person's head.
• Treat delegation like drafting. You wouldn't compose a lease from scratch each time; don't compose the instructions for routine work from scratch either, and make the templates adaptable, or nobody will use them.

Frequently asked questions

How can I improve collaboration between lawyers and support staff?

Start by making the work visible, not by changing how people communicate. Most collaboration problems in a firm are handoff problems: the next person can't see that work is ready, what's required, or by when. Fix that and a large share of the email, meetings and status-chasing stops being necessary. Communication fixes fail because they depend on someone remembering to communicate, and that's exactly what breaks in a busy week.

Why is teamwork important in a law firm?

Because a firm's output is set by how cleanly work moves between people, not by how hard any individual works. A matter is a relay, and every handoff is a place where days can be lost without anyone recording the loss. Two people who get along well can still hand work between them badly, which is why teamwork in a firm is a structural question rather than a social one.

How do I know whether coordination is actually costing us money?

Two tests. First, what share of your fee earners' day goes on internal administration rather than billable work: coordination overhead is salary you've already paid and can't charge for. Second, whether people wait. If support staff routinely can't start the next thing until someone tells them what it is, the firm is running in sequence when it could be running in parallel, and that costs you capacity you're already paying for.

Do we need software for this, or can we fix it with better process?

Most of it is process. Clear ownership on each task, allocating by role rather than by name, agreeing what genuinely needs review: all of that can be done on paper by a rigorous team. Two things can't. Keeping the record current without someone maintaining it as a separate job, and re-routing work automatically when people change. Those need a system, and they're the two that break first as a firm grows.

Why does hiring more people not fix it?

Because coordination cost rises with the connections between people, not with headcount. More operations staff means more people asking others for updates; more fee earners means your existing operations staff are stretched thinner and the reporting slows down. Both raise the wage bill and lower the proportion of it you can bill. Hiring is worth doing for growth, but it's not a fix for this.