How BIM Managers Can Standardize Weekly Revit Publishing With Scheduled Tasks

Every project team has a weekly publishing ritual. Someone opens the model, picks a sheet set, checks the PDF setup, exports, renames, moves files into the right folder, then does it all again for DWG, IFC and NWC. When it works, nobody notices. When it doesn’t (a sheet missing from the set, an IFC exported with last month’s settings, a file named to a convention nobody else uses), the problem surfaces at the worst possible moment: in front of the client or the coordination team.

For BIM managers, the issue isn’t that publishing is hard. It’s that it’s done slightly differently by every person, on every project, every week. Scheduled tasks fix that by moving the “how” out of individual habits and into a defined, repeatable routine, and publishing is one of the areas where automation saves BIM teams the most time. This article walks through how to set that up with Ideate Automation.

Why weekly publishing drifts

Manual publishing drifts predictably. Revit sheet sets are static, so a new sheet added on Wednesday is silently left out on Friday unless someone remembers to update the set. Export setups live in individual models and can be changed by anyone. File naming depends on whoever runs the export. And when the person who “knows how the Friday issue works” is on holiday, the process often lives only in their head.

Standardization means agreeing on what gets published, where it goes, what it’s called, and when it runs, and then removing as many manual decisions from that chain as possible.

Step 1: Define the publishing package once

Start by turning your weekly issue into a defined set of outputs. Ideate Automation ships with ready-made publishing scripts for PDF (combined or individual), DWG, IFC and NWC, plus a script that publishes cloud models to BIM 360/ACC. Each task is built from a script and a set of variables you fill in once: which models, which sheets, which export setup, where the output goes.

A few choices make the biggest difference to consistency:

• Use dynamic sheet lists instead of static sheet sets. With Ideate BIMLink, you can define the sheets to publish by rule, for example every sheet in a given revision, or every sheet with a number starting “A1”. When a new sheet matches the rule, it is automatically included in the next run. Nobody has to edit a sheet set.
• Keep IFC settings outside the model. The IFC export script can read a JSON setup file stored in a shared location, so every model and user exports with the same settings. Our guide to automating IFC export from Revit covers the setup in detail.
• Fix the naming and folder logic. Output names and folders can be built from variables such as the date (for example, a ${today.yyyyMMdd} prefix for an archive copy) or Revit Project Information parameters. Graitec’s guide to using Project Information parameters for export folders shows how each model can send its outputs to its own folder automatically. For standards such as ISO 19650 drawing numbers, Ideate ReNumber rules can drive the file names.

If you’re on the Ideate Software Bundle or an Enterprise subscription, the June 2026 release (3.6) adds Ideate ExportHub: a single HUB-Export_Package script where naming rules, file paths and export settings are set in ExportHub rather than in the task, with support for extra formats such as DXF, DWF/DWFx, FBX and images.

Step 2: Point tasks at a file list, not hand-picked models

Rather than selecting models inside each task, generate a Revit file list with the AUT-Generate_Revit_File_List script and point your publishing tasks at it. This has three practical benefits for a weekly routine:

1. Every task (PDF, DWG, IFC, NWC) publishes exactly the same set of models.
2. When a model is added to the project, you update one text file instead of editing every scheduled task.
3. File lists avoid the roughly 100-file limit that applies when models are picked manually in a task.

Step 3: Schedule it

Once a task has run successfully, scheduling it is straightforward: select the completed task on the Home page, choose Schedule, give it a clear name and description, and set the trigger. The Weekly option lets you pick only the days you need, so a Thursday-night export ahead of a Friday issue is easy to set up.

Two points to plan for:

• Name scheduled tasks carefully. The scheduled task name can’t be edited later, so agree on a naming convention (project, output, frequency) before you start.
• Keep the machine available. Scheduled tasks run under the user’s Windows credentials. They will wake a computer that is locked or asleep, but not one that has been shut down or logged out. Ideate recommends a dedicated machine for regularly scheduled tasks, with sleep set to “Never”.

For cloud projects, the AUT-AdskCloud-Publish_Model script can publish models to BIM 360/ACC on a schedule without Design Collaboration or Cloud Credits. A “Completed” status doesn’t always mean a new version was published: if nothing changed since the last publish, no new version is created, which avoids unnecessary traffic on the hub.

Step 4: Share the standard across the team

A standard only works if everyone uses it. Ideate Automation supports this in several ways:

• Export and import tasks. Scheduled tasks can be exported as .xml files and imported by colleagues, so one well-configured task can be reused across projects.
• Centralize scripts. Library paths can point to a shared network folder, and the settings file can be pushed to users via group policy.
• Lock down what shouldn’t change. In custom scripts, variables can be moved to Additional Options or hidden completely. If your PDF naming is standardized, there’s no reason for users to see, or change, that field.

Step 5: Review, don’t re-run

With scheduling, human time shifts from producing outputs to checking them. Each run is listed with its status (Completed, Completed with errors, Failed), duration and a log. Show Details jumps straight to the primary error in the log, so a Monday check takes minutes rather than a rerun of the whole package.

The same scheduled approach works for checks as well as outputs, such as a weekly model health check report. HKR Architects, for example, schedules model audits over the weekend and reviews the results in a Power BI dashboard on Monday morning.

An example of how to standardize weekly Revit publishing with scheduled tasks

Adapt the timing to your issue day and project size. Long-running exports are good candidates for overnight automation.

Keeping the standard intact after upgrades

After a Revit version upgrade, scheduled tasks need attention. Upgrade and publish the models, refresh the file list in Ideate Automation, update the year in any .txt file lists, then re-schedule the existing tasks. The recommended route is to clone the scheduled task, schedule the clone and remove the old one. Ideate Automation supports the current Revit version plus the three previous ones, and from version 3.6 previously run tasks on the Home page are upgraded automatically.

Conclusion: define it once, schedule it, review it

Weekly publishing will always need a BIM manager’s judgment on what goes out the door. What it shouldn’t need is someone repeating the same clicks every Friday. A standardized, scheduled routine gives you:

• The same outputs every week, built from dynamic sheet lists and shared export settings rather than individual habits.
• Consistent naming and folders, driven by rules instead of whoever ran the export.
• A process the whole team can use, shared as tasks and scripts rather than knowledge in one person’s head.
• Time spent reviewing, not producing, with status and logs showing exactly what needs attention.

Start small: one project, one output (usually the weekly PDF set). Run it manually, compare it with your usual export, then schedule it. Once it’s reliable, add DWG, IFC and NWC and roll it out to other projects.

For more background, see Graitec’s guide to Revit automation and scheduled workflows and the resource on automating PDF, NWC, IFC and DWG exports.