Only 12% of U.S. employees say their company does a good job with onboarding, according to Gallup. That number should sting, because most HR teams already own software built to fix it. If your company runs on Paylocity, the Onboarding module is sitting in your talent suite right now — and whether it saves your week-one sanity or creates busywork comes down to how you set it up. This guide walks through the setup decisions that matter, the configuration steps in order, and the pitfalls we see most often, so your next new hire’s first day starts with a handshake instead of a stack of forms.
What Paylocity Onboarding Actually Does
Start with the question HR admins ask most: yes, Paylocity has onboarding. It’s onboarding software built into the platform’s talent management suite rather than a separate purchase, and it handles the stretch between ‘offer accepted’ and ‘first payroll run.’
In practice, that means new hires get a portal, on desktop or mobile or mobile app, where they complete their paperwork before they ever walk in the door. You build an onboarding program through packets of documents and tasks. The new hire works through them: personal information, tax withholding, direct deposit, e-signatures on policies and the handbook. Federal form I-9 and W-4 forms and state tax forms live in the same flow. When the onboarding checklist for new employees is complete, the data lands in the employee’s human resources and payroll record instead of waiting for someone to rekey it.
If you’re newer to the platform itself, our overview of what Paylocity is covers where onboarding fits within the broader HCM platform. For this guide, the point is narrower: the module is the bridge between a signed offer and a payroll-ready employee. Both ends of that bridge need anchoring, which is where setup comes in.
Before You Build: Three Decisions That Shape Your Setup
Teams open the module and start building packets before they’ve mapped the process those packets are supposed to run. That’s the most common setup mistake we see, and it’s not a technical one. Three decisions shape everything downstream.
First, decide what happens before day one versus during week one. The signed offer letter and the cleared background check usually mark the trigger point. Once both land, the onboarding program starts. Paperwork, tax forms, and direct deposit belong in the pre-start window. Introductions, training, and benefits conversations belong in week one, with people, not a portal
Second, decide what belongs in the packet. Every document you add is something a new hire completes on their phone before they’ve met a single coworker. Required forms, yes. The 40-page culture deck can wait.
Third, decide who owns each task. The module can assign tasks to human resources, the manager, IT, or the new hire, with due dates and reminders. If a task has no named owner, it will slip, and automated reminders can’t fix ownership that was never assigned.
One note on the bigger arc: onboarding researchers often describe four phases, running from pre-boarding through the first year. The module you’re configuring mainly powers the first phase and feeds the second. What happens in months two through twelve still belongs to your managers, and no packet replaces that.
Setting Up Paylocity Onboarding, Step by Step
With those decisions made, the build itself moves quickly. Work in this order.
Build Your Onboarding Event Packets
Paylocity organizes onboarding around events: bundles of documents, tasks, and forms assigned to a new hire when onboarding kicks off. Build your standard packet first. That usually means the offer confirmation, required federal and state forms, company policies that need signatures, and the profile fields you want completed, like emergency contacts and direct deposit.
Then resist the urge to build one packet for everyone. A field technician in Texas and a salaried manager in Illinois don’t need identical documents. Most teams end up with a small set of packet variations by employee type, location, or department. Start with two or three. You can add more once real hires expose the gaps.
Custom fields deserve attention here too. If your payroll or benefits setup depends on data that isn’t in the standard forms (uniform sizes, license numbers, shift preferences), add those fields now, so the information arrives with the paperwork instead of through a follow-up email.
The packet is also where a new hire forms their first impression of your company as an employer, before any human has said hello. A short welcome message from the manager, a first-week schedule, or a photo of the team costs nothing to include and changes the tone of the entire exercise. Forms alone say “process.” A welcome says “we’re expecting you.”
Assign Tasks and Owners
Documents cover only half of onboarding. Tasks cover the rest: order the laptop, create system accounts, schedule orientation, assign a first-week buddy. This task list is your onboarding checklist, built into the event itself — give each item a named owner and a due date.
The due dates matter more than they look and will have an impact on new hire success. Anchor them to the start date, so every new hire triggers the same countdown automatically. A workable default timeline: portal invitation goes out five days before the start date, forms and direct deposit complete by three days before, equipment and accounts ready two days before, orientation and the manager check-in on day one. Adjust the numbers to your hiring reality. A retail team backfilling a shift in four days needs a compressed version of the same sequence, not a different process.
This is also where notifications live. Decide who gets alerted when a task is overdue, because an alert nobody receives is the same as no alert.
Set Up E-Signature and Compliance Documents
E-signature is where the module earns its keep. Handbook acknowledgments, policy sign-offs, and offer paperwork all move through the portal with a timestamped signature attached to the employee record — an audit trail that answers the question before it’s asked. No chasing, no scanning, no ‘I never got that form”.
For the compliance documents, accuracy beats speed. Confirm your I-9 workflow matches how you actually verify documents, since Section 2 still requires human review on a deadline. Load the correct state and local withholding forms for every state you hire in, not just headquarters. If you hire in new states as you grow, add a recurring task to review this list. It goes stale quietly.
Connect Onboarding to Your ATS, Payroll, and HR Records
Two handoffs decide whether onboarding feels automatic or duct-taped.
The first is upstream: your applicant tracking system. If you recruit through an ATS (Greenhouse, Spark Hire, and Ashby all offer Paylocity integrations, among others), connect it so candidate data flows into the onboarding event instead of being retyped. Name spellings, start dates, and compensation details should survive the trip from offer letter to employee record untouched.
The second is downstream: payroll. This handoff is native, since onboarding and payroll share a platform, but it still needs checking. Run a test hire before your first real one. Confirm the tax setup, direct deposit details, and pay group assignment all land where payroll expects them. A first-paycheck problem is the fastest way to undo a good first week.
Best Practices That Separate Smooth Launches From Messy Ones
Setup gets the module running. These habits keep it working.
Open the portal before day one. The preboarding window is the whole advantage. When paperwork is done early, day one belongs to people. The same Gallup research found employees who had an exceptional onboarding experience were 2.6 times as likely to be extremely satisfied with their workplace — and satisfaction in the first months is what employee engagement and retention rates are built on. None of that comes from a great forms experience. It comes from what the forms no longer crowd out.
Keep the packet lean. Every added document is another place for a new hire to stall. If a document isn’t needed before the first payroll run or the first day, schedule it for later instead of front-loading it.
Assume the phone. Many new hires, especially hourly and deskless workers, will complete onboarding entirely on a mobile device. Preview your packet on the mobile app before you assign it to anyone.
Tell new hires the invitation is coming. A portal email from a system they’ve never heard of looks like phishing, and a wary new hire who ignores it stalls the whole sequence. A one-line heads-up from the recruiter or manager (“you’ll get an email from Paylocity today, that’s us”) keeps completion on schedule.
Give every automated task a human owner. Automation moves the paperwork; it doesn’t welcome anyone. The manager’s first-day check-in, the buddy assignment, the week-one lunch — those belong on the task list precisely because they’re human, and they’re the tasks most likely to be skipped when nobody is named.
Review completion reports weekly during heavy hiring. The module shows who’s stuck and where. Ten minutes with that report on Friday catches the new hire whose I-9 stalled before it becomes a problem on Monday.
Common Pitfalls (and How to Avoid Them)
Most Paylocity onboarding problems trace back to a handful of patterns.
Orientation and onboarding get treated as the same thing. The portal handles paperwork; orientation handles people. Teams that try to run orientation scheduling through document tasks end up confusing both. Keep the portal focused on completing records, and schedule orientation as a task with a human owner.
A stalled packet stalls payroll. When a new hire doesn’t finish direct deposit or tax forms, the problem often surfaces at the worst possible moment, during a payroll run. That’s the case for weekly completion checks, and for due dates set safely ahead of the payroll cutoff rather than on it.
Everything gets automated, including the parts that shouldn’t be. If a new hire can complete onboarding without a single human interaction before day one, the module is working and the employee experience is failing. Automate documents. Don’t automate welcome.
Go-live gets treated as done. Your first few hires will expose missing fields, confusing instructions, and documents in the wrong order. That’s normal. Fix in the second week what real hires uncovered in the first, and revisit the packet quarterly, because policies, states, and forms all change.
When It’s Worth Getting Help
Plenty of human resources teams set this module up themselves, and this guide is meant to make that easier. Setup gets harder when you’re hiring at volume, spread across many states, or mid-implementation with a dozen other modules to configure at once. That’s when an experienced partner pays for itself in avoided rework. Our team has spent 15+ years working exclusively on the Paylocity platform, and Paylocity implementation support is one of the things we do most, including onboarding builds shaped around how a company actually hires.
The Short Version
Paylocity Onboarding rewards teams that decide before they build. Map the pre-start window, keep packets lean, name an owner for every task, and test both handoffs before your first real hire. Get that right, and paperwork stops being what a first day is about.
Ready to put this to work? Start with a single packet, built end to end for your most common hire, and let a test run prove the flow. If you’d rather have experienced hands build it with you, we’re easy to reach.
Paylocity Onboarding FAQ
How long does it take to set up Paylocity onboarding?
Paylocity onboarding setup for a single, well-defined packet commonly comes together in days rather than weeks. The timeline stretches with complexity: multiple employee types, multi-state tax forms, and an ATS integration each add configuration and testing time. Mapping the hiring process behind the packets — not configuring the software — is usually the longest part of the build.
Can new hires complete onboarding before their first day?
Yes, and they should. Yes — pre-start completion is what Paylocity onboarding is built for. Once an onboarding event is assigned, new hires can finish tax forms, e-signatures, and direct deposit from any device before their start date. Completing paperwork early frees day one for orientation and introductions instead of forms.
Does Paylocity onboarding handle I-9s, W-4s, and state tax forms?
Federal I-9 and Yes — federal I-9 and W-4 forms plus state and local tax forms are built into the Paylocity onboarding flow, and completed data lands directly in the employee’s HR and payroll record. HR teams still own the verification steps that require human review, such as I-9 Section 2, which must be completed on a deadline.
Does Paylocity onboarding work on mobile?
Yes — Paylocity onboarding software runs in the web browser and the Paylocity mobile app, so new hires can complete the entire flow from a phone. Mobile completion matters most for hourly and deskless workers, who may never sit at a company computer.
