Be clear about what the values represent
An activity value may represent budgeted cost, a contract allocation or another agreed reporting basis. Those are different concepts, and none should be silently treated as cash in the bank. Before loading a schedule, agree what the figures mean, how they will be distributed and which outputs the team expects. Keep the source of the values and any allocation assumptions available for review.
Follow the path from work to receipt
In a hypothetical payment cycle, work is performed, its value is assessed, a payment application is submitted, certification takes place and payment follows under the agreed terms. The interval between those steps matters. A schedule showing when work occurs does not by itself represent the receipt date. Use the actual contract arrangements and the project’s commercial review to establish a suitable cash-flow model.
A cost-loaded programme and a cash-flow forecast answer related, different questions.
Review the assumptions when the sequence changes
A later work area, changed procurement order or revised handover can change the timing of expenditure and the work available for valuation. Revisit those timing assumptions when reviewing the schedule instead of carrying an old financial curve forward unchanged. Keep the construction forecast and the financial model traceable to the same current sequence, while preserving their different purposes and the applicable commercial assumptions.
Use the conversation to expose uncertainty
Show which amounts and dates are confirmed, which are forecast and which depend on unresolved decisions. Discuss what happens if an approval or payment arrives later than assumed. A useful model should help the team recognize timing exposure, not imply certainty through a smooth curve. Have the responsible commercial and finance teams review the assumptions before using the output for funding or contractual decisions.
- Define the meaning of the loaded values.
- Model valuation and payment timing separately.
- Refresh timing assumptions when the execution sequence changes.
This article is general planning commentary. Project requirements and engagement methods are defined for each assignment.
