Article Coordination & decisions ~8 minutes
Construction coordination lives in meetings. Useful ones create clarity. Forgettable ones create the illusion of progress — notes nobody reads, actions nobody owns, and the same agenda item returning for three weeks with slightly different wording and no movement.
Meetings are expensive. Memory is unreliable. Hybrid attendance makes both worse. The discipline is simple to say and hard to keep under programme heat: if it mattered enough to meet, it mattered enough to leave owned work behind.
What good practice looks like
Effective project meetings share a few habits:
- An agenda people saw before walking in — so preparation is possible.
- Attendance that is known — so absences do not silently void decisions.
- Decisions written as decisions, not as vague vibes or “noted.”
- Actions with owners and dates that escape the minutes into real work tracking.
- A record someone joining next month can still understand without calling alumni.
- Recurring series that carry forward open work instead of reinventing context every time.
Industry project controls and governance guides repeat this for a reason. Site translation: can a stranger tell, by Wednesday, what Monday’s meeting changed and who must act?
Good practice does not demand a novel for every toolbox talk. It demands that coordination meetings which move design, sequence, commercial posture, or safety posture leave a trail the project owns.
Where projects slip
- Minutes are decorative PDFs emailed once and never opened again.
- Actions live only in the minutes — then vanish when nobody copies them into work.
- Recurring meetings reinvent context every time because open items have no home.
- Decisions that change design or commercial posture never make it into formal records.
- Hybrid / dial-in attendees are half-present and not listed.
- Chat after the meeting quietly revises what the minutes still claim.
The failure mode is performance: people leave feeling aligned while the programme still lacks owned next steps. That feeling is expensive when the same topic returns unpaid for the third week.
How Cynilo supports this practice
Cynilo treats a meeting as a project record, not a throwaway file.
- Agenda, attendees, decisions, and minutes have a home on the job.
- Actions can become tasks people actually work — instead of lines stranded in a document.
- Links to documents and other records keep “what we discussed” tied to evidence.
- Series and reminders reduce the admin tax of keeping people present and prepared.
Help how-tos cover creating the record and pushing actions. Learn is for the cultural bar above. The product does not run your meeting for you; it stops the outcome from living only in a PDF that dies in Downloads.
What good looks like in a week
In a normal week on a job that leaves a trail:
- Actions from Monday are visible in people’s work queues by Monday afternoon.
- Decisions that change design or sequence are discoverable without asking “who was in that call?”.
- Recurring coordination stops re-litigating settled items.
- New joiners can catch up from the record instead of hunting chat history.
- Attendance disputes are rare because the list was honest.
Interface weeks are the stress test. If decision density rises and the trail thins, you will pay in re-litigation later.
A short story from a multi-package coordination meeting
A multi-package coordination slot ran every Tuesday with tidy minutes and a growing “outstanding” appendix. By week six the same three interface items still sat there. Owners had rotated; dates had slipped verbally; nobody had moved the lines into tracked work. A design hold finally hit programme. The commercial argument opened with “we agreed in coordination” — and closed with nobody producing a task with an owner from those meetings.
The reset was short. Actions leave the room as tasks the same day. Decisions that bind design get a labelled decision line, not a soft paragraph. The minutes PDF got thinner. Movement improved because work finally had a home outside the appendix.
Closing
A meeting without owned next steps is only a conversation with a booking reference. This series walks the coordination spine: minutes are not the work, decisions deserve a durable home, then checklist culture for the repeated field captures that meetings often assume somehow “just happen.”
Next in the series: Minutes are not the work — turning polished notes into owned tasks.
In the product: Help → How-to → Meeting records or Tasks.
Topics:
Modules in Cynilo:
In the product: open Help → How-to when you need specific actions in Cynilo. Learn stays on industry practice.
Previous: Handover while you build
Next: Checklists that stick