Growing teams with mixed types
Full-time salaried, hourly warehouse, and a few contractors should not share one informal rule.
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.
Why it matters
Balances should not live in the head of whoever set up the calendar. When Priya requests two days, the request hits her manager, pending hours stay visible, and the policy on her file is the one that applies.
Peer Roll keeps vacation, sick, and unpaid codes you define. Accruals attach to employment type and tenure, not to a side spreadsheet. Pending requests do not double-count against a close. History stays after the manager changes, so you can answer “what did we approve last March?” Approved leave also paints the shared PTO calendar so coverage is a grid, not a thread. On a phone, those balances stack on the Time off tab so a thumb can request leave without a desktop calendar.
PTO · Example Co.
Time off · manager
Example Co.
Vacation
40 h
Sick
24 h
Pending
16 h
Jordan Lee · vacation
Mar 18–19 · 16 hours · waiting on Sam Rivera
ApproveDecline
Manager view. Pay is not on this screen.
On the record
What you get in Peer Roll.
- Vacation, sick, and unpaid codes you name.
- Balances and pending hours on the employee file.
- Requests that route to the manager of record.
- History that survives a manager or site change.
- A team view of who is out — the shared PTO calendar is that grid.
- Stacked PTO cards on a phone — vacation, sick, and pending, one under the next.
How it runs
A week in this workflow.
01
Set the policy
Name the codes and how they accrue. Attach them to employment types so new hires inherit the right rule.
02
Employees request
They pick dates and a code. Pending hours show on the file before anyone approves.
03
Managers decide
The queue is leave plus time exceptions. Approved time writes to the balance and the coverage view.
Who uses it
Built for the jobs you already have.
Managers who already run coverage
They need to see who is out next Thursday without opening twelve threads.
Related
These workflows share the same record.
PTO calendar
Who is out, on a shared calendar of approved leave.
Approved vacation and sick time land on a team calendar. Managers and operators see coverage for the week. Pending requests stay off the grid until someone signs them. Plan names and enrollments live on benefits.
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.
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, as a CSV. Peer Roll 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.
How Peer Roll compares
The time clock is included in Peer Roll. Teams can switch from BambooHR and keep the payroll they already use. BambooHR alternative.
Want this workflow on your roster?
30-day free trial, no credit card needed. Then $4 per active person per month. The time clock is included.