BBB LiveArch
AboutDocs
Login

Procore-Connected RFIs

Assignment rules, how a connected RFI moves through LiveArch, and how the response returns to Procore.

Overview

On a connected project, the CM/GC raises RFIs in Procore; LiveArch brings each assigned RFI into the design team's review workflow and returns the official response to Procore when it is finalized. LiveArch participates only in RFIs actually routed or assigned to it — Procore does not grant it visibility into unrelated project records. This page covers the Procore-side rules; for the review workflow itself, see RFIs.

Routing: what makes a Procore RFI reach LiveArch

Three conventions on the Procore RFI decide whether it reaches LiveArch — and one field that looks like it should route it, doesn't:
  • Subject and Question — required RFI information must be complete before the record can sync.
  • Attachments — clearly named and organized; they carry into LiveArch with the RFI.
  • Assignees — set to the LiveArch Integration user. The current assignee is what routes the RFI to LiveArch — required, and not immediately obvious.
  • Distribution List — optional, for awareness. Being listed here does not trigger the sync and never replaces assigning the integration user.
The current assignee is what routes an RFI to LiveArch.
If an RFI does not appear in LiveArch, check the assignees in Procore first — confirm it is assigned to LiveArch specifically. This is the most common cause of issues; more info is available in Troubleshooting: Procore Syncing.

Through LiveArch and back

A connected RFI enters at Pending — Draft is skipped because Procore already assigned its number — and LiveArch writes back exactly once, on finalization.
The arriving RFI lands in the project's Pending view. From there it is distributed, reviewed, and finalized exactly like a standalone RFI. When the formal reply is finalized, LiveArch posts the response and its attachments back to the Procore RFI — once. Then verify the round trip:
  1. Open the Procore RFI
    After LiveArch reports the response returned, open the record in Procore.
  2. Check response, status, and attachments
    Confirm the official response text, the closed status, and every attachment arrived.

Follow-up questions

Warning
Do not issue RFI revisions in Procore. A revision does not sync as a new question — use a new RFI for a follow-up or corrected question, referencing the original by number.

Closing or deleting connected records

Coordinate with the BBB project team before prematurely closing or deleting a connected record in Procore. The corresponding LiveArch record may also need attention. An uncoordinated change can leave an orphaned or inconsistent record in one system. If a record already looks out of step, start with Troubleshooting: Procore Syncing.

Support

Questions or issues? We're happy to help — , or use the contact form if you're signed out.