BIM Publisher

BIM Publisher exports the views and sheets of a Revit project in bulk, to any of twelve formats in a single run. Drawings go out as PDF, DWG, DXF, DGN, DWF/DWFx or images; 3D views as IFC, NWC, FBX, OBJ, STL or 3D PDF. PDF goes through Revit's own native exporter, so there is no virtual printer to install and no print driver to configure. You choose what to send in a grid that shows the parameters you care about — add a column for any parameter in the model, group by discipline, filter by revision, or load one of Revit's own sheet sets. Every file is named by a rule you build once, from blocks rather than codes: any sheet, view or project parameter, plus the date, the user, the model and the revision, with date formats, counters, case conversion, and blocks that drop out cleanly when their value is empty — so a sheet with no revision yet gives a clean name instead of one ending in a stray dash. If you would rather not build it at all, type the file name you want for one sheet and Name by example works the rule out for you. The resulting filename is shown on every row as you type, not on a single sample, so the twelve sheets whose rule collapses into one name are visible before you export rather than after. Two rows heading for the same path are flagged in the grid the moment they appear, and the collision policy — overwrite, skip, version or refuse — applies across the whole plan rather than folder by folder. Nothing is written until pre-flight has run. It checks the things that actually go wrong on a real issue: duplicate filenames, a path over the Windows limit, a placeholder sheet, a missing title block, a parameter used in the name that is blank on nine sheets, a destination that is unreachable or read-only, not enough disk space, and a workshared model with changes that have not been synchronised. Blocking problems stop the export; warnings need one acknowledgement. Preview files writes nothing at all and lists every path the run would produce. During the export the window stays responsive, progress is reported per file, and Stop finishes the file in progress and leaves everything already written in place. Afterwards you get an XLSX and CSV report listing every file with its size and duration, including the ones that were deliberately skipped and why — because the question people actually bring to a batch exporter is why a particular sheet is not in the package. Beyond exporting, BIM Publisher keeps a record of what you sent. Recording an issue writes a dated, append-only entry to a register that lives beside the model, holding the sheet numbers, revisions and a SHA-256 checksum of every file that went out, with a formal PDF transmittal by default and an Excel schedule or CSV data copy when you need one. From then on the grid can show what is new or revised since any past issue, and one click selects exactly those sheets, so a re-issue contains what changed rather than everything. Combined PDFs can carry bookmarks nested by discipline and a generated drawing list as page one, every PDF can take a stamp and searchable document properties, and the finished set can be zipped, mirrored to a second destination, or handed to a script. Export configurations save as readable presets, and a read-only shared folder of them is how a whole team works the same way from the day they install it. Nothing phones home: no licence check, no telemetry, and no internet connection is ever required. Full installation and step-by-step instructions are in the Documentation tab.