Most construction businesses review their major projects regularly. The quality of those reviews varies enormously. At one end, a project review becomes a detailed discussion about what happened on site during the month. At the other, management receives a financial report full of numbers but very little explanation of what is changing operationally. Neither is enough. A good project review should connect delivery, commercial position, financial performance and cash. The objective isn't simply to review the project. It is to identify changes early enough that management can influence the outcome.

Start with the forecast outcome Management should be able to understand the expected project result quickly. At a minimum:

  • current forecast revenue
  • forecast final cost
  • forecast profit
  • forecast margin
  • movement from the previous forecast.

The movement is particularly important. A project moving from 10% to 8% margin deserves an explanation. Likewise, a project moving from 8% to 10% should be understood. Management should know what has changed rather than simply receiving a new number.

Review cost to complete Historical costs matter, but the remaining cost determines the final result.

The review should therefore challenge: Remaining labour Productivity Plant Materials Subcontractors Project overhead Program duration Close-out costs A useful question is: "What has changed since last month that should change our view of the cost to finish?" If the answer is nothing, an unchanged forecast may be entirely reasonable. But it should be the result of assessment rather than simply carrying last month's numbers forward.

Connect the financial forecast to the program The project program and financial forecast need to agree. If completion has moved three months, management should understand the financial impact. Additional site overhead may arise. Plant may remain longer. Supervision continues. Temporary works or facilities remain in place. Delay-related commercial positions may emerge. A financial forecast that still assumes the original completion date isn't reflecting the operational project.

Review commercial position separately Variations and claims deserve their own discussion. For material items, management should understand:

  • value submitted
  • value included in forecast
  • customer assessment
  • current status
  • expected resolution
  • cash already spent
  • action required.

This helps distinguish commercially secure project earnings from value that remains dependent on negotiation or entitlement. A large variation balance shouldn't simply appear as one number. Management needs to understand its quality.

Review subcontract exposure Subcontract packages can materially change project outcomes. The review should consider: Current commitment Work performed Approved changes Outstanding claims Expected final cost Commercial disputes Remaining scope The purchase order value is not necessarily the final cost. Known exposures should enter the forecast before the final subcontract account is agreed.

Review WIP and billing A profitable project can still create significant working-capital pressure. Management should therefore understand:

  • WIP
  • unbilled work
  • claims submitted
  • certification status
  • invoice timing
  • unresolved billing issues.

If WIP is increasing, the project team should explain why and when it is expected to convert. The longer value remains unbilled, the more attention it deserves.

Review debtors and cash Billing doesn't finish the process. The customer still needs to pay. Project reviews should identify material overdue debtors, disputed certificates and other collection issues. For larger projects, I would also want visibility over the overall project cash position. How much cash has the contractor effectively invested in the project? When is that expected to reverse? What could delay recovery? This helps management identify projects that may look profitable but are absorbing disproportionate amounts of working capital.

Review risks and opportunities Every project has uncertainty. A useful review should explicitly identify material risks and opportunities rather than allowing them to remain buried in detailed forecasts. Examples might include:

Risks

  • productivity
  • design
  • subcontractor claims
  • program delay
  • customer dispute
  • escalation.

Opportunities

  • procurement savings
  • productivity improvement
  • variation recovery
  • scope optimisation.

The base forecast should remain realistic. Risks and opportunities provide management with visibility around the potential range of outcomes.

Review safety and delivery without losing financial focus Project performance is not purely financial. Safety, quality, program, client relationships and delivery issues can all eventually affect financial outcomes. The project review should therefore connect relevant operational information to the financial forecast. For example: Program delay then additional site overhead Productivity issue then higher labour cost Design problem then variation or rework exposure Client dispute then delayed cash The goal isn't to duplicate the operational project meeting. It is to understand the financial consequences of what is happening operationally.

Finish with actions A project review without actions risks becoming a reporting exercise.

Each material issue should result in: Action Owner Due date At the next review, management should be able to see whether the action occurred. That creates continuity between monthly reviews. It also prevents the same unresolved issues being discussed repeatedly without progress.

Keep the management pack focused More information isn't necessarily better. The detailed project forecast may contain hundreds of lines. Senior management doesn't need to review every one. A good summary might show: Project value Original margin Current margin Margin movement Cost to complete Program position Variations and claims WIP Debtors Retentions Cash exposure

Key risks and opportunities Actions The detail remains available underneath where management wants to investigate further. The objective is visibility, not volume.

Look across the portfolio as well Individual project reviews are important. So is looking across all projects collectively. Management should be able to identify:

  • projects with declining margins
  • projects carrying high WIP
  • projects with significant unresolved variations
  • projects absorbing cash
  • recurring operational issues
  • customer concentration
  • common causes of margin deterioration.

Patterns across the portfolio can reveal issues that aren't obvious when each project is considered independently. They can also improve future tendering and project selection.

Warning signs the review process isn't working I would be concerned if:

  • project meetings spend most of their time explaining historical costs
  • forecast movements aren't clearly reconciled
  • project completion dates and financial forecasts disagree
  • variation balances remain unresolved for long periods
  • cash isn't discussed
  • known risks remain outside the forecast month after month
  • the same actions appear repeatedly without resolution
  • finance, commercial and operations bring different numbers
  • management receives too much detail to identify what matters
  • major project problems continue to surprise senior leadership.

The purpose of the meeting isn't to prove that the project team has prepared the report.

It is to improve the outcome.

A project review should create management intervention The best project reviews create a disciplined monthly conversation. Where are we going to finish? What changed? Why did it change? Where is the risk? Where is the cash? What are we going to do next? That conversation brings operations, commercial and finance together around one view of the project. And it gives management the opportunity to intervene while intervention can still make a difference. Because the value of a project review isn't the quality of the report produced. It is the quality and timing of the decisions that follow it.

Salt Strategic Advisory works with growing construction, infrastructure and project-based businesses to strengthen project reporting, forecasting, financial visibility and commercial decision-making. A strong monthly project review doesn't need to be complicated. It needs to make changes, risks, cash exposure and required actions visible early enough for management to respond.