Module 09

Closeout

Deliverables, punch, certificates, the closeout package, and cold storage — finishing the project with the record intact.

9.1 · Overview

How Closeout is laid out

Sub-tabs: Overview · Deliverables · Punch · Closeout package — certificates live on the Overview. The hero status comes from the certificates, never typed by hand: “Closeout in progress” → “Substantially complete” (with the date and correction-period end) → “Final completion certified.”

Cards count deliverables, punch items, AHJ items, final lien waivers, and the closeout package version.

9.2 · Deliverables

Deliverables

Seed the list mid-construction, not at the end. “Seed from submittals” turns approved submittals into obligations, and each row remembers where it came from (“Seeded from the submittal register · SUB-064”). Manual rows work too. Kinds: O&M manual, warranty, as-built, certificate, attic stock, training record, affidavit, consent of surety, lien waiver.

OutstandingOverdueReceivedReceived outside LODENot requiredNot received

The rules
Every status change writes an event row — nothing is silently marked received.
One stored document can satisfy many rows — never a duplicate upload.
“Not received” is logged, not final — a late warranty is still received, with the note on its event row.
Lien waivers run per-sub or as a G706A roll-up — never both per sub.
Warranty start dates default to the governing certificate date.

9.3 · Punch

Punch

Items belong to a walk — or are marked post-walk, like “owner move-in” — with a title, location, responsible company, photos, and an optional pin on a sheet. The List and the Map are the same list, two ways of looking at it.

Numbers are permanent and never reused. Removing an item requires a note, and the item stays on every issued revision.

OpenReady for reviewVerifiedRemoved

The contractor marks Ready for review; the architect verifies, or returns it with a required comment. A secure share link gives the contractor (or a view-only guest) their lane. Punch revisions snapshot the list as numbered issuances with record PDFs.

9.4 · Certificates

Certificates, two steps

Certify substantial completion. The scope (project or a designated portion), the date, the executed G704, and Exhibit A — a punch issuance whose snapshot count provably is the exhibit count. The correction period stamps at one year, and LODE offers to schedule the warranty walk about 11 months out. Phased projects carry multiple certificates, each with its own clock.

Certify final completion. The preconditions are shown plainly — N punch unresolved, N deliverables outstanding, N waivers outstanding. Certifying anyway never fakes the register clean: outstanding rows flip to “Not received” with logged events, snapshotted as Exhibit B.

Note

The executed paper is the record — LODE renders a summary above it, never an AIA facsimile.

9.5 · Closeout package

The closeout package (formerly Record set)

Copies, not pointers. Every document resolves to a concrete version, copied into a locked archive that no cleanup can touch — with a verification list that can prove no file has changed, and one zip of everything.

Re-issuing creates v2 alongside v1 — both retained, with the issuer’s note. A record set can never be deleted.

9.6 · After closeout

Cold storage

Archive project (in Settings) moves the project to cold storage: read-only, off the active-project count, and restorable when the owner calls three years later — with the closeout package and full history exactly where the project left them.

← Module 08 · Financials Module 10 · Projects & Teams →