New-hire week fails in the inbox. The offer went out as an attachment. The handbook is a hope. The I-9 acknowledgement came back from a personal address — or it did not. When counsel asks who signed the 2026 policy, someone reconstructs a thread.
Staffquorum keeps the packet on the person. Operators assemble it from templates, send it in the product, and watch status on the same record. Employees sign under Me: type a name or draw on a canvas. That is e-sign onboarding packets.
What a packet is
A packet is the hire paperwork that should exist before day five: offer letter, handbook, I-9 acknowledgement — or the files you already use. It belongs to Jordan, not a shared folder.
Create and send from Packets. The employee sees the work on Me. Status on the file is sent, signed, or still open. Sends and signatures are audit events: who, when.
No second login. No chase email whose attachment disappears into a personal inbox.
How the week runs
- Build the packet. Pick templates or attach the files Elena already uses. The packet is on the employee file.
- Send it in the product. Jordan opens Me, types a name or draws a signature. Nothing depends on a side PDF coming back.
- Read status and the trail. The next operator can answer “who signed?” without hunting three inboxes.
The hire checklist still lives on onboarding: laptop, accounts, tax forms, a first 1:1, with owners and due dates from the start date. Reminders when a task is due or late live on onboarding workflows. The packet is the signature. The checklist is the work.
Where the file sits after
Signed packets land on the employee e-file — folders you name, next to later uploads. That library is document library, not a company-wide document system. Documents is the attachment story. E-sign is the signature. The library is where those files sit once they exist.
When counsel asks for Luis’s I-9 and the 2026 handbook, you open his file. You do not search HR_SHARE_FINAL.
What this is not
E-sign packets are not a standalone signing product with its own vendor login. They are not a campaign that emails the whole company a new policy and hopes. They are not a retention engine or a version tree across every policy in the org.
Policy refresh still works the same way: send the new packet, get a list of who signed. That is better than an all-hands note.
We do not claim every workspace already sends invite or reminder mail. When mail is off, the packet is still in the product on Me. The employee can sign when they open it.
Why this beats the hallway PDF
A hallway PDF has no status. A personal inbox has no audit you can show. A shared drive has no owner when Elena is out.
A packet on the file has a state. The next person covering the desk can see it. The employee can finish it on a phone from the Me tab — the same surface as Clock and Time off.
If you already run hire paperwork that way and it works, stay. If Monday still depends on three attachments and a hope, read the e-sign page and join the waitlist. Log in if you already have a workspace.