When the EOR Sends You Incomplete Structural Drawings

If you've been fabricating structural steel for more than a year, you've received a set of drawings that wasn't ready for the shop. Missing connection loads. Anchor bolt patterns marked "TBD." A note on the foundation plan that says "coordinate with structural engineer." Material grades unspecified. General notes that reference a standard detail sheet that wasn't included in the issue. Incomplete EOR packages are not a sign of a bad engineer — they're a sign of a construction industry that routinely issues structural drawings before all design decisions are finalized, because the schedule demands it. The question isn't whether you'll encounter incomplete drawings. It's whether you have a process for managing the gap without losing time, creating liability, or ending up with a shop drawing that has to be redone when the EOR finally issues the missing information. This guide gives you that process.

Why Incomplete EOR Packages Are the Norm, Not the Exception

The structural engineer of record is often working under the same compressed schedule you are. Owners push for IFC documents before the design is fully baked. GCs push for fabrication starts before anchor bolt layouts are confirmed by the civil or geotech. The structural package gets issued for bid — or even for construction — while connection design is still in progress, foundation details are pending civil coordination, or the lateral system is still being iterated against code requirements.

This isn't negligence in most cases. It's the math of a construction schedule where every discipline is overlapping with every other. AISC 360 leaves significant connection design latitude to the EOR, and many EORs exercise that latitude by issuing performance-based requirements — "design connections for the loads shown, LRFD, AISC 360-22" — without working it all the way through. You're left holding a structural package that tells you what the members are but not how they connect, what the slab elevation is but not what embeds it requires.

The firms that lose time on this are the ones that wait for a complete package before doing anything. The firms that create liability are the ones that proceed on assumptions without documenting them. The firms that win are the ones with a systematic approach to identifying the gap, logging it, proceeding intelligently, and protecting themselves when the EOR finally catches up.

The Most Common Missing Information Categories

After working through hundreds of structural packages, the gaps tend to cluster in predictable places.

Connection loads not called out. The framing plan shows a W18x35 beam framing into a W14x99 column. No connection load. No end reaction. The general notes say "all connections AISC minimum unless otherwise noted." That's not enough to detail a shear tab, let alone design a moment connection. You need the governing load combination and whether the connection is shear-only, moment, or needs to transfer axial.

Anchor bolt patterns not finalized. The column schedule shows the base plate size, but the anchor bolt layout says "by others" or references a foundation drawing that hasn't been issued. You can't order anchor bolts, and you can't set sleeves until this is resolved. On projects with cast-in-place foundations, this gap has a hard stop tied to pour dates.

Foundation details not issued with the structural set. The structural drawings reference "see civil/foundation drawings" for embed locations, but the foundation package is on a separate issue cycle. Miscoordination here is where serious field problems come from — embeds in the wrong location, anchor bolts at the wrong projection, slab penetrations not aligned with steel.

Material grade not specified. Members listed without a material callout. Is that HSS4x4x1/4 A500 Grade B or Grade C? Is the plate A36 or A572-50? On seismic work in higher SDC categories, this matters for expected strength calculations. Even on non-seismic work, it affects weld procedure selection under AWS D1.1.

Notes that say "coordinate with fabricator." This one is almost a joke at this point. "Embed plate size and location — coordinate with fabricator and EOR." That note accomplishes nothing. It doesn't tell you who owns the design, what the load is, or what the tolerance band is. It creates a loop where you're waiting on the EOR, the EOR thinks you're handling it, and the GC is wondering why the embeds aren't on the pour drawing.

How to Document What's Missing: The Information Gap Log

Before you can manage the gap, you have to map it. A simple information gap log — a running list of every piece of missing or incomplete information required to produce detailing-ready shop drawings — is the foundation of gap management.

The log should capture: the drawing or specification reference, a description of what's missing, the responsible party (EOR, civil, owner, geotech), the date identified, the date RFI'd, and the status. Run it as a live document that your detailer and PM both have access to. Update it every time something gets resolved.

The gap log serves two functions. First, it keeps the project moving — you know exactly what you're waiting on and can sequence work around open items. Second, it's a contemporaneous record of what information was unavailable at what point in time. If a shop drawing has to be revised because the EOR issued a revised anchor bolt layout after you'd already proceeded on the original, the log shows when you knew, when you asked, and when you got an answer.

How to Write an RFI That Gets Answered Quickly

Most RFIs that go unanswered or get vague responses are poorly written. An effective structural RFI states the specific drawing reference, the specific information gap, the impact on fabrication or detailing progress, a proposed resolution with a yes/no ask where possible, and a response-needed date tied to a real schedule milestone.

Vague RFIs get vague answers. "Please clarify connection at grid B-4" gets you nothing. "Connection at B-4, W16x26 beam to W12x53 column: no end reaction called out on S-201. We require the governing LRFD shear demand to finalize the connection. Proposed: design for maximum uniform load reaction per AISC minimum, approximately 22 kips. Please confirm or provide governing demand. Response required by [date] to maintain [milestone]." That RFI gets answered.

A full breakdown of RFI writing for structural information gaps will be covered in an upcoming post.

When to Start Work vs. When to Wait: The Risk Calculus

Not every gap should stop the clock. Some items can be assumed with low risk; others require a confirmed answer before you put a detailer on the work.

Low-risk assumptions — where proceeding makes sense — typically involve items where the range of possible answers is narrow and the cost of being wrong is a minor revision. Using ASTM A992 for W-shapes where the grade isn't specified, for example, is a reasonable assumption for almost any commercial building application. Designing shear connections for the maximum reaction of the spanning member using AISC minimum is defensible in most cases.

High-risk items — where you should wait — are those where a wrong assumption would require significant rework or where the design decision is genuinely open. Anchor bolt patterns are the clearest example. If the EOR hasn't resolved the hold-down design, proceeding exposes you to rework on base plates, bolt sizing, and potentially the foundation drawing itself.

The calculus is: what's the cost of waiting vs. the cost of being wrong? If waiting two days for an RFI response avoids four hours of rework plus a revision cycle, you wait.

How to Protect Yourself When You Proceed on Assumptions

When you do proceed on engineer assumptions, document them explicitly. A stated assumption in a submittal transmittal — "Connection loads not provided; designed for [X] kips per AISC minimum" — puts the EOR on notice. If they stamp and return without comment, you have implied confirmation. If they catch it in review and issue a correction, you have a documented basis for a change order if the correction requires rework beyond a minor revision.

Do not bury assumptions in drawing notes that reviewers are likely to miss. Call them out in the submittal cover letter or transmittal, in bold if necessary. The goal is to make it impossible for the EOR to say they didn't know what assumption you were working from.

Keep a revision-cause log as well. When a shop drawing revision is triggered by EOR information that wasn't available at the original submittal, tag it. That's the paper trail for scope creep claims.

What a Good Detailing Partner Does When the EOR Package Isn't Ready

A detailer who just waits for a complete package is a liability on a tight schedule. A detailer who charges ahead without documenting assumptions is a liability in a different way. The right approach is structured, proactive gap management.

That means doing the gap log on day one. It means triaging the package on receipt — before a detailer opens Tekla — to identify every open item and classify it by risk and blocking status. It means writing clean, specific RFIs immediately, not after two weeks of waiting. It means sequencing detailing work to advance everything that isn't blocked while maintaining visibility on what is.

It also means staying in contact with the fabricator's PM, not just sending RFIs into the void. If the EOR is slow to respond, the PM may have a direct line through the GC. If the anchor bolt layout is holding up a foundation pour, the GC has a lot more leverage on the EOR's response time than any RFI does.

How NRSteel Handles the Missing-Information Workflow

On every new project, NRSteel runs a package intake review within the first 48 hours. We log every information gap against the drawing index, classify each item by risk and schedule impact, and issue an initial RFI package to the fabricator's PM before detailing begins. That gives you a clear picture of where the EOR package stands, what you're waiting on, and what we can advance immediately.

We carry the gap log through the life of the project — updating status in real time, tracking revision causes, and flagging anything that's trending toward a schedule impact before it becomes one. When we're working against an incomplete EOR package, you're not finding out about a problem when a shop drawing comes back with a major revision mark. You're finding out when we first identify the gap, with a proposed resolution already in hand.

Because we're NC-based and in the same timezone, that communication happens in real time — not the next morning after an overnight handoff. If something breaks loose on a Friday afternoon, we're available. That's not a marketing line. It's just how a detailing partnership should work.

If you're evaluating detailing partners for your next project — especially one where the structural package isn't fully baked — contact NRSteel for a scope review. We work exclusively with fabricators on commercial and institutional structural projects, and managing the upstream information gap is part of the service, not an afterthought.