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.
Staffquorum 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?”
Join the waitlistLeave
Priya Shah · PTO request
Vacation
9.5
Sick
4.0
Pending
16 h
Oct 14–15 · Manager: Maya Chen · Policy: full-time salaried
- RequestedMon 9:14 AM
- Awaiting managerMaya Chen
On the record
What you get in Staffquorum.
- 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 — without a public birthday-style leak of personal data.
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.
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.
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.
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.
Onboarding and offboarding
Checklists that close because the work closed.
Day-one access, equipment, tax forms, and a first-week plan should not depend on whoever remembered the wiki. Offboarding is the same problem in reverse.
Want this workflow on your roster?
Tell us your headcount and what you run today. We will write back from hello@staffquorum.com when we can show you the product.