State progress
Progress on a meeting report is stated, not computed. You enter the percentages, and the rows you create are what shapes the table.
Required role: Project Manager or Collaborator.
How the rows shape the table
There is no settings screen for the progress breakdown. The rows are the breakdown:
| Rows you create | What prints |
|---|---|
| One row per trade | The flat per-trade table |
| One row per zone and trade | A per-building breakdown |
| One row per zone | A rollup per zone |
| A single row with neither | One overall project figure |
Steps
- Open the draft meeting and go to the Progress tab.
- Select Add a row.
- Choose a Zone, or Whole project.
- Choose a Trade, or All trades.
- Enter the % — a whole number from 0 to 100.
- Optionally add a Note.
- Repeat for each line you want on the report, then save.
Result: Progress saved. The rows print in the order you set.
If you create two rows covering the same combination you'll see Two rows cover the same zone and trade. Each zone/trade pairing can appear only once per meeting.
Why totals are never computed
A parent percentage is never derived from its children. Doing that correctly means weighting by the value of each work package from the cost breakdown, which Builddar doesn't hold — and an unweighted average printed on a contractual document is simply a wrong number.
If you want a project total, state it as its own row.
If the progress table isn't relevant to your report, leave it empty and switch Progress off in the template. An empty table reads as an oversight; a hidden one doesn't.