2.4 Project Communications Management

The Importance of Communication Management

Construction projects are complex endeavors involving dozens of different organizations—owners, architects, engineers, construction managers, general contractors, specialized subcontractors, and regulatory agencies. The failure of a project is rarely due to a lack of technical expertise; it is most often the result of poor communication.

Effective Project Communications Management ensures the timely and appropriate generation, collection, distribution, storage, retrieval, and ultimate disposition of project information. The Construction Manager acts as the central hub for this information flow, maintaining order and establishing a clear historical record of the project.

The Project Communication Plan

Before construction begins, the CM should develop a formal Project Communication Plan. This document establishes the "rules of engagement" for how information will be handled.

A robust communication plan defines:

• Roles and Responsibilities: Who is authorized to make decisions or approve changes?
• Lines of Communication: What is the official chain of command? (e.g., subcontractors must communicate through the GC, not directly to the architect).
• Reporting Requirements: What reports are required (daily, weekly, monthly), what should they contain, and who receives them?
• Meeting Schedules: When will routine meetings occur, and who must attend?
• Technology Utilization: What software platforms (e.g., Procore, PlanGrid, e-Builder) will be used for document control?

Formal Communication Tools

Two of the most critical, formalized communication processes in construction are RFIs and Submittals.

Requests for Information (RFIs)

Despite the best efforts during design, construction documents are rarely perfect. A Request for Information (RFI) is a formal written process used by the contractor to seek clarification on drawings, specifications, or unforeseen field conditions.

The RFI Workflow:

1. Discovery: The contractor identifies a conflict (e.g., a structural beam clashes with an HVAC duct in the drawings) or an ambiguity.
2. Submission: The contractor submits a formal RFI to the CM or Architect, describing the issue and often proposing a solution to save time.
3. Review: The design team reviews the RFI and determines the appropriate clarification or design modification.
4. Response: The architect provides a formal response. If the response changes the project scope, it may trigger a Change Order for additional time or money.

Managing RFIs efficiently is critical. Delays in answering RFIs can directly delay construction activities in the field.

Submittals and Shop Drawings

The design documents specify what the final product should achieve, but the contractor must provide the specific materials and components to achieve it. The Submittal process is how the contractor proves they intend to supply the correct materials before actually buying or installing them.

Types of Submittals:

• Product Data: Manufacturer's cut sheets, specifications, and performance data for standard items (e.g., paint, light fixtures).
• Shop Drawings: Highly detailed, contractor- or manufacturer-produced drawings showing exactly how a specific component will be fabricated and installed (e.g., structural steel connections, custom millwork). Shop drawings are much more detailed than the architect's design drawings.
• Samples: Physical examples of materials to verify color, texture, and finish (e.g., carpet swatches, brick samples).

The Submittal Workflow:

1. The contractor gathers data from subcontractors and suppliers, reviews it for compliance with the contract, and stamps it "Approved."
2. The submittal is forwarded to the Architect/Engineer.
3. The design team reviews the submittal solely for conformance with the design intent and marks it (e.g., "Approved," "Approved as Noted," "Revise and Resubmit").
4. The contractor is only authorized to procure or fabricate the item after receiving an approved submittal.

Document Control Systems

A modern commercial construction project generates thousands of documents—drawings, specifications, RFIs, submittals, daily reports, inspection records, and change orders.

Document Control is the process of managing this massive flow of information. The most critical function of document control is ensuring that everyone on the project is working from the current, approved set of documents. Building off an outdated drawing leads to expensive rework.

Today, this is almost exclusively managed through cloud-based Construction Management Software (PMIS - Project Management Information Systems). These systems provide a single source of truth, track revisions, maintain an unalterable audit trail of who viewed or approved a document and when, and allow field workers to access current drawings on mobile devices.

Meetings and Documentation

Regularly scheduled meetings are essential for keeping the project team aligned, solving problems collaboratively, and maintaining momentum.

Types of Meetings

• Pre-Construction Meeting: Held before mobilization to align the team on logistics, safety protocols, and administrative procedures.
• Owner-Architect-Contractor (OAC) Progress Meetings: Typically held weekly or bi-weekly to review schedule progress, cost status, outstanding RFIs/Submittals, and high-level issues.
• Subcontractor Coordination Meetings: Held by the GC with trade foremen to plan the upcoming week's work, manage site logistics, and resolve spatial conflicts.
• Safety Meetings (Toolbox Talks): Held frequently in the field to address specific hazards related to the current phase of work.

Meeting Minutes

Meetings are only as effective as the documentation they produce. Meeting Minutes must be recorded and distributed promptly after every formal meeting.

Effective minutes serve as a legal record of the project. They should not be a transcript of every word spoken, but rather a clear record of:

• Decisions made.
• Action items assigned (who is responsible for doing what).
• Due dates for those action items.
• Issues that remain unresolved.

Failure of a party to object to the contents of the meeting minutes within a specified timeframe (usually a few days) generally means they are accepted as an accurate record of fact, which is critical if disputes arise later.