Procore integration

What Forward reads from Procore

• RFIs (search, status, assignee, response)
• Drawings (latest revision, drawing log, sheet number lookup)
• Submittals (status, ball-in-court, division filter)
• Change orders (open, approved, by sub, by dollar threshold)
• Daily logs (by date, weather, manpower, productivity)
• Observations (by trade, severity, location, status)
• Punch items (by status, room, trade)
• Inspections (by date, type, result)
• Test reports (by system, date, status)
• Schedule activities (predecessor / successor / float / critical-path membership)
• Subcontractor list + pay applications
• Meeting minutes + action items
• Cost codes + budget-vs-actual snapshots
• Project metadata (location, dates, contacts, roles)

What Forward writes (through the approval queue)

• RFI drafts
• Observation drafts
• Punch-item drafts
• Daily-log entries
• Inspection requests
• Delivery-window requests
• Safety-incident drafts

Every write requires PM approval in the Forward dashboard (app.getforward.xyz/drafts) before it posts to Procore. No auto-write surface.

OAuth + permissions

• Connection is per-project (or per-company, with project scoping inside Forward). You can connect one project to evaluate before opening the company-wide grant.
• Forward requests the standard Procore developer-app scopes: read-RFIs, read-drawings, read-submittals, read-changes, read-observations, read-daily-logs, read-schedule, plus write scopes for the approval-queue actions.
• Revoking the Forward grant in Procore terminates access immediately. Forward does not cache project data beyond the active conversation window.
• Forward’s OAuth credentials are managed via Render service env vars; we never see your Procore admin password.

Setup time

On the GC side: ~30 minutes of OAuth + a 30-minute scoping call. We’ll hand-hold the first project. On the Forward side: instant — your project’s data becomes queryable as soon as the OAuth grant lands.