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.
- TriggerProcore webhook · create + update
- OutputPrimary + secondary issue
- DataZero retention
How it works
Three moves, inside Procore.
- 01 / Detect
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
- 02 / Classify
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
- 03 / Surface
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.
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.
Concrete block wall in conflict with existing ventilation on Zone V-43.
“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,”
--
May 20, 2026
Marcus Reyes
May 20, 2026 · 7:35 AM PDT
“Hello, the RFI was identified late, but the response is in RFI-042. As indicated on April 20. Thanks,”
Pending
Marcus Reyes
May 20, 2026 · 7:35 AM PDT
“Hello, see the response in RFI-042.”
Pending
Text alternative. A Procore record view on project 4821 Meridian Heights Tower, RFIs tool, RFI-047. The record is titled “RFI #RFI-047: Concrete block wall in conflict with existing ventilation on Zone V-43.” with tabs General, Related Items zero, Emails zero and Change History fifteen. The request subject is the same wall conflict; the question reads “Hello, concrete block wall in conflict with the existing ventilation duct, plus or minus four inch conflict. Along Zone V-43, wall from C5/57 to approximately the center of Y9/88. Instructions please. Regards.” There are no attachments and it was submitted May 20, 2026. Two responses, both from Marcus Reyes on May 20, 2026 at 7:35 AM PDT and both pending official marking, read “Hello, the RFI was identified late, but the response is in RFI-042. As indicated on April 20. Thanks,” and “Hello, see the response in RFI-042.” Record actions are Close RFI, Edit and Export. Docked beside it, the Storia Issue Intelligence panel for RFI #RFI-047 carries two issues. The first, the primary issue, is 2.2.2 Lack of Access under Construction Coordination and Execution Issues, Constructability Concerns, defined as limited physical access preventing installation, inspection, or maintenance during construction, with the real-world example of a mechanical shaft too narrow for duct routing and inspection clearance. The second, the secondary issue, is 1.2.2 Interdisciplinary Conflict under Design and Documentation Issues, Inconsistency and Conflict, defined as clashes or inconsistencies between different disciplines' design models or drawings, with the real-world example of a mechanical duct shown running through an architectural skylight.
Same Procore
Same Procore. Different visibility.
Procore alone — Each RFI, CE, and PCO opens in its own record. The PM reads the title and decides what kind of issue it is.
Procore + Storia — RFI-047 arrives tagged Primary · Lack of Access (2.2.2) and Secondary · Interdisciplinary Conflict (1.2.2).
Procore alone — Manual triage. Categories get filled in after the fact, or skipped.
Procore + Storia — Automatic. Storia classifies on create and on update, before the response is written.
Procore alone — No change.
Procore + Storia — No change. Storia writes back into the Procore record. The field never leaves Procore.
Procore alone — Project data stays in Procore.
Procore + Storia — Project data stays in Procore. Storia retains nothing on its side.
Integration
Procore App Marketplace
Installed per company. Scoped per project.
- Data flow — Procore is the system of record.Storia reads in, writes a note back. One direction for truth.
- Records — RFI, Change Event, PCO.Classified on create and on update. More record types on request.
- Triggers — webhook, real time.Classification runs the moment a record lands or changes.
- Retention — zero on Storia.Inference runs in memory. Nothing persisted on our side.
- Setup — under 30 minutes.Install 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.
Procore is a trademark of Procore Technologies, Inc. Storia is an independent third-party integration and is not affiliated with, endorsed by, or sponsored by Procore.