Back to Blog
Division Guides4 min read

Multi-Discipline Design Team Coordination Meetings: Agenda, Attendees, and Documentation

How the architect manages multi-discipline design team coordination meetings during design phases - frequency, attendees (structural, MEP, civil engineers), agenda items, coordination issues to resolve, and how these meetings drive document coordination, as tested on the ARE PjM exam.

July 22, 2026

Design Coordination Meetings Are How Multi-Discipline Teams Prevent Field Conflicts - Run Them With Purpose

Architecture projects involving multiple engineering disciplines (structural, mechanical, electrical, plumbing, civil, fire protection) require regular coordination meetings to identify and resolve inter-discipline conflicts before they become expensive construction change orders. A conflict between a structural beam location and an HVAC duct routing that goes undetected through the design and bid phases becomes a field problem that the contractor prices at 3-5x the cost of resolving it in design. The architect's responsibility as the design team coordinator is to organize and lead these meetings, set agendas that focus on coordination issues rather than general updates, and document the decisions and action items that come out of each session. The ARE PjM exam tests design team coordination meetings as a project management competency in the context of multi-discipline coordination requirements.

Meeting Frequency and Timing

Design coordination meeting frequency varies by project phase: Schematic Design: monthly (major system decisions, not detailed coordination); Design Development: bi-weekly (active coordination of structural, MEP, and civil systems with developing architectural design); Construction Documents: weekly or bi-weekly (active conflict resolution as all disciplines produce 50%-90%-100% complete documents). Critical coordination events that require dedicated meetings: end of schematic design (structural system selection, MEP system selection, structural bay confirmed); 50% design development (plenum space coordination, slab edge conditions, core coordination); permit submission (all disciplines review for code compliance conflicts).

Agenda Items

Effective coordination meeting agendas focus on unresolved inter-discipline conflicts, not on status updates that could be handled by email. Typical agenda items: review of open coordination issues from prior meetings; specific plenum space conflicts (duct vs. beam at critical locations - provide section drawings); structural penetration requests from MEP (openings in shear walls or beams requiring structural review); slab edge and facade attachment conflicts; mechanical equipment room space adequacy; elevation conflicts between architectural sections and structural sections; changes to program or scope since last meeting and their inter-discipline implications. Each item should be assigned to a responsible party with a resolution deadline.

Documentation

Coordination meeting documentation: meeting summary within 48 hours; list of open coordination items (COI log) tracking each issue number, description, responsible party, date opened, target resolution date, and resolution description when resolved. The COI log provides the project team a running record of all identified conflicts and their status - unresolved items appear on every subsequent meeting agenda until they are resolved. Before bid issuance, the COI log should be empty (all items resolved and reflected in the documents).

Key Exam Points

  • Coordination meetings: resolve inter-discipline conflicts in design; cheaper than field change orders.
  • Frequency: monthly in SD; bi-weekly in DD; weekly in CD (active production phase).
  • Agenda: specific coordination conflicts, not status updates; assigned responsible party and resolution deadline for each.
  • COI log: running log of all identified conflicts; resolved when reflected in documents; empty at bid issuance.
  • Architect's role: organizer and facilitator; not just participant; responsible for maintaining coordination quality across disciplines.

AREprep's PjM project management and PDD construction documents content covers design coordination meetings, COI logs, BIM-assisted coordination, and the architect's responsibility for multi-discipline document coordination - giving ARE candidates the design team coordination knowledge the exams test in multi-discipline project management questions about how the architect ensures that engineering systems and architectural design are compatible throughout the design process.

Study PjM on AREprep

AREprep's PjM flashcards and practice exams are built around the actual NCARB exam guide - so every study session targets what the exam tests.

Ready to put this into practice?

AREprep has 400 original flashcards, 30 timed mini exams, and 3 full-length simulations for every ARE division.