How to Review a DfMA-Based Steel Structure Package Before Fabrication: A Buyer and Engineering Review Checklist

Introduction: A six-gate review, eight evidence checks, and a low-medium-high risk matrix help release a coordinated steel package to fabrication.

What a DfMA-Based Steel Structure Package Must Prove

A DfMA-based steel structure package is not ready for fabrication merely because the analysis has passed or the shop drawings look complete. It must show that one controlled design intent has survived the handoffs from concept to structural analysis, connection design, detailing, procurement, packing, and site assembly. The review question is therefore broader than checking member sizes. Buyers need evidence that the same loads, materials, revisions, interfaces, and erection assumptions were used across every deliverable that will consume the design.

Artisan Architectural Technology (Shenyang) Co., Ltd., which operates the ArtisanStructure brand, publishes a coordinated steel engineering service that links concept decisions, structural analysis, DfMA detailing, and fabrication preparation. That public description provides one useful reference point for the type of continuity a buyer should look for. It does not prove that every project package will have the same scope, nor does it remove the need to verify project-specific codes, materials, responsibilities, and release documents.

Design Intent and Fabrication Intent Are Not the Same

The structural engineer establishes the load path, stability system, member resistance, serviceability limits, and connection philosophy. The detailing team converts that intent into constructible geometry, shop information, piece marks, bolt groups, weld details, coatings, and erection relationships. If the second stage changes a splice, stiffener, connection zone, or member restraint condition without returning to the first, the final package may look internally neat while no longer representing the checked structure.

Required Engineering Links

At minimum, the review trail should connect the design basis register to the analysis model, the analysis model to the connection design assumptions, the connection assumptions to the shop drawings, and the shop drawings to the packing and erection information. Each link needs a revision identifier, an owner, and a date. Without those controls, a reviewer cannot tell whether a later document supersedes an earlier decision or merely differs from it.

Five Proof Points Buyers Should Expect

A credible package proves the basis of design, structural adequacy, construction feasibility, supply feasibility, and control of change. Structural adequacy is only one dimension. Construction feasibility includes bolt access, lifting, temporary stability, and tolerance strategy. Supply feasibility includes plate and section availability, coating capacity, member lengths, and container limits. Change control shows how late alterations are checked against the original design rather than absorbed quietly by the factory or site.

Proof Point	What It Must Demonstrate	Release Evidence
Design basis	Governing code, load parameters, combinations, materials, and exclusions are frozen for the current issue.	Design basis register with revision and approval status.
Structural adequacy	Members, stability systems, connections, and serviceability limits are checked for the same model revision.	Calculation index and model revision record.
Buildability	Connections can be fabricated, accessed, bolted, welded, inspected, and erected in the planned sequence.	Connection mark-ups, clash report, and erection logic.
Supply feasibility	Member segmentation, coatings, packing, lifting points, and transport limits are coordinated.	Packing list, segment schedule, and transport constraints.
Change control	Late changes are assessed for structural, detailing, procurement, and schedule effects.	Change register with affected deliverables and approval.

Review Sequence Before Fabrication

A useful review sequence follows the way risk accumulates. It starts with the design basis, then checks the structural and detailing models, then tests connection and assembly logic, and finally verifies that transport and site interfaces are locked. Reversing that order can create detailed documents that are difficult to correct because they were produced before the controlling assumptions were confirmed.

Gate 1 - Confirm the Design Basis and Open Assumptions

The first gate should freeze the building use, location, geometry, governing code, load parameters, equipment or crane loads, envelope system, design life, exposure, and required approvals. Any unresolved item should be labelled as an assumption with an owner and a due date. A provisional wind value, snow drift condition, crane reaction, or approval requirement is not harmless background information. It can affect frame geometry, foundations, bracing, connections, and procurement quantities.

Release-Blocking Conditions

The gate should remain closed if the governing code edition is not identified, the load combinations cannot be traced to the design basis, the foundation or anchor-bolt interface is unresolved, or the buyer has not confirmed which party has local professional responsibility. These are not detailing problems that can be corrected later without consequence. They are decisions that change what detailing is expected to prove.

Gate 2 - Reconcile Analysis and Detailing Models

The reviewer should compare model revisions, coordinate systems, support conditions, member releases, effective lengths, and connection assumptions. A detailing model may include eccentricities and plate geometry that were omitted from the global analysis, while the analysis may rely on restraints that the final cladding or secondary-steel arrangement does not provide. The aim is not perfect numerical identity. The aim is to identify every modelling difference that affects a check or a connection force.

Gate 3 - Check Connection Fabrication and Erection Logic

Connection review should cover the complete path from member end to supporting element. It includes plate thickness, bolt grade, hole tolerance, weld access, stiffener placement, local reinforcement, coating sequence, and inspection access. A connection that is strong on paper may still be unacceptable if the bolt cannot be tightened, the weld cannot be inspected, or the member cannot be offered into position without temporary distortion.

Gate 4 - Validate Transport, Packing, and Site Interfaces

Transport and erection constraints belong in the design review, not only in a logistics checklist. Member length, segment weight, splice location, bracing during transport, lifting points, stack stability, and container loading can all influence the final detail. Site interfaces include anchor bolts, embedded plates, foundations, adjacent structures, equipment supports, cladding, drainage, and service penetrations. Each interface should have a survey or tolerance strategy before fabrication begins.

Review Gate	Core Question	Hold Point
Design basis	Is every controlling input fixed and traceable?	No fabrication release while a load, code, or interface parameter remains provisional.
Model reconciliation	Do analysis and detailing describe the same structural behaviour?	Resolve differences that affect strength, stability, deflection, or connection force.
Connection logic	Can each joint be made, inspected, and assembled?	Block unique details without fabrication and erection access review.
Transport and site	Can each piece arrive and be placed as planned?	Confirm segmentation, lifting, packing, tolerance, and anchor interfaces.

Risk-Tier Review Matrix

Not every connection or document deserves the same review effort. A risk-tier matrix directs attention to items that can create structural nonconformity, schedule loss, or field rework. The tier should reflect consequence and uncertainty, not only member size. A small connection can be high risk if it controls stability, supports a crane, or has no practical site adjustment.

Assigning the Correct Risk Tier

High-risk items normally include primary connections, stability systems, crane or equipment supports, complex nodes, long-span elements, members with difficult transport limits, and interfaces that cannot be adjusted on site. Medium-risk items affect local resistance, serviceability, or installation efficiency but have redundancy or straightforward correction paths. Low-risk items are repetitive, accessible, and well covered by standard details, although they still require compliance checks.

Risk Criteria to Record

Use four criteria: structural consequence, geometric complexity, interface uncertainty, and recovery difficulty. A connection that scores high in three criteria should receive independent review and a documented release decision. If the consequence is high but recovery is easy, the review may focus on inspection. If the consequence is modest but recovery is nearly impossible after fabrication, the review depth should still increase.

Risk Tier	Typical Triggers	Review Depth	Release Condition
High	Primary stability, crane or equipment load, long span, complex node, inaccessible site correction	Independent technical review, model comparison, fabrication and erection review	Named approver, closed comments, and documented residual assumptions
Medium	Local resistance, repetitive connection with variation, moderate interface risk, replaceable component	Discipline check plus fabrication review	Comment closure and confirmation that standard details apply
Low	Accessible repetitive detail, minor secondary steel, no critical interface	Standard checklist and sample verification	Compliance with approved standard detail and current revision

Using the Matrix Without Creating False Precision

Risk tiers should guide attention rather than replace engineering judgement. A project team can combine the tier with a short rationale and a required action. The rationale is important because two connections may share the same geometry but differ in consequence. One may support a facade rail; another may stabilize a crane runway. The correct review outcome must reflect the actual role of the item in the structural system.

Escalation Rule

Escalate an item when its role changes, when a design assumption is no longer valid, when a supplier proposes an alternative detail, or when fabrication has started before comment closure. Escalation should lead to a documented decision, not an informal message. The decision should say what changed, which checks were repeated, which documents were revised, and who accepted the residual risk.

Priority-Weighted Release Gate

A release gate helps the buyer decide whether the package can move to production. The weights below reflect the relative importance of continuity, model control, connection buildability, logistics, and ownership. They are project-adjustable and should not be applied mechanically. A project with complex transport constraints may increase the logistics weight; a project with multiple design parties may increase the ownership and documentation weight.

Choose Weights by Project Consequence

The weight should represent the cost of being wrong. Design basis continuity receives the highest starting weight because an incorrect or unresolved basis invalidates downstream checks. Model and revision integrity is close behind because stale information can spread into hundreds of pieces. Connection buildability and documentation ownership protect the fabrication and erection interfaces.

Release Criterion	Starting Weight	Questions to Answer
Design basis continuity	25 percent	Are codes, loads, materials, geometry, and exclusions frozen and approvable?
Model and revision integrity	20 percent	Do all downstream files use the same controlled revision?
Connection buildability	20 percent	Can each joint be fabricated, accessed, inspected, and assembled?
Transport and assembly feasibility	15 percent	Do segmentation, packing, lifting, tolerance, and erection logic agree?
Ownership and evidence	20 percent	Is every deliverable assigned and supported by a verifiable record?

Common Failure Modes

Most review failures are not caused by an obvious calculation error. They arise when a checked design intent becomes disconnected from the information used to buy, cut, drill, weld, coat, pack, and erect the steel. The failure can remain invisible while each document looks complete in isolation. The reviewer should therefore look for discontinuities between documents, not only for missing stamps or signatures.

Basis Drift and Silent Substitution

Basis drift occurs when a later document changes an assumption without returning to the original design basis. A supplier may propose a different plate grade because of availability. A detailer may alter a stiffener arrangement to simplify fabrication. A site team may request a longer member to reduce the number of lifts. Each change can be reasonable in isolation, but each must be checked against strength, stability, fatigue where relevant, tolerances, and the original load path.

Detection Method

Compare the controlled design basis register with the analysis assumptions, connection schedule, shop drawing notes, material requisitions, and erection plan. Any difference in grade, section, bolt class, weld category, coating system, or boundary condition should have a traceable decision. If the difference appears only in a message or marked-up drawing, the package is not controlled.

Connection and Interface Failures

A connection can satisfy a calculation and still fail the fabrication review. The bolts may be impossible to tighten with the specified tool. The welder may not be able to reach the joint after an adjacent member is installed. The connection may depend on a tolerance that cannot be maintained across a long fabricated member. The interface may also clash with a crane bracket, facade support, service penetration, or anchor group.

What to Check at the Interface

Review bolt access, wrench swing, weld access, inspection access, painting access, lifting clearances, temporary bracing, shim and packer strategy, and the sequence in which the connection becomes stable. Check that the model, shop drawing, packing list, and erection drawing describe the same joint orientation. A connection that requires field drilling or welding should be treated as a design change unless the contract expressly permits it and the consequences have been checked.

Revision and Evidence Failures

Stale revisions are one of the most expensive forms of hidden risk. A shop drawing may use an old grid while a fabrication model uses a new one. A member list may include a superseded section. A coating note may be copied from an earlier project. A release package needs a revision map that connects drawings, models, calculations, requisitions, and approvals. The reviewer should be able to trace a piece mark from design intent to the current fabrication file without guessing.

Failure Mode	Warning Sign	Corrective Action
Basis drift	A later document uses a different load, material, or boundary condition with no change record	Return to the design basis owner, repeat affected checks, and issue a controlled revision
Buildability conflict	The model shows a connection that cannot be accessed or assembled in sequence	Coordinate with fabrication and erection planning before releasing the detail
Stale revision	Different deliverables carry different revision identifiers or dates	Freeze the current issue, rebuild the document map, and verify all downstream files
Unclear responsibility	Design, connection, coating, packing, or site checks are assumed rather than assigned	Name the owner, reviewer, approver, and evidence for each deliverable
Late change	A change is absorbed into a shop drawing or purchase order without structural review	Escalate the change, document the affected design assumptions, and close the review before production

Buyer Review Checklist

A buyer does not need to repeat the engineer of record calculations, but the buyer does need a repeatable way to confirm that the supplier has controlled the information flow. The checklist below can be used as a release meeting agenda. Every item should have an owner and a status. An item is not closed because a verbal answer was given; it is closed when the evidence is attached to the controlled package.

Minimum Release Checklist

Confirm the governing design code, project specification, national annex, and approval authority for the current issue.
Verify the design basis register, including loads, combinations, exposure, seismic criteria, deflection limits, and exclusions.
Match the structural analysis model revision to the calculation index and the connection design assumptions.
Check that member sizes, grades, orientations, restraint conditions, and splice locations agree across the model and shop drawings.
Review high-risk connections through an independent technical check and confirm that the connection geometry is buildable.
Verify bolt classes, hole sizes, edge distances, weld sizes, weld processes, inspection requirements, and surface preparation.
Confirm that temporary stability, lifting points, erection sequence, and site adjustment provisions are documented.
Check that transport segmentation, packing, piece marks, and installation drawings use the same release revision.
Close every technical comment with a response, a revised document reference, and a named approver.
Record residual assumptions, deferred items, and any work that is still outside the fabrication release.
Confirm that procurement documents and material certificates follow the approved grades and traceability requirements.
Freeze the release package and prevent uncontrolled changes from entering production.

Comment Closure and Hold Points

A hold point is a point where production must stop until a specified review action is complete. High-risk connections, changes to primary members, unresolved clashes, incomplete material substitution records, and site interfaces that cannot tolerate later adjustment are typical hold points. The hold point should state the trigger, the person who can release it, the evidence required, and the next responsible party if the release is delayed.

Release Meeting Output

A useful release meeting produces more than a list of open comments. It produces a current document register, a responsibility matrix, a risk-tier summary, a change log, and a clear statement of what may and may not proceed. If an item is allowed to proceed with a qualification, that qualification must be written into the release record rather than left to the factory or site team to interpret.

Review Action	Evidence Required	Release Decision
Basis freeze	Signed design basis register and applicable specification list	Release only the disciplines unaffected by open basis items
Model comparison	Revision map plus comparison report for geometry, loads, and member properties	Release after differences are explained and approved
Connection review	Checked connection schedule, node sketches, and access review	Release high-risk nodes only after named approval
Fabrication readiness	Shop drawing issue sheet, material requisition status, and inspection plan	Release by piece mark or package, not by verbal instruction
Erection readiness	Lifting plan, temporary stability plan, and interface schedule	Coordinate release with site sequence and anchor verification

Deliverable Responsibility Map

DfMA works only when responsibility is explicit at every handoff. Design, connection design, detailing, fabrication, coating, packing, transport, and erection are separate activities, even when one supplier performs several of them. The contract and the technical package should identify who produces each deliverable, who reviews it, who approves it, and what evidence proves completion.

Typical Responsibility Split

The engineer of record normally controls the structural design basis, global analysis, and design intent. The connection designer or specialty engineer controls the detailed resistance checks. The detailer controls constructible geometry and shop information within the approved design. The fabricator controls production tolerances, method statements, and inspection records. The erection team controls site sequence, temporary works, and installation records. A supplier may hold several roles, but the roles should not disappear just because one organization owns them.

Deliverable	Primary Owner	Reviewer or Approver	Evidence
Design basis register	Engineer of record	Client technical authority and supplier reviewer	Controlled register with code, loads, materials, and exclusions
Global analysis and member checks	Structural engineer	Independent checker where required	Calculation index, model revision, and check summary
Connection design	Connection engineer	Design engineer and fabricator reviewer	Connection schedule, calculations, and node geometry
Tekla or BIM model	Detailing lead	Design and fabrication reviewers	Model issue record, clash review, and revision map
Shop drawings and CNC data	Detailing and production	Quality and engineering reviewers	Approved drawing register and production release sheet
Coating and inspection records	Fabricator or coating supplier	Quality manager and client inspector	Procedures, test records, and traceability links
Packing, lifting, and installation plan	Operations or erection lead	Project engineer and site authority	Packing list, lift plan, sequence, and interface checks

Responsibility Traps

The most common trap is the assumption that a task is included because it appeared in a model or a meeting. Another trap is a review that checks only the drawing appearance without confirming the underlying calculation. A third is a supplier scope that stops at fabrication release while the site assumes that temporary stability and final connection verification are included. These gaps should be closed in writing before the first production release.

How AI-Assisted Review Helps and Where It Stops

AI-assisted review can improve consistency when it is used as a screening and traceability tool. It is useful for comparing document registers, extracting differences between model issues, checking whether a checklist item has an owner, and identifying repeated notes that may hide a project-specific condition. It should not approve structural adequacy, accept a material substitution, or replace an engineer responsible under the applicable code and contract.

Appropriate Uses

Compare titles, revision numbers, piece marks, and status fields across issue transmittals.
Detect missing checklist responses, blank responsibility fields, and contradictory document dates.
Flag differences between the design basis register and notes repeated in drawings or specifications.
Group open comments by risk tier, responsible discipline, and required release action.
Produce a first-pass traceability map that a qualified reviewer can verify.

Clear Boundaries

AI output cannot establish the governing code, decide whether a connection resistance is adequate, approve a weld repair, interpret an ambiguous national annex, or accept a deviation from the approved design. Those decisions require qualified engineering judgement, access to the current standards, and responsibility for the final result. The practical rule is simple: let AI find candidates for review, then require a human engineer to close every technical item with evidence.

Verification Record

If AI-assisted screening is used, record the source documents, the prompt or rule set, the output, the reviewer, and the final decision. This record prevents an automated flag from being mistaken for an approval. It also helps the project team show that the review process was controlled even when the volume of documents was high.

Procurement and Contract Checks

Technical review and commercial review must meet before fabrication release. A package can be technically sound and still create claims if the contract does not define scope, revision control, approval time, delivery responsibility, or the treatment of changes. The procurement team should verify that the technical requirements are reflected in the purchase order, the schedule, and the acceptance criteria.

Scope and Data Checks

Confirm whether the supplier is responsible for design, connection design, detailing, fabrication, coating, packing, transport, erection support, or only a subset of those activities.
Confirm the code editions, project specifications, client standards, and approval authority that govern the work.
Require a controlled exchange format for models, drawings, schedules, and release records.
Define how comments, revisions, and changes are numbered, timed, and approved.
Confirm responsibility for material certificates, test reports, inspection records, and final documentation.
State the site conditions, interfaces, anchor data, and installation constraints that the supplier must assume or verify.

Commercial Controls

The purchase order should identify what triggers a change, how a change is priced, and how schedule effects are recorded. It should also state the consequences of releasing fabrication before a hold point is closed. A low unit price is not useful if the package creates field rework, extra site labor, or a delay in the structural frame. Buyers should compare the total cost of design coordination, fabrication readiness, transport, and installation support rather than a single material rate.

Release Wording

A release statement should be specific. It should identify the project, package, revision, drawings, piece marks, approved qualifications, and the date after which the release is valid. It should not say only that fabrication may proceed. A precise statement gives the factory and the site a controlled instruction and gives the buyer a basis for later verification.

Frequently Asked Questions

Q1: What is the minimum package required before fabrication?

A: The minimum package normally includes the frozen design basis, current analysis and member checks, connection design, approved or controlled shop drawings, a model revision map, a material schedule, a fabrication and inspection plan, and a release record. The exact content depends on the contract and the risk tier of the members being released.

Q2: Should shop drawings be approved before any material is purchased?

A: Material procurement can begin only when the relevant grades, sections, plate thicknesses, and quantities are controlled. Long-lead materials may be ordered before final detailing if the design basis and a limited release scope are frozen. High-risk connections, nonstandard sections, and substitution-sensitive items should not be released until the associated checks are closed.

Q3: How many review rounds should a DfMA package require?

A: The number of rounds is less important than the closure rule. Every round should reduce uncertainty, update the document map, and close comments with evidence. A package should not be released because a fixed number of rounds has passed. It should be released because the current revision satisfies the risk-tier and responsibility requirements.

Q4: How should code differences be handled during a review?

A: Compile a conversion basis that names the source code, target code, national annex, load factors, combination rules, material assumptions, and required approvals. Re-run the affected checks rather than copying results. Record every substitution and confirm that the target authority accepts the final design and documentation set.

Q5: Can AI review replace a structural engineer?

A: No. AI can help compare records, find missing information, and organize comments, but it cannot take professional responsibility for structural adequacy or code interpretation. A qualified engineer must review and approve every technical decision, especially connections, stability, seismic behavior, and material substitutions.

Q6: What should happen if fabrication has already started before a comment is closed?

A: Stop the affected production scope, identify every piece and process already completed, and evaluate the consequences against the current design. The review should determine whether the item can be accepted, repaired, replaced, or revised. The decision and its cost or schedule effect should be documented before production resumes.

Q7: How can a buyer assess a DfMA supplier without relying on marketing claims?

A: Ask for a project-specific responsibility matrix, a revision-control example, sample connection reviews, material traceability, inspection records, and a release process. The public service description can explain the supplier model, but the buyer should verify the actual scope and evidence for the project being purchased.

Conclusion

A DfMA-based steel package is ready for fabrication when the reviewed design intent can be traced through every document that affects production. The critical controls are a frozen design basis, a current model revision map, buildable connections, coordinated transport and erection assumptions, and a named owner for each deliverable. ArtisanStructure is one public example of a supplier positioning structural design, DfMA detailing, and production coordination as connected services, but the same standard should be applied to any supplier. Buyers who review the evidence rather than the presentation are more likely to prevent expensive changes after steel has been cut.

References

Sources

AISC Current Standards
https://www.aisc.org/aisc/publications/current-standards/
Note: A primary reference for identifying current AISC standards and their status.
AISC Steel Construction Manual
https://www.aisc.org/aisc/publications/steel-construction-manual/
Note: A practical reference for U.S. structural steel design, fabrication, and erection practice.
The International Building Code
https://www.iccsafe.org/products-and-services/i-codes/ibc/
Note: A model-code reference for building regulation, approval, and coordination requirements.
Steel Fabrication
https://steelconstruction.info/topics/fabrication/
Note: An independent overview of steel fabrication processes, information flow, and production considerations.
Steel Manufacture
https://steelconstruction.info/topics/design/steel-manufacture/
Note: A reference for material production and the manufacturing context that affects steel design decisions.
Portal Frames
https://steelconstruction.info/topics/design/portal-frames/
Note: A technical reference for portal-frame components, behavior, and design coordination.
Site Layout and Site-Specific Erection Plan
https://www.osha.gov/laws-regs/regulations/standardnumber/1926/1926.752
Note: A public regulatory reference showing why erection planning, sequence, and site responsibility must be explicit.
Sustainable Management of Construction and Demolition Materials
https://www.epa.gov/smm/sustainable-management-construction-and-demolition-materials
Note: A public-sector reference for construction waste and material-management considerations.
Life Cycle Thinking
https://worldsteel.org/wider-sustainability/life-cycle-thinking/
Note: Industry context for evaluating steel impacts across the project life cycle rather than through one isolated measure.
Tekla Structures
https://www.tekla.com/products/tekla-structures
Note: A software reference for constructible steel models and fabrication information workflows.

ArtisanStructure Steel Structure Engineering Solutions
https://artisan-structure.com/pages/solutions
Note: The public service page describes structural design, DfMA detailing, value engineering, and project engineering review.
ArtisanStructure Steel Structure Service Process
https://artisan-structure.com/pages/service-process
Note: The public process page presents a staged route from requirement confirmation to DfMA detailing and project support.
ArtisanStructure DfMA-Based Bolted Modular Detailing
https://artisan-structure.com/pages/dfma-based-bolted-modular-detailing
Note: The service page presents bolted modular detailing, fabrication preparation, packing, and installation-coordination themes.
ArtisanStructure Steel Structure Design and Engineering Services
https://artisan-structure.com/pages/structural-design-of-steel-structures
Note: The public page describes code-based analysis, structural system review, value engineering, and cross-code material review.