Structural Steel Shop Drawings: Release the First Submittal

Structural steel shop drawings should not reach formal review as a stack of individually finished sheets. Before the first submittal, the fabricator needs to know whether the package transfers the current contract information, exposes unresolved decisions, coordinates connected outputs and gives the reviewer a traceable basis for action. Otherwise, comments become a costly method of discovering missing inputs. This guide gives a detailing or project-engineering coordinator a controlled way to release, conditionally release or hold a first shop-drawing submittal. It does not approve design, prescribe connection details, replace the contract or authorize fabrication.

Define What the First Submittal Must Prove

The first-submittal decision is narrower than drawing approval and earlier than production release. It asks one question:

Is the identified approval-document package sufficiently complete, coordinated and explicit to enter the project’s formal review route for its stated scope?

For projects using ANSI/AISC 303-22, fabrication documents may be shop drawings, a fabrication model or a combination, while erection documents may likewise be drawings, a model or both. The same Code assigns the fabricator responsibility for transferring contract information into accurate and complete approval documents and developing the detailed dimensional information needed for field fit-up. The actual contract can add requirements, change responsibilities or use different terminology.

Keep three gates separate:

The existing steel fabrication drawing approval workflow owns the second and third gates. This article owns only the first.

The controlled object proposed here is a Shop Drawing Information Release Matrix (SDIRM). It links each material information group to its source, package location, resolver, status and release evidence. The name is an East Baoyu editorial control device, not an AISC form or a substitute for the project’s procedure.

Use three package decisions:

• Release for review: all blocking information is covered, the package has passed its required check and every known open item is visible.
• Conditional release for review: only explicitly permitted, non-blocking items remain; each has an owner, due date, affected scope and reviewer instruction.
• Hold: a missing, conflicting or unauthorized input can change the submitted geometry, connection, material, interface, identity or review basis.

Do not shorten these labels to “released.” State for review so no one mistakes the decision for approval or fabrication authorization.

Map Information by Function, Not by Filename

A drawing register proves that files exist, not that the information is present or consistent. Separate the package into functions even when one file performs several:

• Contract baseline: governing design documents, specifications, addenda, accepted RFIs, revision/date and declared precedence.
• Member fabrication: marks, geometry, material, end work and linked details for each submitted shipping piece.
• Assembly and connection: parts, fasteners, welds, connection criteria and assigned substantiating route.
• Erection and interfaces: grids, levels, orientation, attachments, embeds/anchors and adjacent work.
• Material, finish and quality: grades, bills/schedules, substitutions, coating or galvanizing, welding/inspection references and project hold points.
• Document control: index, revision history, check record, transmittal and open-item register.

These are checking functions, not universal sheet types. Projects may package them differently; the contract and responsible professionals decide what applies.

ANSI/AISC 303-22 requires stable drawing identification through revisions and unique identification for model submittals. It also requires discrepancies found during the fabricator’s work to be notified through the defined project route. Apply that logic before review: the package should make its governing identity and known exceptions reconstructable without relying on a personal folder name.

Build the Shop Drawing Information Release Matrix

Create one SDIRM row for each information group that can materially affect the submitted scope. Do not create a row for every note; group information at the level where one missing decision could change several drawings or outputs.

Populate the matrix from the contract baseline outward. A practical pass can cover:

1. drawing/model identity, grids, levels, coordinates, dimensions and controlling references;
2. member and assembly marks, quantities, section/plate identity, work points, orientation and field interfaces;
3. connection responsibility, criteria, forces or reactions, calculations and review route where applicable;
4. material grades, bolts and other fasteners, weld information, substitutions and traceability needs;
5. surface preparation, coating, galvanizing, fire-protection or architectural requirements that affect detailing;
6. erection relationships, embeds, anchors, adjacent trades, openings, access and project-assigned temporary items; and
7. revision, checker, transmittal, supporting-document and open-item identity.

The list prompts coverage; it does not put every field on every drawing. Point to the authoritative location instead of copying a requirement into multiple places that can diverge after a change.

Challenge the Interface Chain

Many first-submittal failures are not missing member dimensions. They occur where information changes owner or representation. Test the chain from the contract source to the field relationship:

Follow sample members through several interfaces:

• grid and elevation to work point, member axis and end condition;
• primary member to secondary steel, opening, embed, anchor or equipment interface;
• connection criterion to plate, bolt, weld and supporting calculation or reference;
• shipping piece to assembly mark, erection location and field attachment;
• material/finish requirement to bill, drawing note and protected or masked interface; and
• revised contract information to every affected drawing, model object, list and supporting record.

A dense sheet can still fail: a dimension may use the wrong baseline, a weld symbol may have an open design basis, or an erection mark may disappear from a revised assembly. Follow the information chain, not the density of graphics.

Do not turn interface checking into unassigned design. When the source is missing or conflicting, record the affected scope and send the question to the authority named by the contract. ANSI/AISC 303-22 states that discovering cross-discipline discrepancies is not generally the fabricator’s responsibility, but discrepancies discovered during the work must be raised. The SDIRM preserves that distinction: it records what was encountered and who must resolve it without implying that the detailer owns the design decision.

Make Connection Responsibility Visible

Connections concentrate geometry, forces, constructability and professional responsibility. Identify the project’s connection-design allocation and make each family traceable to it; do not infer responsibility from who drew the detail. Before release, locate:

• the contract allocation and named responsible professional or entity;
• the governing details or criteria, forces/reactions, project requirements and accepted changes;
• the calculation, design note or substantiating information required by the assigned route;
• the detail, deviation, alternative or question on which the reviewer must act; and
• every open RFI with affected marks, owner and due date.

Hold affected scope if responsibility conflicts, required criteria are missing, substantiation is on another revision or an open answer can change geometry, material, fabrication or field fit-up.

A reusable standard connection can reduce drafting, but it does not eliminate the need to confirm that its assumptions and current project inputs apply. Likewise, a software-generated connection is not self-approving. Present the criteria, responsibility and exception route that the reviewer needs; leave the engineering decision with the assigned authority.

If an alternative connection or value-engineering proposal is being requested, separate it from the baseline-compliant package. State what changes, why review is requested and which members, calculations, materials, schedule or interfaces are affected. A reviewer should not have to reverse-engineer a commercial or design proposal from revision clouds.

Reconcile Drawings, Models and Derived Lists

The package may be drawing-led, model-led or hybrid. Declare what controls, what supports it and what reliance is permitted.

The BIM and Model LOD for Structural Steel Fabrication guide covers model reliability and exchange in depth. For this gate, reconcile only the essentials: drawing and model/package identity; included marks, zones and exclusions; corresponding geometry; grades, parts and bolt/weld references; connection/calculation relationships; and erection location/orientation. Differences need a recorded precedence or disposition.

The 2025 BIMForum LOD Specification explains that model-element content and reliability should be defined for intended uses and does not replace a project BIM execution plan. buildingSMART’s IDS 1.0 can express and check specified alphanumeric IFC information; buildingSMART also states that IDS does not cover geometry. Automated completeness checks can therefore help find absent or malformed attributes, but they do not validate engineering, approve a connection or prove that drawing and model geometry agree.

Record which model or database version generated each output. If a sheet is edited afterward, show how the change returns to source data; otherwise, hold the divergence before later BOM, CNC or erection outputs depend on it.

Classify Gaps by Their Consequence

An open-item count is weak because ten harmless clarifications can matter less than one missing connection criterion. Classify each gap by what it can change.

“To be confirmed” is not a status. It needs a subject, owner, due date, affected scope and permitted work. Conditional release should be rare and project-defined. It is appropriate only when the reviewer can complete the intended review without guessing and when no downstream user can mistake the condition for permission to fabricate.

Use the project document register to control document identity and due dates. Use the SDIRM to control whether the technical information represented by those documents is sufficiently covered for this submittal. One register does not replace the other.

Pass the First-Submittal Release Gate

Release a package for formal review only when the named coordinator can answer yes to all applicable gates:

1. Scope: the submission purpose, structural zones, member marks, document/model set and exclusions are explicit.
2. Baseline: every governing source is identified by current revision/date, and precedence or discrepancies are resolved or visibly held.
3. Coverage: the SDIRM maps each material information group to a findable package location or controlled reference.
4. Responsibility: connection design, interface decisions, open questions and approvals have named owners within the contract route.
5. Coordination: sampled information chains and the drawing/model/list reconciliation show no unexplained conflict.
6. Checking: the required detailer/fabricator check is complete, identifiable and independent where the project or quality system requires it.
7. Open items: every remaining item is explicitly non-blocking for the stated review, with consequence, owner, due date and affected scope.
8. Control: the index, revision description, transmittal and supporting information identify one reconstructable package.

The release record should name the package, revision, scope, checker, SDIRM revision, open-item status, decision, decision owner and date. When held, record the specific evidence needed to reopen the gate. When conditionally released, state what the reviewer may review and what remains excluded.

This gate does not predict a comment-free review. It prevents the reviewer from becoming the first checker and prevents material uncertainty from disappearing inside polished sheets.

Assemble the review package

Include what lets the authorized reviewer understand the basis, scope and requested action:

• controlled drawing/model index with purpose, revision and included scope;
• transmittal naming the review requested, return route and project status terminology;
• SDIRM or equivalent coverage record approved for the package;
• open-item/RFI register showing holds, non-blocking conditions and affected marks;
• connection design or substantiating information required by the contract;
• declared drawing/model/source-data relationship and known exclusions;
• check record required by the fabricator’s quality system; and
• concise revision or deviation summary where the submission is not a clean baseline issue.

Give every supporting item an identity and reason for inclusion. Do not send uncontrolled working files or omit a controlling record merely because it sits in another platform.

After submission, move to the separate approval workflow for statuses, comments, incorporation, resubmission and production release. Keep the SDIRM aligned with controlled revisions.

Prepare a bounded package for East Baoyu

For a fabrication inquiry, send current structural drawings/specifications, member and connection scope, applicable project requirements, responsibility route, material/finish and inspection/documentation needs, model/data formats, milestones, delivery location and open questions. Identify what remains preliminary.

East Baoyu can review the package to confirm the proposed supply route, quotation basis and information still needed for fabrication coordination. Project-specific design, connection engineering, drawing approval and authorization to fabricate remain with the parties assigned by the contract and applicable law.

Use the Steel Structures page for commercial context or contact East Baoyu through the controlled inquiry route. Email: info@baolaipipes.com · Phone: +86-22-28352066 · WhatsApp: +86-130-1228-3281.

Related Resources

• Steel Fabrication Drawing Approval Workflow — review status, comment closure and production release after a controlled submittal exists.
• BIM and Model LOD for Structural Steel Fabrication — model content, reliability, permitted use and exchange boundaries.
• Project Document Register — document identity, revision, status, owner and due-date control.
• Steel Fabrication ITP — downstream quality evidence linking material, welding, inspection, dimensions and coating.

References

The contract documents and legally adopted requirements control. The sources below support the general information-management and structural-steel workflow described here; they do not establish East Baoyu certification, project-specific duties or approval authority.

• ANSI/AISC 303-22 — Code of Standard Practice for Steel Buildings and Bridges
• AISC 303 current-standard overview
• AISC revisions and errata
• BIMForum 2025 Level of Development Specification
• buildingSMART Information Delivery Specification (IDS)

Research checked 2 September 2026. At that date, ANSI/AISC 303-22 remained the current published AISC Code of Standard Practice; AISC had run public review of a future edition that is expected to supersede it. Verify the current edition, errata, contract adoption and project amendments before use.

Disclosure: East Baoyu manufactures and supplies products discussed on this website. This article provides general engineering and procurement guidance, not a project design, certificate, warranty, code interpretation or release authorization. Structured drafting tools may assist research and editing; accountable technical and publication review remains required.