Skip to main content

Your process works until the week gets busy

Cody Halovich · 2 November 2026 · 4 minute read

Every new matter at a small law firm gets the same checklist: run the conflict check, send the engagement letter, put the limitation date in the calendar, call the client back within a day. In a normal week it runs on every file. In the week before a large closing, a client phones to ask whether anyone has started on her matter, and the calendar entry for her file is still blank.

The quiet steps go first

Nobody decided to skip that entry. The closing had a deadline, a client on the phone, and a partner asking for updates. The calendar entry had none of those. It was the step nobody would notice missing until much later, so it waited, and then it was forgotten.

This is how documented processes fail in a busy firm. People triage. The urgent item with someone waiting on it gets done. The file note, the follow-up call, the date entry, the second check before something goes out: those slide to later. The last step in a sequence is the most likely to go, because by then the person has already moved on in their head.

None of this means your people do not know the procedure or do not care about it. They know it well. They ran out of minutes.

The firm knew the rule and ran out of time

The legal profession has measured this better than most. LAWPRO, which insures Ontario lawyers, reports that only about 14 percent of its malpractice claims come from a lawyer getting the law wrong, and around two thirds come from human error: missed calendar dates, clients who did not hear back, matters put off or not looked into deeply enough. It ties the rushed communication to lawyers being busier than ever (LAWPRO practicePRO, 2026).

Read that from the owner's chair. The expensive mistakes are not gaps in expertise. They are routine steps the firm already had written down, skipped in a heavy week by someone who knew better.

The cause sits underneath the busy week. When a person runs every step, each new file adds the full set of steps to someone's calendar. Twice the files means twice the steps, and the week does not get longer. Past a certain volume, the routine steps compete with the client work, and the client work wins every time.

A reminder asks a busy person to remember

The usual response is to tell people again. A memo, a training session, a pop-up reminder, a bolder line in the procedure. Each one asks the same busy person to carry one more thing through a week that was already full. It helps for a few days, then the next heavy week arrives.

The step has to stop depending on memory. When a matter opens, the system enters the limitation date from the intake form, sends the client a confirmation that someone has the file, and holds the file from moving forward until the conflict check is recorded. Nobody has to remember any of it, because none of it waits on a person having a spare minute.

That is the real shift. The checklist stops being something a person runs and becomes something the work runs through.

People move to the cases that need them

Once the routine steps run on their own, the person's job changes. They stop typing dates and sending acknowledgements. They handle what the system cannot: the intake form with a missing date, the client reply that needs judgment, the conflict check that comes back with a name on it.

Do not switch it all on at once. Run the system beside the person who does the work today, on the same files, for a couple of weeks, and have them check every output against their own. When it matches on the routine cases, flip the roles. The system runs the routine. The person takes the odd ones.

That exception work has to be someone's job, written down like any other. Name the person who handles the exceptions, where they land, and how quickly they get looked at. Give that person a short weekly review of what came through. An exception queue that belongs to nobody is just a new step that gets skipped when the week gets busy.

Start with the step that goes missing

This week, ask the people who run your most important process one question: the last time things got heavy, which step slipped? They will know. It is usually small, it is usually near the end, and it is usually the one that caused trouble a month later.

Write that one step down in three lines. What starts it, what it needs, and what done looks like. Then write a fourth line: who handles it when it does not fit the pattern. That page is the first step you can take off a busy person's memory and give to the system.

The next step

Have a question this didn't answer?

The discovery call is free. We'll talk about your operation and tell you honestly whether AI automation is the right move.