What syncs
| ClockLap | Sent as | Notes |
|---|---|---|
| Projects | From Procore projects (name and project number) | Inactive projects are archived |
| Sites (optional) | At the project’s address and position, with a geofence | – |
| Each shift | Timecard entry: hours (as text), date, clock in and out, the person | A changed shift replaces its entry |
Every call names your company in the Procore-Company-Id header. People are matched to your Procore company directory first.
How it works
- Sign in with ProcoreClockLap uses the company you sign in with (or the one you name).
- Choose which projectsOpen projects or all, with sites and geofences.
- Send hours backTimecard entries for approved hours or every finished shift; match people to your company directory.
- Choose how oftenHourly, daily or by hand.
- ReviewSee what the first import would change.
Projects and people
People are matched to Procore users by email, then employee ID; the match is saved as each person’s Procore user ID.
What you need
- A Procore company admin
- Timesheets / timecards enabled in your Procore company
Every run keeps a history: who and what was sent, per-line results, plain-language errors with a fix, and a redacted request log for admins. Webhooks fire on field_service.jobs_imported, field_service.hours_sent.
Questions
Is a changed shift sent twice?
No. ClockLap remembers the timecard entry it made for each shift and replaces it when the shift changes.
Is the Procore connection included in the price?
Yes. Every connection is part of every ClockLap plan: $1 per staff member and $2 per manager or admin a month, with no add-ons.
Is ClockLap affiliated with Procore?
No. ClockLap connects to Procore using its published API; it isn’t affiliated with or endorsed by Procore. The connection is in beta while we verify it with live accounts.