Why a Viewrail Cable Railing Order Taught Me to Check the Code Before the Catalog
Last March, a shop drawing for a Viewrail cable railing order landed in my review queue. The note from sales said “same as the last order.” I opened the PDF, saw a clean stair run, 42 feet of rail, and a 36-inch top rail, and almost approved it. Here’s why I’m glad I didn’t.
I’m the quality and brand compliance manager at Viewrail. That job usually means I review railing layouts and submittals before they reach production. In a normal year, I look at a couple hundred unique designs. Most of them go through without drama. This one nearly didn’t.
What the two-line spec didn’t say
On paper, the order was a no-brainer. The contractor was a repeat customer. The product line was standard. The top rail height—36 inches—is one of the most common options in our cable railing catalog. It even appears on quick-ship configurations in the stair systems catalog.
The problem wasn’t the railing. The problem was the building type, and the order didn’t include drawings.
The project file described the building as mixed-use. That word is enough to change the compliance conversation. For many commercial and multi-family projects, the International Building Code (IBC) requires guards at 42 inches where stairs or landings are open to a significant drop. For many single-family residential projects, the International Residential Code (IRC) uses 36 inches as a common guard height baseline. Same dimension. Different code path.
So the question wasn’t whether 36 inches is a valid handrail height. It can be. Handrail systems compliance requirements in most unamended IBC jurisdictions put handrail height between 34 and 38 inches, measured above the stair nosing. A 36-inch rail sits comfortably inside that range. The question was whether the railing assembly was serving as a guard.
In a typical Viewrail cable railing layout, the posts, cables, and top rail form one continuous barrier. The top rail is the top of that barrier. If the barrier is next to a stair opening with a fall hazard, the guard height has to meet the guard requirement for that project. At 36 inches, this assembly did not.
Why the catalog can’t be the last word
This is where it gets easy to blame the spec sheet. But that would miss the point.
Viewrail’s cable railing catalog includes both 36-inch and 42-inch top rail options. Viewrail stairs and railing systems are designed to be configured for different project conditions. A good catalog gives you choices. It doesn’t give you permission to skip the building code.
Handrail systems compliance requirements are not a manufacturer feature. They are project-specific. The same railing system can be code-compliant on a residential deck and non-compliant on a commercial stair landing two blocks away. The hardware hasn’t changed. The occupancy and geometry have.
So when I flagged the order, I wasn’t saying the catalog was wrong. I was saying the two-line spec wasn’t enough to know whether 36 inches was appropriate for this particular building.
I’ll be straight with you: the sales rep wasn’t happy. The contractor was pushing back. The project was behind schedule, and the installer was already booked. Nobody wanted to hear that the railing might need a different top rail height.
But if that order had gone to manufacturing and then to the field, the railing would have shown up, sat in a storage room, and eventually triggered a very awkward conversation with the general contractor. A reorder would have cost more than the delay. A failed inspection would have cost more than the reorder.
Five minutes of verification beats five days of correction. Trust me on this one.
What happened once we asked for the drawings
I had about 45 minutes to decide whether to hold the release or let it move forward. The normal process would have been to look one more time at the product note, assume the contractor knew his project, and mark the layout approved. I decided to slow it down.
We sent a short request: the stair section detail, the guard condition at the landing, and either the applicable code section or confirmation from the design team. The drawings came back fast. That open side of the landing was more than 30 inches above the floor below. The architectural detail specified a 42-inch-high guard at that location. The 36-inch top rail would have been too short.
The fix turned out to be simple: taller posts, a 42-inch top rail, an updated infill layout, and revised anchor points. We had the capacity to make that adjustment. The project released about a week later than originally planned.
A week late is annoying. A field reorder is painful. A final inspection failure is a nightmare. I’ll take annoying every time.
What changed in our review process
That near miss did two things.
First, it made the guard-height question a formal step in our pre-production review. If an open stair condition is involved, we now ask what code path applies and whether the specified assembly is acting as a handrail, a guard, or both. That sounds like basic stuff, but in a busy production schedule, basic stuff gets skipped.
Second, it reminded us that a catalog should not pretend to be a code consultant. The stair systems catalog can show compatible components. It can list dimensions. But it can’t know the local amendments, the occupancy type, or the specific fall height at a given stair edge. That information comes from the project drawings.
We also added a clearer note in our cable railing catalog and stair systems catalog: catalog dimensions are system options, not a substitute for project-specific code review. We’re not the authority having jurisdiction, and no manufacturer should pretend to be. But it costs a lot less to ask a question before steel is cut than it does to answer it after an inspector says “no.”
What I’d tell a contractor ordering railing next week
Take it from someone who reviews submittals for a living: send the construction drawings. Even a rough section detail is better than a two-line spec that says “customer wants 36-inch rail.” The contractor who says “same as the last job” has a point—until the last job and this job have different code requirements.
If you’re using Viewrail cable railing, glass railing, or any modern stair system, ask yourself three questions before you place the order:
- What type of building is this, and which code does the local jurisdiction enforce?
- Is this railing going to serve as a handrail, a guard, or both?
- What height does the approved architectural drawing require at this specific stair or deck edge?
That checklist sounds too simple. It’s not. Most railing compliance problems I see are not engineering mysteries. They’re communication problems. The designer knew the guard height. The contractor knew the product. The two just never landed in the same review file.
It took me four years and one near miss to understand that lesson. In most cases, the difference between a compliant railing and an expensive mistake isn’t the brand of the hardware. It’s whether someone checked the project-specific condition before the order left the shop floor.
So if you’re about to order a stair system and the only note is “36-inch top rail,” slow down. Ask who verified that height for this specific project. It might take one phone call. Or it might save you a month of rework, a storage fee, and a very bad week on site.
5 minutes of verification beats 5 days of correction. I’ve said that a hundred times, and it was never truer than on the day we almost shipped the wrong guard height.