Performance vs. Prescriptive Railing Specs: How to Choose

A railing specification does one of two jobs. It either tells the bidder exactly what to build — alloy, wall thickness, glass makeup, anchor, finish — or it tells them what the finished assembly has to achieve and leaves the means to the supplier's engineer. Most sections on Canadian projects attempt both at once, and the seams show up three months after award as RFIs, substitution requests and change orders. The fix is not choosing one approach over the other. It is knowing which clauses belong in which category and writing them so they do not contradict each other.

Two kinds of instruction

A prescriptive clause names the outcome physically. 6063-T6 aluminum posts at 1,200 mm centres, 12 mm laminated glass infill, a 42 mm round top cap, RAL 7016 fine-texture powder coat to an AAMA performance class, four anchors per base plate. The bidder prices exactly that, and compliance is a visual check against the drawings. Everyone is comparing the same thing at tender, which is the single biggest argument for prescriptive language.

A performance clause names the outcome functionally. The guard shall resist the design loads required by the applicable building code for the occupancy, shall not deflect beyond a stated limit under those loads, shall accommodate thermal movement across the full run without distress, and shall be designed and certified by a professional engineer licensed in the province of the work. How the supplier gets there is their problem — and, importantly, their liability.

The trouble is that a railing is not one thing. It is a visible architectural element and a structural safety device in the same extrusion. Those two halves want opposite specification strategies.

Where prescriptive language earns its keep

You cannot performance-specify taste. "Architecturally acceptable appearance" is not a testable criterion, and no arbitrator will enforce it. Anything the owner will look at for the next forty years should be nailed down in words and dimensions.

• Profile geometry and sightlines: post face width, top cap section, whether the glass is captured or standoff-mounted
• Colour and finish appearance: exact RAL or custom colour, gloss level, texture, and the finish performance class you expect it to meet
• Glass appearance: standard float versus low-iron, tint, interlayer colour, edge treatment, whether the interlayer edge may be visible
• Open-top versus capped glass, and the cap radius if there is one
• Post rhythm where it matters visually — a repeating bay module on a podium elevation is a design decision, not an engineering one
• Match-to-mockup and match-to-existing requirements on phased buildings

On a second or third tower in the same development, prescriptive language is doing more than protecting appearance — it is protecting the value of the detailing already engineered, reviewed and installed on phase one.

Where performance language protects you

The structural half of the assembly is where prescriptive language quietly transfers risk back to the design team. If the specification names a specific anchor, embedment and edge distance before anyone has scanned the slab, the consultant now owns that decision. When the crew finds post-tensioning where the anchor was supposed to go, the resulting redesign is a change, not a supplier defect.

• Structural design of the guard assembly for the code-required loads at the actual project location and height
• Anchorage design into the as-built slab or curb condition, subject to scanning and confirmed edge distances
• Glass makeup selection — the slab edge condition and mounting method drive whether laminated is mandatory and what interlayer is appropriate
• Wind pressure at height on tall buildings, including local pressure zones at corners and upper floors
• Thermal movement strategy across long continuous runs and across building expansion joints
• Corrosion resistance and material compatibility for coastal or de-icing-salt exposure

Prescribe what the building will look like. Performance-specify what holds it up. Most disputes start when a spec writer swaps the two.

Delegated design without criteria is not a specification

Delegating the guard design to the railing supplier's engineer is normal and sensible — it is how most Canadian commercial railing work is procured. But delegation only works if the delegating document states the criteria. If you write "design in accordance with the applicable code" and nothing else, the supplier's engineer selects their own assumptions, and you have no contractual basis to reject the result.

At minimum, a delegated-design railing section should state the following before it says a single word about extrusions.

• Code edition and jurisdiction, including the provincial code if it differs from the national model
• Occupancy and guard location categories, because required loads and heights differ between an exit stair, a residential balcony and an assembly-occupancy mezzanine
• The design loads the guard must resist — uniform line load, concentrated load and infill loading — taken from the governing code rather than paraphrased
• Deflection limits under design load, stated as an explicit criterion rather than left to the supplier's judgment
• Wind design basis and the reference for local climatic data
• Whether stamped shop drawings and calculations are required, and whether a field review by the sealing engineer is required
• Finish and glass warranty durations, and whether the supplier is the single point of warranty for the assembly

Guards are required wherever the drop exceeds 600 mm, minimum height is commonly 1,070 mm for residential balconies (900 mm applies in some locations, so state which applies where), a 100 mm sphere must not pass through any opening, and the non-climbable zone runs roughly from 140 mm to 900 mm above the walking surface. Those are the numbers a reviewer checks first. Put them in the spec so the supplier's engineer and the reviewer are working from the same sheet.

Five clauses that quietly break a railing section

• A section copied from a project in another province or another climate, still carrying the wrong code reference and the wrong exposure assumptions
• "To manufacturer's standard details" with no manufacturer named — every bidder's standard is different, and the low bidder's standard is the cheapest one
• A prescriptive glass thickness that cannot satisfy the deflection limit written four paragraphs later, forcing an RFI on day one
• Delegated design with no stated loads, so three bidders design three different guards and only one of them is priced honestly
• "Or approved equal" with no substitution procedure, no submission requirements and no deadline — an open invitation to price a lesser system and argue about it later

A hybrid that tenders cleanly

The version that works on real projects fixes the visible and delegates the structural, then closes the loop with a mandatory deviations list. Name a basis-of-design system with its profile, finish and glass appearance. State the performance criteria in full. Require the supplier to submit stamped drawings and calculations, plus a written schedule of every deviation from the specified basis of design. That last requirement is what converts a vague comparison exercise into a reviewable document — the reviewer no longer has to hunt for what changed.

It also lets a supplier with in-house engineering do what they are good at. When the same company draws, seals, fabricates and installs, a performance clause is an invitation to solve the anchorage properly rather than a gap to be exploited.