A release check should prove that the right information reached the right output. The goal is not to inspect every object with equal intensity; it is to find high-consequence mismatches before they become material, labor, schedule, or field problems.
Direct answer
What should be verified before checking a steel model?
Verify the project basis first: current drawings and specifications, addenda, RFIs, design criteria, model status, connection responsibility, approved substitutions, revision log, and the exact release scope.
A technically clean model built from an obsolete issue is still wrong. Freeze the source set used for the check, identify unresolved items, and separate hold areas from releasable work.
Direct answer
What geometry checks catch the most steel coordination problems?
Check grids, levels, work points, member orientation, slopes, offsets, support elevations, edge conditions, openings, penetrations, embeds, concrete interfaces, and clearances against the controlling architectural and structural information.
- Trace primary load-path members through plans and elevations.
- Review sloped, skewed, curved, cantilevered, and transfer conditions separately.
- Check top-of-steel, centerline, and work-point conventions.
- Confirm deck edges, slab steps, stairs, walls, equipment, and facade interfaces.
- Review field measurements and survey adjustments with their dates and sources.
Direct answer
What belongs in a connection coordination check?
Confirm design responsibility, forces and criteria, connection type, member compatibility, bolt and weld access, edge distances, copes, stiffeners, continuity elements, protected zones, clashes, and the planned erection state.
Sample ordinary connections and inspect every unusual condition. Repeated connections deserve system-level checks for rule consistency; special connections deserve focused geometry and responsibility review.
Direct answer
How should shop and erection deliverables be checked?
Check that drawings, lists, CNC files, and reports agree with the released model, contain the information their users need, and carry consistent marks, quantities, material, revision, and status.
| Output | High-value checks |
|---|---|
| Shop drawings | Views, dimensions, parts, holes, welds, bolts, notes, quantities, finish, and readable scale. |
| Erection drawings | Marks, orientation, grids, elevations, locating dimensions, field work, zones, and sequence context. |
| Lists / reports | Material totals, grades, lengths, revisions, sequences, finishes, and filter scope. |
| CNC / exports | Correct model issue, member identity, units, operations, file names, and exceptions. |
Direct answer
What makes a steel release controlled?
A controlled release has a defined scope, approver, timestamp, source revision, output set, exception list, destination, superseded-file process, and confirmation that downstream teams know what changed.
Record holds and open questions alongside released work. If a revision arrives after fabrication begins, identify affected status immediately: detailed, approved, released, nested, cut, fitted, welded, coated, shipped, or erected.
No automated “success” message should replace an explicit human decision that the package is fit for its intended next use.
Practice with a fictional example
Make a checked item reproducible
A fictional checklist says “revisions checked” without naming the drawing issue or affected area. A second reviewer cannot tell what was actually compared.
- Choose a bounded area and identify the current drawing set.
- For one checklist item, record the evidence used, the observed result, and any exception.
- Repeat only after the remaining items have their own evidence; do not check the entire list because one sample passed.
What a useful result looks like
A useful check can be repeated by another person from the recorded sources. Browser checkmarks are personal records; they are not engineering approval. When a source changes, decide which earlier checks must be repeated rather than treating completion as permanent.
Primary references
Sources and governing context
These links provide authoritative starting points. The current contract documents, adopted codes, applicable law, and qualified project professionals control a specific project.
- AISC Code of Standard Practice ↗
- AWS D1.1 Structural Welding Code — Steel ↗
- OSHA 29 CFR 1926 Subpart R — Steel Erection ↗
Published by Quantum Steel Design. Read about our use of sources and AI assistance. To report an error, contact QSD with the page address, the passage, and the supporting reference. Please omit confidential project information.