WIP: register or argument?

If your WIP requires a few conversations to confirm, it is not WIP. It is an estimate.

Work-in-progress numbers have a habit of looking fine until somebody asks where the number came from. What work does it relate to. Was the time approved. Does the contract allow it to be billed. Is it genuinely recoverable, or is everyone being politely optimistic.

That is the moment WIP stops being a number and becomes a trust test. And the result of that test is binary: you either hold a WIP register or you hold a WIP argument.

The mistaken diagnosis

Most firms read a weak WIP number as a finance problem. Finance owns the balance, finance reports it, so finance must be where the fix belongs — tighter month-end process, a better spreadsheet, an extra review meeting.

That reading is wrong, and it is expensive because it directs effort at the last mile of a chain that broke much earlier.

WIP is not produced at month end. It is produced continuously, by every commercial decision made between the sale and the invoice. Finance is simply the first function forced to state the total out loud. When the number cannot be defended, the failure being exposed is upstream: sales agreed one thing, delivery worked through the messy middle, and finance is left working out what is billable, what should be held, and what is quietly becoming a write-off.

What a WIP register actually requires

Reliable WIP needs three things, and they are unglamorous.

Clear rules for what counts. Which time is billable under which contract, at what rate, under what conditions. Not a convention that experienced people know — a rule the system applies the same way every time.

Current records. Time, cost, milestone and approval states that reflect where the work actually is, not where it was a fortnight ago. WIP built on stale inputs is arithmetic performed on fiction.

Traceability back to source. Every entry in the balance should link to the work it relates to, the contract term that permits billing it, the approval that cleared it, and the reason it is billable, held, adjusted or written off.

The third one is the one firms skip, and it is the one that decides whether the number survives a question. Good WIP is not a more confident estimate. It is an estimate that has stopped being an estimate, because each component can be traced rather than defended.

Where WIP loses its provenance

The leaks are small and individually reasonable.

A discount agreed in the sale that never reached the billing rules. Assumptions in the quote that proved a little optimistic. Scope that grew politely, in increments nobody wanted to make a fuss about. Time entered against the wrong engagement and corrected informally. A change order agreed verbally and documented later, or not at all.

None of those events announces itself. Each one severs a link between a number and its justification.

By the time the margin problem appears in reporting, it has usually been leaking for weeks — through pricing, handover, change control, time capture and approvals. Margin in professional services rarely disappears in one dramatic moment. It drifts through small commercial gaps that look manageable right up until somebody has to explain the final figure.

So the more useful question is not why delivery lost margin. It is whether the margin was ever properly protected in the first place. Where those rules get set is covered on our scoping and quoting page.

The mechanism that makes WIP traceable

The fix is structural, and it is the same fix in every firm: billing and delivery have to share the same governed records, rather than keeping two accounts of the same event.

In practice that means the engagement carries its commercial rules from the point it is quoted. Time entered against it inherits those rules. Approval is a state on the record rather than an email thread. Change orders attach to the engagement they change. Each WIP line is composed of source entries that each link back to work, approval and contract term.

Then the balance is not assembled at month end. It is read.

The part of DAY ONE that does this is the invoicing engine, where traceability runs back to an individual timesheet record — which is what allows an approved invoice, and the WIP behind it, to be explained without reconstruction. There is more on how that works on our invoicing and WIP page.

What this costs

Governing the chain means agreeing your billing rules, approval gates and change-control process before delivery starts, rather than settling them when the invoice is drafted. That is a real cost, paid up front, by senior people, and some firms will decide they would rather keep the flexibility and absorb the argument later.

It also constrains behaviour that currently feels like service. If a rule says work outside an agreed scope is not billable until a change order exists, somebody has to raise the change order before doing the work. Firms whose culture is to say yes first and sort it out afterwards will feel that as friction, because it is friction — the deliberate kind.

And there is a limit worth stating: this does not make the number better, only honest. A firm whose WIP has been quietly optimistic will often find that a traceable register is smaller than the one it replaced. That is the correction working, but it does not feel like a win in the first month.

Register or argument

The distinction is not accounting pedantry. A WIP register is something you can invoice from, report on, and defend to an auditor or an acquirer. A WIP argument is something you negotiate internally every cycle, and lose a little of each time.

What separates them is not effort at month end. It is whether the rules travelled with the work from the beginning.

If WIP still moves after invoices are drafted, that is the signal — and the place to look is the handover between sale and delivery, not the spreadsheet. Our Rowland case study sets out what changed for one firm that rebuilt that chain, including what it took to get there.