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.pdfPublish 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.
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.
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.
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.
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.