Measure Twice, Pour Once: Running an ADA Clearance Audit in the Model
Photo: Jerzy Strzelecki, CC BY-SA 3.0, via Wikimedia Commons
A client calls about a back-door ramp, a bathroom refresh, or a small retail fit-out. The contractor is ready to mobilize. The drawings look fine. Then someone notices the ramp eats the entire sidewalk, or the new door lands six inches from a return wall. By that point, the cheapest fix is a change order and a few weeks of apologies.
That is the moment a 3D modeler can save everyone a lot of money. Not by acting like a code official, and not by pretending a render is a permit set. By doing the unglamorous work of testing clearances in geometry before the concrete truck rolls.
The cheapest place to fail is the viewport
Accessibility problems are spatial problems. A 5-inch rise needs 60 inches of run at 1:12. A 32-inch clear door width is not the same as a 36-inch door slab. A 60-inch turning circle looks generous on a floor plan until a casework run quietly clips it. These are all things a model can show you in seconds, if the model is built to answer the question.
The trick is to stop treating ADA review as a drawing-markup exercise and start treating it as a geometry audit. You are not stamping a set. You are giving the client a clear look at where the design works and where it does not, while every fix is still a drag handle instead of a demolition hammer.
Build a small clearance kit you reuse on every project
You do not need a custom plugin for most of this. A simple collection of proxy objects, saved in your asset library, will cover a surprising amount of ground:
- A slope wedge generator, or a few pre-built wedges for common rises, so you can drop in a 1:12 ramp and see what it does to the site plan.
- A 60-inch diameter turning circle, modeled as a flat disk with a bright material.
- A 30-by-48-inch clear floor rectangle for fixtures, sinks, and forward approaches.
- Door maneuvering clearance L-shapes for pull-side and push-side, latch-side and hinge-side.
- A 36-inch-wide route ribbon that you can bend through a plan like a garden hose.
- A threshold gauge for the 1/4-inch and 1/2-inch vertical transition checks.
Keep these in a clearly named collection, maybe ADA_proxies, with colors that scream at you. Link their dimensions to parameters so you can resize them without rebuilding. The goal is not visual polish. The goal is to make the invisible clearance visible at a glance.
The five checks that earn their keep
1. Slope, rise, and landings
The standard running slope for a ramp is 1:12, or about 8.33 percent. A 30-inch rise is the maximum before you need a landing. Model the ramp as actual geometry, not a painted arrow on a plan. Add the handrail zone at 34 to 38 inches and check that the landing at the top and bottom is level and long enough. Cross slope matters too: keep it at 1:48 or flatter. If the ramp wants to launch a wheelchair into the parking lot, the model will tell you before the excavator does.
2. Turning space and clear floor area
A 60-inch circle is the classic turning test. Drop the disk into the bathroom, the kitchen, the checkout lane, and watch what it hits. Then check the 30-by-48-inch clear floor space at the fixtures and approach points. This is where small commercial fit-outs get humbled. A trash can, a display rack, or a decorative column can turn a compliant plan into a puzzle.
3. Door maneuvering clearances
Door clear width gets all the attention, but the rectangle in front of the door is where remodels quietly fail. Pull-side and push-side clearances are different. Latch-side and hinge-side approaches are different. Model the door swing and the clearance rectangle together, and you will catch the classic problem: a new accessible door that opens into a wall, a case, or a change in floor level. Thirty-two inches of clear width is the target, but the approach space is what makes it usable.
4. Route continuity
Accessibility is not a collection of isolated features. It is a route. From the accessible parking space or the public sidewalk to the entrance, through the lobby, to the primary function. Model that route as a ribbon and keep it at 36 inches minimum, with 60-inch passing spaces where needed. If a planter or a sign eats six inches, the route fails. A route ribbon makes that obvious in a way a floor plan often does not.
5. Vertical transitions and thresholds
A quarter-inch vertical change is generally fine. A half-inch change needs a bevel. Anything more needs a ramp. Model the thresholds, the exterior landings, and the transitions between materials. Exterior landings have their own slope limits, and a model view from eye level will show the trip hazard that a plan view hides.
Turn the checks into views a client can actually read
A compliance review is not a dump of 40 screenshots. Pick the views that tell the story. Start with an annotated orthographic plan showing the route, the turning circles, and the clearance rectangles. Add one eye-level view at the ramp landing and one at the main door. If you have time, record a short walkthrough that follows the route from the sidewalk to the service counter.
Use a consistent color code. Green means the clearance works. Yellow means it needs field verification because the existing conditions are fuzzy. Red means the geometry fails and the design needs to change. Keep the annotations simple: dimension, code reference, and a plain-English note. The client does not need a treatise. They need to know where to spend their attention.
Package it as a red-yellow-green memo
Put a one-page summary at the front. List the green passes so the client knows what is settled. List the yellow items with the specific field measurement that will resolve them. List the red items with a model view, the relevant standard, and a suggested fix that includes a dimension. Attach the model views as an appendix, and keep the file names boring and searchable.
One important note: this is a design review, not a legal certification. The authority having jurisdiction has the final say, and local amendments can be stricter than the federal baseline. If the project is in a state with its own accessibility rules, say so in the memo and tell the client to confirm with the local building department. That is not a disclaimer to hide behind. It is part of being a good collaborator.
Model now, argue less later
The ramp is not a render. It is a relationship between rise, run, landing, and route. When you model that relationship early, you give the client something better than a pretty picture: a chance to fix the expensive stuff while it is still cheap. Measure twice in the viewport. Pour once in the real world.