Schedule programme
A schedule programme is a schedule that has become contractually binding. The difference from a construction schedule lies not in how it looks, but in its status: the same document becomes a schedule programme once it is agreed as part of the contract or formally approved.
When a schedule becomes binding
Binding force does not arise from circulating a schedule. It arises from agreement: a completion date fixed in the contract, an expressly agreed interim date, or an approved programme attached to the works contract.
- The schedule carries a version and an approval date.
- It is visible who approved it and when.
- Later versions replace the earlier one traceably, rather than silently overwriting it.
Why the status matters
An unapproved programme is treated as non-binding. Without a binding date, a delay can be observed but not asserted as default. In practice, schedule claims rarely fail for lack of delay – they fail because the intended state was never recorded in a binding form.
Versioning a schedule is therefore not a matter of tidiness, but the precondition of its binding force. In Menira every version remains as its own state, dated and traceably linked to the one before.