Features
The people-ops pieces operators run every week.
Directory, time with punch evidence, PTO, documents, onboarding and offboarding, manager tools, HR-only notes, in-app help, and roles. This is the product — not a poster of a roadmap.
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.
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.
Documents
Files on the record, not in a drive named HR_SHARE.
Offer letters, handbooks, I-9 packets, and signed acknowledgements attach to the employee. Access follows the same roles as the rest of the product.
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.
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.
HR-only notes
Private context that does not leak to the team view.
People ops sometimes needs a note that is not for the manager and not for the employee. Staffquorum keeps that space on the file — behind a role.
Help and tutorial
Guidance in the product, not a PDF nobody opens.
Employees need to know how to punch and request leave. Managers need to know how to close a week. Staffquorum puts a short tutorial and contextual help in the app.
Roles and access
Who can open a file is a product decision.
Operators, managers, and employees do not share a login. Sensitive fields sit behind roles you can explain to counsel — and to the person whose file it is.
People directory
One record per person. Searchable. Owned.
Name, legal data, job, site, manager, employment type, and status sit on a single employee file. The directory is how you find someone, not a weekly export from payroll.
- Reporting lines so approvals know where to go.
- Sites and remote flags for time and PTO rules.
- Status that reflects hire, leave, and termination, not a cell color.
People
Directory
| Employee | Role | Site | Manager | Status |
|---|---|---|---|---|
MCMaya ChenClock Out | Operations | Austin | — | Active |
JHJordan HaleClock In | Field tech | Dallas | Maya Chen | Active |
PSPriya ShahClock Out | Finance | Remote | Maya Chen | PTO |
LOLuis OrtegaClock In | Warehouse | Houston | Elena Brooks | Active |
EBElena BrooksClock Out | People ops | Austin | Maya Chen | Active |
Employee time tracking
Clock in with location and IP on the punch.
Staffquorum treats attendance as evidence. Each punch stores time, device, source IP, and location when the browser or device can provide it. That matters for multi-site teams, field techs, and anyone who has sat through a wage-hour review with a half-complete log.
- In and out punches, breaks, and manager exceptions.
- Timesheets that close against the employee record.
- Site match when you define a yard, floor, or warehouse.
Time 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
Leave
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
PTO management
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 adjust a policy once, not in twelve calendars.
- Vacation, sick, and unpaid codes you define.
- Pending hours that do not double-count against a close.
- History that stays after the manager changes.
Documents
Files on the record, not in a drive named HR_SHARE.
Offer letters, handbooks, I-9 packets, and signed acknowledgements attach to the employee. Access follows the same roles as the rest of the product. We do not treat a shared folder as document control.
- Templates for new-hire packets.
- Acknowledgement tracking so you know who signed.
- Separation from the public birthday list and the all-hands chat.
Documents
Luis Ortega · Houston
- Offer letter.pdfSignedAug 12
- Employee handbook 2026SignedSep 2
- I-9 packetOn fileAug 14
- Direct deposit formPendingDue Fri
Onboarding
Day one · Jordan Hale
- Send new-hire packetPeople ops
- Create accounts and badgeIT
- First-week planManager
- Acknowledge handbookEmployee
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: collect the laptop, cut the accounts, keep the file.
- Task owners by role: manager, IT, people ops, the employee.
- Due dates that follow the start date or last day.
- A remaining-work view so nothing hides in email.
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. Staffquorum also sends a birthday digest to the manager of record. Dates stay on the employee file — not a company-wide calendar.
Manager digest
This week on your team
- Luis Ortega · birthdayThu · Warehouse
- Elena Brooks · birthdaySat · People ops
- Priya Shah · PTOTue–Wed
Sent to the manager of record. Dates stay on the employee file, not a shared calendar.
HR-only notes
Private context that does not leak to the team view.
People ops sometimes needs a note that is not for the manager and not for the employee. Staffquorum keeps that space on the file, behind a role, with an audit event when someone opens it.
- Visible to operators you grant — not the default manager view.
- Invisible in the employee’s own profile.
- Separate from birthday digests and public coverage lists.
Employee file
HR onlyNote on Priya Shah
Prefers email before phone for leave follow-ups. Intermittent leave documentation is on the file — do not discuss in the manager queue.
Visible to operators. Hidden from Maya Chen (manager) and from Priya’s own view. Last opened by Elena Brooks · today 8:41 AM.
In-app help
How do I clock in?
- 1. Open Time on your phone or desk.
- 2. Tap In. Wait for the on-site or off-site note.
- 3. If the location looks wrong, tell your manager before the week closes.
Help and tutorial
Guidance in the product, not a PDF nobody opens.
A short tutorial on first login. Contextual help on punch, leave, documents, and approvals. Replay it when a new supervisor starts. People ops should not re-teach the clock every Monday.
Roles and access
Who can open a file is a product decision.
Operators, managers, and employees do not share a login. Sensitive fields (compensation, medical notes, government IDs) sit behind roles. See roles and access for the day-to-day split, and Security for encryption, backups, and how we talk about HIPAA.
- Least-privilege defaults. Extra access is granted, not assumed.
- Audit events when a record or document is opened or changed.
- No SOC 2 or HIPAA badge on this page. We will not invent one.
Want these workflows 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.