Front-line supervisors
Maya needs two techs on the Dallas yard Thursday. The calendar shows Priya is already out — before the schedule is locked.
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.
Why it matters
When Maya asks who is out Thursday, she opens the calendar — not twelve threads and a wall chart in the break room.
Peer Roll draws the PTO calendar from leave a manager already approved. The grid shows who is out, which code, and which site. Pending requests stay in the approval queue. Birthdays do not appear here — those stay on a private manager digest. This page is coverage. Plan names and enrollments live on benefits. The calendar does not shop plans, run open enrollment, or hold a carrier file. Accrual rules and the request itself live on PTO. The calendar is the shared view of what was approved.
PTO calendar · Example Co.
PTO calendar
Example Co.
Thu · Jordan Lee
Vacation · Dallas yard · approved leave
Fri · Riley Patel
Sick · Houston warehouse · approved leave
Pending stays off the grid
A request paints the calendar after approval.
On the record
What you get in Peer Roll.
- Shared calendar of approved leave — vacation, sick, unpaid you named.
- Pending requests stay off the grid until the manager approves.
- Filter by team, site, or the people you manage.
- Same leave data as balances and the hours handoff — not a second calendar file.
- No birthdays, medical notes, or plan elections on the grid.
- Coverage only — plans and enrollments live on benefits, not on this calendar.
How it runs
A week in this workflow.
01
Approve the request
The manager of record signs the leave. Pending hours stay on the file until then. They do not paint the calendar.
02
It lands on the grid
Approved dates show the person, the code, and the site. Operators and managers read the same week.
03
Read coverage
Thursday’s yard, the Austin desk, a remote week. You see who is out without opening twelve threads.
Who uses it
Built for the jobs you already have.
Multi-site operators
Austin, Dallas, Houston, and remote. Coverage is per site, from the same approved leave as the employee file.
Related
These workflows share the same record.
Benefits admin
Plans and enrollments on the file — not a carrier platform.
Operators name the plans the company already offers. Enrollment sits on the employee record. That is light benefits admin — not shopping, not a carrier file, not open enrollment as a broker.
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.
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.
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.
Guides
How this job shows up on the public site.
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.