Issuances and addenda
Upload the base set and each addendum as separate issuances and Struction keeps the lineage — which sheet supersedes which, what's current right now, and what changed from one version to the next.
Updated 5 minApplies to: MapFeedback →
What an issuance is
An issuance is one release of documents from the design team: the base package you bid from is an issuance, and each addendum, bulletin or revised set that follows is another. Struction keeps them in the issuance band above the project card, oldest first, and tracks each sheet across them, so it can tell you that FS01-01 has two versions and which one is current.
A reissued sheet is matched to its earlier version by its sheet number. Once it is, the map shows only the current version — the sheet count doesn't go up — and the older one stays available from the sheet's version controls.
Good to know — Don't delete the old sheet when a revision arrives. Add the revision as part of a new issuance instead — the superseded sheet is what Struction compares the new one against.
Upload issuances when you create the project
The create flow's documents step lays your files out in issuance columns, the same way the New issuance dialog does. Put the base set in the first column and each addendum in its own column after it. For each issuance you set:
- Set type — Conceptual Design, Schematic Design, Design Development, Construction Documents, Issued for Bid, Issued for Permit, Issued for Construction, Addendum, Bulletin or Record Set.
- Delivery — Full set, or Changed sheets only. Most addenda are changed sheets only: the sheets that aren't in it stay current without being reissued.
- Issued — the date the set was issued. It's required.
Upload every issuance, not just the latest. Struction can't show you what changed between two versions when it has only seen one of them.
Add documents as they arrive
When an addendum lands, click the + between the issuance cards (Add new set) and drop its files into the new column. To add a late sheet to an issuance that already exists, use that issuance's + (Add documents). Issuances already in the project are locked — their set type and date can't be changed in the dialog — so add them in issue order. See Upload for the dialog step by step.
Adding an addendum re-runs the project's processing, including scope generation. Watch the progress line on the new issuance's card. When it's done, the card's summary says what changed — for example 0 sheets changed · 1 not compared — and opens into a list of each document in the run, which you can search by sheet or title.
Pick the version you’re looking at
Zoom into a sheet that has more than one version and the bar across the top of the canvas lists its issued sets side by side — Issue for Bid, Addendum 1 — with the current one selected. Click a set to see that version on its own, or press its number key: 1 for the first set, 2 for the second, and so on. The breadcrumb says where you are — Map › Fire Protection › FS01-01 › Addendum 1 — and its last crumb is a menu of the same sets. A sheet that has only ever been issued once shows no version controls.

Compare: what changed
- Click Compare in the sheet's bar. It pairs the set you're on with the one issued just before it.
- The set buttons become a fade slider: the older set's name, the slider, the newer set's name. Slide it to fade between the two versions; hold B to flip to the older one for a moment.
- Change ink is drawn over the sheet: red is what was removed, green what was added and blue what moved.
- Click the ✕ on Compare to stop.

Not every pair can be compared. When Struction couldn't compare a sheet, the run summary says not compared and the bar says No change ink for these sets — the fade between the two versions still works. When it compared them and found nothing, the bar says No changes.
Sheets are compared as they're drawn, which can leave the two versions slightly out of line. The lock at the end of the slider lets you line them up by hand: open it, drag the drawing, then click Done (or Reset).
Spec sections that changed between issuances have their own Compare switch in the spec reader, with Removed and Added switches so you can read one side at a time.
What chat does with issuances
While you're comparing two sets of a sheet, chat knows which pair you're looking at, so a question like what changed here? is answered from the same two versions you see on screen. If there's no comparison for the pair, chat says so — I couldn't verify what changed … because the drawing comparison is unavailable — rather than telling you the sheet is unchanged.
What Compare doesn’t do
Compare tells you what changed; it doesn't decide what that means for your price. Scopes are regenerated after an addendum, but review the scopes that cite the reissued sheets yourself. Takeoffs and markups on a superseded sheet aren't carried onto its replacement.
Workflow example — Addendum 3 lands three days before bid with fourteen reissued structural sheets. You add it as a new issuance and wait for its card to finish. Then you open S2.01, click Compare, and read the green: two added grade beams and a thickened slab region. You measure the new beams on the current sheet, then check the red for anything you'd already priced that's gone.
More docs