The Question Neither Your Ops Meeting Nor Your Finance Meeting Is Asking

Most established operational businesses run two management rhythms. There's an operations meeting — weekly, focused on delivery — and a finance meeting, usually monthly, focused on results. Both are run by capable people. Both cover their own territory well.

And there's a specific question that falls between them, which is where a great deal of margin visibility is lost.

Two meetings, one business

The operations meeting deals with the physical business. Where is each job up to, what's on programme and what isn't, who's on which site next week, what's holding up the fitout, whether the crane is booked. It is grounded in what's actually happening on the ground, and the people in the room know their jobs intimately.

The finance meeting deals with the financial record. Revenue and margin against budget, debtors and ageing, cash position and forecast, overhead variance, bank covenants. It is accurate, it reconciles, and it is typically several weeks behind the operational reality.

Neither meeting is wrong. But operations discusses progress without cost, and finance discusses cost without progress. The two never meet at job level.

Where the gap shows up

The question that requires both, and gets asked in neither, is this: for each live job, what is the relationship between physical progress, claimed value and cost incurred?

Three numbers. Every one of them exists somewhere in the business.

Physical progress lives with the project manager, and is usually reliable, if approximate.

Claimed value lives with the contract administrator, in a claims schedule that may or may not be visible to anyone else.

Cost incurred lives in the accounting system, though usually with a lag and often without committed costs included.

Individually, each is unremarkable. Together, they tell you the truth about a job while there's still time to act.

A job 70% complete, claimed at 55%, at 68% of budgeted cost is under-claimed. It's performing fine, but you are financing the client. That's a cash conversation, and it's fixable this week.

A job 45% complete, claimed at 50%, at 62% of cost is in trouble. It is running over and the over-claim is masking it. The reported margin looks acceptable and will deteriorate sharply on the next claim cycle.

A job 80% complete, claimed at 80%, at 84% of cost is telling you the estimate was two points light — useful information for the next tender, and worth acting on before you price similar work.

None of those readings are available from either meeting on its own.

Why WIP is wrong in so many businesses

This is the practical explanation for something operators often assume is a technical accounting problem. WIP adjustments arrive at month-end, they're large, they're difficult to explain, and they move reported profit in ways nobody predicted.

The technical cause is usually that percentage complete has been estimated by finance from cost incurred, rather than assessed by operations from actual progress. Cost-based percentage complete is circular — it assumes the estimate was right, which is precisely what's in question.

The structural cause is that the two people who could have given an accurate answer were never in the same room, looking at the same job, at the same time.

One list, three columns

The fix isn't another report. It's a meeting.

Fortnightly. Every live job on one list. Four columns: physical progress percentage, claimed to date percentage, cost incurred against budget percentage, and a comment. Operations and finance both in the room, with the project managers.

Twenty jobs takes forty minutes once the rhythm is established. The first session takes longer, because you'll find something in it — an under-claim, a job running hot, a variation delivered and never priced.

The value isn't in the document. It's in the fact that the person who knows the site and the person who knows the ledger are reconciling the same job in real time, before the month closes and the information becomes historical.

The broader point

Finance without operational context produces accurate reports about a business you can no longer influence. Operations without financial context produces a business that is busy, well-run and less profitable than it should be.

Most businesses have both functions performing well. What they lack is the point at which the two reconcile — and that's usually a meeting, not a system.