Meet on Job Status Every Month
Once a month, the project managers, the controller and the owners should sit at the same table and look at the same report.
It sounds simple. In a lot of companies, it never happens. The project managers see their jobs. The controller sees the books. The owners see whatever reaches them. Everyone has a different picture.
The exam item
One ROOI exam item reads: Project managers, the controller, and the principals meet on job status.
For each job, the report shows three things: percent complete, cost to date and the forecast at completion.
$90,000 found in month three
Here's an example. A $1.5 million job was bid at 15 cents of margin per dollar. The forecast now says 9 cents.
That's $90,000 of margin that won't show up.
Found in month three, there are choices. Talk to the foreman. Look for a change order. Adjust the crew. Rethink the sequence. Found at closeout, there's a write-down.
The meeting matters as much as the report
The meeting matters as much as the report.
A report emailed around gets skimmed. A report on the table, with the people who own each number in the room, gets questions. Why did this forecast drop? What's the plan? Who's on it?
When the field and the office look at the same numbers, nobody gets surprised. That's the whole point.
Who owns your numbers?
The meeting works best when every number has an owner.
When a job starts losing money, whose job is it to notice first? If the answer is the owner, at closeout, the numbers don't have owners.
Here's one way to split it, as an example:
- The estimator owns the estimate.
- The project manager owns the job budget.
- The foreman owns field hours.
- The controller owns the monthly profit and loss.
- The owner owns the return on overhead.
Each person knows their number, sees it often and answers for it. That's how problems get found in week three instead of month nine.
How I'd run it
Keep it simple and keep it regular:
- Same day every month, after the statement is done.
- Every open job on one report, in the same format.
- Each project manager walks through their jobs: percent complete, cost to date, forecast.
- Any forecast that dropped gets a reason and a plan.
- The controller ties the jobs back to the company numbers.
- The owner looks at what it all means for the year's return.
An hour or two, once a month. It's some of the best time an owner can spend.
Good inputs make good meetings
The meeting is only as good as the numbers it uses. Labor hours by cost code, reported weekly, make the forecast real. Read report labor hours against the estimate weekly. A useful monthly statement ties it to the company. Read is your financial statement useful.
What changes after a few months
After a few months of meetings, something shifts. Project managers start bringing the bad news early, because they know the meeting is coming and they'd rather show up with a plan. Forecasts get more honest. The controller and the field stop working from different numbers. And the owner stops being surprised at closeout, which is worth the hour by itself.
Check your systems
The ROOI exam asks whether you meet on job status, and 19 other questions about how information and responsibility move through your company.
You'll see your score against same-size firms, the pretax profit at stake each year and the first step to close each gap.