User guide/Issuing Files
Module 02
Issuing Files
The core of the product: bringing an issuance into the record, confirming what LODE read, and setting it in stone. Every other module builds on this workflow.
2.1 · Starting
Starting an issuance
New issuance starts one of two ways:
Either way, you’re asked for a name (“ASI 03” — numbered kinds number themselves), a kind (ASI, Addendum, Bulletin, CCD, RFI Response, Permit/Bid/CD Set…), the issuance date, and three places to drop files: Drawings / Specs / Supplemental.
Issuing requires being assigned to the project, with upload rights (Owner or Admin).
2.2 · Upload rules
What LODE accepts
| Rule | Value |
|---|---|
| Format | PDF only — one multi-sheet PDF per issuance |
| File size | 500 MB per file |
| Pages | 1,000 for drawings · 10,000 for specs |
| Issuance date | Required — it decides which version is newest |
| Password-protected PDFs | Refused |
| Exact duplicates of a file already issued | Refused |
Up to three files upload at once. A dropped connection retries on its own, and refreshing the page won’t lose progress.
2.3 · Title blocks
Title block regions
Drag boxes over the title block for Sheet Number (required), Sheet Title, and Sheet Index — the index is an advisory cross-check only; it never overrides what’s on the sheet. Then: “Lode it”.
Tip
2.4 · Processing
What happens after “Lode it”
The PDF splits into sheets. If the file carries its own sheet labels and bookmarks, LODE reads those — near-instant. Otherwise LODE reads the sheet number and title straight off each title block: “Digging deeper to verify sheet names… 42 of 259 verified.”
Two prompts can appear mid-process:
2.5 · Batch Review
Confirming the read
Each sheet card shows its number, title, and discipline, how confident LODE is in the read, exactly what it read off the sheet, and the revision chain.
Flag chips mark what needs a look:
The workflow:
If the read went wrong across many sheets: redraw the title block regions and “Re-run sheet read” — never fix sheet-by-sheet.
Caution
2.6 · Set in Stone
What Set in Stone does
Incoming sheets match against the current set. Matched sheets supersede their prior versions — kept in history. Unmatched sheets insert as new, in correct order; A201A never collides with A201. Every output set updates on its own.
Afterward: Files › Index (rename with conflict checks, void and reinstate with a reason), Files › Revision Log, and the viewer — Compare shows prior vs current zoomed in lockstep, with the differences highlighted.
2.7 · Outputs
Outputs & sharing
| Output | What it is |
|---|---|
| Field Set | The current set, one clean PDF. |
| Combined Set | All scopes merged. |
| Revision Record Set | Full history, superseded and voided sheets stamped. |
| Sheet Index | The authoritative list of what’s current. |
| Field Specs / Spec Index | The same outputs for specifications. |
“Send” is a transmittal — opens and downloads are logged. Share links are revocable. The Document Compiler combines PDFs into one file, ready to issue.
2.8 · Troubleshooting
When something looks wrong
| Symptom | What to do |
|---|---|
| File won’t upload | Check PDF format, 500 MB, 1,000 pages, password protection. |
| UNCLASSIFIED sheets | Set title block regions, re-scan. |
| Wrong titles across many sheets | Redraw regions and re-run the sheet read — not sheet-by-sheet. |
| Index mismatch | Keep or Use index — the index is advisory only. |
| Issued in the wrong order | Nothing to fix — issuance dates decide. |
| Misfiled after finalizing | Files › Index rename or void — every change is logged. |