What we're actually looking at
A workflow audit maps one process end to end — every step, every handoff, every place a matter stalls between intake and the file closing. It is not a software recommendation and not a strategy session. It is a map of what actually happens, as opposed to what the procedures manual says happens.
At a firm of about a dozen people, that map almost always surfaces the same three gaps, in roughly the same order.
The conflict check nobody can point to
The most common failure isn't dramatic. It's a conflict check that happened, probably, but that nobody can produce a record of.
Without a document management system that can generate a searchable client and matter list, checking for a conflict means a person — usually a paralegal — searching by memory, a shared spreadsheet that's a few weeks out of date, or asking around the office. The check gets done. But it gets done inconsistently, and there's no artifact proving it happened until someone — a client, an insurer, opposing counsel — asks for one. That's the gap: not that conflicts get missed often, but that the firm can't demonstrate its own process when it matters.
Billing reconstructed from memory
The second pattern: time entries written up at the end of the day, or worse, the end of the week, instead of at the moment the work happens. A call that ran 22 minutes becomes "0.5 hrs" because that's what's rememberable three days later. Nobody's stealing time. The system just doesn't capture it as it happens, so the record drifts toward round numbers and toward whatever's easiest to defend if a client asks.
Matter numbers, assigned twice
The third: new matter numbers assigned by whoever opens the file first, sometimes to two different matters in the same week, because the numbering lives in someone's head or a notebook rather than in a system that hands out the next number automatically. Small, but it compounds — billing, conflicts, and document filing all inherit whatever number the matter got assigned, so an error here doesn't stay contained to one place.
What the audit changes
None of these three are software problems first. They're workflow problems that happen to get fixed with software. A workflow audit's job is to find them, price what each one is actually costing — not in the abstract, but in the hours a specific person spends working around the gap every week — and recommend the smallest build that closes it. Sometimes that's a document management system. Sometimes it's a shared intake form. It's never the whole practice management suite the firm was quoted last year and never fully implemented.