Features/Closeout
Closeout
The end of the job starts in the middle.
Closeout fails when it starts at the end — a punch list built from memory and a deliverables chase through a year of email. In LODE, closeout has been accumulating all along: every approved submittal already knows what it owes the record, every punch item is a pin on the sheet it lives on, and the final record set compiles from everything the project produced.
This is a tab on every LODE project, not a separate product. Closeout runs on the same record the drawings live on — nothing is exported to it, nothing drifts from it.
Punch, on the plan
Every punch item is a pin on the sheet it lives on — located, statused, verified. The list and the map are the same thing, so nothing gets walked twice or found never.
Walk-throughs by link
Hand the walk to a sub or an owner’s rep as a token link — no seat, no account. Items update from the field, and the record keeps who verified what.
Deliverables, pre-seeded
The register seeds from approved submittals mid-construction — O&M manuals, warranties, as-builts. By the time anyone says “closeout,” the list already exists.
Certificates on the record
The executed paper is the record — certificates live as documents with a summary rendered above them, never retyped into a system that could drift from the signature.
The final record set
The compiled end-state of everything the project produced: current drawings and specs, the revision record, the registers. The set you hand over, and the one you keep.
Then, cold storage
A finished project doesn’t need an active slot. Move it to cold storage — included in every plan — and the whole record stays: drawings, registers, history. A cold project takes no project slot and counts at a quarter of its size against storage. Bring it back whenever the job comes back.
Closeout that assembled itself.
The deliverables chase is the worst archaeology in construction: a year later, someone greps an inbox for a warranty. LODE inverts it — the moment a submittal is approved during CA, its closeout obligations are seeded into the deliverables register. The end of the job is a checklist that has been quietly writing itself since the middle.
- Seeded from approved submittals — the register exists before closeout begins
- Each deliverable traces to the submittal, spec section, and approval behind it
- Outstanding items are visible all through construction, not discovered at the end
- The final record set closes the loop the first issuance opened
Finish the way you started: on the record.
We'll be in touch when early access opens.