TEMPLATE · PRODUCTIVITY & TECHNOLOGY
A construction schedule template,
and the day it stops
being enough.
The table below is the fields a construction schedule needs to carry if it is ever going to answer a payment question, not just a planning one. Copy it into your own system. The paragraph underneath it is the part most templates leave out: the exact day a plain copy of this table starts failing, and why.
This is a record-design template, not a legal reading. The reference-date mechanics it is built on are set out, with their primary source, in our separate reading of the BIF Act: /insights/construction-schedule. Nothing here states what any contract requires.
The template.
One row per stage or milestone. Copy the header row into a spreadsheet or your scheduling tool.
Seven fields. Most scheduling tools already capture the first two and silently drop the rest, because the rest only matter when something is disputed.
| Field | What goes in it |
|---|---|
| Stage / milestone name | As the contract or programme names it, not a shorthand only one person understands. |
| Planned date | The date in the programme version current when this row was created. |
| Actual date | The date the stage was actually reached, filled in once, not edited over. |
| Confirmed by | A named person, not a role. Who stood on site, or who approved the record. |
| Claim-bearing? (Y/N) | Whether the contract ties a reference date to this stage. If you do not know, write "not yet determined" rather than guessing. |
| Programme version this row belongs to | The version number or issue date of the programme this row was recorded against. |
| Evidence reference | A photo, a site diary entry, an inspection record - whatever would let someone else verify this row six months later. |
The day it stops tracking
what you need.
A plain copy of this table, kept as one live file that gets overwritten with every revision, works right up until one of three things happens.
None of this is a prediction about your project. It is the three points where a plain spreadsheet copy of the table above and a dated, versioned record of it start producing different answers to the same question.
- A claim is served and disputed: The question becomes what the programme said on the day the claim was served, not what it says today. A live file that has been revised eleven times since has no record of what it said in March. Our reading of the BIF Act's reference date definition sets out why that specific date matters: /insights/construction-schedule.
- A resequencing moves a claim-bearing stage: If the contract works a reference date out from a stage, moving that stage in the programme is not only a planning decision. The template's "claim-bearing" column exists so that question gets asked at the time of the revision, not six months later.
- Two people disagree about who confirmed a stage: "Confirmed by" names a person, because a stage that three different people half-remember confirming is a stage nobody can actually stand behind later.
What we would put in a system
The template above, held so that a past version can be recovered rather than only read as it is today.
| Beyond the template field | Why it is load-bearing |
|---|---|
| The whole table is versioned, not just edited | A dispute is reconstructed from what the table said on a past date. Editing a live file in place destroys that date. |
| Claim-bearing dates are flagged before a revision, not after a dispute | Flagging it at the time means a resequencing decision gets made with the payment consequence visible, not discovered later. |
| Evidence references are kept with the row, not in a separate folder | A row that says "see evidence" with nothing attached is not evidence six months later, once the folder has been reorganised twice. |
Questions people ask
about schedule templates
Is there a free construction schedule template?
The table on this page is one: seven fields, free to copy into a spreadsheet or your own tool. What it adds to a typical template is the claim-bearing and programme-version columns, which most templates do not carry because they only matter once a claim is disputed.
What is a construction programme template missing?
Most leave out who confirmed a stage by name, which programme version a date belongs to, and whether the contract ties a payment claim to that stage. Those three are the ones a dispute actually asks for.
Why does my construction schedule not match my payment claims?
Under Queensland's Building Industry Fairness (Security of Payment) Act 2017, a payment claim's entitlement runs from a reference date, which the contract may work out by reference to a stage. If the schedule and the claim are kept in different systems by different people, the two can drift without anyone noticing until a claim is disputed. Our separate reading sets out the mechanism: /insights/construction-schedule.
Do I need special software for this?
No. The template is seven columns and works in a spreadsheet. What a system adds is versioning - keeping last month's table alongside this month's, rather than one file that has been edited over - which a spreadsheet does not do on its own unless you save a dated copy each time it changes.
Bring us one schedule
and one disputed claim.
Send us a programme and the claim it was supposed to support. We will show you which of the seven fields it already carries, which it does not, and what a versioned record would have held on the day the claim was served.
This page is a record-design template, not legal advice. It does not interpret any contract and does not state what any reference date is tied to. The legal mechanics it is built on are read, with their primary source, in /insights/construction-schedule.
Built from
This page makes no new legal claim. Every mechanic it references is read and sourced in the linked reading, as at 4 November 2026.
RELATED READING
Other readings on the same records.
- The Code is a dataset now, and one edition has carried three versions: NCC 2025 ran through three data.gov.au records in forty-seven days, two now titled superseded. The ABCB's test is the date you accessed the file. (Productivity & Technology)
- The industry where being small means staying manual: The Productivity Commission's 53% and the innovation gap that follows firm size. (Productivity & Technology)
- A feasibility assumptions checklist, and which category fails first: An assumption register template that classes each input as fact, estimate, published-escalating or basis-choice, so a re-run starts from the one that moved. (Development & Reporting)