Someone on your project is working from the wrong drawing.
LODE compiles the current drawing set from every issuance you bring in, keeps the history, and keeps it ready to download. Then the rest of the project runs on that set: bidding, construction administration, financials and closeout, with everyone looking at the same sheets.
ASI 03 affects 6 sheets. Three revisions concentrate around the north stair assembly. One new sheet added: A201A.
Missing a revision costs more than you think.
70%
Of construction rework starts in the drawings, not in the field.
Autodesk / Quality
48%
Of rework comes down to bad data and missed communication: the right version never reached the right person.
PlanGrid / FMI
5.5 hrs
Lost every week looking for current drawings and project information.
PlanGrid / FMI
$177B
Spent every year in U.S. construction on rework, disputes and hunting for information.
PlanGrid / FMI
Most of it is avoidable. The drawings existed. The revision was issued. Someone just did not have the current set.
How it happens.
The Field Superintendent
The crew builds the north stair to the bid set. ASI 02 moved it eight inches. The revision was issued; it never made it past an email thread. The architect points at the revised drawings. The super never had them.
Rework in the tens of thousands. Days of delay.
The Project Manager
Six people in a coordination meeting argue about a detail Bulletin 3 already settled. Two hours on a question answered six weeks ago, because nobody in the room had the current set.
Hours of billable time. Zero progress.
The Architect
An RFI arrives about a condition ASI 01 addressed months ago. The contractor is three months into construction and still working from the bid set. Now it is a credibility problem as well as a drawing problem.
Client frustration. Another RFI. The log grows.
The whole project in one place.
A CA platform here, a markup app there, a whiteboard somewhere else, and the project falls through the gaps between them. LODE keeps every phase on the same drawing set, from the first trace on Sketch Paper to the closeout set. This is the navigation of a LODE project:
How it works.
Upload each issuance
The bid set first, then every revision as it goes out. Drop in the PDF, drawings or specs.
LODE compiles the current set
It reads the sheet numbers, works out which revision of each sheet is current, and keeps the cross-references pointed at the right sheets. Spec sections get the same treatment.
Run the project on it
A Field Set for the crew. A Revision Record Set for the file. RFIs, submittals and pay apps that name the sheets they are about.
Live Review
One review, not five copies to merge.
Usually each reviewer marks up their own copy and someone merges them afterwards. In LODE every markup lands on the same sheet as it is made, so there is one set of comments, current at all times, and nothing to collect.
Everyone works on the same sheet, together or at different times. When you overlap, you see each other’s cursors.
Comments are resolved where they were made, with a name, a time and the revision they were made on.
Reviewers join from a link. A consultant marking up one package does not need a seat.
Mark it up, measure it, count it.
Once the set is compiled, your team marks it up, measures off it and works through what changed. All of it sits on a separate layer; the source PDFs are never touched.
Comments and threads
Open and resolved discussions, pinned to the sheet they are about.
Measure and count
Calibrated lengths and areas, and a count tool. The numbers carry forward when a sheet is revised.
Revisions keep your markups
When a sheet is superseded, you choose which comments move to the new sheet and which stay with the old one.
Sketch Paper
Trace paper, with the drawings underneath.
Every project gets an infinite canvas for the thinking that starts before the first issuance and never really stops. Lay trace over any sheet, draw on it, stack trace on trace, fan the stack out to compare options. Others can be on the same canvas with you.
A sheet you place stays pinned to the version you dropped, and tells you when a revision supersedes it. When something is worth keeping, save it to Files and it becomes part of the project.
DOC, the assistant.
DOC reads your project and answers in plain language. Ask what changed in an issuance, ask about a sheet or part of one, ask about a spec section, or ask where that material decision from a year ago ended up. It only reads what you let it read.
ASI 03 affects 6 sheets. Three revisions concentrate around the north stair assembly, including a revised guardrail condition on A201 and a new enlarged plan on A201A. The roof assembly on A301 has been updated — this sheet has been revised in 3 of 4 issuances to date.
No sheets were removed. One sheet added.
DOC is off by default and turned on per project. Everything else works without it, and your drawings are never used to train a model.
Your documents are yours.
We claim no rights to your files. Download everything, any time.
Delete everything, any time, permanently.
Your drawings are never shared or sold.
Processed to compile the set. Never used for training.
AI is optional. Everything works without it. Turn DOC on per project if you want it.
Winding down? Keep every drawing in cold storage from $9/mo and pick up again when you are ready.
We make money when you subscribe, and from nothing else.
What changes.
Not a feature checklist against one product. This is against the way document control is done today: inboxes, shared drives, per-seat platforms and a coordinator holding it together by hand.
| Others | LODE | |
|---|---|---|
| The project | A different tool for every phase, and gaps between them | One place, first sketch to closeout |
| The current set | Whoever kept the latest email attachment | Compiled from every issuance, automatically |
| Revision history | Overwritten files and renamed PDFs | Every issuance kept. Rebuild the set as it stood on any date |
| Markups | Flattened into the file, or lost with it | A separate layer, tied to the sheet and revision it was made on |
| Design review | Rounds of markups, merged by hand | Everyone marks up the same sheet, live |
| RFIs, submittals, pay apps | Scattered across inboxes, spreadsheets, and PDFs | Logs in the project, linked to the sheets they refer to |
| Subs & consultants | A seat for everyone, or nothing | A link and a portal. No seat |
| Your files | Check the terms | Yours. Download or delete everything, any time |
| AI on your drawings | Check the terms | Off by default, per-project opt-in, never trained on |
| Buying it | Per-seat, per-module, ask for a quote | A subscription |
Put your next drawing set through it.
We'll be in touch when early access opens.