Project closeout checklist: what to document before final handover

Buildpeer

September 30, 2026

Completing field work does not mean a project is ready for handover.

Before handover, it may still be necessary to verify progress, resolve pending items, organize evidence, and gather the documentation that must be kept after execution is complete.

A project closeout checklist helps ensure that this information is complete and that any outstanding items are identified before formalizing the handover.

The necessary documents may vary depending on the type of project, the contract, and the procedures established between the parties. However, there are some elements that should be reviewed in most closeouts.

‍

What closing a project means

From a technical and documentary standpoint, closing consists of verifying that the work corresponding to the scope is finished and that the information needed to document what was executed is organized.

This goes beyond simply having no personnel working on-site.

A project may have finished most of its activities and still have pending observations, documents to update, information to submit, or elements that require a final review.

That is why the closeout should not begin on the last day of execution. A good portion of the necessary information is generated throughout the entire project.

An office project may have its finishes installed and still not be closed: it might be missing the final approval of three finish submittals, the warranty for the air conditioning system, or the as-built drawings for the electrical installation that was modified mid-project.

‍

Why documentation becomes so important at closeout

During execution, many situations are resolved as the project progresses.

The problem arises when those decisions are not recorded and, at the time of preparing the handover, someone needs to know what happened.

Evidence of an activity, a response to a request for information, a record of a modification, or the final version of a document might be missing.

Reconstructing that information at the end may require reviewing emails, messages, photographs, and files from different people.

A good closeout aims to avoid exactly that.

A typical example: six months after handover, the client reports a leak on the roof. Without evidence of how that area was waterproofed or a record of what material was used, resolving the warranty becomes a debate based on memory between the contractor and the client, rather than a quick consultation of the closeout file.

The documentation generated during construction should provide a clear understanding of what was executed, which pending items were resolved, and what information the project recipient needs to retain.

‍

The checklist, category by category

The exact content of the checklist will depend on each project. As a starting point, here are some categories worth reviewing.

Physical progress and evidence

Verify the progress made against the project scope.
Check that all pending activities have been identified.
Organize relevant photographic evidence generated during execution.
Confirm that the site log or corresponding construction records are up to date.

Evidence does not have to be limited to the final result. For certain activities, it may be important to also keep records of the process, especially when part of the work will no longer be visible after construction is complete.

‍

RFIs, submittals, and issues

If the project uses RFIs and submittals, it is advisable to review their status before handover.

Identify any RFIs that remain open and define the necessary follow-up.
Review the final status of submittals related to the work performed.
Confirm that relevant issues and observations have their follow-up documented.
Keep responses, revisions, and related documents available.

Not all projects use the same processes or terminology. The important thing is to identify what information remains open and what needs to be resolved or documented before closing.

‍

As-builts and final documentation

The final documentation should accurately represent the information that needs to be preserved after execution. Depending on the project, this may include:

As-built drawings or equivalent documentation reflecting the final conditions of the work performed.
Current revisions of drawings and documents.
Applicable specifications and technical documentation.
Records of modifications made during execution.

Having this information facilitates future interventions, maintenance, and inquiries regarding what was actually executed.

‍

Warranties and manuals

When the scope includes materials, equipment, or systems that have warranties or require subsequent operation, it is advisable to gather the corresponding documentation.

Available warranties for installed materials and equipment.
Information on validity and applicable terms.
Operation and maintenance manuals.
Technical information required for the delivered equipment or systems.

The required documentation will depend on what is established for each project and the elements included in the delivery.

Punch list and handover

Before closing, it is also advisable to review the observations that arose during the final inspections.

Identify pending items from the final review or punch list, when the project uses this process.
Record which items were addressed and which remain open.
Maintain evidence of follow-up where applicable.
Prepare the handover and acceptance documentation required for the project.

The goal is for all parties to have clarity regarding the status of the work at the time of handover.

‍

What happens when documentation is incomplete

Not all missing documents cause an immediate problem.

In many cases, the difficulty arises later on.

You might need an equipment manual during maintenance, a warranty might require specific documentation, or someone might need to check what was installed in an area that is no longer visible.

Questions may also arise about a decision made during construction, requiring a review of the project history. For example, if someone asks why a different material was used than what is shown on the original plans, and there is no RFI or documented modification authorizing the change, there is no way to confirm if it was an approved decision or an execution error.

This is similar to other common construction management mistakes: it is rarely one single major error, but rather several small, undocumented details that accumulate.

When information is scattered, reconstructing it later can be time-consuming and may depend on people who are no longer involved in the project.

That is why the closeout also serves to leave a record that remains useful long after the handover.

‍

Closeout should be prepared during execution

Waiting until the final weeks to gather all the documentation usually makes the closeout process more complicated.

RFIs, submittals, evidence, issues, document revisions, and site logs are generated at different stages of the project.

This is part of the same process that should already be in the resident engineer's daily toolkit: recording evidence and closing out pending items as they occur, rather than reconstructing them at the end.

If that information is organized as it happens, the closeout work consists mainly of reviewing what is complete and what remains pending.

If it wasn't done during execution, the team will have to reconstruct part of the history just when they are also focused on finishing and handing over the project.

That is why a closeout checklist can be used long before reaching the final handover.

‍

Before the next handover, prepare for closeout during execution

Project closeout shouldn't be the moment the team starts looking for what was documented.

If progress, evidence, RFIs, submittals, issues, and revisions are recorded as execution happens, reaching the handover mainly consists of reviewing what is complete and addressing what is still pending.

The exact list will be different for each project, but the principle is the same: the information needed to close out a project is built throughout its execution.

If you are looking for a way to keep your project documentation organized from execution to handover, schedule a demo and we will review your case.

Preguntas Frecuentes

What documents are needed for project closeout?

It depends on the project, the contract, and the procedures established between the parties. It may include progress records, photographic evidence, logs, RFIs, submittals, issues, as-built drawings, current documents, warranties, manuals, and handover documentation. The final list should be defined according to the specific requirements of each project.

When should the project closeout checklist be prepared?

During execution. This doesn't mean preparing the handover package from day one, but rather keeping the information that will later be needed for closeout organized. When evidence, issues, revisions, and documents are recorded as they are generated, preparing the final handover becomes much simpler.

Who is responsible for preparing the project closeout?

It depends on how responsibilities are distributed in each project. Preparation may involve the site manager, project manager, supervisor, contractor, project administration, and others responsible for generating or validating documentation. The important thing is to define who must deliver each item and who verifies that the required information is complete.

What happens if there are still pending items at the time of handover?

It depends on the nature of the pending item and what has been agreed upon between the parties. The important thing is that open items are clearly identified, have an assigned owner, and have a record of their status and follow-up. This prevents uncertainty after the handover regarding what remained pending and what actions were required.

Is the technical closeout of a project the same as the IMSS closeout?

No. The technical and documentary project closeout relates to the completion of work, outstanding items, and the information required for handover. Procedures related to the IMSS involve separate obligations and processes. Their requirements must be reviewed in accordance with applicable regulations and do not replace the technical and documentary project handover process.

Transform your construction projects