Automated Procore RFI Tracking
Every morning, WebRun opens your Procore RFI log, finds RFIs that are still open and past their due date, notes who holds the ball in court, logs each one to a shared Google Sheet, and posts the project team a ranked chase list in Slack.
How do I track overdue RFIs in Procore automatically?
WebRun keeps your construction RFIs from slipping. Each morning it opens your Procore RFI log, finds the ones still open and past their due date, notes the ball-in-court party, logs them to a shared Google Sheet, and posts the project team a ranked Slack chase list, so no overdue RFI stalls the schedule unseen.
- Overdue RFIs surface every morning before they stall the schedule
- Every open RFI past due is tracked in one shared aging sheet
- The project team opens Slack to a ranked chase list, most overdue first
Built for general contractors · construction project managers · project coordinators · commercial builders
What does WebRun do on every run?
The exact actions WebRun takes, in order - in plain language, so you can adjust anything.
-
WebRun signs in and gets to work
Opens
app.procore.comin a real browser with your saved login - no setup, no API keys. -
1
Procore - find open, overdue RFIs
procore.com
WebRun opens Procore to find open, overdue RFIs. - Open Procore and go to the project's RFIs tool
- Filter the RFI log to Open with a due date in the past
- Capture the RFI number, subject, ball-in-court party, due date, and days overdue for each
Done when Every open, overdue RFI is listed with its number, owner, and days overdue.
-
2
Google Sheets - log the RFI aging list
google.com
WebRun opens Google Sheets to log the RFI aging list. - Open the shared RFI aging sheet for the project
- Add or update a row per overdue RFI with its number, subject, ball-in-court, due date, and days overdue
- Sort the sheet so the most overdue RFIs sit at the top
Done when The aging sheet reflects today's open, overdue RFIs, most overdue first.
-
3
Slack - post the chase list
slack.com
WebRun opens Slack to post the chase list. - Post a ranked chase list to the project channel
- Put the most overdue RFIs first with the ball-in-court party named
- Leave the message for the team to action. Never reply to or close an RFI on its own
Done when The project team has today's prioritized RFI chase list in Slack.
How is each run configured?
Secure by default
Connect once, stays signed in
WebRun signs in once and keeps each session in a persistent environment, so every run picks up right where it left off.
Every action is checked against this policy before it runs.
Questions, answered
Will it answer or close RFIs on its own?
No. WebRun only reads the RFI log and posts an internal chase list for your team. It never responds to an RFI, shifts the ball in court, or closes anything in Procore.
How does it decide which RFIs are overdue?
It reads each RFI's live status and due date in Procore, keeps only the ones still Open with a due date in the past, and ranks them by how many days they are overdue.
What if an RFI was answered overnight?
It checks the live status in Procore each morning, so any RFI that has been answered or closed drops off the chase list automatically.
Related templates
Put this on autopilot.
Turn it on in minutes - or have our team set it up for you.