Your WIP Report Shouldn't Be the First Time You Find Out a Job Has a Problem
The WIP meeting begins.
A project's projected margin dropped.
Everyone looks at the project manager.
“What happened?”
The problem usually didn't happen yesterday.
It may have been developing for weeks—or months.
The real question is:
Why is the WIP report the first place leadership is seeing it?
WIP Is an Output
A WIP schedule is incredibly important in construction accounting.
But WIP doesn't create good financial management.
It reflects it.
Accurate WIP depends on what happened upstream:
Job-cost accuracy
Timely commitments
Change management
Cost forecasting
Revenue projections
Project-manager involvement
Communication between accounting and operations
If those processes aren't working, the WIP report simply exposes the problem after the fact.
Margin Erosion Usually Leaves Clues
Projects rarely lose margin without warning.
There are usually signals:
A subcontract package comes in over budget.
Production isn't meeting expectations.
A pending change hasn't been approved.
A cost exposure isn't reflected in the forecast.
Schedule delays create additional general conditions.
Material pricing changes.
A buyout savings assumption doesn't materialize.
A PM knows something is going wrong but hasn't quantified it yet.
Individually, these may seem manageable.
Collectively, they change where the project is going to finish.
Forecasting Should Be Continuous
A monthly forecasting process shouldn't mean:
“It's month-end. Update your forecast.”
Strong project financial management happens throughout the month.
When something changes, the forecast should change.
That doesn't mean leadership needs a new WIP schedule every Tuesday.
It means the people closest to the project are continuously evaluating:
What do we know today that changes where this project is going to finish?
That's a much more powerful question than:
“Did you update Procore?”
Accounting Can't Forecast the Project Alone
Accounting can identify trends, challenge assumptions, review cost activity, and facilitate the WIP process.
But accounting isn't managing the subcontractors.
It isn't seeing field productivity.
It isn't negotiating every change.
It isn't sitting in project meetings.
The project team has information accounting doesn't have.
Accounting has financial information and perspective the project team may not have.
You need both.
The strongest WIP processes aren't owned exclusively by accounting or operations.
They're a shared financial management process.
Make WIP Less About the Meeting
If your WIP meeting regularly produces surprises, don't just redesign the meeting.
Look at everything happening before it.
Are project teams forecasting consistently?
Are commitments current?
Are pending changes visible?
Are cost exposures identified?
Are PMs trained to understand margin?
Does accounting know what's happening operationally?
Do your systems make this information easy to see?
The goal isn't a better WIP meeting.
The goal is fewer surprises by the time you get there.
At Mosaic Performance Architects, we help contractors strengthen the processes connecting project management, forecasting, accounting, and WIP—so leadership has better financial visibility before problems reach the financial statements.
Good WIP reporting starts long before the WIP report.