Programme of works
The tasks in the order the job runs them, their dates in working days, the critical path, and how far the work is behind.
The programme says when each part of the job should be built. HodariQ keeps it next to the BoQ and the site reports, so it can tell how much of the work should be done by today and how much the site says is done.
Where it is
Open the contract and press Programme at the top of the contract workspace (or the Programme button on Details). Contractor and consultant firms both have it: a consultant QS can keep the contractor's programme to follow the job. QS Officers and Senior QS / Managers change it; Accounts and Directors see it.
Make it
- 1Press Make from the BoQ: one task per bill of the Contract BoQ, in the bill order, the first With the job and each other one After the bill before.
- 2Type each task's Length in working days. Leave it empty if you do not know it yet.
- 3Change Starts where the job runs differently: With the job (possession of site), After another task, with a lag of some working days, or On a date.
- 4Rename tasks, move them with the arrows, add a task with Add task (a task that is not a bill, such as a site hoarding, carries no value), remove a task with the bin. A task that waited on a removed one now follows what the removed one followed.
- 5Crew and Note for the planner are free text (2 gangs, before the rains).
How the dates are worked out
- The job starts on Possession of site (else the contract date). Working days are the site's report days of Settings › Site Portal; when no report days are set, Monday to Saturday.
- A task of 6 working days that starts on Monday 5 January 2026 ends on Saturday 10 January. The task after it starts on the next working day, Monday 12 January, plus its lag.
- A task with no length has no dates, and every task after it shows Waits on that task.
- A task cannot wait on itself, even through other tasks: HodariQ refuses it.
- The last end date is the programme's end. When it is after the completion date (revised by extensions of time), Ends turns red and says by how many days.
Critical path and slack
The slack of a task is how many working days it can slip before a task after it, or the end of the job, moves. A task with no slack is on the critical path: its bar has a red outline. In the example, Substructure (6 days) and then the PC and Provisional Sums (3 days) end on 14 January and are both critical; a site hoarding of 2 days with the job ends on 6 January and has 7 working days of slack.
Should be done and done
Each task that is a bill is worth that bill of the Contract BoQ, less approved omissions. HodariQ spreads it evenly over the task's working days: by a date, a task should be done in the share of its working days gone. Should be done by today adds this up for all tasks, as a % of the Contract BoQ. Done (site reports) is the work the site reported item by item (see Work done, item by item) at contract rates, as a % of the same total. Certified to date is shown under it.
A task is in Furthest behind when the work done is a fifth of the task (20 points) or more behind what should be done by now; its row turns yellow and its Done red. The contract workspace shows the same two figures under Programme, in red when the job is 5 points or more behind.
The bar chart
One bar per dated task, with week marks, a black line for today and a red line for the completion date. The green part of a bar is the share done as reported by the site.
Good to know
Done counts only the site's reports; the programme does not move by itself when the work is late. Change the lengths or starts to re-plan: the dates, slack and critical path are worked out again at once.
Something unclear? Ask us on WhatsApp: we answer the same day.