Preventing RFI Delays in Facade Construction Projects

Last Updated: November 6, 2026

Table of Contents

• Why Facade RFIs Stall Programmes
• Step 1: Get Facade Design Coordination Right Before Construction
• Step 2: Build Complete Glazing Shop Drawings to Reduce Questions
• Step 3: Write RFIs That Can Be Answered the First Time
• Step 4: Set Up an RFI Log Template and Tracking Routine
• Step 5: Set Response Deadlines, Priorities and Escalation Paths
• Booking a Shop Drawing Review for Your Next Facade Package
• Frequently Asked Questions

Why Facade RFIs Stall Programmes

Preventing RFI delays in facade construction starts with understanding why requests for information pile up on glazing and cladding packages. A single unclear detail at the shop drawing stage can turn into weeks of waiting on site.

A request for information (RFI) is a formal question a contractor sends to the designer when documents are unclear, incomplete or conflicting. Readers who want to see how these requests can be avoided altogether can read how to avoid RFIs in facade construction. Facade work makes RFIs more likely because window walls, curtain walls and shop fronts depend on tight coordination between architects, engineers, fabricators and installers.

Common causes include:

• Conflicting dimensions between architectural and structural drawings
• Missing sub-sill or subhead details for window and door systems
• Unclear thermal or performance requirements
• Late design changes that were not carried through to fabrication drawings
• Specifications that do not match the chosen product system

When an RFI sits unanswered, fabrication slips, installation teams stand down and costs rise. A glazing package that is not ready on time can hold up the building envelope and every trade that follows it.

Step 1: Get Facade Design Coordination Right Before Construction

Facade design coordination is the cheapest place to prevent RFIs. Learn what window wall design coordination involves before construction starts. Most of the problems that stall a programme can be found on paper before anything is ordered or built.

Start by agreeing one set of controlling documents. Decide which drawings and specifications take precedence when they disagree, and record that decision in the project file.

Next, run a coordination review with the architect, facade engineer, structural engineer and glazing contractor. Check:

• Opening sizes against structural openings and tolerances
• Anchor and fixing locations against slab edges and embedments
• Thermal and acoustic requirements against the proposed system
• Access and maintenance requirements for operable windows and doors

A common mistake is treating coordination as a one-off meeting. Facade details change as the design develops, so the coordination check needs to repeat at each design milestone.

Watch out: if a detail changes after fabrication drawings are approved, the whole package may need reissuing. Lock critical details early.

Step 2: Build Complete Glazing Shop Drawings to Reduce Questions

Glazing shop drawings turn the design intent into fabrication and installation instructions. Incomplete shop drawings generate questions, and questions generate RFIs. Our checklist of common glazing construction errors shows which mistakes drive this rework.

A complete package should typically include:

• Elevations with all window, door and panel positions
• Sections through typical and critical details, including sill and head conditions
• Setout drawings showing sub-sill and subhead locations
• Schedules for frames, glass types and hardware
• Notes on sealants, flashing and waterproofing interfaces

Before issuing shop drawings, check them against the architectural drawings and specifications. Confirm dimensions, glass types and performance values match. Flag any gap for the designer to resolve rather than assuming an answer.

Facade shop drawings for architects cover what to review and how to coordinate with contractors before construction begins. Our guide to facade shop drawings for architects explains what a complete package should contain. Reviewing a full drawing set this way helps prevent avoidable questions on site.

Step 3: Write RFIs That Can Be Answered the First Time

An RFI that is vague or incomplete usually comes back with a second question. Writing a clear request saves time for everyone.

Each RFI should include:

• A clear subject line naming the element and location
• The specific drawing, detail and revision reference
• A short description of the conflict or gap
• The proposed solution or the options being considered
• The date a response is needed to protect the programme

Keep each RFI to one issue. Combining several questions makes it harder to answer and easier to lose.

Use plain language and attach a marked-up sketch where it helps. A simple annotated section often answers more questions than a paragraph of text.

Step 4: Set Up an RFI Log Template and Tracking Routine

An RFI log is the simplest way to see which requests are open, overdue or blocking work. Without one, RFIs get lost in email threads and the programme absorbs the delay quietly.

SUBMIT →

A practical log includes these columns:

Review the log at a fixed routine, such as a short daily check on site and a weekly review with the design team. Review aging requests first, because they are the ones most likely to cascade into delay.

A log that is only read is a diary; a log that is measured is a management tool. The metrics worth tracking on a facade package are:

• Average response time by priority, the mean days from raised to answered. Compare it with the targets in Step 5, not with a generic industry figure.
• Aging, the number of open RFIs older than their target, and the age of the oldest open item. A single 30-day-old P1 is a bigger warning than twenty 3-day-old P3s.
• Overdue rate, overdue RFIs as a proportion of open RFIs. A rising rate usually precedes a programme slip by several weeks.
• Reopen rate, answered RFIs that come back because the answer was incomplete or did not address the question. A high reopen rate points to vague RFIs or unclear ownership rather than slow responders.
• RFIs per drawing or per facade area, for example, RFIs per 100 square metres of curtain wall or per shop drawing sheet. This normalises the count so you can compare packages and elevations fairly.

Interpret the numbers together rather than in isolation. A low average response time with a high reopen rate means answers are fast but poor. A low overdue rate with a high RFI count per drawing means the design documentation is thin and questions are being generated faster than they are being closed. A rising aging figure on P1 items is the clearest early signal that fabrication or installation is about to be held up.

Watch out: if the log is maintained only by the contractor and not shared with the design team, the response clock and the aging figures become one-sided and the escalation path in Step 5 has nothing to trigger on.

Use the metrics to feed back into prevention. If one elevation or one system interface, say, the transition between curtain wall and precast, keeps generating RFIs, that is a detail to resolve in the next design coordination review rather than a run of bad luck.

Step 5: Set Response Deadlines, Priorities and Escalation Paths

Not every RFI carries the same weight, and treating them as if they do is how facade packages lose weeks. A question about a sealant colour can wait; a question about an anchor embedment that blocks the curtain wall shop drawing release cannot. Prioritise by schedule impact, so the requests that hold up procurement, mockups, fabrication or installation get answered first.

A practical way to do this is a simple priority matrix agreed at the start of the package:

These targets are examples, not rules, agree them with the design team and record them in the project procedures or contract so they are enforceable rather than aspirational.

Define an escalation path with named roles and time triggers. A workable pattern is:

• Day 0: RFI issued to the nominated design lead, with the response target stated.
• Target plus 1 day: reminder to the design lead and copy to the project manager.
• Target plus 3 days: escalate to the architect or facade engineer of record and the contractor's project manager.
• Target plus 5 days: escalate to the owner's representative or superintendent, with the schedule impact and any cost exposure stated in the escalation note.

Decision ownership needs to be clear before the first RFI lands. The architect usually owns design intent and appearance; the facade or structural engineer owns structural and performance compliance; the contractor owns means and methods and the construction programme; the facade subcontractor owns fabrication and installation detail within the specified system. When an RFI crosses those boundaries, route it to the single owner who can decide, and copy the others rather than sending it to everyone and hoping someone answers.

Watch out: an RFI that is escalated without a stated schedule impact tends to be triaged as low priority, so always attach the activity, the date it is needed and the consequence of a late answer.

Track response rates against the targets over time. If the same type of question keeps coming up, or if P1 response times are consistently missed, that points to a coordination gap to fix at the design stage rather than a discipline problem to manage on site.

Booking a Shop Drawing Review for Your Next Facade Package

If your next facade package is at the design or tender stage, a shop drawing review is one of the most effective ways to reduce RFIs later. You can book a facade and window shop drawing review during the design phase. BluePrint Facade provides facade and glazing shop drawings, including window wall and curved window design for complex projects. We work with product systems from brands such as Alspec, Capral and Darley.

To discuss your drawings or request a quote, submit an enquiry through our website. Pricing depends on project scope, drawing volume and delivery requirements, so contact us for a tailored quote.

Add blueprintfacade.com.au as a preferred source on Google →