The Procore lookup tax

What we sampled

Across the PMs we’ve sat with at mid-size commercial general contractors (operations of 4 to 12 active projects, organization sizes between 2 and 12 PMs), one pattern shows up in every diary study we’ve done: a meaningful slice of each PM’s day is spent answering field-foreman text messages of the form “hey, where’s the…” or “what’s the latest on…”.

We asked PMs to count the inbound texts they’d call “pure lookup” — questions whose answer already exists in the project’s Procore (or Autodesk Construction Cloud, or OneDrive) but the field can’t reach it. The range came back tight: 40 to 80 inbound lookup texts per PM per day, with the average clustering around 55.

Where the time goes

Each lookup text resolves like this:

1. Foreman texts the PM with the question.
2. PM is mid-task. Stops, reads the text, decides whether to answer now or queue it.
3. If now: opens Procore on phone or laptop.
4. Navigates to the relevant project + module (drawings, RFIs, submittals, change orders).
5. Finds the specific record.
6. Screenshots it or copies the relevant snippet.
7. Texts back.
8. Returns to original task with context loss.

The clock time is 60-90 seconds best case. The context-switch cost (the time it takes to return to your previous deep-work state) is harder to measure but real — we estimate 2-4× the clock time for cognitively demanding tasks like procurement review or contract negotiation.

The aggregate math

Conservative version, taking the 55 texts/day midpoint:

• 55 texts × 75 seconds = ~68 minutes/day of clock time.
• 5 days/week × 6 PMs = 34 hours/week of clock time, just on lookups.
• Add 2× for context switching = ~68 hours/week of effective senior PM time lost.

Worth being explicit: that’s 68 hours of senior PM time per week, across one 6-PM organization, going to questions whose answers already exist in the project data. It’s not making the field worse; the field is texting because that works for them. It’s creating the wrong cost-allocation between “who has access” and “who needs the answer.”

Why the obvious fix doesn’t work

The PMs we interviewed had all considered “just give the field Procore access.” All had rejected it. The reasons clustered into three:

1. Cost. Procore’s GMV-based pricing model has seat overlays on some tiers. Adding 30-50 tradespeople adds budget against licenses that get used twice in six months.
2. Adoption. Tradespeople don’t open project-management apps. Every other field-tech tool of the past decade has hit this wall — Procore’s dashboard included.
3. Permission complexity. Even read-only Procore access is a non-trivial config: which projects, which directories, which docs. Maintain that across 40-60 hires-and-quits a year and you’ve burned a half-FTE on access management.

The texting-layer wedge

Forward starts from a different premise. The field is going to text someone anyway. The interface question isn’t “what app should we install on every iPhone in the trade contractor’s crew” — it’s “what phone number should they text instead of the PM”.

Forward is that phone number. Field worker texts; the bot reads from Procore + Autodesk + OneDrive; replies with a cited answer in seconds. No app, no login, no training. Writes (RFI drafts, observations, punch items, daily-log entries) route through a PM approval queue in the Forward dashboard.

The math changes:

• ~70% of the lookup texts get answered by the bot directly (the obvious-from-the-document ones). Those never reach the PM.
• The remaining ~30% are higher-value (genuinely need PM judgment) and arrive with the field-conversation context already attached.

On our pilot projects we’re measuring the displacement explicitly — we count the bot-answered texts and attribute them as PM-time recovered. Pilot data is early; the directional number is 20-30 PM-hours per week recovered per active project.

What this is NOT

Forward isn’t a Procore replacement. The data still lives in Procore. The approval queue is a layer on top. The OAuth grant is revocable in 5 seconds. The texting layer compounds the value of your existing PM-stack investment rather than creating a parallel system of record.

How to try it

Drop your email above for an early-access conversation. We’ll wire your Procore + Autodesk + OneDrive on one pilot project in roughly 30 minutes of OAuth + a short scoping call. Pilot pricing is per phone-line, not per seat.

Or text +1 (682) 300-6750 right now — the live demo answers the most common lookup-question shapes against a synthetic commercial project.