If you have been following this blog series, you will remember the story I shared about a former client who nearly went to litigation over a communication mistake. A firm brought me in to help them find better ways to collaborate with owners, GCs and trades on a project. Design meetings ran smoothly, decisions got made, and everyone moved forward. Then the building was finished and the client was furious. A piece of equipment they believed they had asked to be excluded was missing, and in their mind that was a mistake to be fixed at the firm’s expense. The PM pushed back, certain the client had never said any such thing. The disagreement escalated fast, and a lawsuit started to look likely.
What saved the firm was luck, not process. The PM dug through a desk drawer and found a handwritten note from a meeting months earlier, confirming the client had indeed instructed the equipment be left out. The lawsuit was avoided, but only because one person happened to keep a scrap of paper that could have just as easily been thrown away.
That should never sit well with anyone running a project or a firm. A near lawsuit was decided by luck.
Meetings Are Where the Real Decisions Happen
Executives tend to think of project risk in terms of budget, schedule, and safety. Meetings rarely make that list, yet meetings are where scope gets narrowed, where verbal commitments get made, and where the story of who agreed to what actually originates. A coordination meeting is where a clash gets resolved with a shortcut nobody documents. An owner meeting is where a scope reduction gets agreed to in conversation and never makes it into a change order. By the time a dispute surfaces, the project is relying entirely on someone’s memory of a conversation that happened months earlier.
This is a leadership blind spot, not a documentation nuisance. A firm can have excellent design work, a well run schedule, and a strong safety record, and still end up exposed in litigation because nobody can produce a clean record of who decided what and when. The equipment dispute did not happen because the PM was careless. It happened because the system the firm relied on to capture decisions was a person’s memory and, if they were lucky, their own handwriting.
Verbal Agreements Are Not Evidence
There is a habit in construction of treating a conversation as settled once everyone in the room nods. It feels efficient in the moment. It is a liability the moment anyone outside that room asks for proof. A client, an owner’s counsel, or an insurer does not care that everyone remembers agreeing to something. They care whether there is a record, timestamped and attributable, that shows it. The PM in this story got lucky because he happened to keep a note. Most people do not keep that note, and most firms have no process that would have caught it even if he had thrown it away.
This is the argument for treating meeting records the same way a firm treats contracts and change orders, as documents with legal weight rather than as informal minutes nobody expects to read again. Autodesk Build’s Meetings tool reflects that shift by tying every recorded decision to the project record itself rather than to whoever happened to be taking notes that day, and by making that record permanently searchable rather than something someone has to remember they kept.
Decisions Need Owners, Not Just Notes
A documented decision is only half the protection. The other half is making sure someone is actually accountable for acting on it, and this is where a lot of firms fall short even when they think they have good meeting discipline. Most project teams have some version of a RACI framework in their heads, an informal sense of who is Responsible, Accountable, Consulted, and Informed on a given decision. The problem is that this framework almost never gets written down at the moment a decision is made. It lives as an assumption, the same way the equipment exclusion lived as an assumption in that PM’s memory until a piece of paper happened to prove otherwise.
Some firms use more detailed versions of this model, RACI-VS, which adds Verifier and Signatory roles to account for who confirms the work was done correctly and who has formal sign off authority, or RASCI, which separates out a Support role from the people doing the work. Whichever variant a firm uses, the model is only useful if it is applied to real decisions in real time rather than existing as a chart in a project execution plan that nobody references during an actual meeting. If the equipment decision had been captured with a named Accountable party and a named Responsible party for communicating it back into the drawing set, the firm would have had a structural answer to the client’s claim instead of a lucky drawer.
This is where the connection between meetings and issue tracking earns its keep. A decision that becomes a tracked issue in Autodesk Build carries an assigned owner, a status, and a history, which is the RACI model made durable instead of theoretical. The Accountable party is not just accountable in a spreadsheet, they are accountable in a record the whole project team can see. That visibility is what turns a meeting from a conversation into a form of evidence.
What This Means for Leadership
None of this is really about which software you choose to work with. What matters is whether a firm's decision making leaves a trail or depends on luck, and whether the accountability structure a firm believes it has actually exists outside of good intentions. Every executive who has sat through a client escalation knows how fast a project's credibility erodes when nobody can produce a clear answer to a simple question, what did we agree to, who owned it, and when. The firms that consistently avoid that position are the ones that have made documentation and ownership a habit built into how meetings run, not a framework discussed once during project kickoff and never revisited. Where the software comes in is whether it is a connected application that gives every project participant access to the same data, the same roles and responsibilities, and the same visibility into follow through.
The near lawsuit in this story ended the way it did because of a lucky project manager with a note drawer. The next firm that finds itself in that position may not be so lucky.
Cedar Rock Consulting helps construction teams close exactly this kind of gap, whether that means adopting connected tools like Autodesk Build, applying a real RACI or RASCI structure to project decisions, or simply building better habits around how decisions get captured and owned. Visit cedar-rock.net to learn more.