Closeout — BuildingCX

A handover that was already true.

Closeout pulls from records here instead of collecting them.

01Nothing re-collected

Every approved checklist and passed test is already in the package.

Closeout doesn't ask anyone to go find the signed forms and passed tests again — they're the same records the tracker and functional testing modules already hold, pulled straight into the handover document.

Screenshot — closeout document list pulling from approved records

02Built around finishing

Closeout is designed around every issue being closed first.

The workflow expects checklists approved, tests passed and issues closed before a package is called done — so what ships as closeout reflects the real state of the building, not a best-effort snapshot.

Screenshot — closeout readiness, tracked against open issues

03One file, not a folder

Everything merges into a single exportable package.

Checklists, test results and closed issues, plus whatever O&M manuals and as-builts you add manually, merge into one document instead of a zip file the owner has to sort through.

Screenshot — the merged closeout export, ready to download

Questions about closeout

What counts as 'ready' for closeout?

Every checklist approved, every test passed or accepted, and every issue closed. The tracker shows the gap before you export.

Can we add documents that aren't generated by the platform?

Yes — O&M manuals, as-builts and anything else attach as manual items alongside the generated records.

Does the owner get their own copy?

Yes, through the read-only portal, or as the merged export itself if you'd rather hand over a file directly.

Can we export a partial package before everything's closed?

You can export at any time, but the workflow is built around finishing first — the tracker shows exactly what's still open, so an early export reads as a snapshot, not a handover.

The handover package assembles itself.