Closeout Package Assembly for General Contracting

Read the contract, general conditions, and closeout sections of the specifications to see what documents must be delivered at the end of the project. Look for specific mentions of manuals, warranties, as-built drawings, commissioning reports, training records, and any special owner formats.

Check with the client’s representative and the architect to see if they have a standard closeout package template or example from another project. Some organizations have set expectations about binder structure, digital formats, or portal uploads.

Create a list of document categories such as “Administrative,” “As-Builts,” “Warranties,” “O&M Manuals,” “Testing and Commissioning,” “Training,” and “Regulatory Approvals.” Under each category, note key items like “signed contract,” “certificate of occupancy,” or “fire alarm test reports.”

Decide which parties need full packages (for example, client facilities team, client project management, architect) and which need partial sets (for example, major subcontractors may only need certain sections). Note this alongside your category list.

Build a one- or two-page matrix listing document categories down one side and recipients across the top, marking which groups receive which sections. This becomes your blueprint for assembling the package.

Sit down with the project manager to confirm that your understanding of requirements is correct. Adjust based on their feedback and then treat this matrix as the standard for the project.

Decide whether you will maintain the closeout checklist as a spreadsheet, in your project management platform, or both. Pick a tool that is easy to update and that can be shared with the project manager and superintendent.

Set up columns such as category, document name, description, responsible party (internal or subcontractor), required format, required for which recipients, received date, reviewed/approved status, and included in owner package (yes/no).

Using the closeout contents matrix, enter each required document as its own row in the log. Be specific—for example, “RTU-1 O&M manual” instead of just “mechanical manuals.” This makes follow-up much easier later.

For each row, identify who is responsible for providing the document: GC staff, commissioning agent, subcontractor, or design team. Enter this in the responsible party column so there is no confusion.

Save the log in a shared project directory where the project manager, superintendent, and closeout coordinator can access it. Control editing permissions so that only designated people can change the status fields.

Walk through the log with the project team in a meeting so everyone understands what documents are needed and how their status will be tracked.

From your checklist, identify items such as the executed owner–contractor agreement, major change orders, substantial completion certificate, and final completion certificate. Include any special agreements like allowances reconciliations or settlement letters.

Work with your internal project management and accounting teams to obtain signed contracts, change orders, and completion documents. Ask for digital copies in PDF format so they can be placed directly into the closeout package.

Arrange administrative documents in a sensible sequence: contract and amendments first, then major change orders, then completion certificates and final correspondence. This helps anyone reviewing the history understand the project at a glance.

Review each document to ensure it is fully executed—signed by all required parties and dated. If signatures are missing, coordinate with the project manager to obtain them before including the documents in the package.

Create a “01 Administrative” folder within your closeout file structure and save all finalized administrative documents there with clear file names.

Mark each administrative item as “received” and “reviewed” in your closeout log once you have verified it is complete and ready for inclusion.

Check with the project manager and whoever led the as-built process to confirm that the as-built set has been reviewed and accepted by the architect and client. Verify that you have the “FINAL” versions, not drafts.

Identify which formats must be included in the closeout package (PDF, CAD, BIM model) for each discipline. Confirm that file naming follows the agreed conventions so sheets are easy to locate.

Add a “02 As-Built Drawings and Models” folder to your closeout directory, with subfolders for each discipline (Architectural, Structural, Mechanical, Electrical, Plumbing, Site, etc.).

Place the approved as-built PDFs and any required native files into the appropriate subfolders. Do not rename files unless absolutely necessary; if you must, keep the original names referenced in a simple index.

Using the as-built sheet index, confirm that all required sheets are present in the closeout folders. Spot-check a few files to ensure they open correctly and are not corrupted.

Mark as-built items as “received” and “reviewed” in your log. Include the folder paths in the log notes so others know exactly where to find the files.

Check with whoever led warranty and O&M manual collection to confirm that all required documents are finalized and stored in the project’s warranty/O&M folders. Ensure the warranty summary document is complete.

In your closeout directory, create separate folders for warranties and O&M manuals. Within each, create subfolders by system (HVAC, Electrical, Plumbing, Roofing, etc.) to match how facilities staff think about the building.

Place the final, reviewed warranty certificates and summary into the Warranties folder. Maintain clear naming that includes system/equipment name and vendor so documents are easy to identify later.

Move the accepted O&M PDFs into the O&M Manuals folder, grouped by system and location. Double-check that the manuals match the installed equipment and are not just generic brochures.

If possible, include cross-references in your warranty summary or table of contents to where related O&M manuals are stored in the closeout package. This helps users move between coverage and maintenance instructions.

Update checklist entries for warranties and O&M manuals to show they are received, reviewed, and placed into the closeout package structure.

From your closeout and inspection requirements, list documents such as HVAC test and balance reports, fire alarm acceptance tests, sprinkler certifications, elevator inspections, and commissioning reports.

Contact commissioning agents, testing companies, and relevant subcontractors to obtain any outstanding reports or certificates. Provide a deadline and remind them that closeout depends on their documents.

Review each report for completeness. Check that it includes project identifiers, dates, test results, and signatures from the responsible professional or company. If anything is missing, request corrections.

Create a closeout folder for testing and commissioning and add subfolders by system (for example, HVAC, Fire Protection, Electrical). Save each report in the appropriate location with clear file names.

Scan or save copies of final inspection sign-off cards and certificates from building, fire, and other authorities. Place them in a “Regulatory Approvals” subfolder within this section or under a separate “06 Approvals” folder if that’s clearer.

Mark each required testing, commissioning, and inspection document as received and reviewed in the log. Note any unusual results or conditions in the log for future reference.

From the contract and commissioning plan, list systems that require training, such as HVAC controls, fire alarm, emergency power, and specialty equipment. Note which subcontractor or vendor is responsible for each training session.

Ask responsible parties to provide training agendas, presentation slides or handouts, and sign-in sheets showing who attended and when. These documents show that the training obligation was fulfilled.

If training sessions were recorded (video or audio), obtain copies in a common format. Confirm files can be opened and played on standard software before including them in the package.

Create a dedicated folder within the closeout structure and store agendas, handouts, sign-in sheets, and recordings there. Group them by system or training date so they are easy to follow.

Write a brief one- or two-page summary listing each training session, date, systems covered, and attendees. This helps the client quickly see what was done and what knowledge exists within their team.

Update the checklist to show that training documentation has been fully collected and placed into the closeout package.

Decide on a top-level numbering scheme such as “01 Administrative, 02 As-Builts, 03 Warranties, 04 O&M, 05 Testing and Commissioning, 06 Training, 07 Approvals.” Apply the same structure to both digital folders and any physical binders.

Draft a simple table of contents listing each section and a brief description of what it contains. This will serve as the first page in the package and as a quick navigation aid.

Review file names and adjust if necessary so that they clearly describe the contents (for example, “RTU-1_OandM_ManufacturerName.pdf”). Avoid long, cryptic names that are hard to read.

If the client wants physical copies, print essential documents on good-quality paper and file them in labeled binders matching the digital structure. Use tab dividers with section names so users can quickly flip to the right area.

If a document in one section relates closely to another (for example, a warranty linked to a specific test report), note this relationship in the table of contents or in a short “using this package” guide.

Ask a project team member who was not heavily involved in assembly to find specific documents using only the table of contents and folder labels. Adjust labels or structure based on feedback if they struggle.

Choose one or two people who understand the project but were not deeply involved in assembling the package—often the project manager and a field engineer. They will bring fresh eyes to the review.

Give reviewers a copy of the closeout checklist and contents matrix along with access to the digital package and, if applicable, physical binders. Explain that they should verify both presence and basic quality of documents.

Have reviewers verify that at least a sampling of documents in each section is correct, readable, and relevant. For critical items (such as as-builts, major warranties, and approvals), ask them to confirm every required document is present.

Ask reviewers to jot down any missing items, confusing naming, or quality problems. Collect their notes and discuss them together to decide which issues must be fixed before release.

Address all critical deficiencies, such as missing documents or obviously wrong files. For major corrections, have the reviewer quickly re-check those specific areas.

Once the internal review is complete and corrections are made, mark the closeout package as “internally approved” in your checklist log, including the date and names of reviewers.

Verify how the client wants to receive the package (for example, secure file transfer, shared drive access, USB drives, physical binders). Clarify how many copies are needed and where they should be sent.

If providing digital media, label drives or discs with project name, date, and contents summary. Prepare a formal transmittal or cover letter listing what is included and any special notes or instructions.

Send the package using the agreed method and obtain confirmation of receipt—either by signed transmittal, email acknowledgment, or delivery tracking. Store this confirmation with your project records.

Place a full digital copy of the closeout package in your internal project archive under a clearly named folder such as “Closeout Package – Final.” Confirm it is included in your backup system.

Set permissions on the archived closeout package to read-only for most users. This prevents later changes that would make your internal copy differ from what the client received.

Update the checklist log to show that all items are not only collected and reviewed but also delivered and archived. Note the delivery date and method so future staff can see when and how the package was handed over.