7.4 Project Communication: Paths, Instruments, Meetings & the Record

Project Management objective 2.3 asks you to determine appropriate communication to the project team — owner, contractor, consultants, and internal staff. On a project that goes wrong, the communication record is what determines who pays, which is why this objective is tested through consequences rather than etiquette.

The Contractual Communication Structure

Communication paths on a design-bid-build project are not a matter of preference; they follow privity of contract. AIA A201 requires that communications between the owner and the contractor be through, or contemporaneously reported to, the architect, and that communications with the architect's consultants and the contractor's subcontractors run through their respective prime parties.

Why it matters: the architect who is bypassed cannot administer the contract, cannot maintain a complete record, and may be held to have known of a condition they were never told about. A contractor who receives direction directly from the owner may later claim a change; if the architect never saw it, the architect cannot rebut it.

Selecting the Right Instrument

The instrument carries legal weight independent of its content.

The error the exam punishes is using a low-authority instrument to do a high-authority job: answering an RFI in a way that actually directs extra work, or confirming a scope change by email instead of by change order.

Meeting Discipline

Every recurring project meeting needs a defined owner, attendee list, agenda, and minutes protocol.

• Minutes are prepared by whoever chairs the meeting. The architect typically chairs design meetings; the contractor typically chairs construction progress meetings.
• Minutes must be distributed promptly and must state the period within which corrections may be submitted. After that period the minutes stand as the record.
• Minutes record decisions, action items, owners, and due dates — not narrative transcription.

Internal Communication

Internal communication is the objective's quietest half and a common source of project failure. The project manager owes the internal team:

• A written work plan so each person knows their deliverables, hours, and dates.
• Written transmittal of every client decision to the whole team, because a decision known only to the person in the room becomes a coordination error two weeks later.
• A single place where the current consultant backgrounds live, so no one works over a superseded file.
• A defined escalation path for issues the team cannot resolve within its authority.

Documenting for the Record

Three habits determine whether the project record protects the firm:

1. Contemporaneous. Write it when it happens. A memo written after the dispute begins is worth a fraction of one written the day of the event.
2. Factual. Record observations, dates, and statements. Speculation about motive is a liability.
3. Confirming. After any consequential verbal instruction or telephone decision, send a written confirmation stating what was said and inviting correction. Silence in response is powerful evidence; there is no equivalent evidence of an unconfirmed conversation.

Exam Tip: When an item describes an owner giving direction straight to the contractor, the architect's correct response is never to ignore it and never to countermand it unilaterally. It is to require that the direction be documented and routed through the contract's communication structure — because the architect must be able to evaluate whether it is a change in the work.

The Communication Plan

A project of any size needs a written communication plan established at the start, not improvised at the first conflict. It answers four questions for every recurring exchange:

The most consequential entry is the owner's single point of contact. A client organization in which a facilities director, a department head, and a board member all issue direction will produce conflicting instructions, and the architect who acts on the wrong one has no defense. Establish at the outset who holds authority to approve scope, schedule, and cost, and confirm that person in writing.

Document Control and Digital Data

Communication fails as often through file management as through conversation.

• A single system of record. One project management platform or server location holds the current documents. Email attachments are copies, never the record.
• Naming and version control. A consistent file naming convention carrying dates or revision numbers prevents work over superseded backgrounds — the most common and most expensive coordination failure in design.
• Transmittals state a purpose. Every set that leaves the office goes out with a transmittal identifying the documents, the recipient, the date, and the purpose: for review, for coordination, for permit, for construction. The purpose statement matters legally, because documents issued "for coordination" that a contractor then builds from create a dispute about reliance.
• Digital data protocols. AIA E203 (Building Information Modeling and Digital Data Exhibit) with G202 (Project BIM Protocol Form) establishes who may rely on the model, at what level of development, and what the model's status is relative to the drawings. Absent those exhibits, the printed documents govern and the model carries no contractual reliance.
• Record retention. The firm's retention policy should outlast the statute of repose in the jurisdiction. The project record is the firm's primary defense, and the claim usually arrives years after final payment.