A new hire’s first week says a lot about an organization. When the process is smooth—forms ready, accounts set up, the right people notified—it signals that the company is organized and takes the hire seriously.
When it isn’t smooth, the new employee spends their first morning chasing down their manager for a DocuSign link, filling out the same address twice in different PDFs, and wondering if HR has heard of email.
The stakes are higher than they look. According to Gallup, only 12% of employees say their company’s onboarding process is adequate. SHRM research puts it bluntly: roughly 80–86% of new hires decide whether to stay or leave within their first six months. And replacing an employee can cost roughly 50%–200% of their annual salary, depending on role seniority and complexity (multiple HR studies including Gallup and SHRM).
The bottleneck is almost always the forms. Not because onboarding is complicated, but because most onboarding form setups weren’t designed—they accumulated.
This guide is about designing it properly.
On this page
What an onboarding form is actually for
The obvious answer is “collecting information”. But that’s only one of three jobs an onboarding form needs to do.
Job 1: Collect data accurately, once. The new hire enters their legal name, address, banking details, and emergency contacts one time, and that data flows to wherever it needs to go—payroll, IT, facilities, compliance. Not re-entered by an HR coordinator. Not typed into three different systems.
Job 2: Trigger the right actions. When someone submits their onboarding form, a chain of things needs to happen: payroll gets banking details, IT gets a laptop request, their manager gets a notification, their department gets added to a calendar invite. A form that sits in an inbox waiting for a human to manually forward it is a bottleneck, not a system.
Job 3: Create a paper trail. Signed acknowledgments of the employee handbook, NDA, and data protection policy aren’t just bureaucracy—they’re legally meaningful. If a dispute arises later, the question “did they sign it?” needs a clean answer.
Most onboarding form setups handle Job 1 adequately, Job 2 poorly, and Job 3 inconsistently. This guide addresses all three.
What to include: field-by-field
The sections below cover a complete onboarding form. Not every organization needs all of them—use conditional logic to show or hide sections based on role type, employment status, or location.
Personal information
| Field | Notes |
|---|---|
| Full legal name | Must match government ID—flag this in the field description |
| Preferred name | Separate from legal name; used for email, Slack, badges |
| Date of birth | Required for benefits enrollment and some compliance |
| Home address | Use Address Autocomplete to reduce errors |
| Personal email | For pre-start communication before work email is set up |
| Phone number | Mobile preferred; used for IT account setup and emergencies |
| Emergency contact name + relationship + phone | At least one required |
Employment details
These fields are often pre-filled by HR and presented to the employee for confirmation, rather than left blank for them to complete.
| Field | Notes |
|---|---|
| Job title | Pre-fill from offer letter |
| Department | Triggers routing to the right department head |
| Start date | Used to time IT provisioning and access requests |
| Employment type | Full-time / part-time / contractor — determines which other sections appear |
| Work location | Office / remote / hybrid — determines equipment needs |
| Manager name | For notification routing |
Tax and payroll
These fields handle sensitive financial data. Make sure the form is served over HTTPS and that submission data is encrypted at rest. See how PlatoForms handles data security for specifics.
| Field | Notes |
|---|---|
| Tax identification number | SSN in the US; varies by country |
| Filing status | For payroll withholding; based on the employee’s W-4 |
| Bank name | For direct deposit setup |
| Account number + routing number | Mark as sensitive; do not display in submission previews |
| Payment method preference | Direct deposit vs. check — if your payroll system offers options |
Equipment and access requests
This section is often routed directly to IT, separate from the HR submission.
| Field | Notes |
|---|---|
| Laptop preference | Mac / Windows — if applicable |
| Required software | Dropdown with common tools; open text for others |
| Building access needed? | Yes/No; if yes, which locations |
| Remote work equipment needed? | Monitor, keyboard, headset, etc. |
Benefits enrollment
This section typically only appears for full-time employees—use conditional logic based on employment type.
| Field | Notes |
|---|---|
| Health insurance plan selection | Dropdown with available plans |
| Dependents to add? | Yes/No; if yes, collect names and dates of birth |
| Dental / vision enrollment | Yes/No per plan |
| 401(k) / pension contribution | Percentage or flat amount |
| Beneficiary name + relationship | For life insurance and retirement accounts |
Agreements and acknowledgments
This is the section most organizations handle poorly—printed, signed by hand, scanned, emailed, and filed in a folder that nobody ever looks at again.
Each item below should be a digital signature field with a timestamp. Not a checkbox.
| Document | Notes |
|---|---|
| Employee handbook acknowledgment | “I have received and read the employee handbook” |
| Non-disclosure agreement | If required for the role |
| Code of conduct | Ethical guidelines and conflicts of interest |
| Data protection and acceptable use policy | Especially important for roles handling customer data |
| Background check consent | If applicable, this should be first—delay can hold up the start date |
Template: New Employee Onboarding Checklist — includes a signature field pre-configured for agreements.
Role-specific variations
A single onboarding form with conditional logic handles role variation more cleanly than maintaining separate forms. Use a dropdown at the top—“I am joining as: Full-time employee / Part-time employee / Contractor / Intern”—and show only the relevant sections.
| Role type | Sections to show / hide |
|---|---|
| Full-time employee | All sections including benefits enrollment and 401(k) |
| Part-time employee | Benefits enrollment conditional on eligibility; no 401(k) in some jurisdictions |
| Contractor / freelancer | Skip benefits, 401(k), and building access; add W-9 / tax form upload |
| Intern | Simplified—personal info, emergency contact, equipment, handbook acknowledgment |
| Remote employee | Show remote equipment section; skip building access |
Related templates for role-based documents: Employee Application Form · Employment Contract Template
Building it: what PlatoForms handles
Starting point: migrate what you already have
Most organizations don’t start from zero. Choose whichever applies:
If you have existing PDFs — Upload them to PlatoForms and use AI field recognition to detect fields automatically. For most HR PDFs (I-9, W-4, direct deposit form, NDA), AI identifies field types, labels, and groupings without manual setup. You can then layer conditional logic, signature fields, and routing on top of the original structure. For small to medium PDFs, this is typically the fastest path.
If you’re currently using Google Forms — Import your existing form directly. Questions, options, and structure carry over without rebuilding. From there you can add the things Google Forms doesn’t support: signature fields, conditional sections, multi-department routing, and PDF output.
See the full walkthrough: How to Import Google Forms to PlatoForms.
Conditional sections by role
The Logic panel handles showing and hiding sections based on employment type, location, or any other field. One form, cleanly adapted to each hire’s situation. When a contractor selects their role type at the top, the benefits section disappears and the W-9 upload field appears. The new hire sees only what’s relevant to them.
Digital signatures with audit trail
The Signature field lets new hires sign acknowledgments from any device—phone, tablet, laptop. PlatoForms generates a signature certificate for each signed document with a timestamp and the submission data at the time of signing. If you ever need to verify that someone signed the NDA on their first day, the record is there.
Routing to multiple departments
Payroll doesn’t need to see the equipment request. IT doesn’t need to see the banking details. Use Logic-based Email Routing to send each section’s data to the right team automatically on submission—payroll gets the tax and banking fields, IT gets the equipment request, the manager gets a notification. No manual forwarding.
Generating onboarding documents from the submission
Once a new hire submits their form, many HR teams need to immediately produce documents pre-filled with what was just collected—an offer confirmation letter, a welcome packet with their name and role, an equipment order form. PDF Templates let you design a PDF output format inside PlatoForms: static text plus dynamic variables pulled from the submission (employee name, role, start date, department). When the form is submitted, the PDF generates automatically. Find it at Form Editor → More (⋯) → PDF Template.
Sending the form before day one
New hires typically receive their onboarding form by email before their start date. Use Form Notifications to send a branded confirmation immediately on submission, and share the form link directly in your offer acceptance email or via the Bulk Pre-fill feature—which lets you pre-populate fields like name, role, and start date from a CSV so the new hire only fills in what you don’t already know.
Multi-language support
If your organization hires internationally, PlatoForms supports multi-language forms and includes AI-powered translation to generate field labels and instructions in other languages in one click. Useful if your onboarding form needs to work in both English and Spanish, for example, without maintaining two separate forms.
Mobile-first completion
New hires may complete their onboarding form on a phone, especially if they’re still wrapping up their previous role. A Conversational layout presents one question at a time, which works significantly better on mobile than a long scrollable form and tends to improve completion rates for longer forms.
Start from a template: New Employee Onboarding Checklist
Before you publish: a checklist
Content
- Legal name field is clearly distinguished from preferred name
- Sensitive fields (SSN, banking) are marked and not displayed in submission previews
- Employment type dropdown triggers the right conditional sections
- Background check consent appears before any processing that requires it
- All agreement sections have signature fields, not checkboxes
Routing
- Payroll receives tax and banking fields
- IT receives equipment request fields
- Manager receives a submission notification
- New hire receives an automatic confirmation with next steps
Usability
- The form has been tested on a mobile device
- A new hire with no context can complete it without needing to call HR
- Required fields are limited to what’s needed before day one
- Completion time is under 15 minutes for a full-time employee
One last thing
Onboarding forms are often the first real interaction a new hire has with your internal systems. A form that’s clear, organized, and works on their phone signals something about the organization they’re joining. A form that makes them scan and email PDFs signals something else.
The technology isn’t the hard part. The discipline to keep the form current—updating it when benefit plans change, when a new compliance requirement comes in, when the IT equipment list shifts—is what separates onboarding forms that work from ones that quietly drift out of date.
Need a starting point? Browse the PlatoForms HR form templates, including employee information forms, NDA templates, and timesheet forms. Or if your organization already has PDF onboarding documents, convert them to online forms and add signatures and routing on top.
