BIM DOCUMENTATION

Documentation automation

From standards to rules

The process began with established criteria for producing drawings: levels, view types, scales, templates, dimensions, tags, and sheet formats. I first used Dynamo to break those decisions down into operations, test their logic, and identify what information each step required. That sequence later evolved into C# commands connected to the Revit API. The intention was to apply shared criteria through a repeatable procedure, not to invent a new graphic standard.

Calculating the extent of a plan view

One of the most interesting challenges was deciding how much a general plan view should show without manually adjusting its crop region. The tool examined the positions and geometries of relevant model elements to estimate a spatial envelope, or bounding box, that could serve as a reference for the plan. Choosing which elements to include was part of the problem: a CAD reference or another object unrelated to the area being documented could distort the result. This analysis turned a visual decision into a programmable geometric operation.

Preparing documentation as a sequence

Once the spatial reference was defined, the add-in accessed the active document and followed the configured rules to create views, associate them with the appropriate levels, apply available templates, and set scales. It also performed dimensioning and tagging tasks before preparing the sheets. Bringing these steps together in a single add-in allowed the team to apply representation criteria through a continuous workflow, rather than relying on several separate scripts or repeating manual instructions.

Keeping the composition in the user's hands

Automation alone did not determine how the views should be arranged on a sheet. For that stage, I developed a WPF preview interface that made it possible to review positions, move elements, and identify potential overlaps before placement. The tool therefore prepared the documentation while a person decided on its final layout. The plan-documentation workflow was successfully tested on three archived projects; sections and elevations remained outside this version. The experience showed how to turn standards into software without replacing the professional review of deliverables.