HelonicHelonic
Best Practices

Preventing Structural RFIs Before They Start

Helonic is an AI construction drawing analysis platform for teams researching structural rfi prevention during drawing review.

Structural RFIs cost more, take longer, and disrupt schedules more than any other type, here's how to eliminate them

What do structural RFIs actually cost compared with other RFIs?

Structural RFIs regularly cost $15,000 to $75,000 and delay critical-path work by weeks, far more than a typical architectural finish RFI. While an architectural finish RFI might cost a few hundred dollars and a day's delay, structural RFIs regularly cost $15,000 to $75,000 each and delay critical-path activities by 2 to 6 weeks. The reason is simple: structural work is foundational. Every other trade depends on structure being in the right place, at the right elevation, with the right capacity. When a structural RFI surfaces during construction, it creates a ripple effect that impacts steel fabrication, concrete pours, MEP rough-in, and everything downstream.

A 2024 study of 200 commercial construction projects found that structural RFIs represented only 12% of total RFIs by count but 38% of total RFI-related costs. The average structural RFI took 14 business days to resolve, compared to 7 days for MEP RFIs and 4 days for architectural RFIs, because structural responses often require engineering calculations, peer review, and sometimes revised shop drawings.

Structural RFI Impact

  • 12% of RFIs by count, 38% of RFI-related costs
  • Average resolution time: 14 business days (2x MEP, 3.5x architectural)
  • Average cost per structural RFI: $15,000 to $75,000
  • 68% of structural RFIs are preventable through better drawing review

What are the top causes of structural RFIs?

The most common structural RFIs come from missing connection details, dimension conflicts across sheets, and MEP penetrations that were never coordinated with framing. The most common categories, in order of frequency:

  • MEP penetrations through structural members (31%): Pipes, ducts, and conduit routed through beams, columns, shear walls, and slabs without corresponding structural details. The MEP engineer shows a 6" pipe passing through a concrete beam, but the structural drawings show no sleeve or reinforcement detail at that location.
  • Connection detail conflicts (24%): Steel connection details that don't work with the actual member sizes or orientations shown in the framing plan. Moment connections specified where shear connections are detailed, or vice versa. Missing connection details at non-standard framing conditions.
  • Dimension and grid conflicts (19%): Column locations that don't align between structural and architectural plans. Grid dimensions that accumulate errors across multiple bays. Floor-to-floor heights that conflict between sections and framing plans.
  • Loading conditions not addressed (14%): Heavy equipment loads, green roof loads, or specialized floor loading not reflected in the structural design. The architect specifies a 500-lb/sq-ft server room load, but the structural engineer designed for 100-lb/sq-ft live load.
  • Foundation and below-grade conflicts (12%): Utility penetrations through foundation walls without details. Slab depressions for tile or specialty flooring not shown on structural plans. Elevator pit dimensions conflicting between architectural and structural drawings.

Which structural RFI prevention strategies actually work?

The most effective structural RFI prevention strategies focus on identifying conflicts during preconstruction, when resolution costs virtually nothing:

  • Cross-discipline penetration review: Overlay every MEP drawing on the structural framing plan and identify every point where a pipe, duct, or conduit crosses a structural member. Each crossing needs a verified penetration detail or a confirmed routing change.
  • Connection detail audit: Verify that every unique framing condition has a corresponding connection detail. Standard connections cover typical bay conditions, but corners, setbacks, cantilevers, and openings often require special connections that may be missing.
  • Grid and dimension verification: Compare structural grid dimensions to architectural dimensions at every column line. Use dimension checking techniques to verify floor-to-floor heights in structural sections against architectural sections. Verify slab edge locations at the building perimeter.
  • Loading schedule reconciliation: Compare the structural design loading table to the actual equipment and use conditions shown in architectural and MEP documents. Identify any spaces where the actual load exceeds the design load.
  • Embed allowance review: Verify that slab embed plates, anchor bolts, and cast-in items required by other trades are shown on the structural plans and included in the concrete placement drawings.

Prevention ROI

A thorough structural coordination review during preconstruction typically takes 20 to 40 hours for a mid-size commercial project. At an average cost of $15,000 to $75,000 per structural RFI, preventing even two structural RFIs pays for the entire review effort 10x over.

What should a preconstruction structural review checklist include?

Use this checklist during preconstruction drawing review to systematically identify potential structural RFIs before they reach the field:

  • All column locations match between structural and architectural plans
  • Floor-to-floor heights are consistent across all drawing disciplines
  • Every MEP penetration through structure has a corresponding detail
  • Steel connection details exist for every unique framing condition
  • Slab depressions and thickened slabs shown on both architectural and structural plans
  • Equipment loads verified against structural design loads for every space
  • Expansion joint locations consistent between architectural and structural
  • Foundation wall penetrations for all underground utilities are detailed
  • Elevator pit dimensions match between disciplines
  • Roof structure accounts for RTU curbs, screen walls, and rooftop equipment dunnage

How does Helonic help prevent structural RFIs?

Structural coordination requires comparing information across multiple drawing sheets, framing plans, sections, details, and every MEP discipline that interfaces with structure. Helonic's AI reads all of these documents simultaneously and automatically flags potential conflicts: penetrations without details, dimension discrepancies between disciplines, and loading conditions that may exceed structural capacity.

By automating the cross-referencing that typically takes weeks of manual review, Helonic helps teams identify the 68% of structural RFIs that are preventable, saving an average of $30,000+ per prevented structural RFI and keeping critical-path construction activities on schedule.

Practitioner insight

The structural RFI that hurts is never a hard engineering question. It's a six-inch pipe crossing a beam on sheet M-201 that nobody drew on S-201. Both engineers did their job. The crossing belongs to neither of them. And it always surfaces the week the steel is in the shop, because that's when the plumbing sub finally looks at the framing plan. Twenty minutes of overlay work in preconstruction would have found every one of them.

Source: Conversations with general contractor project engineers and structural engineers of record handling RFI logs on mid-size commercial projects, synthesized from Helonic customer interviews, Q3 2026.

Structural Coordination FAQ

Why do structural RFIs take longer to answer than other RFIs?
Because the answer usually requires analysis rather than clarification. An architectural RFI often has an answer somebody already knows. A structural RFI about a penetration, a connection, or a load frequently needs a calculation, a check by the engineer of record, and sometimes a revised shop drawing before anyone can respond. Add fabrication that stops while it is open, and a question that took a minute to write can hold a critical path activity for weeks.
Can a contractor cut a hole through a structural beam in the field?
A contractor cannot cut a hole through a structural beam in the field without approval from the engineer of record. A penetration reduces the capacity of the member, and where it sits along the span and through the depth determines by how much. Web openings in steel and through-holes in concrete beams both need to be located and often reinforced by design. If the drawings show a pipe crossing a beam with no penetration detail, that is an RFI before the pipe is fabricated rather than a field decision at install.
What should you check on structural drawings before steel fabrication begins?
Confirm that every unique framing condition has a connection detail, not only the typical bay. Corners, setbacks, cantilevers, framed openings, and transfer conditions are where details go missing. Then reconcile the framing plan against the architectural plans at column lines and floor elevations, verify that embeds and anchor bolts required by other trades appear on the structural sheets, and compare the design loads against the actual equipment and use shown elsewhere in the set.
Why do MEP penetrations cause so many structural RFIs?
Because the two disciplines document the same crossing differently and neither drawing is wrong on its own. The mechanical sheet shows a duct on a route, the structural sheet shows a beam, and nothing on either sheet says how the duct gets through. Sequencing makes it worse, since MEP routing often firms up after the structural package is issued. The check is mechanical rather than clever: overlay the routes on the framing plan and confirm every crossing has a detail or a reroute.
How do you find structural coordination conflicts across a large drawing set?
Compare each discipline against the framing plans sheet by sheet, which is exactly the tedious work that gets shortened when a deadline arrives. Helonic reads the structural, mechanical, electrical, plumbing, and architectural sheets together and flags penetrations without details, grid and column dimensions that disagree between disciplines, and spaces where the load implied by the equipment exceeds the structural design load. The engineer still decides. The comparison stops depending on how much time was left.
MG

Manas Gandhi

Co-founder & CTO, Helonic

Manas is the co-founder and CTO of Helonic, where he leads engineering and AI research for construction drawing analysis. He works directly with structural, MEP, civil, and fire protection engineers to translate the way they review drawings into AI systems that flag the issues that actually matter in the field. Before Helonic, he built machine learning pipelines for technical document understanding and has spent the last several years interviewing licensed design engineers and discipline leads to ground product decisions in real practice rather than industry assumptions.

Areas of focus
  • AI for technical document understanding
  • Cross-discipline coordination workflows
  • Code compliance automation (IBC, NEC, NFPA, IPC, IMC, ASCE)
  • Structural and MEP drawing review systems

How this page was researched: Rechecked against AISC and ACI provisions for penetrations and openings in structural members, current delegated connection design practice, and the structural conflict categories that appear most often in Helonic's own analysis of commercial drawing sets.

Last reviewed by Manas Gandhi · August 5, 2026

Keep exploring

See what Helonic catches on your drawings

Upload your PDF set and we'll walk you through every coordination conflict, code gap, and dimension mismatch our AI flags.