Where does work wait in a professional services firm?

Rarely in the doing. A fee earner can usually draft a letter, check a schedule or review a file quickly once they have it. The delay is in getting it to them and getting it away from them. Common waiting points:

  • a new instruction sitting in a shared inbox until someone decides who should take it;
  • a draft waiting for partner review, with no sign of how long it has been there;
  • an invoice held because nobody has confirmed the work is complete;
  • a request to a colleague for information that is answered, then lost in a thread;
  • a status update that exists only in one person's head.

None of these is hard work. Together they are the reason a two hour job takes a week to leave the building, and why senior people spend their days chasing rather than advising. The partner bottleneck describes one version of this.

What parts of a workflow can be automated?

The mechanics of movement. Specifically:

  • Routing: deciding who should pick something up, based on rules you already apply informally, such as client, work type, value or availability.
  • Handoffs: passing work on with everything the next person needs attached, so they do not have to go looking.
  • Approvals: sending items to the right approver, reminding them, and holding the next step until they respond.
  • Status: recording where each item is, so anyone can see it without asking.
  • Logging: keeping a record of who did what and when, which doubles as an audit trail.

Where the workflow involves reading or summarising incoming material, such as sorting enquiries or triaging email, AI handles that part and passes a structured result on. See email triage and enquiry qualification for two common starting points.

What should stay manual?

Decisions that carry professional or commercial accountability. Whether to accept an instruction, whether advice is right, whether a fee is appropriate, whether a document can go to a client. A well designed workflow makes each of those decisions faster and better informed. It never makes them on someone's behalf. Anything going to a client is signed off by a named person.

What does a rebuilt workflow look like?

Take a firm where new instructions arrive by email to a shared address. Today, a coordinator reads each one, guesses who might take it, forwards it, and follows up if nothing happens. In the rebuilt version, each message is read on arrival, the key details are pulled out, the conflict and onboarding checks are started, and the instruction is routed to the right team with a summary. The team lead accepts or reassigns it in one step. The coordinator stops forwarding and starts handling the exceptions that need a person.

The same approach applies to invoice approval, document sign-off, supplier onboarding and internal requests for information.

How is a workflow rebuilt in 30 days?

We start by following real items through the workflow and noting each point where they stop, who unblocks them and how. That map shows which rules are already being applied informally, which approvals matter and which are habit. The routing and approval logic is then built into the tools you already use and run against live items for two weeks. In week four the team switches over and the old route is closed. Support continues for 30 days after go-live.

If you are not yet sure whether your hours are lost in handoffs or in the work itself, the audit helps separate the two.