Features/Construction Administration
Construction Administration
Who has it, and for how long.
CA is where projects drown: RFIs in one inbox, submittals in another, and the answer to “who’s holding this up?” costing a meeting to reconstruct. In LODE, every CA record is born on the project record — an RFI cites the sheet and revision it questions, the submittal register writes itself from your specs, and the ball-in-court is always visible, with a clock on it.
This is a tab on every LODE project, not a separate product. Construction Administration runs on the same record the drawings live on — nothing is exported to it, nothing drifts from it.
RFIs that cite their sheets
Dual numbering, typed questions — clarification, reference with a sheet chip, sketch — and hop-by-hop routing. Reopen keeps the same record, appends the exchange, and restarts the clock.
Ball-in-court, with a clock
Multi-party routing tracks exactly who holds each record and for how long — per hop, not per record. The question that used to cost a meeting is a column.
Submittals from your specs
The register seeds itself from your CSI spec sections — nothing to type, nothing to forget. Full lifecycle from submission to approval, with response packages intaken to the record. With DOC on, DOC Review takes the first pass.
Observations, for the record
Field observations with upload-for-record — what was seen, when, by whom, filed where the project can find it again.
Revisions as CA records
ASIs and bulletins are managed as CA records and flow into the same revision engine that compiles the set — the drawing change and its paper trail are one thing.
The contractor portal
Your GC works the record by link — no seat, no account. Responses and submittals land directly on the project. Notifications stay in-app; LODE never blasts inboxes.
The register writes itself.
A submittal log is usually a spreadsheet somebody builds by reading the specs line by line — and it goes stale the day the first addendum lands. LODE generates the register from the spec sections it already compiled, keeps it pointed at the current revision of every section, and walks each submittal through its lifecycle on the record.
- Seeded from Division sections — the log exists before the first submittal arrives
- Every submittal knows its spec section, and every section knows its current revision
- Response packages are intaken to the record, not attached to an email
- Approved submittals seed the closeout deliverables register automatically
CA without the archaeology.
We'll be in touch when early access opens.