CodedConstructs
← Back to Projects
Inconsistent standards BIM

A standard way to manage Revit drawings

A custom toolbar for revising, plotting and transmitting drawings through one consistent process inside Revit.

Discipline BIM
Client context BIM & drafting team
Tools involved Revit, C#

The problem

Small teams that live in Revit tend to hit the same wall: there is no standard way to get drawings out the door. Revisions, plotting, and pushing sheets onto a CDE like ACC or Aconex all happen a little differently depending on who is doing them. Newer Revit versions and free add-ins like PyRevit help in pieces, batch plotting here, revision handling there, but none of them give the team one consistent way of working across the whole issue. So the process drifts, and the drift shows up in the drawings.

What I built

I built a custom toolbar that covers the whole cycle. Revisions roll up or down across selected sheets, on auto or a set value. Batch plotting sends a saved set to PDF or DWG, named from the sheet data. And transmit assembles the issue into a folder ready for a CDE, or straight up to ACC where the team has access.

I have built variations of this for several teams now, each one matched to how they issue.

What makes this work

The whole team now handles drawings the same way, which matters more than any single button. The transmit step is where it lands: an issue gets assembled with all its details attached, who sent it, who approved it, how many sheets, in one action without leaving Revit, so every set goes out looking like it came from the same process, because it did.

What changed

Getting a set out, revised, plotted, transmitted, becomes one standard routine inside Revit, instead of a different manual process every time depending on who is at the keyboard.

Notes on maintainability

Built as variations for several teams, so the revision and transmittal steps match how each one issues.

Recognise this on your own projects?

If your team is doing something similar by hand, get in touch. I'll tell you whether it looks worth turning into a tool.

Discuss a workflow See more projects