Skip to main content

Site meetings

Site meetings in Builddar are built around one idea: your report is the result of the follow-up, not a document you write.

You don't start each meeting with a blank page. The project keeps a single register of points — the subjects being followed on the job. Every meeting is a dated view of that register. Anything still open carries into the next meeting on its own, keeping its original date and its full history. When you publish, Builddar freezes that view and produces the report.

info

Site meetings are a separate module. If your project doesn't include it you'll see Meeting reports are not enabled — ask your organization administrator to turn it on. See Products.

The two objects​

ObjectWhat it is
PointA subject being followed — an action, a decision, a piece of information. It belongs to the project, not to a meeting. It is numbered once and keeps that number for life.
MeetingOne dated meeting, numbered sequentially as CR 1, CR 2, and so on. It records who attended, what progress was stated, and what happened to each point that day.

A point is raised at a meeting — that's how its history starts — but it outlives that meeting and every report after it. This is why the register is the durable thing and the report is a snapshot.

The tabs​

A project's Meeting reports area has these tabs:

TabWhat you do there
MeetingsThe list of meetings. Open the next one from here.
RegisterEvery point on the project, filtered however you need.
AgendaThe open points in the order the meeting will be run.
AttendanceWho was convened, and who turned up.
ProgressThe progress percentages you state for this meeting.
ReportsThe published documents and their revisions.
TemplatesWhat prints on the report, and the prose around it.

Point statuses​

Points use their own vocabulary — deliberately not the issue workflow.

StatusMeaningTerminal
To doRaised, not startedNo
In progressBeing worked onNo
PendingWaiting on something or someoneNo
DoneResolvedYes
For the recordNoted, no action expectedYes
DroppedAbandonedYes

Terminal statuses are what stop a point carrying into the next meeting. Everything non-terminal carries forward automatically.

Point categories​

Every point has one of five fixed categories, which is how the printed report is sub-headed: Administrative, Studies, Execution, Decision, Information. Execution is the default.

Grouping​

The register renders grouped by Trade, Zone, Company, or Category. This is presentation only — it changes how the register reads on screen and in the printed report, never the data underneath. You set it per meeting with Group the register by.

History is append-only​

A point's history is never edited and never deleted. A correction is a new entry. Over a project's life a mature point reads as a chain:

Raised at CR 18 · Reminder at CR 19 · Comment at CR 20 · Closed at CR 21

Eight kinds of entry are recorded: Raised, Comment, Status changed, Due date changed, Reminder, Reopened, Closed, and Carried forward. That last one matters more than it looks — a point that appears in a report unchanged emits none of the others, and on a mature project that is most of the rows.

Publishing is final​

Publishing is not a save. It freezes the meeting, its attendance and its progress permanently, and sends the report out. There is no way back. A correction means issuing a revision, which produces a new document alongside the original — the published version keeps its file, unchanged.

Each publication produces the full report plus one extract per company, so a contractor receives their own points rather than the whole document.

Guides​

Last updated on