WIP Management for Accounting Firms: Before It Manages You

What WIP actually measures in a firm

WIP is work the firm has delivered but not yet billed — effort that has left the building without a price attached. It is not an accounting abstraction: it is the gap between what the team did and what any client has been asked to pay for.

That gap is where fee pressure hides. Every week a file sits unbilled, the eventual invoice drifts further from the client's memory of the work, and the conversation gets harder.

Why WIP accumulates silently

WIP grows because delivery and billing run on different clocks: work happens daily, invoicing happens at milestones, and nothing in between forces a look at the widening gap. Scope creep compounds it — small unpriced additions feel too minor to bill and too awkward to raise later.

Stalled files are the other engine. A project waiting on client documents or a partner review is still accruing effort in everyone's mental ledger, but no one is watching its age.

The 20-minute weekly WIP review

Once a week, sort open engagements oldest-first and ask three questions of each: can any portion be billed now, what exactly is blocking completion, and has the scope moved beyond the letter. Twenty minutes of this beats any quarter-end cleanup, because the answers are still fresh enough to act on.

The discipline is the sort order. Newest work is always the most interesting and the least in need of attention; the review exists to force eyes onto the files everyone has stopped mentioning.

• Can any portion be billed now?
• What is the specific blocker, and whose is it?
• Has scope moved beyond the engagement letter?

Age WIP the way you age receivables

Put open work into the same buckets you use for receivables — current, 30, 60, 90-plus days — and treat movement between buckets as the alarm, not the balance itself. A firm that ages receivables religiously but never ages WIP is watching the second-oldest problem and ignoring the oldest.

The older the bucket, the harder the eventual conversation, because the client's memory of the work's value decays faster than the firm's memory of the effort.

Bill in motion, not at the end

The engagement letter is where WIP is prevented: write billing points into the scope — on acceptance, at interim delivery, at filing — so invoicing follows delivery instead of trailing it by a season. A letter that only prices the total has already decided the firm will carry the work.

SpidNums builds engagement letters from the Services catalogue with custom line items where needed, and load-from-history means last year's structure — including its billing points — is the starting draft, not a blank page.

Prevent WIP with status hygiene

Most aged WIP was once a project that quietly stopped moving, so the cheapest prevention is making stalls visible the week they happen. Statuses must mean something, and changing them must be trivial, or the board decays into fiction within a month.

In SpidNums, projects and their ordered tasks change status inline from the table or Kanban view, and the dashboard's 'Needs attention' list surfaces work that is drifting — which is usually the same work that will surface in the WIP review three weeks later, at higher cost.

Write off deliberately and keep the reasons

Some WIP will never bill at full value, and writing it off promptly is healthier than carrying it as fiction. The discipline is recording why: scope misjudged, work stalled on the firm, client relationship subsidised. Reasons turn write-offs from losses into pricing data.

Patterns in the reasons are next year's fix. Repeated 'scope misjudged' on one service type means the catalogue price is wrong; repeated 'stalled on client' means the document collection system needs teeth.