Playbook · September 2026 · 6 min read
Why the site programme and the budget drift apart
The programme says one thing and the cost report says another. The gap usually starts because the dates and the money live in different files.
On most jobs the programme is a chart and the budget is a workbook. They are updated by different people, on different days, and nobody notices they have diverged until a review. The site has poured a slab the chart still shows as next month, or the chart shows finishes underway while the cost sheet has not recorded the material.
The drift is not a discipline problem first. It is a storage problem. If the task dates, the bill of quantities, the expenses, and the payments are separate files, each one can be “right” and the job can still be wrong.
Put those records on the same project. A task with a start and a due date is what the Gantt draws. A BOQ line is quantity times rate, calculated on the server. An expense has a category and a date. A payment is incoming or outgoing. The cost report then reads those records instead of a pasted summary.
A practical check, once a week, is short. Open the project. Look at milestones marked delayed. Look at expenses recorded since the last check. Look at payments in against what the programme says is complete. If those three disagree, the disagreement is visible while the job can still be corrected.
Best CPMS keeps that set in one workspace: planning for dates, finance for the BOQ, expenses, and payments, and reports that export to CSV. The programme and the budget drift when they are copies. They stay closer when they are the same project.