Features/Planning

Planning

One timeline, and it can’t lie.

Design has a schedule, construction has a schedule, and they usually live in different files owned by different people. LODE keeps one timeline for both — and because it lives on the record, its milestones aren’t promises on a bar chart. They’re checkpoints, confirmed against what the record actually shows.

Project Scheduledesign + construction
DD completeNov 14
CD set issuedFeb 02
GMP executedMar 21
Structure top-outJun 30
Substantial completionDec 12
DashboardFilesPlanningBiddingCAFinancialsCloseoutLODE

This is a tab on every LODE project, not a separate product. Planning runs on the same record the drawings live on — nothing is exported to it, nothing drifts from it.

Design and construction, together

SD through closeout on one timeline. The handoff from drawing to building isn’t a change of software — it’s a scroll.

On the record, not beside it

The schedule lives in the project, next to the documents it schedules. When the CD set issues, the timeline knows — because the issuance is the evidence.

Checkpoints, confirmed

Key milestones are confirmed deliberately, against the record — a date turns green because the thing happened, not because someone dragged a bar.

QAQC on the calendar

Quality reviews scheduled like the work they check — a layer on the same timeline, not a spreadsheet someone maintains on the side.

Events and milestones

Add what matters — reviews, deadlines, site walks — with the project’s parties attached, so who’s involved is part of the entry.

The firm view

The Hub rolls every project’s schedule up to one firm-level view — where the crunches collide, before they collide.

A milestone is evidence, not a promise.

Every schedule slips the same way: the bar chart says one thing, the documents say another, and nobody reconciles them until the argument. LODE’s checkpoints close that gap — a milestone is confirmed against the record, so the timeline and the truth are the same surface. When the date turns green, the issuance behind it exists.

  • Checkpoints confirmed deliberately — a dialog, a decision, a record
  • Milestones satisfied by issuances the record can show
  • Slips visible early, because the timeline reads the same record you do
  • Design and construction share the arc — no re-keying between phases
Checkpointconfirmed against the record
CD set issuedFeb 02

Satisfied by the CD Set issuance — the date and the documents agree

A milestone isn't a promise on a bar chart — it's confirmed against what the record shows

Put the schedule where the truth is.

We'll be in touch when early access opens.