Project Communications & Documentation Protocols

Project communication and documentation

Communication is a project resource. A timely decision transmitted to the right people can protect a critical milestone; an undocumented verbal direction can lead several disciplines to produce incompatible documents. The manager should select a communication method based on the decision, audience, urgency, and required record. More messages do not necessarily produce better coordination. The goal is a traceable instruction or decision that recipients can act on and later verify.

Establish authority and distribution

At kickoff, identify the owner's authorized representative, architect's representative, consultant leads, and contractor's representative. Record who may approve scope, fees, expenditures, and changes. These powers can be delegated differently on different projects. A committee member's design preference is not automatically an authorized owner directive. Route unresolved competing requests to the designated representative and record the final decision.

A201–2017 permits direct owner–contractor communication. Communications affecting the architect's professional responsibilities must include the architect, and the owner must keep the architect informed of other relevant project communications. It is inaccurate to say that every owner–contractor conversation is prohibited. Communications with the architect's consultants normally go through the architect under the contract's communication framework. Construction-management and design-build arrangements require corresponding distribution procedures; identify those relationships before applying a traditional design-bid-build communication chart.

Prepare a communication matrix with each recurring deliverable, author, reviewer, decision-maker, recipients, due date, and record location. Include owner consultants whose reports affect the design. For example, a geotechnical recommendation needs the structural engineer and civil consultant, not just the owner. A furniture vendor's final equipment schedule may affect electrical loads and accessibility even though that vendor has no agreement with the architect. The manager coordinates information without assuming the vendor's professional responsibilities.

Agendas produce usable decisions

An agenda should state the meeting purpose, topics in priority order, required decisions, documents to read, and expected participants. Send a cost-estimate reconciliation before a budget meeting so participants can evaluate alternatives instead of encountering figures for the first time. Separate information items from decisions. Identify the person whose approval is needed and the latest date that protects the schedule.

Suppose a DD review must resolve an HVAC approach, ceiling height, and owner equipment loads. Put the linked items together, attach the relevant consultant sketches, and request attendance by authorized owner and engineering representatives. Reserving the last five minutes for a major systems choice creates avoidable uncertainty. Close the meeting by reading back decisions and action items, including unresolved dependencies.

Minutes are a contemporaneous record

Useful minutes identify the project, date, attendees, documents reviewed, decisions, qualifications, open questions, and action owners with deadlines. Distinguish a proposal from an approval. “Owner considering ceramic tile” is different from “Authorized owner representative approved ceramic tile option T2.” Identify associated cost and schedule conditions rather than recording an unqualified approval that nobody actually gave.

Issue minutes promptly under the agreed project protocol. Invite factual corrections and retain revisions with dates. A project may request corrections within a stated review period, but silence does not automatically create legal acceptance, waive claims, or amend the contract. A disputed item should be identified and clarified; do not erase the original record or pretend that an unanswered email establishes consent to additional fees.

A good action log might contain:

The dates are illustrative. Their purpose is to connect commitments to downstream work. Update the log at each meeting and escalate missed dates that affect the critical path.

Email, memos, and telephone follow-up

Use an email for a focused request, distribution, or confirmation that does not require a formal contractual instrument. Put the project and subject in the title, reference the current document revision, state the requested action and due date, and link the record location. Avoid mixing unrelated instructions in a long thread. Send a memo when explaining a substantial recommendation, comparing alternatives, or documenting a decision with technical and financial consequences.

A telephone call can resolve an urgent ambiguity quickly, but follow it with a factual written confirmation when project decisions are involved. There is no universal 24-hour contractual deadline for every confirmation. Choose a prompt interval suited to the risk and project procedure. If a verbal request would change the architect's services, document its scope and obtain the applicable service authorization rather than substituting a friendly email for an amendment. Some additional-service circumstances permit beginning work to avoid delay with prompt notice; read the governing clause.

Preserve the record and control revisions

Store correspondence in the project repository rather than only in individual inboxes. Use access permissions and an index so another team member can find the operative decision when staff change. Preserve superseded issued documents with their transmittals; distinguish them from work in progress. Do not circulate an unreviewed background as a permit set or rely on an obsolete attachment merely because its filename looks familiar.

A transmittal should state the issue purpose, recipients, date, revision, included sheets or files, and any reliance limits. If a consultant receives revised plans, explicitly identify changes affecting its work. Asking everyone to discover revisions by comparing entire sets wastes review time and creates gaps. When a decision changes approved design objectives, update the decision log, notify affected disciplines, revise the baseline, and verify implementation at the next review.

Worked communication choice

The contractor tells the owner that moving an electrical room will save two weeks. The owner emails approval to the contractor and copies no designers. The manager should obtain the proposed change, coordinate structural and MEP effects, assess owner cost and schedule consequences, and document the required construction and professional-service authorizations. An email expressing owner preference does not establish a coordinated design or authorize the architect to ignore code review. The next step is a documented evaluation with the affected team, followed by the correct approval instrument and controlled issue of revised documents.

Reference: AIA B101 edition comparison.