Skip to main content
INTEGRATIONS

Runs with your stack.

ProPunch is the verification layer under the tools you already run. Every verdict and photo flows into the systems your GC and your crews live in.

WHERE PROPUNCH SITS

The layer beneath the tools you run.

Procore
CompanyCam
Punch + photos
GC punch items
Photos
Photo feed
PROPUNCHThe field verification loop

Crews verify every door at the source. The verdicts and their photos push up into the tools your team already opens every morning.

PROCORE CONNECTOR

Verified punch items, straight into Procore.

Two-way. When a door fails, the verdict and its photo flow into your project’s Procore Punch List — where your GC already lives. And when your GC reports a punch item in Procore, it flows back into the ProPunch project, photos included. No re-keying, no screenshots pasted into email. Import a Procore project to bring its units straight into ProPunch and start verifying.

Punch itemsEvery verified fail creates a Procore punch item, with the failure photo attached.
Project importPull a Procore project and its units into ProPunch to verify against your live scope.
The field punch list that feeds Procore

Every photo, bound to a verdict.

COMPANYCAM CONNECTOR

Every verdict-bound photo — punch fails and delivery records alike — lands in the CompanyCam project your crews already document in. The photo that proves the fail is the same photo your team files, tagged to the door it belongs to. And your CompanyCam photo feed is browsable right on the ProPunch project — no tab-switching to see what the crew documented.

Every verdict is exportable.

YOUR DATA, STRUCTURED

Door-level verdicts are structured, timestamped, and portable — not locked behind a screen. Photos and punch items sync today, and export and API access are available on request. Your record stays yours.

PARTNERSHIPS & PLATFORM

Build with us.

Running a platform your contractors depend on? We connect where the field verdict matters. Bring us the integration and let’s talk about what your teams need next — priced by the door, never by the seat.

SETUP GUIDE

Set up the Procore connection.

Six steps, one sign-in. An admin connects once for the whole organization; each project is then linked to its Procore counterpart.

  1. Sign in to ProPunch as an adminOwner or admin role — connecting is an organization-level action.
  2. Open Admin SettingsProcore is listed under Construction Platforms.
  3. Choose Connect ProcoreYou are sent to Procore to authorize.
  4. Authorize with your Procore loginApprove the request. You are returned to ProPunch with the connection active.
  5. Open a ProPunch projectAny project you want to mirror into Procore.
  6. Link it to the Procore projectIn the project’s Procore row choose Connect, pick the matching Procore project from the list, then Link. Repeat for each project you want connected.

What happens next

Failed checklist items sync to your Procore Punch List immediately, with the failure photo attached. Punch items created in Procore appear in the linked ProPunch project within 15 minutes. Webhooks are being validated now and will make that return trip near-instant.

Permissions the authorizing user needs

In the Procore project you are linking: Punch List — Standard and Locations — Standard. Add Drawings — Read Only only if you plan to use the drawings import. ProPunch acts as the user who authorized it and never exceeds that user’s own Procore permissions.

Support

Email hgibson@siteline.co, Monday to Friday, US Eastern. First response within one business day; if the connection is down, within four business hours.

What we read from Procore, what we write, and how long we keep it is set out in the connected services section of our privacy policy.