New-hire week
Jordan starts Monday. Offer, handbook, and I-9 acknowledgement should be signed before day five — on the file, not in three inboxes.
E-sign packets
A packet you send. A signature in the app. Status on the file.
People ops builds an onboarding packet from templates — offer letter, handbook, I-9 acknowledgement. The employee signs in Staffquorum. The file shows sent, signed, or still open, with a trail.
Why it matters
When counsel asks who signed the 2026 handbook, you open the packet on the file. You do not hunt an inbox for a PDF that may or may not have come back.
Staffquorum keeps e-sign onboarding packets in the product. Operators assemble a packet from templates on Packets, send it to the person on the roster, and watch status on that same record. Employees sign under Me — type their name or draw a signature on a canvas. Create, send, sign, status, and audit stay together. No second login. No chase email with an attachment that disappears into a personal inbox.
Join the waitlistPackets
Jordan Hale · Day one
- Offer letterSignedSep 8
- Employee handbook 2026SignedSep 9
- I-9 acknowledgementAwaitingDue Fri
Sign in the app
TypeDraw
Jordan Hale
Typed name on file. Elena sent the packet Sep 8. Jordan signed the handbook Sep 9, 4:12 PM.
On the record
What you get in Staffquorum.
- Templates for offer letters, handbooks, and I-9 acknowledgements.
- Operators create and send a packet from Packets — tied to the employee file.
- Employees sign in the app: type a name or draw on a canvas.
- Status on the file: sent, signed, or still open.
- An audit trail of who sent, who signed, and when.
- Packets on Me for the employee — same record operators already run.
How it runs
A week in this workflow.
01
Build the packet
Pick templates — offer, handbook, I-9 ack — or attach the files you already use. The packet belongs to the person, not a shared folder.
02
Send it in the product
The employee sees the packet on Me. They type their name or draw a signature. Nothing depends on a side attachment coming back.
03
Read status and the trail
The file shows who signed and when. Sends and signatures are audit events. You can answer a later question without reconstructing a thread.
Who uses it
Built for the jobs you already have.
Policy refresh
The handbook changes. You send the new packet and get a list of who signed — not a hope that people opened the all-hands note.
Related
These workflows share the same record.
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.
Mobile employee self-service
Clock, Time off, and Me — on a phone they will actually use.
Employees and managers get a phone bottom bar: Clock, Time off, and Me. Large punch controls, stacked PTO, and document or onboarding cards. Same record as the desk.
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.
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.