How to pick
- Start with a task that happens every week, follows clear rules and annoys more than one person.
- Time it once by hand. That number tells you what a tool is worth (try the payback calculator).
- Prefer tasks that read the model and write files. Tasks that change the model need a preview and a log.
1. Creating sheets and placing views
Making dozens of sheets, setting title block fields and dropping the right plan on each is a job for a sheet list in Excel plus a tool that builds everything from it. On data center projects that means one set of sheets per hall, per building. Fits: Dynamo for one-off sets; a C# add-in when it runs on every project. Try the sheet list demo.
2. Creating views from a template
Plans, enlarged plans, sections and 3D views per level, area or hall, each with the right view template, scope box and name. Fits: pyRevit or Dynamo for simple rules; an add-in when names and templates follow a company standard.
3. Renumbering
Sheets, rooms, doors, grids and equipment drift out of order with every change. A renumber tool follows a path or a rule, for example racks by hall, row and position (DH1-A-03). Fits: pyRevit for a toolbar button; an add-in when the numbering scheme feeds other systems. See the rack ID demo.
4. Batch PDF, DWG, IFC and NWC exports
Weekly sets and coordination files across many models are the classic overnight job. Fits: a batch add-in or cloud job. Details on batch and overnight automation.
5. Schedules and parameters to and from Excel
Export a schedule, let someone fill in data in Excel, then write it back to the model with a preview of what changes. Fits: Dynamo for a single schedule; an add-in for round trips with checks and a change log.
6. Filling and checking parameters
Empty asset IDs, mismatched feed fields and inconsistent names break schedules, handover data and any AI assistant reading the model. A checker that lists problems, then a fixer that applies rules, saves days at handover. Fits: an add-in; start with a model health check.
7. Tagging
Tagging every rack, panel or piece of equipment in every view, without overlaps, is slow by hand. Fits: pyRevit or an add-in with your tag families and offsets.
8. Cleaning up warnings
Duplicate instances, overlapping elements and room separation issues pile up. Some can be fixed by rule, others need a person, but a tool can sort and report them so the team works the list. Fits: an add-in report, run weekly.
9. Family and content audits
Which families are unused, in-place, oversized or off-standard. A weekly report keeps models small and libraries clean. Fits: pyRevit or a batch add-in.
10. Model checks before every issue
Before a milestone, run the same checks every time: naming, parameters, view templates, linked models, data center rules such as A/B feed separation. Fits: an add-in that writes an Excel issue list, or a custom tool an AI assistant can call. See AI for Revit.
Dynamo, pyRevit or C#?
| Tool | Best for | Watch out for |
|---|---|---|
| Dynamo | Visual scripts your team may edit, one model at a time, Dynamo Player | Dynamo 4.0 made PythonNet3 the default Python engine, so older graphs may need changes |
| pyRevit | Quick toolbar buttons and company toolbars in Python | Open source under GPL-3.0; needs pyRevit installed on each machine |
| C# add-in | Tools used daily, batch work, windows, installers, version control | One build per .NET runtime; see Revit 2027 migration |
More detail in Dynamo vs pyRevit vs C# add-ins.
Where to start
Pick one task from this list, time it, and run a fixed-price pilot: $750 to $1,500, about 1 to 2 weeks, with a written acceptance test on your Revit version. If the pilot doesn't pass the written acceptance test on the agreed Revit version, we fix it at no charge. If it still doesn't pass within 10 business days of your test report, we refund the pilot fee in full. This doesn't cover changes to the scope, the test model or the Revit version after the scope is signed.
Revit LT doesn't run add-ins or Dynamo; these tools need full Revit or the AEC Collection.