- Mon-Fri 9am-5pm
- [email protected]
If you are asking how to reduce RFIs in construction, start before construction begins. Most requests for information are not caused by a lack of effort. They often begin where two reasonable design decisions meet: a duct crosses a beam, a ceiling zone cannot fit all services, equipment lacks maintenance clearance, or a late architectural change affects several engineering systems at once.
For architects, the useful question is not simply, “How do we answer RFIs faster?” It is, “Which RFIs can we prevent by resolving interfaces earlier?”
That shift changes engineering coordination from a drawing-production task into a design-management tool.
For projects where MEP and structural interfaces are significant, InnoDez’s MEP engineering and structural engineering scopes can be coordinated around the same architectural constraints. On complex model-based projects, Autodesk’s overview of Model Coordination is a useful reference for understanding how model exchanges and automated clash detection can support—not replace—coordination decisions.
An RFI is useful when the contractor encounters a legitimate unknown. It becomes avoidable when the question could reasonably have been resolved during design.
Common examples include:
The recurring pattern is the interface between disciplines.
Not every square foot deserves the same coordination effort. Start where several systems compete for limited space or where a late change would have broad consequences.
Typical high-risk areas include corridors with congested ceilings, mechanical rooms, electrical rooms, shafts, kitchens, amenity areas, roof zones, transfer floors, and locations with deep structural members.
A risk-first review is often more useful than applying the same level of review everywhere.
Architects often carry constraints that may not appear as engineering criteria: a ceiling height must remain, a façade cannot accept a louver, a shaft cannot grow into a unit, or a service area is tied to leasing.
Identify those constraints explicitly. Engineers can then test routing, equipment, and structural impacts while options still exist.
The purpose is not to make architecture subordinate to engineering. It is to expose engineering consequences early enough to protect important design choices.
Modern coordination does not require every project to be modeled in BIM.
For straightforward work, well-managed AutoCAD drawings, disciplined backgrounds, standardized details, and structured review checklists can be efficient and appropriate.
For complex projects, Revit/BIM can add value by improving model-based coordination, visualizing spatial conflicts, and keeping related views aligned.
The right question is not “CAD or BIM?” It is which workflow gives the project enough coordination fidelity without unnecessary production overhead?
A permit-ready design can still create field questions. A constructability review asks additional questions:
These checks make drawings more useful for construction.
Significant design changes should be treated as multi-discipline events.
| Architectural change | Engineering impacts to review |
|---|---|
| Ceiling lowered | Duct depth, piping slope, lighting, sprinklers, access |
| Shaft moved | Plumbing stacks, duct risers, electrical feeders, structure |
| Unit layout revised | Diffusers, fixtures, panels, loads, framing |
| Roof equipment relocated | Structure, curbs, drainage, screening, service access |
| Wall type changed | Penetrations, fire/smoke interfaces, outlets, supports |
The point is not complicated software. It is disciplined coordination. Shared markups, digital issue tracking, BIM views, and repeatable checklists can make the process easier to manage.
AI-assisted tools can support repetitive review tasks such as comparing document sets, finding inconsistent notes, summarizing markup sets, identifying missing references, or searching large drawing/specification packages.
However, AI should support—not replace—engineering judgment. A tool may flag that two notes differ. A qualified engineer must determine which note is correct for the actual project.
The useful model is technology-assisted QA with engineer verification.
These questions are more useful than asking whether a project is “fully coordinated,” because coordination is not binary.
When engineering constraints are discovered late, architecture often absorbs the change: ceilings drop, shafts grow, rooms shrink, façades change, or visible components move.
Finding constraints earlier gives the team more options. That is why RFI reduction is not only a contractor benefit; it can also protect design quality.
No. Some RFIs are legitimate and unavoidable because site conditions, owner decisions, substitutions, and construction discoveries change. The goal is to reduce avoidable RFIs caused by unresolved design interfaces.
No. BIM is a coordination tool, not a substitute for decisions. It adds value when teams use it to identify, assign, resolve, and verify meaningful issues.
Early enough that major spatial, system, and structural decisions can still change without redesigning completed work.
Identify the highest-risk coordination zones and the decisions that must be resolved before the next design milestone.
The most effective RFI strategy starts before construction. Architects need a focused process that identifies the interfaces most likely to create redesign, field questions, or compromises to design intent—and resolves them while the team still has options.
