Document Control and Information Flow

Introduction
In the PMI Construction Professional (PMI-CP) framework, Document Control and Information Flow sits within the Communication Tools and Strategy domain. Construction projects generate enormous volumes of information, including drawings, specifications, RFIs (Requests for Information), submittals, transmittals, change orders, meeting minutes, daily reports, inspection records and as-builts. Document control is the disciplined system that makes sure the right information reaches the right people in the right format, at the right time, and in its latest approved version.

Why It Is Important
1. Prevents rework and errors: Building from a superseded drawing is one of the most common and costly causes of rework in construction. Revision control ensures field teams work from current, approved documents.
2. Contractual and legal protection: Construction is heavily contractual. A complete, auditable record of notices, approvals, RFIs and change orders is critical for claims, disputes, delay analysis and dispute resolution.
3. Supports decision-making: Timely information flow lets stakeholders make informed decisions without delays to the critical path.
4. Regulatory compliance and safety: Permits, inspection certificates, safety data sheets and quality records must be controlled and retrievable.
5. Stakeholder alignment: Owners, designers, contractors, subcontractors, suppliers and authorities all depend on a single source of truth.
6. Handover and operations: Accurate as-built drawings, O&M manuals and warranties enable smooth project closeout and facility operation.

What It Is
Document control is the set of processes, roles, tools and standards used to create, review, approve, distribute, store, retrieve, revise, archive and dispose of project documents. Information flow describes the pathways and sequence in which information moves between parties, for example Architect to General Contractor to Subcontractor, and back again for RFIs and submittals.

Key components include:
- Document Management Plan / Document Control Procedure: Often part of, or linked to, the Communications Management Plan. It defines naming conventions, numbering, metadata, review cycles and responsibilities.
- Version and revision control: Revision codes (e.g., Rev A, B, 0, 1), status codes (For Information, For Review, For Construction, Superseded, As-Built), and clear marking of superseded documents.
- Document register / log: A master list of all controlled documents with current revision and status. Typical examples are the drawing register, RFI log, submittal log and change order log.
- Transmittals: Formal cover records showing what was sent, to whom, when, and for what purpose. They provide proof of distribution.
- Distribution matrix: Defines which stakeholders receive which document types. It is closely related to the RACI and the communications matrix.
- Approval workflows: Defined review and approval routes and turnaround times, for example a 14-day submittal review period specified in the contract.
- Common Data Environment (CDE): A centralized digital platform, often aligned with BIM and ISO 19650, where information moves through states such as Work in Progress, Shared, Published and Archived.
- Access and security controls: Permissions, confidentiality and backup.
- Records retention and archiving: Retention periods per contract, law and organizational policy.

How It Works (Typical Workflow)
1. Plan: During planning, the project manager establishes the document control procedure as part of communications and information management planning. This covers tools (CDE, Procore, Aconex, SharePoint), naming standards, roles (document controller) and workflows.
2. Create: Originators produce documents using approved templates and numbering.
3. Review and approve: Documents follow defined workflows. Submittals, for instance, go from subcontractor to GC review to designer review, and come back with a status such as Approved, Approved as Noted, Revise and Resubmit, or Rejected.
4. Distribute: Documents are issued via transmittal to the parties listed in the distribution matrix. Recipients acknowledge receipt.
5. Use and track: Logs are updated. RFIs are tracked for response times, and overdue items are escalated.
6. Revise: Changes go through change control. New revisions are issued, superseded copies are withdrawn or watermarked, and field sets are updated.
7. Archive and close out: Final records, as-builts, O&M manuals and lessons learned are compiled, handed over and archived per retention policy.

Information flow patterns to know:
- Formal vs. informal: Contractual instructions must flow through formal, documented channels. Verbal directions should be confirmed in writing.
- Contractual chain of communication: Subcontractors typically communicate with the owner through the GC, not directly. Bypassing the chain creates confusion and liability.
- Push, pull and interactive communication: Transmittals are push communication. A CDE or portal is pull communication. Coordination meetings are interactive.
- Integration with change control: Document changes affecting scope, cost or schedule must pass through the integrated change control process.

Common Construction Documents and Their Flow
- RFI: Contractor to designer, via the GC. It seeks clarification. It is not a change order, but it may trigger one.
- Submittals: Shop drawings, product data and samples go from subcontractor to GC to designer for compliance review.
- Change Order / Variation: A formal, signed modification to the contract, following change control.
- Field instruction / Site instruction: Should be documented and confirmed in writing.
- Daily reports and meeting minutes: Contemporaneous records that are vital for claims.
- NCR (Non-Conformance Report): A quality record of deviation, tracked through to closure.
- As-builts: Record of actual constructed conditions, required at closeout.

Exam Tips: Answering Questions on Document Control and Information Flow
1. Look for the formal, documented process. PMI favors answers that follow the established procedure. Examples include issuing a transmittal, logging an RFI, updating the register, or confirming verbal instructions in writing. Avoid answers that rely on informal shortcuts.
2. Current revision is king. If a scenario mentions work performed from an outdated drawing, the root cause is usually weak revision control or distribution. The best answer is to check the document register, withdraw superseded copies and reinforce the procedure.
3. Assess before acting. When a conflict between documents arises, the best first step is usually to review the contract and specifications or submit an RFI. Do not let the crew guess, and do not stop the whole project.
4. Respect the chain of communication. If a subcontractor or owner tries to bypass the contractual chain, the correct answer usually redirects communication through proper channels and documents it.
5. RFIs are not change orders. If an RFI response changes scope, cost or time, the next step is to initiate the change control process, not to proceed immediately.
6. Refer to plans. Questions on who receives what, or how documents are handled, point to the Communications Management Plan, the document control procedure or the distribution matrix. Choose answers that consult or update these plans.
7. Single source of truth. Prefer answers that centralize information in a CDE or project management information system (PMIS) over scattered emails.
8. Record everything for claims. In dispute or delay scenarios, contemporaneous records are the strongest evidence. These include daily logs, minutes, transmittals and notices. Pick answers that preserve and organize them.
9. Proactive tracking. If submittals or RFIs are overdue and threaten the schedule, the best answer is to review the log, escalate per the procedure and assess the schedule impact. Waiting is not the answer.
10. Closeout matters. Questions about project end typically point to compiling as-builts, O&M manuals, warranties, archiving records and capturing lessons learned.
11. Watch for distractors. Be wary of options such as tell the team verbally, email everyone the file, let the superintendent decide, or ignore the old version. These lack control and traceability.
12. Think predictive and adaptive. In agile or hybrid contexts, information flow may be more collaborative, using information radiators and daily stand-ups. Even so, contractual construction documents still require formal control.

Sample Question
A subcontractor installed ductwork based on Rev B drawings, but Rev C was issued two weeks ago. What should the project manager do first?
Best answer: Investigate the document distribution and register to determine why Rev C did not reach the subcontractor, then assess the impact and process any rework through proper channels. Address the process gap in the document control procedure.

Key Takeaways
- Document control ensures accuracy, traceability and accountability.
- Information flow must follow defined, contractual and documented pathways.
- Always integrate document changes with change control.
- In exam scenarios, choose the answer that is formal, documented, proactive and plan-based, and that addresses the root cause.