Contents
A Revit room finishing automation plugin reads each room's boundary and builds its finishes as real elements: finish walls around the perimeter, a floor finish and a ceiling inside it, skirting along the base, each one tagged with the room it belongs to. By hand, that's hours of thin walls, parts and shape handles per floor. With a plugin, the rules are written once and every room follows them.
The geometry is what people worry about. It's rarely what goes wrong.
In high school, the founder sat a final that was a debugging test: broken code, find the mistakes, graded out of 20. The class high was 18. The founder's score was 23.5 out of a possible 24. The one deduction was a spelling mistake. The most dangerous bugs aren't the complicated ones. In a finish model they're a door with no threshold rule, a small gap in a room boundary, a room nobody gave a finish.
Why room finishes are slow to model by hand
Revit offers two ways to record finishes. The first is the room's text parameters: Base Finish, Wall Finish, Floor Finish and Ceiling Finish. They fill a finish schedule, and they produce no quantities at all.
The second is modelling finishes as separate elements: thin walls against the main wall, thin floors on the structural slab, Parts to split wall layers. That gives real quantities, but every room needs its walls built, joined to the host wall, set to height, and cut at every opening by hand. In a building with hundreds of rooms that's days of work, repeated after every design change.
What a room finishing plugin actually builds
The Revit API returns each room's boundary through SpatialElement.GetBoundarySegments. From that boundary, the plugin builds:
- Finish walls along each boundary segment, at a height read from the room itself.
- A floor finish with Floor.Create, which since Revit 2022 takes a closed loop of curves, a floor type and a level.
- A ceiling at the height set for each room type.
- Skirting, as a wall sweep or a line-based family, broken at doors.
- Openings cut in the finish walls wherever the host wall has a door or window.
- The room number and name written onto every element, so schedules and takeoffs sort by room.
IT-Eneca's Finishing plugin is one example of the pattern: it creates wall finishes from room boundaries, copies heights from the room, and writes the room number or name into each finish element.
The finish rules come from the room, not the modeller
The plugin doesn't decide that the kitchen floor is ceramic. That decision is made before it runs, in a table linking each room type to Revit types:
- Room type to finish: a toilet gets wall tiles to a set height and a slip-resistant floor, an office gets paint and carpet.
- Host wall type to finish wall type: a concrete wall and a block wall may need different finish build-ups.
- Exceptions: rooms that don't follow the general rule and have to be named one by one.
That table is the most important part of the job. A plugin is only as accurate as its rule table, and no amount of precise geometry makes up for a room whose type was left blank.
The small details that break automated finishes
These take up most of the development and testing time:
- Door thresholds: where does the floor finish stop, at the wall face, at the door's centre line, or under the full wall thickness?
- Gaps in room boundaries: a wall with Room Bounding switched off, or a separation line that doesn't quite close, leaves a room without a closed boundary.
- Columns and shafts: elements inside a room that change its boundary and need finishes of their own.
- Unplaced and redundant rooms: rooms that exist in the schedule but have no valid area or boundary.
- Curved walls: boundary segments that are arcs, which the finish wall has to follow.
A good plugin reports every room it couldn't process, and why. Before running finishes at all, a Revit model checker will catch unbounded and redundant rooms.
When the design changes
Finishes change many times over a project. A plugin that runs once leaves elements behind that no longer match their rooms after the first design change.
To update, every element it creates has to store its room's ID in a shared parameter. On the next run, the plugin rebuilds elements whose room changed, reports elements whose room was deleted, and leaves the rest alone. Otherwise every rerun lays a duplicate layer over the last one.
Finish takeoff and the room schedule
Modelled finishes give material quantities from real geometry. Check two things before trusting the numbers: finish walls overlapping at corners, which counts area twice, and openings deducted from wall area.
A schedule sorted by room number puts each room's floor, wall and ceiling areas side by side. Exporting Revit schedules to Excel covers how to move those numbers into Excel without losing the link to the elements.
An off-the-shelf add-in, a Dynamo graph, or a custom plugin
The Autodesk App Store has several free and commercial finishing add-ins. If each room has one finish type and you don't need special rules for doors or updates, try one of those. You don't need us, or anyone like us, for that.
A Dynamo graph is a good way to test the rules on one floor, and custom Dynamo script development covers when a graph is enough. A custom plugin earns its cost when the office's finish rules, Persian room names, updates after design changes and error reporting all have to live in one tool. That's the kind of work our custom Revit plugin development covers.
Conclusion
Building walls, floors and ceilings from room boundaries is the well-understood part of automating finishes in Revit. The small things decide the result: door thresholds, boundaries that don't close, rooms without a type, reruns after a design change. A plugin that reports those gives you a takeoff you can rely on. What's the first thing you'd want to change? Tell us about the workflow.
FAQ
How does room finishing automation in Revit work?
A plugin reads each room's boundary through the Revit API and, following a rule table, builds finish walls, floors, ceilings and skirting. The room number and name go onto every element so schedules and takeoffs sort by room.
What's the difference between room finish parameters and modelled finishes?
Wall Finish and Floor Finish are text parameters that only fill a schedule. Modelled finishes are real elements and give material quantities from geometry.
What does the plugin do at doors?
It cuts openings in the finish walls where the host wall has a door and breaks the skirting there. Where the floor finish stops at the threshold has to be set in the rules before it runs.
If the design changes, do finishes have to be fixed by hand?
Not if each element stores its room's ID. On the next run the plugin rebuilds elements for changed rooms and reports elements whose room was deleted.
Is Dynamo enough for automated finishes?
For testing the rules on one floor or one project, yes. For everyday use across an office, with updates and error reports, a custom plugin is more dependable.
Why does the modelled finish takeoff differ from a manual estimate?
Usually because finish walls overlap at corners or openings weren't deducted. Both have to be checked in the plugin's rules and the schedule before the quantities are used.
When don't you need a custom plugin?
When each room has one finish type and you need no special rules for doors or updates. One of the ready-made add-ins on the Autodesk App Store will do.