Construction projects generate enormous volumes of documentation, drawings, specifications, submittals, RFIs, change orders, meeting minutes, inspection reports, test results, payment applications, lien waivers, certificates of insurance, and correspondence. On a mid-size multifamily project, the complete documentation record may include thousands of individual documents produced over 18 to 24 months.
That documentation serves two purposes. During construction, it is the operational record of what decisions were made, by whom, and on what basis, the information that resolves disputes, supports change order decisions, and tracks the project’s financial and schedule status. After construction, it is the evidence record that supports warranty claims, defect litigation, and future capital improvement decisions, and the operational baseline that building managers need to maintain the building’s systems.
Projects where document control is treated as an administrative formality rather than a core construction management function consistently produce both more expensive change order disputes during construction and more expensive defect discoveries after completion.
The Core Documents That Must Be Controlled
Construction documents (drawings and specifications). The construction documents are the baseline against which all field work is measured. Document control requires that the current approved versions of all drawings and specifications are the documents being used in the field, not superseded versions, not markups that have not been formally incorporated, and not the architect’s working drawings that were never formally issued for construction. On projects where drawing revisions are issued frequently, the GC’s field teams sometimes work from superseded drawings because nobody tracked which version was current. The deficiencies this produces are discovered at punch list, after the work is completed and covered.
Submittals. The submittal log tracks the status of every required submittal through its review cycle, submission date, review return date, disposition (approved, approved as noted, revise and resubmit), and the date the approved submittal was transmitted to the subcontractor for installation. Materials installed before their submittal is approved, or installed based on a revise-and-resubmit response that required the shop drawing to be corrected, are frequent sources of quality deficiencies that are not identified until the building is occupied.
RFIs. The RFI log tracks every request for information through its response cycle. RFIs that are not closed, where the question was asked but never formally answered, leave field crews making independent decisions about how to proceed. Those decisions may or may not reflect what the design team intended, and they typically are not documented in a way that allows the decision to be reconstructed after the fact.
Change orders. The change order log tracks every change order from initial proposal through approval, the scope of work, the pricing backup, the schedule impact claimed, the owner’s response, and the final approved amount and schedule impact. The log is the basis for the budget tracking tool and the source document for disputes about what was and was not included in the approved change order amounts.
Daily construction reports. Daily reports from the GC and from the owner’s representative or construction manager record what work was performed on each day, what crews were on site, what weather conditions existed, and what issues arose. Daily reports are the most granular documentation of construction progress and are the primary evidence in delay and disruption claims, because they establish what was happening on specific days and what conditions affected the work.
Who Is Responsible for Document Control
The GC is responsible for maintaining their own internal document control, ensuring that the field teams have current drawings, that submittals are transmitted to subcontractors after approval, and that RFI responses are distributed to the trades they affect. The owner’s representative or construction manager is responsible for maintaining the owner’s record, a parallel documentation system that includes the GC’s submittals, the design team’s responses, and all project correspondence from the owner’s perspective.
In practice, many projects operate with weak parallel documentation, the GC maintains their records, the design team maintains their records, and the owner has no independent, complete project record. When a dispute arises, the owner’s ability to reconstruct what happened depends entirely on what the GC and design team share voluntarily rather than on the owner’s own contemporaneous documentation.
An owner’s representative who maintains a current, complete project record, including digital copies of all submittals, RFI responses, change order documentation, meeting minutes, inspection reports, and correspondence, gives the owner an independent evidentiary foundation that is not dependent on what the GC chooses to provide.
Construction Management Software and Document Control
Most commercial construction projects now use project management software, Procore, Autodesk Construction Cloud, PlanGrid, or similar platforms, that provides a centralized document management environment accessible to all project participants. These platforms are valuable tools when they are used consistently; they are worse than manual document control when they are used inconsistently, because the platform creates the impression of organized documentation while actually containing an inconsistent mix of current and superseded documents.
The construction manager’s role in software-based document control is to establish and enforce the protocols for how the platform is used: who can issue drawings and specifications, how revisions are numbered and tracked, how submittals and RFIs flow through the system, and what constitutes an official document versus a working draft. Without enforced protocols, the platform becomes a file dump rather than a document control system.
The Closeout Record
At project completion, the documentation record should be organized and delivered to the owner in a format that supports ongoing building operations. The closeout record should include: as-built drawings for all trades; equipment operating manuals and maintenance instructions for all installed equipment; product warranties for all major materials and systems; test reports and commissioning records for mechanical, electrical, and plumbing systems; the approved submittal record for all major materials; and the final payment applications and lien waiver record.
Owners who accept a project without a complete closeout document package will encounter operational gaps, facility managers who don’t know where utilities are routed, building owners who can’t identify materials for warranty claims, buyers who can’t demonstrate to purchasers that the building was constructed with specified materials.
Related: Construction Management Services · Owner’s Representative Services · Construction Project Closeout · Construction Management Guide
Markets: Construction Management Seattle WA · Owner’s Representative Dallas TX · Construction Management El Paso TX