Article
How Architects Should Document Coordination Meetings With Engineers and Consultants
Coordination meetings with engineers and consultants carry real project risk. Here is how documentation makes those meetings more accountable and less legally exposed.
Coordination meetings between architects, structural engineers, MEP consultants, and other specialists are where the most technically consequential decisions happen on a project. A change in ceiling height affects mechanical clearances. A shift in a structural grid affects floor plate efficiency and curtain wall layout. These interdependencies require clear communication and, more importantly, clear documentation of what was communicated. When something goes wrong, the question is always: what was agreed, and who was responsible for what?
Architecture project communication and meeting notes context
This guide focuses on architecture meeting notes, architecture coordination meetings, and tracking design decisions with clear project communication.
Consultant coordination is higher stakes than it appears
The casual character of coordination calls, usually informal, often on short notice, can create a false impression that the stakes are low. In practice, these calls produce commitments that affect construction cost, project schedule, and contract obligations.
A verbal agreement that a structural revision would be incorporated into the next drawing set, not followed by written confirmation, can become a dispute when the revision does not appear. A decision about MEP routing that was not documented becomes ambiguous when the relevant engineer is unavailable during a construction question.
The documentation bar for consultant coordination should be equal to the documentation bar for owner communication. The risk profile is similar and the paper trail matters equally.
Who should be taking notes in coordination meetings
In many coordination meetings, no one is designated as the note-taker because everyone assumes someone else will handle it. The result is that documentation does not happen or happens inconsistently.
As the lead architect or PM, you should own the record for every coordination meeting you facilitate. This does not mean writing everything yourself during the call. It means ensuring that a usable record is produced and distributed within 24 hours of the meeting.
In practice, this is most efficiently handled by recording the call, generating a transcript, and processing the transcript into structured notes. The recording solves the note-taking problem without requiring divided attention during a technical discussion.
What to capture that most teams miss
Standard meeting notes capture decisions and actions. Coordination meeting notes should also capture conflicts and their resolution status.
A structural-MEP conflict identified in a coordination call may not have a resolution in that meeting. It becomes a pending item assigned to a specific engineer with a deadline. If that item is not tracked, it will resurface later as a constructability issue or a change request, both more expensive to resolve.
Tracking conflicts separately from decisions creates visibility. A project report showing five open structural-MEP conflicts and their current status is far more useful than a set of notes where those conflicts are buried in paragraphs.
Distribution matters as much as the note itself
A meeting note that is produced but not distributed to all relevant parties has limited protective value. If stakeholders do not confirm receipt of the record, the shared understanding created in the meeting is not reinforced.
Distribute coordination summaries to all meeting attendees and to the relevant project file within 24 hours of the meeting. Include a brief line inviting corrections or clarifications within 48 hours. This practice creates a baseline of shared understanding and gives you documentation that the record was distributed and reviewed.
Teams that follow this discipline consistently find that the first moment of disagreement is almost always productive because the written record is already established.
Where Datum Notes fits in
Datum Notes helps architecture teams document coordination meetings by processing transcripts into structured summaries that separate decisions, action items, and open conflicts. If your coordination documentation is currently informal or inconsistent, a structured system that takes five minutes per meeting is worth building before the project needs it.
Learn more at Datum Notes to see how architecture teams keep project knowledge searchable across meetings.