Article Coordination & decisions ~8 minutes
Projects lose months re-litigating decisions that were “everyone agreed” until nobody can prove who agreed to what, on which evidence, and with what residual conditions. Decisions need a durable home — meeting record, letter, or formal answer — not only a vibe that felt solid on a Teams call.
Corridor consensus is fast. Chat is faster. Both evaporate when people rotate or when money appears. Material decisions that change design, sequence, access, or commercial posture must live where the project can still find them.
What good practice looks like
Write the bind where the project owns it.
In practice:
- Material decisions are written where the project owns them — not only where conversation happened.
- Cross-links exist when a decision rests on a drawing, RFI, or risk item.
- Later staff can find the rationale without calling alumni.
- Contradictions between chat and the formal record are resolved by updating the home — not by collecting screenshots.
- Conditions and caveats travel with the decision so “agreed” does not mean “agreed without the constraints.”
- Commercial and design both know which vehicle holds the binding statement for a given class of decision.
Boards of decision registers, design query processes, and letter books all aim at the same need. Site translation: if two competent people cannot find the same binding statement, you do not have a decision — you have a rumour with attendees.
Where projects slip
- Corridor consensus that never reaches minutes or letters.
- Chat decisions that contradict minutes — and quietly win until they lose in a workshop.
- Formal letters that never reference the meeting that caused them.
- RFI answers that settle design without anyone updating the coordination record.
- “Agreed in principle” used as if it were approved for construction.
- Decision homes that exist but cannot be searched — buried in unlabeled PDFs.
The cost is re-work and re-argument. Programme pays twice: once to decide poorly (or undocumentedly), again to rediscover what was meant.
How Cynilo supports the practice
Meetings, correspondence, and RFIs sit in one product world so decisions can be found beside the documents they affected. Meeting decision lines, letter books, and reliable answers are different doors to the same idea: binding statements need a shelf.
Help How-tos cover those modules. Learn connects to Minutes are not the work and the Documents series on formal issue and questions you can rely on. The product does not invent your governance matrix; it stops decisions from living only in disappearing channels.
What good looks like in a week
On a job where decisions have homes:
- Material settlements from coordination appear as labelled decisions the same day.
- Design-binding answers cite the record they live in when site asks “are we sure?”
- New joiners find rationale without Slack archaeology.
- Letters that formalise meeting outcomes point back clearly.
- Conflicts between informal and formal channels trigger an update to the home, not another informal layer.
The weekly test: pick three design or sequence changes from the last fortnight. Can you open the binding decision home without interviewing someone who has since left? If not, “everyone agreed” is still your system.
A short story from a façade interface decide-fest
A façade interface went through three “agreed” sessions — two meetings, one chat thread — about bracket spacing. Site started detailing from the chat. Design later issued a letter reflecting the second meeting. Steelwork had already moved. The dispute was not about engineering skill; it was about which “agreed” had a home.
The package introduced a simple rule: interface decisions that affect fabrication need a meeting decision line and confirmation in the vehicle the contract treats as binding (often a letter or formal answer), with the drawing revision cited. Chat stayed useful for speed. It stopped being authoritative. Rework from ambiguous agreement fell sharply.
Closing
Meetings create the moment. Minutes witness it. Decisions need a shelf that survives the week. Coordination also depends on the repeated checks crews run between meetings — which is where checklist culture begins.
Previous: Minutes are not the work
Next in the series: Stop reinventing the checklist every morning — same questions, comparable proof.
In the product: Help → How-to → Meetings
Topics:
Modules in Cynilo:
In the product: open Help → How-to when you need specific actions in Cynilo. Learn stays on industry practice.
Previous: Minutes are not the work
Next: One checklist culture