Procore tracks what happens on the project. WeReno shows where it happens — in the model, in context, at the specific room or element it affects. Used in isolation, each tool gives you half the picture. Connected, they give every stakeholder a complete, spatially accurate view of the project without any double-entry or manual sync.

The integration closes a gap that costs project teams hours every week: the gap between the project management system and the model. An RFI opened in Procore now surfaces in the twin at the exact element it refers to. A daily log entry in Procore updates zone progress in WeReno. Here's what syncs and how to set it up.

What the integration syncs

• RFIs — Linked to model elements; status updates sync bidirectionally between Procore and WeReno
• Issues and observations — Tagged to zones in the twin, visible in context alongside zone completion status
• Submittals — Visible against the specification element they relate to; approval status reflects in the twin
• Daily logs — Aggregated per zone in the twin's progress view; GC's daily entries become zone-level completion updates
• Schedule (via Procore Schedule) — Phase progress reflected in twin zone status; upcoming milestones visible per zone

Setting up the connection

1. In WeReno: navigate to Settings → Integrations → Procore → Authorise — this opens the Procore OAuth flow
2. Select the Procore project to link to the current WeReno twin
3. Map Procore locations to WeReno zones — this step takes approximately 10 minutes for a 20-zone project
4. Enable sync — bidirectional updates run every 15 minutes automatically after this point

The zone-level RFI view

Once the integration is active, every open RFI is visible on the zone it affects. Navigate to any zone in the twin and you see all open items in that zone: their age in days, their Procore assignee, and their current status. High-RFI zones stand out visually — a heatmap overlay shows issue concentration across the model, making it immediately clear which areas need attention.

Best practices for the integration

• Use consistent location naming in Procore before linking — the mapping step is faster and more accurate when Procore locations match WeReno zone names
• Assign a "model coordinator" role in Procore to own the location mapping and keep it accurate as zones evolve
• Set RFI auto-closure to sync when Procore marks them resolved — this keeps the twin's open issue count accurate without manual updates
• Review the zone-issue heatmap weekly in WeReno to spot concentration patterns before they become programme risks

What teams report

Within 30 days of enabling the Procore integration, most teams reduce their weekly coordination meeting from 60 minutes to 20 minutes. The reason is straightforward: zone status and open items are visible to everyone before the meeting. There's nothing to report that the twin hasn't already communicated. The meeting becomes an exception review rather than a status briefing.

The second benefit that teams consistently report is RFI resolution speed. When an RFI is linked to a model element and the relevant context — adjacent elements, trade sequence, recent daily logs — is visible in the twin, the person resolving it has everything they need without pulling multiple sources together. Average RFI resolution time drops by 30–40% in the first 60 days of the integration being active.