Field and yard teams
Techs and warehouse leads punch from a phone. You need more than a timestamp if the punch is later disputed.
Time and attendance
A punch should carry evidence.
Clock in and out with device, source IP, and location on the punch. Exceptions stay visible to the manager who has to sign them.
Why it matters
If a wage-hour question arrives, you can show when the punch happened, which device sent it, which IP it came from, and where the browser or phone said it was. That is a file, not a story.
Peerroll records attendance as evidence. Each punch stores time, direction (in, out, break), device, source IP, and coordinates when the device can provide them. You can define worksites so a punch can match on-site or flag as off-site. Managers close timesheets against the employee record — not a forwarded screenshot. On a phone, the same punch is a large Clock control in mobile self-service — not a desktop form squeezed onto a small screen.
Join the waitlistTime clock
Jordan Hale clocked in
- Punch
- 7:58 AM CT · In
- Location
- Dallas yard32.7767, −96.7970 · 42 m
- Source IP
- 198.51.100.24
On-site match. Punch stored with device, IP, and coordinates.
- Yesterday · OutDallas yard · 198.51.100.24
- Yesterday · InDallas yard · 198.51.100.24
On the record
What you get in Peerroll.
- In, out, and break punches with a stored trail.
- Location and IP on the punch, not in a later investigation.
- Site match when you define a yard, floor, or warehouse.
- Manager exceptions that stay attached to the week.
- Timesheets that close against the same person in the directory.
- Phone Clock tab with large punch controls — same trail as the desk.
How it runs
A week in this workflow.
01
Employee clocks in
They tap In. Peerroll stores the time plus whatever location and IP the session can provide.
02
The punch is matched
If you set a worksite, the product can show an on-site match or an off-site flag for the manager to review.
03
The week closes
The manager reviews exceptions and closes the timesheet. The trail stays on the employee file.
Who uses it
Built for the jobs you already have.
Hybrid offices
Some people are on a floor you can name. Some are remote. The rule is the same: the punch is incomplete without the trail.
Related
These workflows share the same record.
People directory
One employee record. Searchable. Owned.
Name, job, site, manager, documents, and status sit on a single file. The directory is how you find someone — not a Friday export from payroll.
PTO and time off
Leave that follows a policy, not a memory.
Accrual rules, request workflows, and balances live on the person. Managers approve what they can see. Operators set a policy once.
Payroll hours handoff
Approved hours leave as a file, not a Friday reconstruction.
Managers close the week. Operators export approved hours and approved PTO to the payroll system the employer already uses — CSV or an API payload. Peerroll does not run payroll.
Manager tools
Approvals, coverage, and birthday emails that stay private.
Managers get the queue they already run: time exceptions, leave requests, and who is out. Birthday dates stay on the file — not a company-wide calendar.
Want this workflow on your roster?
Tell us your headcount and what you run today. We will write back from hello@peerroll.com when we can show you the product.