Revit batch exports and overnight automation
Sheet sets, coordination files, data exports and model audits that someone on your team runs by hand every week. We build tools that open each Autodesk® Revit® model, do the job and log the result, so the files are ready in the morning.
Jobs that are safe to batch.
The safest jobs to run unattended read the model and write files. Jobs that change the model can be batched too, with a preview, backups and a log.
PDF sheet sets
Weekly review sets and milestone issues from a saved sheet list, named to your standard, across every model in a project.
DWG, IFC and NWC
Consultant and coordination exports with your export settings, dropped in the right folder with the date in the name.
Excel and Power BI data
Schedules, parameters and asset lists to Excel or a database, so dashboards refresh without anyone opening Revit.
Model audits
Warnings, file size, in-place families, imported CAD and naming checks, written to one report per model.
Upgrade and compact
Open a folder of old models in the new Revit version, audit, compact and save, with a list of any that failed.
Bulk parameter updates
Set or fix parameters across many models from a spreadsheet. Runs only after a preview and with backups, because it changes model data.
On your computer, or in the cloud.
Desktop batch tool
A Revit add-in or pyRevit command that works through a list of models on a workstation, for example after hours. It uses your own Revit licenses and your network folders.
- No cloud fees
- Works with models on your network or synced from the cloud
- Simple to run: pick a list, press start, read the log
Cloud jobs with Autodesk Platform Services
For models in Autodesk Forma (formerly Autodesk Construction Cloud), Design Automation for Revit can run the same job on Autodesk servers, with no workstation left on.
- Since December 8, 2025 some Autodesk Platform Services (APS) APIs are metered: a free monthly tier, then Autodesk Flex tokens, billed by Autodesk to your account.
- We estimate the usage before we build.
Built to be trusted while nobody is watching.
- Every run writes a log: which model, what was exported, how long it took, what failed and why
- One failed model doesn't stop the rest of the batch
- File names and folders follow your standard, set in a settings file you can edit
- Model changes run inside Revit transactions, with a preview first and backups before a batch
- Tested on sample models and a copy of yours, on each Revit version you name
- No telemetry, no license server, full source code handed over
| Option | What it covers | Price (USD) | Estimated time |
|---|---|---|---|
| Pilot | One batch job, for example weekly PDF sets for one project, with a written acceptance test | $750–$1,500 | 1–2 weeks |
| Batch tool | Several jobs, a settings file, a schedule and a log viewer, built as an add-in for your Revit versions | $4,000–$15,000 | 2–8 weeks |
| Retainer | New jobs and fixes each month from an hours bank | $2,000–$4,000 a month | ongoing |
Prices exclude any applicable taxes. Needs full Autodesk Revit or the AEC Collection; Revit LT doesn't run add-ins.
Batch automation FAQ
Doesn't Revit already batch print?
Revit can print and export sets from one open model. A batch tool works across many models, names and files the results to your standard, keeps going when one model fails, and records what happened.
Can it run while we sleep?
Yes. A desktop tool can start from Windows Task Scheduler on a workstation that stays signed in, or the job can run in the cloud with Design Automation for Revit.
We already use Dynamo for this. Why change?
If a Dynamo graph works for one model, keep it. Batch work across many models is where an add-in is more reliable. See Dynamo vs pyRevit vs C#.
Have a Revit task your team repeats every week?
Tell us about it. Within 2 business days of the call you get a written scope with a fixed price for a pilot or first phase, and an estimate range for anything bigger. No obligation.