Building a document intake workflow that survives your busiest month

Most firms have an intake process that works beautifully at twelve matters and falls apart at forty. It is tempting to read that as a staffing problem. It usually is not. It is a design problem that was invisible at low volume, because at low volume one person can hold the whole thing in their head.

The tell is specific: when things get busy, work starts being tracked in a person rather than in a system. Ask where a matter stands and the answer is “let me check with Dana”. That is fine in March and it is a serious problem in the week Dana is out.

Here is how to build an intake that does not depend on anyone’s memory.

Define “complete” before anything arrives

The root cause of intake chaos is that nobody wrote down what a finished file looks like.

For each matter type you handle, list the documents required to consider intake complete. Not a wish list, the actual minimum. A personal injury intake might be six items. A simple estate plan might be four. Write them down once, per matter type, and the list becomes the thing you work against rather than a judgement somebody makes each time.

This single artefact does more for throughput than any software. It turns “how is the Okafor matter going” from a conversation into a comparison. It lets a new hire do intake in week one. It makes the chase specific, which is the only kind of chase that works.

Then encode it. If your system supports document types, make them match the list rather than being generic; document rules and types covers defining your firm’s own set. Generic types like “Other” are where intake goes to die.

One intake queue, not five

At volume, the killer is not the work, it is reconciliation. If documents arrive by email, by portal, by post and by hand, somebody has to merge four streams into one picture every morning, and that person is doing an hour a day of work that produces nothing.

Collapse it. One channel in, everything else is an exception that gets moved into that channel the moment it arrives. The post gets scanned and uploaded the same day. The document handed over at a meeting gets photographed before the client leaves the room.

This is also where a lot of the chasing disappears, because a single queue makes “what is outstanding” a filter rather than an investigation. Finding documents covers the search and filter side once the volume is real.

Make ownership explicit on arrival

Two failure modes bracket every intake process. Either everything is assigned to one person, who becomes the bottleneck, or nothing is assigned to anyone, and documents sit in a shared space that everybody assumes somebody else is watching. The second is more common and much worse, because it looks fine until a deadline passes.

The fix is that every incoming document gets an owner at the moment it arrives, not at the point somebody triages it later. Owner means one named person, not a team. Teams do not follow up. People do.

Document assignments covers how assignment works mechanically, and user roles and permissions is worth reading alongside it, because the roles decide who is even eligible to own what.

A practical refinement: assign to a role for routine matter types and to a person for anything unusual. Routine work should not require a decision. Unusual work should.

Status has to be visible without asking

If checking the state of a matter requires opening files, your process has a hole in it that grows linearly with volume.

What you want is a single view where the state of every open intake is legible at a glance, with three categories at minimum: waiting on the client, waiting on us, and done. Anything more elaborate than that tends not to get maintained.

The discipline is that status changes when the work changes, not at a weekly review. A status field updated once a week is a status field that is wrong four days out of five, and people stop trusting it, and then they go back to asking Dana. Document status and approvals covers the states available and how they move.

The test for whether this is working: a partner should be able to answer “what are we waiting on for the Okafor matter” from their phone, in the corridor, in under fifteen seconds. If they cannot, the status is living in someone’s head.

Automate the chase, personalise the escalation

Chasing is the largest hidden cost in intake, and most of it is unnecessary. The first reminder, the second reminder and the third reminder are all identical, all predictable, and all a waste of a skilled person’s afternoon.

Let the system send those. Reminders that go out on a schedule are not rude, they are what the client expects from a bank or an insurer, and the client who forgot genuinely wants the nudge. Notifications and alerts covers what can be sent automatically. On keeping your own staff from being buried by the same traffic, be warned that the controls are coarse: one firm-wide email switch and no per-person settings — see notification preferences.

Where a person should get involved is the escalation. After the third automated reminder, something is actually wrong. The client cannot find the document, or does not understand what is being asked, or has gone quiet for a reason that matters to the matter. That is a phone call, and it is worth a skilled person making it, which they now have time to do.

Build for the month you dread

The last principle is a design stance rather than a step. Do not build the process that works in a normal week. Build the one that works in the worst week of your year, and then run it all the time.

Concretely, that means the process should not require the person who designed it. It should survive somebody being out for a fortnight. It should let a temp or a new hire be useful on day two with a written page in front of them. And it should degrade gracefully: when you fall behind, it should be obvious what is behind, rather than everything looking equally fine until something is very much not.

Firms that do this find the busy month is still busy. It is just no longer frightening, because the answer to “where are we” is on a screen instead of in a person.

If you want to compare your current intake against this shape, tell us what your matter types look like and we will map it out with you.