Chapter 3: Document Control on Active Construction Sites

Clause 7.5 document control on construction sites must handle drawing revisions, RFI responses, change orders, and submittals across multiple trailers, multiple subcontractors, and varying connectivity — far more chaotic than a manufacturing plant. The site-document-control workflow that passes accredited audits: a single source-of-truth platform (Procore, Aconex, or PinnacleQMS), enforced revision control on every drawing and specification, RFI logs with traceable closure, change-order signoff matrix, and weekly document-control walks by the QC manager. PinnacleQMS construction clients reduce drawing-related NCRs by 60% within 90 days of platform adoption.

Construction document control breaks every assumption that ISO 9001 auditors carry over from manufacturing. A plant has one shop floor, one set of work instructions, and a controlled-document binder behind the quality manager's desk. A jobsite has six trailers, eleven subcontractors, four revisions of the same structural sheet pinned to four different walls, a superintendent texting field changes from a half-bar LTE connection, and a concrete pour scheduled for 6:00 AM tomorrow that depends on a rebar shop drawing nobody can confirm is the latest. The ISO 9001:2015 requirement for "documented information" is identical in both worlds. The execution is not. This chapter walks Canadian and US construction contractors through the site-level document control workflow that survives accredited audits, keeps drawing-related non-conformances out of the closeout package, and protects the contractor when an owner disputes scope two years after substantial completion.

Section 1 — Drawing and specification revision control on site

Drawing control is where most construction QMS programs fail their first surveillance audit. The auditor walks into a trailer, asks for the current architectural set, and finds Rev 4 on the plan table while the steel erector outside is working from Rev 6. Findings of this type appear in roughly half of all construction-sector audits PinnacleQMS supports. The following controls eliminate the pattern:

1. Designate a single electronic source of truth — Procore, Aconex, BIM 360, or PinnacleQMS — and prohibit drawings from being downloaded, printed, or emailed outside that platform without a controlled-distribution stamp.
2. Apply a revision watermark to every printed sheet that includes the revision letter, issue date, and expiry trigger ("superseded upon next issue"). Sheets without the watermark are considered uncontrolled and shall not be used for construction.
3. Maintain a master drawing log on the platform that lists every sheet number, current revision, date issued, issued-by, and supersedes-revision field. The log is the auditable record, not the sheets themselves.
4. Lock superseded revisions in a "Superseded" folder with read-only access. Deleting old revisions destroys traceability and triggers findings under clause 7.5.3.2.
5. Require the project document controller — not the superintendent, not the project engineer — to publish revisions. Single point of release prevents two trailers issuing conflicting Rev 5s.
6. Distribute revisions through automated platform notifications keyed to trade. The mechanical sub gets mechanical revisions; the steel erector gets structural revisions; everyone gets architectural and civil.
7. Conduct a weekly document-control walk where the QC manager pulls three random sheets from three random trailers and verifies they match the current platform revision. Document the walk in a one-page log.
8. Specifications are documents too. Section 03 30 00 (cast-in-place concrete) and the project specification book require the same revision control discipline as drawings — auditors check this and crews routinely miss it.
9. Address books — the list of who receives what — are themselves controlled documents. When a subcontractor's project manager changes mid-project, the document distribution matrix is revised, signed, and reissued.
10. Reconcile the drawing log against the submittal log and RFI log monthly. Drawings that triggered RFIs or submittals must show the revision the RFI/submittal references; mismatches get resolved before they become as-built problems.

Section 2 — RFI workflow

Requests for Information are the construction industry's controlled-change mechanism, and they are nearly always the weakest link in a contractor's document trail. RFIs sit in inboxes for three weeks, get answered verbally in a coordination meeting and never documented, or get distributed to one trade and not the four others affected. Accredited auditors know exactly where to look.

1. Every RFI carries a unique number from a single project register. Two trailers issuing RFI-047 in the same week is an immediate finding.
2. The RFI form captures: originator, trade, drawing reference (sheet and revision), specification reference, question, proposed solution, schedule impact, and cost impact flag. Missing fields equals incomplete documented information.
3. A response service-level agreement is written into the QMS — typically 5 to 10 working days for non-critical and 24 to 48 hours for schedule-critical RFIs. The platform timestamps both submission and response so the SLA is auditable.
4. Closure requires a written response from the architect or engineer of record, attached to the RFI in the platform. Verbal answers from a job walk are not closure — they are inputs to a written response.
5. Distribution on closure is automatic and trade-keyed. If the RFI affects mechanical, structural, and architectural scope, three subs receive the closure notice; the platform records read-receipts.
6. RFIs that result in design changes trigger drawing revisions or sketches (SK-series). The link between the RFI number and the resulting SK or revised sheet is recorded in the drawing log so cost-and-schedule impacts are traceable to source.
7. The QC manager reviews the open-RFI log weekly. Any RFI older than the SLA is escalated in writing to the design team and copied to the owner's representative — silence is not a closure mechanism.
8. The closed-RFI log becomes part of the project closeout package. Owners increasingly require this register at substantial completion, and litigation discovery reaches for it first when scope disputes arise.

Section 3 — Change orders and contract document control

Change orders sit at the intersection of document control, contract administration, and quality management. Failures here are not just clause 7.5 findings — they expose the contractor to claim losses that dwarf any audit consequence.

1. Every change order, change directive, and field directive carries a unique number, a clear scope description, a cost impact, a schedule impact, and references to the originating RFI, ASI, or owner directive.
2. The signoff matrix is documented in the project quality plan: who signs at what dollar threshold. A field super may approve a $500 directive; a $50,000 change requires the project manager and the owner's representative; a $250,000 change may require a regional VP and a written contract amendment.
3. Pending change orders — work proceeding under a directive but without a fully executed CO — are tracked on a separate log with weekly review. The longer they sit, the more documentation gaps accumulate.
4. The contract documents themselves (prime contract, subcontracts, addenda, bulletins) are revision-controlled with the same discipline as drawings. When Addendum 4 is issued during bid and Bulletin 2 is issued during construction, both must show on the contract document register.
5. Change orders that affect the QMS scope — a new building added mid-project, a change from one structural system to another — trigger a revision of the project quality plan, the inspection and test plan, and any associated submittal requirements.
6. The QC manager confirms that subcontractor change-order packages flow through the same controlled register. A sub-tier change order that bypasses the prime's register creates a documentation gap that surfaces during closeout.
7. Closeout reconciliation matches every executed change order to a corresponding drawing revision or specification clarification. Change orders without document trail are a red flag in both the audit and any subsequent dispute. PinnacleQMS construction clients pursuing ISO 9001 certification report that this single discipline recovers an average of $180,000 per project in previously undocumented scope.

Section 4 — Submittal log management

Submittals — shop drawings, product data, samples, mockups, and quality submittals — are where the contractor's quality story meets the designer's specification intent. A weak submittal log is the single fastest way to a major non-conformance.

1. The submittal log is generated from the project specifications during preconstruction, not improvised during execution. Every spec section that requires a submittal is mapped to a numbered entry.
2. Each submittal entry shows: number, spec section, description, type (shop drawing, product data, sample, mockup, certification), required-by date driven by procurement and schedule, submitted date, returned date, and disposition.
3. Disposition codes follow the project specification — typically "No Exception Taken," "Make Corrections Noted," "Revise and Resubmit," "Rejected." Plain-English approvals do not satisfy traceability requirements.
4. A submittal cannot be marked closed on a "Revise and Resubmit" or "Rejected" disposition. Resubmittal carries the same number with a revision suffix (e.g., 03 21 00-001 R1) until disposition is acceptable.
5. Long-lead items — structural steel, mechanical equipment, switchgear, glazing — are flagged in the log with a critical-path indicator. Weekly review by the project manager and QC manager focuses on these first.
6. Quality submittals (welder qualifications, concrete mix designs, NDT procedures, weld procedure specifications, mill certificates) carry the same control as product submittals. Auditors specifically pull these to verify trade qualification and material conformity.
7. Mockup submittals trigger physical mockup inspections; the inspection record links back to the submittal number so the auditor can trace specification → submittal → mockup → field acceptance in a single chain.
8. Sample retention — paint chips, brick samples, sealant bead samples — is a documented information requirement. The QC manager maintains a sample log identifying where physical samples are stored and how long they are retained.
9. Subcontractor-managed submittals (mechanical, electrical, fire protection) flow through the prime contractor's register; sub-tier silos create gaps.
10. The closed submittal log becomes part of the operations and maintenance manual at closeout, paired with as-builts, warranties, and commissioning records.

Section 5 — As-built drawings and project closeout

As-builts are where a contractor's document control either pays off or produces a frantic, six-week scramble before substantial completion. The disciplined approach starts on the first day of construction.

1. The redline set is established at project mobilization. A controlled set of drawings is designated "as-built master" and updated continuously by the responsible trade — mechanical contractor for mechanical, electrical for electrical, civil for underground.
2. Redline updates are made at minimum weekly and reviewed monthly by the project engineer. Weather, holidays, and crew turnover do not pause the cadence.
3. RFI closures, change-order revisions, and field directives that affect installed work are reflected on the redlines within five working days of closure or completion.
4. At project closeout, the redlines are translated into clean record drawings — typically by the design team or a survey contractor — and those record drawings are reconciled against the redlines, the closed RFI log, and the executed change-order log.
5. The closeout package includes record drawings, closed RFI log, executed CO log, closed submittal log, equipment O&M data, warranties, training records, and commissioning reports. Each item references the others so an owner — or an accredited auditor on a future surveillance — can trace any system end-to-end.
6. Owners with mature facilities standards (most US federal, most Canadian Crown corporations, healthcare authorities) require electronic deliverables in specified formats. The project quality plan identifies these requirements in preconstruction so the closeout team is not reformatting at the last minute.
7. The QMS requires a final document-control review by the QC manager confirming that every controlled document has a final disposition and every superseded revision is archived. This signoff is the contractor's evidence that clause 7.5.3.2 controls were maintained for the full project lifecycle.

Common construction-site document-control audit findings

The following patterns appear repeatedly in accredited audits of construction contractors, and 98% of contractors who close them sustain certification across the full three-year cycle.

1. Uncontrolled drawings on site — printed sets without revision watermarks, sheets in trailers that do not match the platform's current revision, taped-up sketches with no SK number or originator.
2. RFIs answered verbally — coordination meeting minutes referencing "discussed and resolved" without a written closure attached to a numbered RFI in the register.
3. Change orders executed but not reflected on drawings or submittals — scope added in the field with no document trail, surfacing only when an owner's commissioning agent raises a discrepancy.
4. Submittal log gaps — spec sections that required submittals but show no entry in the log, or entries closed without a clear disposition code.
5. Subcontractor documents outside the prime register — mechanical sub maintaining its own RFI numbering, electrical sub running its own submittal log in a spreadsheet, with no roll-up to the project register.
6. Redlines not maintained — as-built sets that were updated through framing and stalled at drywall, with the final eight months of project changes captured nowhere.
7. Closeout packages missing the cross-references — record drawings without the RFI and CO logs that explain the deviations from contract documents, leaving the owner with a thin package and the contractor with weak evidence in a later dispute.

Construction document control is enforced by platform discipline, weekly walks by a QC manager who actually walks, and a project quality plan that names the document controller, defines the SLAs, and integrates RFIs, change orders, submittals, and as-builts into a single auditable chain. PinnacleQMS construction clients combine the PinnacleQMS document control hub with the structured implementation process and accredited auditor support tailored to the construction sector. Contact PinnacleQMS to map current site document workflows to ISO 9001 clause 7.5 and the additional ISO 45001 documented-information requirements that owners increasingly bundle into prequalification — most contractors are 60 to 90 days from a clean surveillance audit once the platform discipline is in place.