Features/Planning
Planning
One schedule for design and construction.
Design has a schedule, construction has a schedule, and they usually live in different files owned by different people. LODE keeps one for both, in the project, so a milestone is not a bar on a chart. It is confirmed against what was actually issued.
A design and construction schedule in LODE lives in the project, next to the drawings it schedules. A milestone turns green when the issuance behind it exists, not when someone drags a bar.
Last updated
Planning is a tab on every LODE project, not a separate product. It works from the same drawing set, so nothing has to be exported to it.
How does LODE schedule design and construction?
SD through closeout on one timeline, in the project. Key milestones are confirmed deliberately against the documents. QA/QC reviews, site walks and deadlines go on the same calendar with the people attached. The Hub rolls every project's schedule into one firm view, so the crunches show before they land on the same week.
Design and construction, together
SD through closeout on one timeline. Going from design to construction is a scroll, not a change of software.
In the project, next to the drawings
The schedule lives in the project, next to the documents it schedules. When the CD set is issued, the timeline knows, because the issuance is the evidence.
Checkpoints, confirmed
Key milestones are confirmed deliberately. 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, on the same timeline, not in a spreadsheet on the side.
Events and milestones
Add reviews, deadlines and site walks with the people involved attached to the entry.
The firm view
The Hub rolls every project’s schedule up into one firm view, so you see the crunches before they land on the same week.
A milestone means the issuance exists.
Why does a milestone depend on an issuance?
Every schedule slips the same way: the bar chart says one thing, the documents say another, and nobody reconciles them until the argument. Here a milestone is confirmed against the project, so the timeline and the documents agree. When the date turns green, the issuance behind it exists.
- Milestones confirmed deliberately, with a decision written down
- A milestone is met by an issuance the project can show
- Slips are visible early, because the timeline reads the same documents you do
- Design and construction on one schedule, with nothing re-entered between phases
Satisfied by the CD Set issuance — the date and the documents agree
Who is Planning for?
The architect's project lead and the firm's principals. The project view keeps the timeline honest against the documents; the firm view in the Hub shows every project's dates together.
Frequently asked questions
Is this a Gantt chart?
It is one timeline for design and construction with milestones, events and reviews on it. The difference is that a milestone is confirmed against the project's documents rather than dragged.
Can the schedule cover design phases as well as construction?
Yes. SD through closeout sits on one timeline, so moving from design to construction is a scroll, not a change of software.
Who can see the schedule?
Everyone on the project. The firm-wide view in the Hub is for the firm's members and rolls every project's schedule into one.
Can I put QA/QC reviews on it?
Yes. Quality reviews are scheduled like the work they check, on the same timeline, with the people involved attached to the entry.
Does the schedule import from other tools?
Not today. Milestones, events and reviews are entered in LODE, where the issuances that confirm them already are.
Keep the schedule next to the drawings.
We'll be in touch when early access opens.