Document Control, Close-Out Package, and Transmittals

Why Close-Out Documents Matter

A construction project is not finished when the last nail is driven. It is finished when the owner has everything needed to operate, maintain, and legally occupy the building. That final transfer of information is called the project close-out, and it is governed by the contract's general conditions. Owners, lenders, insurers, and code authorities all rely on close-out documents. A missing warranty certificate or an unmarked as-built drawing can delay certificate of occupancy, trigger contract penalties, or create liability years later. As a construction manager or estimator, you are responsible for tracking, assembling, and transmitting every required item on time.

The Close-Out Checklist

Before you can assemble a close-out package, you need a complete list of what the contract requires. Start by reading the general conditions section of the project contract. Typical required deliverables include:

• As-built drawings (marked to show field changes)
• Operations and Maintenance (O&M) manuals for every installed system
• Warranty certificates from subcontractors and equipment manufacturers
• Attic stock (spare materials such as extra tile or paint)
• Testing and balancing reports
• Certificate of substantial completion
• Lien waivers from all subcontractors and suppliers
• Training records showing owner's staff were trained on systems

In Procore, you enter these items as Action Items, assigning each one a responsible party and a due date. This creates a live tracking record. Every stakeholder can see what is complete and what is outstanding. When the package is 100% complete, the transmittal can be issued. Never send a partial close-out package without written owner approval; doing so creates an audit gap and may constitute incomplete contract performance.

As-Built Drawings in Bluebeam Revu

As-built drawings document every field change made during construction—relocated conduit runs, resized duct sections, adjusted dimensions, or substituted materials. They are the permanent record of what was actually built, and they are essential for future maintenance and renovations.

The industry-standard workflow in Bluebeam Revu is:

1. Open the original contract drawing PDF in Revu.

2. Refer to the field-change log provided by the superintendent or project engineer. This log lists the sheet number, the change description, and the location on the drawing.

3. Draw a revision cloud around the area that changed, using the Revu markup tools (Shapes → Revision Cloud).

4. Place a delta tag (triangle with a revision number inside) adjacent to the cloud. Number tags sequentially: Δ1, Δ2, and so on.

5. Add a markup note linking the delta to the field-change log entry.

6. Once all changes on a sheet are marked, use Flatten (Document → Flatten) to permanently embed the markups into the PDF so they cannot be accidentally moved or deleted.

7. Export a final stamped PDF. Many firms add an AS-BUILT stamp—typically in red—on each modified sheet.

A sheet with no field changes does not receive a revision cloud but may still be included in the package for completeness. Check the contract to confirm which sheets must always be submitted.

Safety note: As-built drawings for mechanical, electrical, and plumbing systems are also safety documents. Future workers doing maintenance on electrical panels or gas lines rely on accurate as-builts to identify what is energized and where shutoffs are located. Inaccurate or missing as-builts can contribute to struck-by, electrocution, and confined-space hazards. Treat markup accuracy as a safety obligation, not just an administrative task. When field personnel are verifying changes before you mark them up, they must follow all applicable site safety requirements—PPE, lockout/tagout (LOTO) for electrical verification, and confined-space entry procedures where applicable.

O&M Manuals and Warranty Logs

O&M manuals are collected from subcontractors and equipment manufacturers. They describe how to operate, service, and troubleshoot installed systems—HVAC, elevators, fire suppression, and so on. Confirm that each manual matches the actual equipment installed, not a generic model. Substitute equipment that was approved via a Request for Information (RFI) or submittal must be documented with the correct manual.

A warranty log (sometimes called a warranty summary) lists every warranty in the package: the item covered, the warrantor's name and contact information, the warranty period start date, and the expiration date. Many contracts require a one-year general contractor warranty on workmanship in addition to manufacturer warranties. The warranty log is the owner's quick reference; without it, tracking hundreds of individual certificates is unmanageable.

Transmittals in Procore

A transmittal is a formal, dated record that documents exactly what was sent, to whom, and when. In Procore, the Transmittals tool lets you:

1. Create a new transmittal and assign it a number (transmittals are numbered sequentially).

2. Select the recipient (the simulated owner contact in training; the actual owner's representative in practice).

3. Attach every close-out document: the as-built PDF package, O&M manuals, warranty log, lien waivers, and any other checklist items.

4. Set the transmittal purpose (e.g., "For Record" or "As Required").

5. Send and confirm delivery. Procore timestamps the record automatically.

The completed transmittal is the audit-ready proof that the contractor fulfilled its contractual close-out obligations. Courts, arbitrators, and bonding companies use transmittal records to resolve disputes about whether deliverables were provided.

Quality Check Before Sending

Before finalizing the transmittal, verify:

• Every checklist item is marked complete in Procore Action Items.
• Every sheet with a field change has a revision cloud and delta tag, and markups are flattened.
• The warranty log covers every warranted item and has accurate dates.
• O&M manuals match installed equipment models.
• All attachments open correctly—check file links before sending.

If any mandatory item is missing, the entire package must be resubmitted after correction. Submitting an incomplete package and hoping the owner does not notice is not acceptable practice; it is a contract breach and an ethics violation.