Revit prints files and forgets them. Plot publishes the pack — every file named to your convention, checked before it leaves, written one at a time while Revit stays responsive, and recorded in the model, with a transmittal beside the files, so “what did we send, and to whom?” always has an answer.
Issue day from Revit alone is renamed files, a zip built by hand, and an email as the only record of what left the office.
Plot writes files and one record of having written them. It never synchronises with central; when the model is busy, the record queues politely and waits.
The picker filters by Print Set or search — and Plot's Sets ▾ button remembers reusable selections, Tender or As-built. A Changed since last issue chip shows only the sheets that are new or whose revision moved since the last recorded emission. And a sheet that cannot publish — no title block, empty, a placeholder — wears a red Blocked badge before it ever enters the selection, painted over New, because a blocked sheet keeping a “New” promise would be a false one.
Drag sheet, view and title-block fields into a name structure. Each chip carries its own prefix and suffix — printed only when the field has a value, so an empty field takes its separator with it — and a transform: UPPERCASE, zero-pad, date. The preview updates live. Save the structure into the model for the team, keep office standards per client, round-trip awkward names through Excel, and sort the output into per-token sub-folders like {Current Revision}/{Sheet Number}.
P-2201-A-101-C03 - Ground Floor Plan.pdfNine formats sit in one list, and picking one swaps the controls beside it. PDF brings Colour, Greyscale or Black & white, four raster qualities, and three switches for what a Revit PDF normally leaks: crop rectangles, scope boxes, and the section tags pointing at a view that is on no sheet. DWG and DXF take a named export setup — layer mapping and CAD version. Print takes a printer and a Revit print setting. PNG takes a long-edge size.
Publish writes one item per call, so Revit never freezes and the counter never lies. Each row flips live to ✓ written, ⚠ written with a warning — a stamp that failed to apply is never silent green — or ✗ failed with the reason; Cancel is live, and Retry failed re-runs exactly what failed. Check standards tests the pack against Canon on demand — never automatically — and Block non-compliant refuses to emit what that test flagged, including what it could not check. On Revit 2025 and newer, a Background PDF switch hands the jobs to Revit's worker process and gives you Revit back in seconds.
Press Publish and, before the first file, Plot asks Dictum what this pack still owes: which of the sheets about to leave carry a decision nobody has recorded, with the sheet, the decision's code, what it says, and a badge — BLOCKS ISSUE, COST, PROGRAMME or MINOR. Blocking findings are counted apart from merely outstanding ones. Publish anyway is the primary button and Enter is bound to nothing, so the pack goes out one deliberate click later. With nothing to say, it never opens.
You can publish anyway — this never stops a delivery. What it stops is publishing without knowing.
Pick a 3D view and answer one question — coordination, handover, quantity take-off, a lightweight viewer, energy — and schema, property sets, detail, position and links are set at once, every option explained in plain words with its consequence underneath. A view check reads the section box, hidden categories, unloaded links, closed worksets and the shared site before the file is written; and the class mapper shows what every Revit category becomes in IFC — then stamps the applied mapping into the model, so drift gets caught next time.
Scan the model and six numbers land: elements, proxies now → with standard, not exported now → with, re-classed by rules, manual overrides in model, problems. The proxy pair is the one reviewers read first. Pick a category to set what it becomes in IFC2x3, IFC4 or IFC4.3, then add the rules Revit's own mapper cannot express — by family name, type name, family or type, or a parameter. Apply to model writes the classes onto the types in one transaction; Show me selects whatever drifted.
What every Revit category becomes in IFC — and why. Nothing is written until you apply.
Every emission is recorded in the model itself — issue label, folder, format, per-sheet revisions and their Canon standing — and the run writes a transmittal in CSV and HTML stating the purpose (from a closed list, so it can be audited) and the recipient, with each file's weight, so a zero-byte file betrays itself unopened. If a borrowed model refuses the write, the emission queues and a banner offers Record now — nothing is lost, and nothing ever synchronises. History reopens any past package: export the register, reissue the exact set, or jump into the comparator against where it landed.
Combine PDF writes the whole set as one document, in the order of the list, with a bookmark per sheet and a cover index page; + individual sheets keeps the loose files beside it, which is what the archive and the next comparison need. Sub-folder sorts the output by any field, so {Current Revision} splits the pack per revision. Zip the delivery packs those files, their sub-folders and both transmittals into one archive named after the issue — written last, after the watermark and the bookmarks, so nothing goes in half-made.
Every per-sheet PDF Plot writes carries the sheet's identity embedded in its metadata, so the comparator matches this issue to the last exactly — surviving renames and renumbers, and falling back to the sheet number for PDFs from any other tool. Drag the curtain across a sheet, zoom into a detail, step through the pack — and the matcher also says what the previous delivery had that this one doesn't.
A governed emission is only governed if there is a record of it. Plot writes every publish into the model itself, so the audit trail travels with the file rather than living in somebody's folder. From there the register exports as a CSV to send or file with the project; any past emission can be compared visually against what is in the model now; and one can be loaded back as the current selection to re-publish at today's revisions — which is exactly what a reissue is, and exactly the thing that is otherwise reconstructed by hand from an email.
This is an actual HTML report Plot exports — self-contained, works offline, shareable as one file. Scroll it right here, or open it full-screen.
Plot ships on the Sheets panel of the BIMIO tab. Pick the set, name it once, and publish with the record written. Revit 2024–2027, full trial, no card.