Skip to main content
Procore

RFI Best Practices

  1. Last updated
  2. Save as PDF

DO NOT simply forward subcontractor RFIs written in Procore to the design team without first (a) researching and understanding the question you are asking and (b) editing the request to meet KAST standards.  We waste an inordinate amount of time on bad RFI responses, which are often a result of poorly-written RFI questions.  Do not simply lob RFI grenades over the fence to the design team hoping that they understand a question that you yourself do not understand.

Before closing an RFI you must (a) review the response and check the drawings to see if you believe the answer is valid and (b) check with the RFI author (KAST staff, subcontractor, etc.) to verify that the response meets their needs

KAST RFI standards may be summed up as:

  1. Ensure you understand the question being asked
  2. Cite the affected drawings and/or specs
    1. Include the date the drawing was issued and the date KAST received the drawing (date stamp)
  3. Write separate RFIs for separate issues
  4. Be sure to number your questions when asking a multi-part question
  5. Include attachments, marked up when possible
  6. When forwarding responses to subs, be sure to include clear direction (price and proceed, price only, for information only, etc.)

You may find more information on RFIs and the KAST Standards for RFIs here.

Process for vetting an RFI response with a sub or other creator within Procore

  1. CALL THE PERSON THAT ORIGINALLY CREATED THE RFI
  2. Mark the response as official (subs can only see “official” RFI responses)
  3. Do not close RFI
  4. Click “email” button at top-right
  5. Send RFI to original author asking if the response adequately addresses their issue
  6. They can respond to this email and it will be retained in the RFI under the “emails” tab, and you will receive a copy of the email
  7. If the author indicates that the response is insufficient, create a response to the RFI and ask for additional information or clarification
    1. Best practice is to NOT create “revision” RFIs.
    2. You may create a PDF of the author’s response email but do not simply say “see attached” without describing the issue in your response.