Document Controls by Delivery Method

Implement documentation procedures for the selected delivery method

A project documentation policy must fit how the work is procured and built. A traditional single-package design-bid-build issue, several CMc early packages, multiple CMa prime contracts, and design-build performance criteria create different information risks. The manager translates practice-wide standards into the project's issue purposes, reviewers, approval authority, package boundaries, and distribution. A consistent sheet number is helpful, but it does not alone produce a clear and coordinated contract record.

Establish the current document baseline

At kickoff, identify the delivery method, agreements, required deliverables, authorized reviewers, digital protocols, and owner decision procedure. Define document states such as work in progress, coordination, owner review, permit, bid, and construction. A document's issue purpose should be explicit. A draft shared for engineering coordination should not quietly become a field instruction because the contractor found it in a folder.

Use a register identifying package, revision, date, author, review status, issue purpose, recipients, and superseded version. Archive issued sets and their transmittals. Keep live working models separate from contractual issues and identify any model versions enumerated as Contract Documents. Establish conflict and reliance procedures in the agreements rather than inventing automatic precedence between all printed and digital information.

Design-bid-build controls

For a single coordinated bid package, verify cross-discipline references, specifications, schedules, scope, code analysis, and the approved estimate before issue. During bidding, changes and clarifications affecting the bidder basis generally need the prescribed addendum procedure and distribution to the participating bidders. Answering one bidder privately with a changed scope can leave unequal information and incompatible prices.

After construction execution, distinguish RFIs and interpretations from changes to price, time, or scope. A revised drawing may require a Change Order, Construction Change Directive, or minor-change instruction depending on the facts. Identify the governing instrument and its authority. Record the revision as part of the contract history instead of replacing the original set without explanation.

CMc and early-package controls

Early foundations, structure, or procurement packages can be issued before the rest of the design is complete. Define each package's included work, exclusions, assumed interfaces, dependent decisions, and remaining design information. Verify that the scope used for an estimate or GMP proposal matches the identified issue dates. A drawing labelled “early release” does not mean all later changes are included at no additional cost.

Assume foundation drawings are released while rooftop equipment is still being selected. The manager should identify load assumptions, coordinate structural and equipment decisions, and explain the consequence of exceeding the approved basis. If the later equipment alters loads, evaluate foundations and construction work already procured. Merely distributing a new mechanical schedule does not establish that structural design or the GMP has been updated.

Schedule review gates before release and reserve time for corrections. Fast-tracking may shorten elapsed time but increases interface and rework risk. Clear scope boundaries and records reduce that risk; they do not eliminate the need to evaluate a later change under the agreements.

CMa and multiple-prime controls

Separate owner-held prime contracts require a package interface matrix. Identify who supplies, installs, connects, tests, and warrants components crossing packages. Coordinate temporary facilities, access, sequencing, common testing, and closeout responsibilities. The CMa and architect's respective review and routing duties should match B132, C132, A132, and A232 as applicable.

For a roof penetration, the matrix should identify the equipment supplier, curb installer, structural support designer, roofing trade, and flashing responsibility. “By others” is not an assignment unless those others' contracts actually include the work. If two packages both exclude it, the manager must resolve the gap through the applicable owner approvals and contract changes. Track the same resolution in specifications and drawings, not only meeting minutes.

Design-build criteria and conformance records

In design-build, distinguish owner criteria, proposal commitments, design-builder design documents, and contract modifications. Specify measurable required outcomes and any prescriptive constraints, identify how conformance is reviewed, and document owner decisions. A criteria consultant's review should stay within its assigned scope and not silently assume the architect-of-record role.

If the owner revises a performance criterion after agreement, compare it with the accepted basis and assess design, price, schedule, and approval effects. Record whether the change is an owner requirement, a correction needed to satisfy the original criteria, or a proposal by the design-builder. Those different causes can lead to different contractual outcomes. The word “design-build” alone does not make every revision the design-builder's uncompensated responsibility.

Release and verification workflow

For any delivery method, the manager should confirm the issue basis, complete the required interdisciplinary review, obtain the appropriate approval, transmit identified documents, and verify recipient access. Identify superseded sheets and distribute changes to all affected participants. Back-check implementation in related models, schedules, specifications, and estimates.

A useful audit trail answers: what was issued, why, to whom, under what authority, and what it replaced. When a conflict is found, preserve that history and resolve the discrepancy through the governing procedure. A controlled repository supports coordination, but software permissions cannot replace professional review or owner authorization.

Apply the policy to a scenario

A contractor uses a DD coordination plan for fabrication after receiving a later construction issue. The manager should identify the transmitted versions, permitted reliance, actual required work, and notice history before assessing correction or entitlement. Then improve distribution and revision controls so the operative set is unmistakable. The immediate goal is a documented, coordinated solution; the long-term goal is a project policy that matches its delivery structure and makes preventable information gaps visible before construction.

Reference: AIA A201 document and change procedures.

Package-release controls