Fox & SantiagoTechnology, applied.Call (877) 244-9687

Problem guide

Questions to the engineer, owner or customer go unanswered

A question that stops the work goes unanswered when it leaves as a text or a call and never becomes a logged request with an owner and a needed-by date. That holds for a foreman's question to an engineer, a machinist's question about a customer's print, or an accountant's question to a client. In construction, a 2013 Navigant Construction Forum analysis of 1,362 projects, mostly in Australia and New Zealand, found the share of formal RFIs with no reply ran from slightly under 19% to 35% by region. Log every question with the date the work needs the answer.

Rolled drawings and a hard hat on a job trailer table

How it actually happens

Most questions to the engineer never start as RFIs. They start as a foreman looking at two sheets that disagree. The duct on the mechanical drawing runs through the light fixture on the electrical one, or the curb detail does not fit the unit that showed up. He calls the project manager. The project manager says he will find out.

Follow a typical one, as an example. The project manager is on another site and writes the question up two days later, from memory and a blurry photo. It goes to the general contractor, who logs it and forwards it to the architect, who sends it to the mechanical engineer. Under an unmodified A201-2017, that path is the contract: the sub talks to the general contractor, the general contractor to the architect, and the architect to its consultants. Nobody along the way knows the crew needs the answer by Thursday, because the request never said so.

Meanwhile the crew has a choice. Wait, and move to other work out of sequence. Or build to the foreman's best guess and hope. Most crews keep moving. When the answer finally comes back, it lands in the project manager's inbox. If it matches the guess, nothing happens. If it does not, the work comes out.

The same path exists wherever the answer belongs to someone outside. A machine shop's question about a customer's print goes to a buyer, then to the customer's engineer. An accounting firm's question about a client's transaction goes to the client's bookkeeper, who asks the owner. A clinic's question about a missing order goes by fax to the referring office. In each case the question leaves without a needed-by date, the answer comes back to whoever happened to ask for it, and the person doing the work waits or guesses.

The construction data says the waiting is normal, not bad luck. In the 2013 Navigant analysis of ACONEX project data, the median reply took 9.7 days, and between about 19% and 35% of requests got no reply at all, depending on region. In a 2016 case study of one building project, 61.66% of responses missed a required five-day turnaround. Those figures come mostly from projects outside the US, and they count only questions that were formally logged. The ones that stayed in a text thread are not in anyone's numbers.

Software tracks the request once it exists. Procore will not let a Standard-level foreman set a due date, and it will not tell him the answer unless someone put him on the distribution list. ServiceTitan stores the reply but leaves the status where someone last set it. Fieldwire will not open an RFI without an assignee and a due date. Each tool assumes a person in the office does the writing up and the passing back.

Ask the date, not just the question

The single most useful field on a request is the date the work needs the answer. It turns a question into a deadline the reviewer can rank, and it lets you show later, on paper, that the wait cost you time.

Signs you have this problem

  • People ask the same question twice because nobody knows whether the first one went out
  • Answers arrive by phone and never reach the person who asked
  • Work proceeds on a best guess and gets redone when the answer finally comes
  • The project lead cannot list which questions are open, who has them, or since when
  • A request shows Closed in the log and nobody can find the answer in it

What usually causes it

  • The question is asked by phone or text and only becomes a written request when someone in the office has time to write it upThe field-to-office split
  • The request sits with the engineer, owner, customer or client with no needed-by date and no reminderApproval drag
  • Open questions live in inboxes and a log nobody reviews, so nobody can see which ones are agingThe invisible queue
  • The answer comes back to the project lead and stops there instead of reaching the person who askedThe handoff gap

Find your cause

Ask these in order. The first yes is usually where yours starts.

  1. Do questions reach the log more than a day after they are asked?If yes: the write-up is the first delay. Let the person who has the question start the request themselves, with a photo or screenshot.
  2. Do your requests go out without a needed-by date?If yes: the reviewer has no way to rank yours. Add the date the work needs the answer and the activity it holds up.
  3. Does your contract, statement of work or engagement letter name a response period?If yes: if not, the only standard is reasonable promptness. Ask for a working-day number at the next contract or kickoff.
  4. Have people found out about an answer only after doing the work the other way?If yes: the answer stops at the project lead. Make sending it to the asker and filing it with the document part of closing the request.
  5. Are requests closed in your log that have no answer attached?If yes: closed is being used for given up. Reopen them or note the reason, because Procore, for one, allows closing without a response.

How it breaks in each industry

Commercial electrical
Questions cluster around conflicts between the electrical and architectural sheets: a fixture over a duct, a panel in a wall that moved. Under the unmodified A201-2017 the sub's question reaches the engineer through the general contractor and the architect, so it passes at least three desks each way.
HVAC and mechanical
Questions come up about equipment substitutions, clearances and control sequences, often when the unit is already on site. If the answer waits more than a few days, the crew sets the unit on a guess or moves to other work and loses the sequence.
Commercial roofing
Details at penetrations, curbs and edges decide whether the manufacturer will warrant the roof. A question about a detail that is not on the drawings has to be answered before the membrane goes down, because it cannot be checked afterward.
Specialty manufacturing
A print calls out a tolerance or a finish that the shop cannot hold or does not recognize. The question goes to the customer's buyer by email, the buyer forwards it to their engineer, and the job sits on the schedule board marked waiting while the machine runs something else.
Accounting and professional services firms
An engagement stalls on questions to the client: a missing statement, an unexplained transaction, a document request. The questions go out in one email, the client answers some of them, and the open items list lives in a spreadsheet that only the senior on the engagement updates.
Healthcare practices and clinics
Staff need an answer from a referring provider's office or a payer before they can schedule or bill: a missing order, an unclear diagnosis code, a coverage question. The request goes by fax or phone, the answer comes back to whoever picked up, and the person who asked finds out when the patient calls.

Where it breaks between systems

Procore RFIs, who can set the date
The due date fills in from a default number of days set in the RFIs tool's settings, and only Admin-level users can see or change it. A foreman or sub with Standard permission can create an RFI only in Draft and send it to the RFI Manager, so the question waits in Draft until the manager opens it.[5]
Procore RFIs, who hears the answer
A Standard-level creator is not notified of the official response unless they are on the RFI's distribution list. Notifications are also disabled when assignees are updated through Bulk Actions.[7]
Procore RFIs, ball in court and closing
Ball in court stays with assignees until all required responses are in, then moves to the RFI Manager. Overdue email reminders go out only if that setting is enabled. RFIs can be closed without responses, so a Closed RFI is not proof it was answered.[9]
Autodesk Build RFIs
The creator submits the RFI to a manager, who assigns up to 10 reviewers, picks the official response, marks it Answered, and then closes and distributes it. Autodesk's help notes that mandatory fields do not block some status changes, for example on RFIs created before the field was made mandatory.[10]
Fieldwire RFIs
Fieldwire's help says RFIs come with Business Plus or through its sales team, that contributors cannot move an RFI out of Draft, and that an RFI opens only once an assignee and a due date are set. A manager can record an answer received outside Fieldwire on the assignee's behalf.[11]
ServiceTitan project RFIs
An RFI is created in Draft with subject, question, due date, priority, and schedule and cost impact fields, sent from its Email tab, and then moved to Sent by hand. A reply threads into the Email tab but the status changes only when someone changes it. RFIs appear only if the project type has them enabled.[12]

By the numbers

FigureWhat it measures
About 19% to 35%[1]Share of formal RFIs that received no reply, by region, from slightly under 19% in the Middle East to an average of 35% in Asia. The report adds that smaller projects with fewer RFIs tend to have higher no-reply rates. Navigant Construction Forum, April 2013, built on ACONEX platform data from 1,362 projects, about 79% of them in Australia and New Zealand; hosted by CMAA.
6.4 and 9.7 days[1]Average time to first reply (6.4 days) and median reply time (9.7 days) across the same 2013 data set. Two different measures, not an average and a median of one thing. Replies were quickest in Australia and New Zealand and slowest in the Middle East.
796 RFIs and $859,680[1]Average RFIs per project in the data set, and Navigant's estimated cost to review and answer them per project, at an assumed 8 hours and $1,080 per RFI in 2012 to 2013 rates. The hours and rates are an informal estimate from design professionals Navigant interviewed, not a measurement.
7.7 days, 55% on time[1]Average RFI response time on Wisconsin highway projects, where 55% were answered within the requested period (Hanna and others, 2012, as tabulated in the Navigant report). Highway work, not building trades.
11.5 business days, 61.66% late[2]Average response time against a required 5 days on one building project with 1,484 RFIs, where 915 responses were late. The same paper found no statistically significant link between how early an RFI was raised and how long the answer took. A single case study (Shim, Carter and Kim, ASC conference proceedings, 2016).

Rules that apply

AIA A201-2017, Sections 3.2.2 to 3.2.4, reporting as a request for information[3]
Under the unmodified form, the contractor promptly reports errors, inconsistencies, omissions and code nonconformities it finds to the architect as a request for information. Added cost or time from the answer goes through Article 15 claims. A contractor that fails to report pays the costs that reporting would have avoided.
AIA A201-2017, Sections 4.2.11 and 4.2.14, the architect's response time[3]
The architect answers requests for information in writing within any time limits agreed upon or otherwise with reasonable promptness, and issues supplemental drawings if appropriate. The form sets no number of days; only the contract or Division 01 can.
AIA A201-2017, Section 4.2.4, who talks to whom[3]
Communications with the architect's consultants go through the architect, and communications with subcontractors and suppliers go through the contractor. That is why a sub's question to the engineer passes the general contractor and the architect both ways.
FAR 52.236-21(a), discrepancies on federal construction[4]
Where drawings and specifications differ, the specifications govern. A discrepancy in figures, drawings or specifications goes promptly to the contracting officer, who decides in writing, and any adjustment the contractor makes without that determination is at its own risk and expense.

Measure it in your own shop

From: Your RFI or open-questions log in Procore, ServiceTitan, Fieldwire or a spreadsheet for the last 90 days, plus the project lead's texts and email over the same period.

  1. List every question you can find, logged or not, with the date it was first asked.
  2. For each one, find the date it was logged, the date an answer came back, and the date the asker got the answer.
  3. Count the questions never logged, and the logged ones with no answer today.
  4. Find the median days for each leg: asked to logged, logged to answered, answered to asker.

Reading it: Questions never logged are invisible to the customer and to any contract time limit. The no-answer share is your own version of the Navigant no-reply rate, which ran from about 19% to 35% by region in 2013 construction data. The longest leg tells you whether the delay is in your office, with the reviewer, or on the way back to the person who asked.

What does not fix it

Buying an RFI module
Every RFI tool needs someone to write the question up, set a due date and pass the answer on. In Procore the field user cannot even set the due date. The module stores the request; it does not raise it or deliver the answer.
Telling people to use judgment and keep moving
On an unmodified A201-2017 job, not reporting a discrepancy can put the avoidable cost on you, and on federal work an adjustment without a written determination is at your own risk. Outside construction, work done to a guess is work you redo at your own cost.
Saving questions for the weekly meeting
Median reply times in the Navigant data were already over a week. Adding up to seven days of waiting for the meeting before the question is even asked makes people decide alone.

What to try this week

  1. Write it down the same dayAny question that stops or changes work goes into the log the day it is asked, with the document reference, a photo or screenshot, and the asker's proposed answer. A text to the project lead does not count until it is logged.
  2. Put a needed-by date on every requestSay when the work needs the answer, not just when you asked. The sample RFI specification in the Navigant report asks the contractor to state why a response is needed and when.
  3. Agree the turnaround in writingAn unmodified AIA A201-2017 asks only for reasonable promptness or any time limit the parties agree. Ask at kickoff for a number of working days in the contract, statement of work or engagement letter, and get it in writing.
  4. Close the loop to the askerWhen the answer comes back, send it to the person who asked and file it with the document it changes. In Procore, a Standard-level creator is only notified of the official response if they are on the RFI's distribution list.
  5. Review aging every weekList open questions by days outstanding against the needed-by date. Chase the ones past due by name, and raise the oldest at the next customer or owner meeting.

Where do-it-yourself stops

These steps get questions logged, dated and chased. The question still starts as a phone call, waits for someone in the office to write it up, and comes back to a person who has to remember to pass it on. The lasting fix is a tool built around how your people actually ask, so a question raised where the work happens arrives logged with its photo and needed-by date, and the answer finds its way back to the person who asked. That is what a Workflow Spec designs.

How a Workflow Spec fixes it for good

Questions people ask

How long should an engineer take to answer an RFI?

The unmodified AIA A201-2017 sets no number of days; it requires a written answer within any agreed time limit or otherwise with reasonable promptness. A sample specification in the 2013 Navigant report used ten working days, with notice if the owner needs longer. Put your number in the contract.

How often do RFIs go unanswered?

In the 2013 Navigant Construction Forum analysis of ACONEX data on 1,362 projects, mostly in Australia and New Zealand, the share of RFIs with no reply ranged from slightly under 19% to 35% depending on region. The report says smaller projects tended to have higher rates. No comparable US trade figure was found.

What does an RFI cost?

Navigant's 2013 estimate, based on informal input from design professionals, was about 8 hours and $1,080 to receive, review and answer one RFI at 2012 to 2013 rates, or $859,680 for an average 796-RFI project. That is review time only, not delay or rework.

Can the crew go ahead without an answer?

It can, but the risk moves to you. Under the unmodified A201-2017 the contractor must report discrepancies as a request for information, and on federal work FAR 52.236-21 puts any adjustment made without the contracting officer's written determination at the contractor's risk and expense.

Why did the foreman never hear the answer in Procore?

Procore notifies a Standard-level RFI creator of the official response only if they are on the RFI's distribution list. Add the field asker to the distribution list when the RFI is opened.

Next step

How we fix this

This guide is how to find it and work around it. If it keeps coming back, it is rarely the only thing costing you. We come on site, find the issues costing you the most, and fix them, starting with the most pressing.

Fox & Santiago, Genesee, Idaho. We work nationwide, for clients across the United States, from our headquarters in Genesee, Idaho.