The technical failures that stall projects at the finish line — and the disciplined documentation practices that eliminate them.

You are weeks, sometimes months, into a project. The design is resolved, the architect’s drawings are complete, the structural engineer has delivered their package, and the permit application has been submitted. Then the plan check correction notice arrives — dense with technical citations, referencing code sections you have never encountered, and itemizing deficiencies across a drawing set that your entire professional team believed was ready.

This moment is familiar to far more developers, homeowners, and project managers than the industry comfortably acknowledges. Structural drawing rejections at plan check are common, consequential, and — in the majority of cases — entirely preventable. They are not the result of arbitrary reviewer preferences or bureaucratic capriciousness. They are the result of identifiable, recurring technical deficiencies that a rigorous documentation practice eliminates before submission.

This post explains precisely what those deficiencies are, why they occur, and what professional standard of practice looks like when the goal is a first-round approval.

What Plan Check Reviewers Are Actually Evaluating

To understand why structural drawings fail, it helps to understand the lens through which they are reviewed. A plan check structural engineer — licensed, experienced, and working from a defined checklist — is verifying one central proposition: that the structural drawings demonstrate, with sufficient technical specificity, that the proposed structure will safely resist all applicable loads in compliance with the adopted building code and its local amendments.

This is not a subjective assessment. It is a technical verification against an explicit standard. The reviewer is not evaluating aesthetic choices or construction methodology preferences. They are checking whether your calculations are complete, whether your drawings are coordinated, whether your code references are current, and whether every structural element in the building has been explicitly accounted for and designed.

When drawings fail this verification, a correction notice is issued. When they pass, a permit is approved. The path from the former to the latter is entirely a function of documentation quality.

The Most Common Reasons Structural Drawings Are Rejected

Insufficient or missing structural calculations

Structural calculations are the mathematical backbone of the structural drawing set. They demonstrate, element by element, that every beam, column, shear wall, connection, and foundation is adequate for the loads it must carry. A plan check reviewer will not approve a drawing set that lacks the calculations to support it.

The most frequent calculation deficiencies fall into several patterns. Gravity load calculations that address beam and column sizing but omit foundation design — leaving the reviewer unable to verify that the soil bearing capacity is adequate for the imposed loads. Lateral analysis that is referenced on the drawings but not included in the calculation package. Load path narratives that describe how loads travel from roof to foundation in general terms but do not provide the step-by-step numerical verification that confirms adequacy at each transfer point.

A complete calculation package is not a summary — it is a rigorous, organized, and fully cross-referenced body of mathematical work that a reviewer can follow from loading assumptions through member design to foundation adequacy without encountering gaps.

Incomplete or ambiguous connection details

Connection details are among the most scrutinized elements of a structural package, and among the most frequently deficient. A structural drawing that specifies a beam size without specifying how that beam connects to its supporting element — the fastener type, size, spacing, number, and embedment — is an incomplete drawing. The reviewer cannot verify adequacy from intent. They verify from specifics.

Common connection detail failures include: moment connections shown schematically without the welding specifications or bolting patterns required for verification; hold-down anchors called out by product designation without the installation details and embedment depths required for code compliance; post-base and column-cap connections specified by hardware model number without the loading verification that confirms the selected hardware is adequate for the actual design loads; and shear transfer details at diaphragm boundaries that show a concept without the nail schedules, strapping specifications, and blocking details required to confirm load transfer.

The standard is unambiguous: every connection that transfers a structural load must be detailed with sufficient specificity that a licensed contractor can build it correctly and a plan checker can verify its adequacy without inference.

Lateral force-resisting system deficiencies

The lateral force-resisting system (LFRS) — the collection of shear walls, moment frames, braced frames, and diaphragms that resist wind and seismic loads — is one of the most technically demanding and most frequently deficient aspects of residential and light commercial structural packages.

Lateral system deficiencies take several forms. Shear wall schedules that specify wall lengths and nailing but omit the hold-down forces and the hold-down hardware specifications required to prevent the wall from overturning. Diaphragm designs that confirm in-plane shear capacity but do not address collector elements — the members that gather distributed diaphragm forces and deliver them to the shear walls. Irregularity analyses that are required by code for certain building configurations but are simply absent from the submission.

In seismic design categories C through F — which apply to a significant portion of the United States — the lateral analysis requirements are detailed and unforgiving. A structural package that does not address them comprehensively will not pass plan check.

Foundation design inconsistencies and omissions

Foundation deficiencies are among the most consequential structural plan check failures, because they are often the result of a disconnect between the structural engineer and the geotechnical (soils) engineer whose report should be informing the foundation design.

Specific failures include: foundation designs that do not reference or incorporate the recommendations of the geotechnical report, or that use bearing pressure assumptions different from those in the report; continuous footings that are sized for gravity loads but do not account for the uplift forces generated by the lateral system above them; spread footings under shear wall hold-downs that are designed for bearing only, without the tension reinforcing required to resist the hold-down anchor’s uplift load; and grade beam designs that do not address the soil expansion or liquefaction conditions identified in the geotechnical investigation.

A structurally complete foundation package traces a continuous path from the geotechnical report’s recommendations through the foundation design to the connection details that transfer loads from the superstructure above.

Code edition and local amendment non-compliance

This category of failure is administrative in appearance but consequential in practice. Structural drawings that cite the wrong code edition — an outdated IBC, ASCE 7, or ACI 318, for example — or that fail to acknowledge and comply with the jurisdiction’s local amendments will be flagged regardless of the technical quality of the structural design itself.

Local amendments are not footnotes. Many jurisdictions have adopted substantive modifications to the model codes that affect seismic design parameters, wind speed maps, snow load requirements, or specific detailing standards. California’s CBC, for instance, incorporates amendments to the IBC that affect structural design in ways a practitioner working from the model code alone would miss. New York City’s Building Code diverges from the IBC on multiple structural provisions. These are not obscure technicalities — they are the governing standard in their respective jurisdictions, and a structural package that ignores them will be rejected.

Coordination failures between structural and architectural drawings

A plan check reviewer reviews the full permit package — architectural and structural together. Discrepancies between the two sets are identified and cited as correction items, because a discrepancy means that one or both sets are wrong, and the reviewer cannot proceed on ambiguous documentation.

Common coordination failures include: beam sizes on structural drawings that are incompatible with the ceiling heights or floor-to-floor dimensions on architectural drawings; columns shown on structural plans that do not appear on architectural floor plans; shear wall locations on structural drawings that conflict with door and window openings on architectural drawings; and foundation plans that do not match the building footprint on the architectural site plan.

These failures are not the result of individual incompetence — they are the result of a process in which architectural and structural drawings are produced in parallel without a formal coordination and cross-check step before submission. BIM-based workflows, when properly implemented, catch most of these conflicts automatically. Firms working in 2D CAD must implement manual coordination protocols to achieve the same result.

Why These Failures Occur — The Systemic Root Causes

Understanding individual deficiencies is useful. Understanding why they occur is more useful, because it points to the practice-level changes that prevent them.

Schedule compression at the documentation phase

Construction documentation is the phase most frequently subjected to schedule pressure, and the phase in which quality is most sensitive to it. When the CD phase is compressed — because earlier phases ran long, because a contractor’s mobilization window is creating external pressure, or because a client is eager to break ground — the quality-control steps that catch deficiencies before submission are the first casualties. Calculation reviews are abbreviated. Coordination checks are skipped. Details are left incomplete with the intention of resolving them “in the field.”

Plan check is an unforgiving environment for this approach. Reviewers are not construction partners who will work through ambiguities collaboratively. They cite deficiencies and return the package.

Late or inadequate structural consultant engagement

Structural engineers engaged late in the documentation process — brought in after the architectural drawings are substantially complete rather than during design development — produce less well-integrated structural packages. They are responding to an architectural design rather than participating in it, which means structural requirements that could have informed design decisions instead drive revisions. The resulting packages are more likely to contain coordination conflicts and more likely to require multiple rounds of revision before the structural drawings are ready for submission.

Insufficient internal quality control

The most preventable cause of plan check rejection is the absence of a formal internal review process before submission. A senior engineer reviewing the package against the jurisdiction’s published structural plan check checklist — available from most building departments — will identify the majority of correctable deficiencies before a reviewer sees them. Firms that do not conduct this review are, in effect, using the plan check process as their quality control, at the expense of the client’s schedule and holding costs.

What a First-Round Approval Actually Requires

A structural package that achieves first-round approval is not an exceptional document — it is a complete one. The standard it must meet is explicit and knowable. The following are the non-negotiable elements.

A complete, organized calculation package that addresses all gravity loads, all lateral loads, all foundation elements, and all critical connections, with clear cross-references between calculations and the corresponding drawing details.

Fully detailed connection specifications for every structural load transfer — beams to columns, columns to foundations, shear walls to diaphragms, hold-downs to foundations — with hardware designations, installation specifications, and the loading verification that confirms the selected hardware is adequate.

A complete lateral system design including shear wall schedules with hold-down forces and hardware, diaphragm design with collector element design, and irregularity analysis where required by code.

A foundation design that references and incorporates the geotechnical report, addresses both gravity and uplift conditions, and details the connection to the lateral system above.

Current, jurisdiction-specific code references throughout the drawing set and calculation package, with explicit acknowledgment of applicable local amendments.

A formal coordination review confirming that structural and architectural drawings are consistent in all respects before submission.

Insider Tips: What Professional Firms Do Differently

Download and work from the jurisdiction’s structural plan check checklist. Most building departments publish the checklist their reviewers use. Firms that prepare submissions against this checklist — rather than against a generic internal standard — produce packages that align with what reviewers are looking for. This is not gaming the system; it is understanding the standard and meeting it.

Assign a senior engineer to a pre-submission package review. The single most effective quality-control step available is a senior review by someone other than the engineer who produced the package, conducted against the plan check checklist before submission. This review will identify the majority of correctable deficiencies at a cost that is a fraction of a single correction cycle.

Resolve all architectural-structural coordination issues before submission, not after. A formal coordination meeting between the architect and the structural engineer of record, conducted on the near-final package, is standard practice on well-run projects. The cost is a few hours of professional time. The benefit is a submission that does not generate correction notices from coordination conflicts.

Include a structural narrative for complex or unusual systems. On projects with non-standard structural systems — long-span structures, transfer structures, significant lateral irregularities, or innovative materials — a written structural narrative that explains the design approach, identifies the governing code provisions, and summarizes the analysis methodology is not required, but it is valuable. It gives the reviewer context, reduces the likelihood of misinterpretation, and signals a level of professional thoroughness that experienced reviewers notice.

Do not submit under time pressure. A premature submission that generates a correction notice adds more time to the overall schedule than the days saved by submitting early. If the package is not ready, the correct decision is to take the additional time required to complete it properly. Every correction cycle costs weeks. The difference between a ready and an almost-ready submission is not a few days — it is the difference between one review cycle and two or three.

The Cost of Getting It Wrong

A single structural plan check correction cycle in a major metropolitan jurisdiction typically adds four to eight weeks to the pre-construction timeline. A second correction cycle adds another four to eight. The carrying costs on a commercial project or a luxury residential development during this period — financing, holding costs, contractor delays, material escalation — are real, measurable, and in virtually every case significantly exceed the professional fees that would have produced a complete submission in the first place.

There is also the less quantifiable but equally real cost of professional credibility. Contractors who receive late-released structural drawings revise their pricing. Lenders who see permit delays ask questions. Repeat clients who experience correction cycles on multiple projects begin looking for other firms. The downstream consequences of plan check failures extend well beyond the correction notice itself.