Who Checks Component Shop Drawings on a Job?

Who Checks Component Shop Drawings on a Job?

Written by

in

A component package can be technically sound, fully modeled, and ready for production, yet still create expensive field problems if the wrong person assumes someone else checked it. So, who checks component shop drawings? The short answer is: several parties do, but each checks for a different purpose. Clear ownership is what prevents an approval stamp from becoming a false sense of security.

For trusses, wall panels, floor systems, steel connections, engineered wood, and other prefabricated building components, the review path must be defined before drawings hit the shop floor. The manufacturer checks design and production readiness. The contractor checks coordination and constructability. The design team checks conformance with the contract documents. Where delegated engineering applies, the component engineer checks the engineered design within that scope.

Who Checks Component Shop Drawings First?

The component manufacturer or fabricator is the first line of defense. This is not a courtesy review. It is the quality gate that determines whether a component can be built accurately, delivered on time, and installed without forcing the field to solve a design problem.

Inside a well-run component operation, that review usually includes the component designer, a checker or senior designer, production leadership, and, when required, the engineer responsible for the delegated design. The exact workflow varies by plant size, software, project risk, and component type. But the principle does not change: no drawing should move from design to production based on a single set of eyes when the project carries meaningful structural, scheduling, or liability exposure.

The internal team checks the inputs that drive the design: architectural plans, structural plans, specifications, loading information, bearing conditions, elevations, connection requirements, and applicable design criteria. They also verify that the drawing package communicates what production and installation need to know, not merely what design software generated.

For roof trusses, this may include spans, pitches, profiles, concentrated loads, girder locations, bearing widths, web conflicts, bracing notes, and truss-to-truss relationships. For wall panels, it can include framing layouts, opening locations, hold-downs, headers, sheathing, hardware, transport limits, and installation sequencing. A clean model does not automatically equal a buildable component.

The General Contractor Checks Coordination

The general contractor typically manages the submittal process and routes component shop drawings to the appropriate reviewers. The GC’s role is central because components touch the entire job: foundations, structural steel, masonry, mechanical systems, fire protection, architectural finishes, crane access, and sequencing.

A contractor review should focus on whether the package fits the actual project conditions. Are dimensions consistent with the latest plans? Are field measurements available where they need to be? Do bearings exist where the component design assumes they exist? Are openings, pockets, embeds, and connections coordinated with adjacent work?

This is where many avoidable failures begin. A truss drawing may satisfy the supplied framing plan, but the supplied plan may be outdated. A wall panel layout may be structurally correct, but it may block a mechanical chase or arrive before the site is ready to receive it. The GC is best positioned to identify those project-wide conflicts before they become field rework.

That said, contractor review does not transfer component design responsibility to the GC. The contractor coordinates the work. The manufacturer and delegated engineer remain responsible for the work within their stated design and engineering scope.

The Architect and Engineer Review for Conformance

The architect and engineer of record are commonly part of the shop drawing review path, but their review has limits. In most project delivery structures, they review submittals for general conformance with the design intent and contract documents. They are not re-designing every component or taking over the fabricator’s means, methods, production details, or delegated engineering responsibilities.

The engineer of record may review critical items such as loads, reactions, bearing assumptions, connection concepts, diaphragm requirements, lateral-force-resisting elements, and interface conditions with the primary structure. The architect may focus on dimensions, appearances, openings, elevations, finish requirements, and alignment with the architectural set.

Approval language matters. A stamp marked “reviewed,” “approved as noted,” or “no exceptions taken” is not a blanket guarantee that every dimension, connection, or fabrication detail has been independently verified. The contract documents, submittal requirements, and local code determine the actual scope of review.

For this reason, component manufacturers should never treat a design professional’s submittal stamp as a replacement for their own internal checking process. It is an important control point, not a handoff of accountability.

Delegated Design Changes the Review Path

Many component systems involve delegated design. Roof trusses are a familiar example, but the same model can apply to engineered wood, cold-formed steel framing, precast connections, stairs, rails, specialty supports, and other systems.

Under delegated design, a licensed specialty engineer may design and seal the component package within a defined scope. That engineer checks the structural adequacy of the component design based on the project criteria and information provided. The engineer of record then reviews the delegated submittal for compatibility with the overall building design.

This division of responsibility only works when the scope is explicit. If loading criteria are missing, bearing conditions are vague, or the plans contain conflicts, the delegated engineer cannot safely fill gaps through assumption. Questions must go back through the established RFI and submittal process. Fast production is valuable. Fast production based on unverified inputs is exposure.

What Each Reviewer Should Actually Check

A strong review process assigns reviewers to the decisions they can truly validate. Blurring those roles slows approvals and creates gaps at the same time.

The component design team should validate design criteria, member geometry, calculations, connections, production feasibility, and clear component documentation. The production team should verify manufacturability, plate or hardware availability, cutting and assembly concerns, handling limits, and labeling requirements.

The contractor should confirm field conditions, dimensions, installation access, sequencing, trade coordination, and alignment with the current construction schedule. The design team should confirm that the package conforms to the design intent, contract requirements, and overall structural system. The delegated engineer should confirm engineered adequacy within the assigned scope.

On complex jobs, the installer also deserves a formal review point. Install crews often catch practical issues that are invisible in plan view: crane picks, panel set order, temporary bracing access, connector reach, and tolerance conflicts. Their feedback is most valuable before fabrication, not after trucks are loaded.

Approval Is Not the Same as Ready for Fabrication

One of the most damaging habits in component production is treating “approved” as a universal release signal. A drawing may be approved by the architect with notes, still awaiting a field dimension, or dependent on an unresolved RFI. It may be structurally engineered but not yet coordinated with the latest mechanical layout. It may be ready to price but not ready to cut.

Plants need a release status that is operationally precise. For example, a package can be classified as design complete, internally checked, submitted, approved as noted, released for production, or held pending clarification. The labels are less important than the discipline behind them.

A release gate should identify the current drawing revision, required approvals, open questions, engineering status, material availability, delivery sequence, and site-readiness constraints. This protects production teams from building yesterday’s design and protects project managers from promising dates against incomplete information.

The Workflow That Protects Margin and Schedule

The best component operations do not rely on heroic checking at the end of the process. They build review into the workflow from estimating through fabrication.

At handoff, the estimator or project manager should document the design assumptions made during pricing. During design, the component team should flag missing criteria and contradictions immediately, not bury them in a later submittal. Before release, an independent checker should review the highest-risk conditions: unusual loads, long spans, complex rooflines, transfer conditions, nonstandard bearings, multi-trade interfaces, and revisions made under deadline pressure.

Capacity plays a direct role here. When a plant’s design team is overloaded, checking becomes the first task squeezed by the next bid deadline or production emergency. That is not a quality problem caused by careless people. It is an operating-capacity problem. Dedicated technical production support, including experienced offshore component designers and checkers, can keep review moving without forcing your in-house leaders to choose between bid velocity and drawing control.

All Points Technical was built around that reality: specialized teams can extend design capacity, maintain 24-hour workflow continuity, and give component businesses the room to check work properly before it reaches the floor.

Make the Review Path Visible Before the First Submittal

The fastest path through component approvals is not fewer reviewers. It is a visible sequence of reviewers with defined authority, current inputs, and a firm release rule. Put the responsibility matrix in the project kickoff documentation. Identify who submits, who reviews, who resolves comments, who can authorize revisions, and who gives the final production release.

When that structure is in place, component shop drawings stop being a stack of paperwork moving between inboxes. They become a controlled production document that protects installation, schedule, and margin. That is the standard serious component operations should demand before the first board is cut.

Comments

Leave a Reply

Your email address will not be published. Required fields are marked *