This article is a practical review framework for a Primavera P6 programme update. It is intended to help engineering and project teams turn a topic request into a controlled record that can be checked by another person. It does not replace the contract, approved method statement, manufacturer instructions, authority requirements, inspection and test plan, or

Earned value reporting only works when the numbers behind it come from one controlled sequence. Most failed EVM cycles I would flag as governance problems, not software problems: the schedule was updated on one date, the costs were keyed on another, and someone quietly overrode progress to make the curves look better. The purpose of

A programme update is the project team’s controlled record of what was actually achieved up to a defined data date and what the schedule now forecasts. It is more than changing a few activity percentages. The update should connect site records, schedule status, logic, calculated dates, variance analysis, and the narrative issued with the programme.