how-to
How Can You Avoid RFIs in Facade Construction?
Last Updated: October 28, 2026
Quick Summary
To avoid RFI in facade construction, assign a named owner to every interface, settle design responsibility in writing before shop drawings begin, and run constructability and clash-detection reviews before fabrication. Most facade RFIs come from uncoordinated drawings, unclear interfaces and specifications that leave questions open.
- An RFI is a formal written query raised when construction documents are ambiguous, incomplete or conflicting.
- Set the response authority matrix at contract award and name a single point of contact per discipline.
- Agreed response timeframes belong in the contract, not in a site meeting.
- Run constructability review on the facade package before tender, checking access and installation sequence.
- Track the RFI rate per facade package, average response time and repeat causes to measure prevention.
Table of Contents
- Why Facade Construction Generates So Many RFIs
- Facade Design Coordination Before Documentation Starts
- Common Facade Specification Mistakes That Trigger RFIs
- The Facade Shop Drawing Review Checklist
- Constructability and Sequencing: Catching Problems Before Site
- Using a Construction RFI Template and Digital Issue Tracking
- Submit Your Facade Documentation for Review Before Tender
- Frequently Asked Questions
Why Facade Construction Generates So Many RFIs
Every RFI on a facade package costs time you did not budget for. To avoid RFI in facade construction, start by understanding why the questions arise in the first place. A request for information (RFI) is a formal written query raised when construction documents are ambiguous, incomplete or conflicting, and the contractor needs a binding answer before proceeding.
What an RFI Is and When It Is Used
An RFI is used when the contractor cannot build from the documents as issued. Common triggers include missing dimensions, unclear interface details, conflicting specifications and undefined responsibility. It creates a formal record so the answer is documented and traceable. That record matters, but every RFI also signals a design document that fell short.
On a facade package, the trigger is usually one of four mechanisms:
- Interface ownership is unassigned. The slab edge, sub-sill, flashing upstand and fire-stop junction each sit between two trades. If the contract documents do not name who sets the level, who owns the tolerance and who seals the junction, the site team raises an RFI rather than guess.
- Delegated design boundaries are blurred. Curtain wall, window wall and glazed systems are often delegated to the subcontractor, but the performance outcome (water tightness, structural deflection, thermal and acoustic ratings) stays with the head designer. When the boundary between performance and fabrication detail is not written down, the submittal review becomes a negotiation and the RFI is the fallback.
- Tolerance stack-up is unresolved. Structure is built to one tolerance, the facade is fabricated to another and the survey is taken to a third. If the documents do not state which tolerance governs at each interface, the installer cannot confirm fit and must ask.
Common Causes of Facade RFIs
Facade packages generate more than their share of queries because they sit at the junction of structure, glazing, cladding and weatherproofing. The usual culprits:
- Ambiguous or incomplete drawings
- Conflicting architectural and structural documents
- Undefined interfaces between trades
Roles, Responsibility and Authority to Respond
Not every question should become an RFI. Before one is raised, the project team should know who has authority to answer it. Typically the superintendent or contract administrator manages the RFI register, the facade consultant or architect answers design intent questions, the structural engineer answers structural questions, and the subcontractor answers fabrication detail within its delegated scope. When the nominated responder is unclear, RFIs bounce between parties and response timeframes slip.
Response Timeframes and Cost Impact
Agreed response timeframes belong in the contract, not in a site meeting. A common pattern is a stated period for the principal to respond, with the contractor entitled to claim time if the response arrives late. The cost impact compounds: a late answer can idle a crew, hold a crane, or force a sequence change that ripples through following trades.
The article attributes most facade RFIs to a handful of recurring mechanisms and causes.
| Mechanism or cause | What goes wrong |
|---|---|
| Interface ownership unassigned | No one named to set level, own tolerance or seal junction |
| Delegated design boundaries blurred | Boundary between performance and fabrication detail not written down |
| Tolerance stack-up unresolved | Documents do not state which tolerance governs at each interface |
| Existing conditions never surveyed | As-built structure rarely matches original drawings on refurbishment |
| Ambiguous or incomplete drawings | Contractor cannot build from documents as issued |
| Conflicting architectural and structural documents | Conflicting specifications and undefined responsibility |
| Specifications that do not match the selected system | Performance figures quoted without the test standard |
| Access and installation sequence left to contractor | Sequence must be inferred rather than stated |
Facade Design Coordination Before Documentation Starts
Bring the structural engineer, facade consultant, builder and key subcontractors together before a single shop drawing is drafted. Confirm the primary structure setout, movement joints and tolerances first. These decisions drive every downstream detail.
Interface and Trade Coordination Details
Most facade RFIs live at the interfaces. Nail these down early:
- Slab edge and sub-sill: who sets the level and who owns the tolerance?
- Structural openings: confirmed sizes and positions against the actual frame
- Waterproofing and flashings: where the facade membrane meets the roof and podium
- Fire and smoke seals: which system, at which junctions
Document each interface with a named owner. When responsibility is clear, the question rarely gets raised.
Common Facade Specification Mistakes That Trigger RFIs
Specifications cause as many queries as drawings. Common facade specification mistakes include:
- Specifying a performance figure without naming the test standard
- Naming a product that no longer matches the selected system
- Copying a specification from another project without updating it
- Leaving access methods and installation sequence undefined
Each gap becomes a question on site, so close them early to avoid RFI later. A specification that names the standard, the system and the evidence required removes the ambiguity before it reaches the builder.
The Facade Shop Drawing Review Checklist
A structured facade shop drawing review checklist catches problems before fabrication. Reviewers should confirm every item below against the design documents, not just the drawing in front of them.
- Setout matches structural drawings and surveyed levels
- Sub-sill and subhead dimensions confirmed
- Mullion profiles and glazing dimensions checked
- Interface details match adjacent trades
For a deeper walkthrough of what to check, see our guide to facade shop drawings for architects.
Shop Drawings, Submittals and Design Responsibility
Design responsibility must be settled before shop drawings begin. Who owns the performance outcome, and who owns the fabrication detail? Get this in writing. When responsibility is blurred, the submittal review becomes a negotiation and the RFI is the fallback. Our team works through this step in detail in our guide on how to create facade shop drawings for curtain walls.
Constructability and Sequencing: Catching Problems Before Site
Constructability review asks one question: can this actually be built in the order proposed? Run it on the facade package before tender. Check that frames can be installed with the access available, that glazing follows structure in a workable sequence, and that interfaces close in the right order. For facade and window shop drawings that hold up under construction, the sequence has to be resolved at the design stage.
Tolerances and Anchors
Structure is never built to the tolerance the facade is fabricated to. The constructability review should state, for each interface, which tolerance governs and how the facade absorbs the difference:
- Slab edge and sub-sill: the survey tolerance on the slab edge, the setting-out tolerance on the sub-sill and the fabrication tolerance on the frame are three different numbers. If the documents do not say which one controls, the installer cannot confirm the frame will fit and will raise an RFI.
- Anchor embedment and edge distance: cast-in anchors, drilled anchors and bracket fixings each have minimum edge distances and embedment depths. A bracket that works on the drawing may not work if the slab edge is closer than assumed.
- Movement and deflection: the structure moves under wind and live load, and the facade must absorb that movement at joints and connections. The review should confirm the movement allowance is stated and that the joint detail can physically accommodate it.
Access and Installation Sequence
The order in which facade elements are installed is a constructability question, not a site preference. The review should confirm:
- Whether frames can be delivered and lifted into position with the access available at each stage of the build
- Whether glazing follows structure in a sequence that lets each panel be installed without removing work already complete
- Whether the facade closes before or after adjacent trades (roofing, waterproofing, fire stopping) and which trade must finish first at each junction
- Whether temporary weather protection is needed while the facade is open, and who provides it
A sequence that works on paper can fail once the slab above is poured and the crane is committed elsewhere. Resolving it at review keeps it a drawing issue.
Field Verification Before Fabrication
The survey should capture:
- Actual opening sizes and positions against the structural grid
- Slab edge levels and deviations from the design setout
- Condition of the substrate and any existing embedment or fixing points
- Any obstructions that affect anchor or bracket placement
Digital Coordination and Issue Tracking
Model-based coordination catches clashes before they become RFIs. A federated model that combines structure, facade, services and fire stopping lets the team run clash detection and resolve interfaces in the model rather than on site. The output should feed a structured issue log, separate from the formal RFI register, so that questions are closed in coordination before they are raised formally.
Measuring Whether Prevention Is Working
Prevention is only credible if it is measured. Track the RFI rate per facade package, the average response time, the ageing of open RFIs, the repeat causes and the rework cost attributable to facade queries. Compare the rate before and after a prevention measure is introduced. A falling RFI rate with a stable scope is evidence the design review and constructability checks are doing their job; a rising rate after fabrication starts is evidence they are not.
Using a Construction RFI Template and Digital Issue Tracking
A construction RFI template standardises the query so nothing important is missing. At minimum, capture:
- RFI number and date raised
- Drawing and specification references
- The precise question
- Proposed solution or options
- Required response date
- Nominated response authority
- Cost and time impact if unresolved
If documentation timing is on your mind, our article on turnaround times for glazing shop drawings sets out what to expect.
Submit Your Facade Documentation for Review Before Tender
The cheapest RFI is the one never raised. If you want to know exactly what a review covers, see what facade engineering documentation services include.
Facade RFIs rarely come from bad luck. They come from uncoordinated drawings, unclear interfaces and specifications that leave questions open. BluePrint Facade produces facade and glazing shop drawings for window wall, curtain wall and curved window systems, working with established systems including Alspec, Capral and Darley.
Frequently Asked Questions
What are the most common causes of RFIs on facade projects?
Facade RFIs usually trace back to four sources: ambiguous or conflicting drawings, missing interface details between trades (for example slab edge to curtain wall), specifications that name a performance outcome without a tested system, and shop drawings that arrive without a documented design review. Each one hands the contractor a reason to stop and ask a question. Fixing these at documentation stage, before tender, removes most of the volume.
How can you reduce RFIs in facade construction?
Run a structured facade shop drawing review checklist before drawings leave the office, hold a coordination workshop with the structural and services teams to lock in interfaces, and issue a construction RFI template so any question that does arise is answered once and recorded. Pair this with digital issue tracking so closed items stay closed. The aim is to avoid RFI volume building up during installation, when every response costs programme time.
What information should facade shop drawings include?
Shop drawings should show setting-out dimensions, slab edge and structural interface details, drainage and weathering paths, thermal and acoustic performance data for the named system, fixing and anchor details, tolerances, and the sequence of installation. They should also state which product system (Alspec, Capral, Darley or similar) the detail is based on, so reviewers can check compliance against the specification without guessing.
How do design reviews help prevent construction RFIs?
An early design review catches conflicting documents, incomplete information and constructability problems while changes are still cheap. On facade work, that means checking that the architectural drawings, structural drawings and specification agree on the same system, the same tolerances and the same interfaces. A review that closes these gaps before shop drawings are issued stops the questions turning into site delays and rework.
