Trace each railing tag into its elevation, infill type, anchorage, and specification clauses, then compare height, infill spacing, base connection, handrail extensions, and movement joints for the same run before treating a repeated tag as one uniform assembly.
Assemble the review package
Gather railing elevations and details, the railing schedule or legend, stair and ramp plans, structural or slab-edge details showing the receiving substrate, and the issued metal railings specification. Include glass, cable, or mesh infill product data where used. Review one railing run and connection type completely before assuming a similar-looking tag elsewhere carries the same infill, anchorage, or extension requirement.
WBDG publishes UFGS 05 52 00: Metal Railings as a public guide-specification reference (accessed September 21, 2026). Use your project’s issued specification and amendments for the actual comparison; the guide specification does not automatically govern your project. The checklist below is an original suggested review workflow, not a reproduction of the UFGS requirements.
Eight checks to run against the issued set
Use one record per location or system. The CSV contains the same eight prompts plus fields for source revisions, observed evidence, the review owner, the decision, and closure references.
| Check | Sources to compare | Question to resolve |
|---|---|---|
| Railing type assignment | Plan/elevation tag + railing schedule | Does every tagged run resolve to a defined railing type, and is a code-height guard distinguished from a handrail or a decorative rail? |
| Height | Elevation dimension + specification height criteria | Does the dimensioned top-of-rail height match the height range stated in the specification for that railing type and location? |
| Infill and spacing | Elevation infill + infill-spacing clauses | Is the infill material (picket, mesh, glass, cable) and its spacing identified for the run, consistent with the schedule rather than a generic railing note? |
| Material and finish | Railing schedule + material/finish clauses | Do the specified metal, coating, and finish match the schedule, including any distinction between interior and exterior runs? |
| Anchorage and base connection | Structural/slab-edge detail + anchor and baseplate clauses | Can the base connection, embed, or core-drilled anchor be traced from the detail into the specification, including the receiving substrate? |
| Handrail extensions and returns | Stair/ramp plan + extension clauses | Are extensions, returns, and wall-mounted brackets shown at the top and bottom of each run consistent with the specified requirement? |
| Expansion and movement | Elevation run length + expansion-joint clauses | Are expansion or slip joints located at building movement joints and long runs consistent with the specified spacing? |
| Submittal and mockup scope | Specified samples or mockup + scheduled railing types | Do requested submittals and any mockup represent every distinct railing type, infill, and finish shown? |
Worked example: a mezzanine guard tagged like an interior handrail
Illustrative example: a railing schedule tags a mezzanine-edge run as the same type used for an interior stair handrail, but the elevation shows a taller guard with cable infill rather than pickets, and the specification lists different infill-spacing and anchorage clauses for guards than for handrails. The shared tag does not identify which clause set applies to the mezzanine run.
Confirm which railing category the mezzanine run belongs to from the elevation and any code-related project documentation, correct the schedule tag, and coordinate the anchorage detail and infill spacing to the applicable specification clause. Recheck the base connection against the actual slab-edge condition before closing the item.
Avoid a false conflict
A shared railing tag does not establish that two runs share the same height, infill, or anchorage; guards, handrails, and decorative rails can carry different requirements even when drawn with a similar line weight. Conversely, a difference in anchor type between an interior and exterior run is not automatically a conflict if the substrate differs.
When requirements disagree, follow the project’s document-control and clarification process. Do not assume that drawings always override specifications, or the reverse. Identify the exact sources and request an authorized decision.
Close the issue across the affected documents
Record the location or tag, drawing and specification references, issue dates, observed difference, and the decision needed. Assign an owner and keep the item open until the response identifies the governing requirement. Check the revised drawings and specification references together; a response email alone may leave the issued package inconsistent.
For the overall process, use the guide to drawing and specification conflicts. Mark an inapplicable checklist row with a reason, and distinguish a verified correction from a question that still needs design information.
Where Groundbook fits
Groundbook’s drawing and specification review helps investigate potential disagreements in the documents you supply. Include the relevant specification sections and drawing references, then verify the cited evidence with the responsible reviewers before acting on a finding.