Read every RFI, CE, and PCO as it lands.
Webhook fires on create and on update. Storia scans the record for coordination gaps, scope ambiguity, missing information, and change risk.
Trigger · webhook
Procore App Marketplace/Issue IntelligenceIssue intelligence,
Issue intelligence,
inside Procore.
The moment an RFI, change event, or PCO lands in Procore, Storia reads it, classifies it against a structured issue taxonomy, and writes a Primary and Secondary issue back to the record, surfaced in a side panel, without leaving Procore. The system of record stays Procore. Storia retains nothing.
Procore webhook · create + updatePrimary + secondary issueZero retention
Schematic · record to classificationProject · NORTH SLAB
Procore record
RFI-047
Concrete block wall in conflict with existing ventilation
May 20 · OPEN
Webhook · on create + update
Storia classification
Primary · 2.2.2
Lack of Access
Construction Coordination / Constructability Concerns
Secondary · 1.2.2
Interdisciplinary Conflict
Design & Documentation / Inconsistency & Conflict
Written back into the RFI
How it works
Three moves, inside Procore.
Assign a Primary and Secondary issue.
Classify the record against a 3-level taxonomy. RFI-047 reads as Lack of Access (2.2.2), with Interdisciplinary Conflict (1.2.2) as the secondary frame.
Output · 2 issue tags
Write the classification back into Procore.
A side panel docks beside the record with the Primary and Secondary issues, taxonomy paths, definitions, and worked examples. The PM reads it without leaving the RFI.
Surface · embedded side panel
Inside the record
Where the field already looks.
Record viewProject4821 · Meridian Heights TowerToolRFIsSearch
RFIs / RFI-047 · Concrete block wall in conflict with existing ventilation on Zone V-43
RFI #RFI-047: Concrete block wall in conflict with existing ventilation on Zone V-43.
Request
Subject
Concrete block wall in conflict with existing ventilation on Zone V-43.
Question
“Hello, concrete block wall in conflict with the existing ventilation duct (± 4″ conflict). Along Zone V-43, wall from C5/57 to approximately the center of Y9/88. Instructions please. Regards,”
Attachments
--
Submitted
May 20, 2026
Responses · 2
From
Marcus Reyes
May 20, 2026 · 7:35 AM PDT
Response
“Hello, the RFI was identified late, but the response is in RFI-042. As indicated on April 20. Thanks,”
Mark official
Pending
From
Marcus Reyes
May 20, 2026 · 7:35 AM PDT
Response
“Hello, see the response in RFI-042.”
Mark official
Pending
Rendering of the Storia panel docked in a Procore record. Procore chrome shown generically.
Same Procore
Same Procore. Different visibility.
| Dimension | Procore alone | Procore + Storia |
|---|---|---|
| Issue visibility | Each RFI, CE, and PCO opens in its own record. The PM reads the title and decides what kind of issue it is. | RFI-047 arrives tagged Primary · Lack of Access (2.2.2) and Secondary · Interdisciplinary Conflict (1.2.2). |
| Time to classify | Manual triage. Categories get filled in after the fact, or skipped. | Automatic. Storia classifies on create and on update, before the response is written. |
| Workflow change | No change. | No change. Storia writes back into the Procore record. The field never leaves Procore. |
| Data retention | Project data stays in Procore. | Project data stays in Procore. Storia retains nothing on its side. |
IntegrationProcore App MarketplaceInstalled per company. Scoped per project.
Data flowProcore is the system of recordStoria reads in, writes a note back. One direction for truth.
RecordsRFI, Change Event, PCOClassified on create and on update. More record types on request.
TriggersWebhook, real timeClassification runs the moment a record lands or changes.
RetentionZero on StoriaInference runs in memory. Nothing persisted on our side.
SetupUnder 30 minutesInstall from the App Marketplace, scope the project, done.
30 minutes · Your records
See it on your own Procore project.
Bring a real project. We install the app, scope it to one job, and walk through the issues Storia finds in the first thirty minutes. No deck.
Real recordsNo new dashboard for the fieldZero retention