Team practices

How to Review Work Without Becoming a Bottleneck

When every draft waits on one senior's desk, the chamber moves at the speed of their inbox. Review can protect quality without becoming the choke point.

In many chambers, everything funnels through one person. Drafts pile up on the senior's desk, juniors wait to hear back before they can move, and the whole practice runs at the speed of a single overloaded inbox. The senior feels indispensable and exhausted in equal measure. The instinct that causes this, that quality requires checking everything personally, is understandable and self-defeating. The senior becomes the constraint on the very output they are trying to protect. Review can be rigorous without being a bottleneck, but it takes deliberate design.

Make drafters submit context with the work

Half the time a reviewer spends is reconstruction: what is this, what was it for, what did the drafter already decide. Push that work back to the drafter. Require a short cover note with every submission stating the purpose, the source documents relied on, the choices made and why, and the points the drafter is unsure about. Now the reviewer starts oriented, goes straight to the risk, and reviews in a fraction of the time. A draft submitted without its context should come back unread, with a request for the note.

Review by risk, not by arrival order

Not every document needs the same scrutiny, and treating them as if they do is what clogs the desk. Sort by consequence:

  • High stakes, an unusual pleading, a novel argument, a hard limitation date: full personal review.
  • Routine but consequential: review the risky sections, trust the standard ones.
  • Low stakes and well within a junior's proven competence: spot-check, or let it go.

Applying maximum rigour to a routine notice steals the attention a difficult petition needs. Match the depth of review to what is actually at stake.

Push the standard down, not just the tasks

The lasting fix is not reviewing faster; it is needing to review less. Every recurring correction is a signal that a standard lives only in your head. Write it down, a checklist, a playbook, an annotated model, so juniors can meet it before the work reaches you. A team that has internalised the standard submits cleaner drafts, and the reviewer moves from catching basic errors to exercising the judgment that only they can supply.

Give feedback that reduces the next review

Comments that fix this draft but teach nothing guarantee the same review next time. Comments that explain the underlying reasoning shrink future review, because the drafter stops making the class of error. The extra minute spent explaining why an edit was needed is an investment that pays back every subsequent draft. Over months, this is what turns a junior from someone whose work must be checked into someone whose work can be trusted.

Keep a shared record of corrections

When a reviewer's decisions live only in scattered comments, the same point gets corrected across three different juniors who never see each other's feedback. A shared note of recurring corrections and settled preferences lets drafters self-correct before submitting, and it stops the reviewer being the sole keeper of every standard. The knowledge becomes the chamber's, not one person's, which is exactly what makes the reviewer dispensable in the healthy sense.

Let go of what does not need you

The hardest step is accepting that some work does not require your eyes at all. A competent junior handling a routine matter within their proven range does not need every line checked. Reserving your review for where it changes the outcome, and trusting your team elsewhere, is not a lowering of standards. It is the only way a practice grows beyond what one person can personally inspect. A reviewer who checks everything protects today's quality at the cost of tomorrow's capacity.