Prepare a new employee’s first day, minimum access, equipment, role context, required training, and early follow-up while keeping personal and employment records in the HR system of record.
The public downloads are plaintext. After import, readable project content is encrypted on your device, while operational metadata remains visible to the service.
Reuse is governed by the Public Template license.
Already use SealTask? Open this template in SealTask.
🌱
Complete template · v1
Employee onboarding
Sections
5
Tasks
14
Schedule anchor
Employee start date
Coordinate an approved employee start from preboarding and minimum access through first-week readiness and follow-up.
Employee start date: The official first day; readiness tasks are scheduled before it and early support follows it.
01
Prepare
Confirm authoritative records, ownership, role context, and first-day logistics.
Confirm the authorized start and HR record
Verify in the HR system that the hire, official start date, manager, role, work location, and onboarding owners are authorized.
High priority10 days before employee start date
□ Authoritative HR onboarding record is active
□ Manager and operational owners are recorded
Route required HR and payroll workflows
Assign approved source-system workflows for employment documents, payroll, tax, benefits, eligibility, and policy acknowledgements.
High priority9 days before employee start date
□ Required specialist workflows have owners
□ Sensitive details remain in approved systems
Prepare the role and first-week plan
Ask the manager to define role purpose, immediate priorities, key relationships, decision boundaries, and one useful first outcome.
High priority7 days before employee start date
□ Role context and current priorities are ready
□ A realistic first useful outcome is defined
Confirm first-day logistics and welcome owner
Confirm approved arrival or remote-login instructions, time zone, workspace readiness, and the person responsible for the welcome handoff.
Medium priority5 days before employee start date
□ Approved first-day instructions are delivered
□ Welcome and contingency owner is named
02
Access & equipment
Fulfill approved device, account, security, and workplace readiness requests.
Prepare and record approved equipment
Fulfill the authorized device and workplace request, record assets in inventory, and verify delivery or collection arrangements.
High priority5 days before employee start date
□ Issued assets are recorded in inventory
□ Secure delivery or collection is confirmed
Provision the approved role-baseline access
Create required accounts from the approved role baseline and route every exception through the organization’s access-request process.
□ Employee knows the approved recovery and reporting path
03
First week
Provide context, relationships, learning, and a useful first work milestone.
Deliver the manager welcome and role context
Review team purpose, role expectations, current priorities, communication norms, decision boundaries, and the first-week plan.
High priorityOn employee start date
□ Role expectations and priorities are reviewed
□ Open questions have owners and follow-up dates
Complete critical team introductions
Introduce the people needed for immediate work and explain each relationship, responsibility, and preferred collaboration channel.
Medium priority2 days after employee start date
□ Introductions focus on immediate working relationships
□ Purpose and collaboration context are explained
Start required role and policy learning
Assign the authoritative learning modules and role-specific material with realistic due dates and a named question owner.
Medium priority3 days after employee start date
□ Required learning is assigned in its source system
□ Employee knows where to take policy questions
Start the first useful work outcome
Give the employee a bounded, supported piece of real work with clear success criteria, source context, and review timing.
Medium priority4 days after employee start date
□ Scope and success criteria are clear
□ Reviewer and help path are available
04
Follow-up
Resolve gaps, review access, and confirm the next onboarding milestone.
Run the first-week check-in
Review readiness gaps, workload clarity, relationships, learning progress, access problems, and the next useful milestone.
Medium priority5 days after employee start date
□ Readiness gaps have accountable owners
□ Next milestone and support cadence are agreed
Review access and equipment against actual work
Confirm each material access grant and issued asset remains needed, resolve missing access, and remove inappropriate exceptions.
High priority7 days after employee start date
□ Material grants are reviewed against current duties
□ Missing or excessive exceptions are resolved
Confirm authoritative onboarding records are complete
Ask each specialist owner to close or escalate outstanding HR, payroll, security, training, equipment, and workplace records.
Medium priority10 days after employee start date
□ Authoritative onboarding records are current
□ Outstanding exceptions have owners and deadlines
05
Done
Verified onboarding work moves here after its source-system outcome is complete.
Completion stage — move finished work here.
Who this template is for.
People operations and HR teams coordinating a repeatable employee start.
Hiring managers who own role readiness, introductions, expectations, and useful first work.
IT, security, workplace, and payroll partners fulfilling approved onboarding requests.
When to use it.
After the organization has authorized a hire and established an official start date.
When HR, the manager, IT, security, payroll, and workplace teams have interdependent readiness tasks.
When early employee follow-up is inconsistent or access is granted without a clear role-based owner.
How to put it to work.
Anchor on the first day
Set the planning anchor to the official start date. Preparation schedules backward, while first-week and follow-up work schedules after it.
Keep HR data authoritative
Track operational completion here, but route identity, compensation, tax, benefits, background, accommodation, and employment records through approved HR systems.
Review access after use
Provision the smallest role-based access needed for the first useful work, then confirm after the first week that each grant remains appropriate.
Customize before you commit.
Replace generic HR, payroll, IT, security, and workplace gates with the owners and service targets used by your organization.
Create role-specific task groups for equipment, software, regulated training, and first deliverables only after the responsible owner approves them.
Use an employee identifier or neutral reference in operational tasks when names or roles require additional confidentiality.
Add a separate internal-transfer path when the person already has equipment, access, records, or relationships that require review rather than recreation.
Keep the system boundary clear.
SealTask coordinates readiness and follow-up. HRIS, payroll, identity, learning, workplace, and document systems remain authoritative for personal data, employment decisions, access grants, and signed records.
Coordinate in SealTask
Readiness tasks, owners, due dates, neutral request references, and operational completion status.
Role-context preparation, introduction planning, first-work milestones, and follow-up reminders.
Confirmation that an approved source-system request or record has been completed.
Offer letters, employment agreements, policy acknowledgements, eligibility evidence, and personnel records.
Authoritative access entitlements, device inventory, security events, training evidence, and performance records.
Common mistakes to avoid.
Treating account creation as readiness
A login alone does not create a useful first week. The manager must provide context, priorities, relationships, decision boundaries, and a realistic first outcome.
Requesting broad default access
Copying another employee’s permissions can overexpose systems. Start from the approved role baseline and add exceptions through accountable source-system requests.
Copying personnel data into tasks
Operational convenience does not make a task board the HR record. Keep personal, employment, payroll, and accommodation details in approved specialist systems.
Questions about this template.
What should an employee onboarding checklist include?
Include authoritative HR and payroll setup, equipment, approved role-based access, security readiness, manager preparation, first-day logistics, introductions, required learning, a useful first outcome, and early follow-up.
When should employee onboarding begin?
Operational preparation can begin after the hire and start date are authorized. Personal data and employment actions should follow the organization’s approved HR process and access rules.
Should payroll, tax, or accommodation details go in this template?
No. Track that the responsible source-system workflow is complete, but keep those details and supporting documents in systems designed and authorized for the record.
Is this template employment or HR compliance advice?
No. It is a general coordination starting point. HR, legal, security, payroll, and other responsible owners must define the requirements, records, timing, and review that apply to each employee.
Build the next part of the workflow.
Related template
Project kickoff checklist template
Prepare a decision-focused kickoff, align the team on scope and responsibilities, then turn the meeting into owned actions and a dependable operating cadence.
Convert scattered updates into a short, verified weekly briefing that separates decisions from background, surfaces risks early, and protects authoritative source records.
An interview-style guide to coordinating candidate and employee work while the ATS, HRIS, payroll, case-management, and background-check systems remain authoritative.
Client-side encryption means plaintext is encrypted on the user’s device before it is sent to a service. The service receives ciphertext. Whether this creates an end-to-end or zero-knowledge boundary depends on who controls the keys and whether the provider can cause or observe decryption.
Plaintext is the readable input to encryption; ciphertext is the transformed output intended to be unreadable without the correct key. Metadata is data about a record or interaction—such as who, when, how large, or which records are related—and may remain visible even when content is ciphertext.
This disclosure covers encrypted workspace content and its server-visible metadata. The workspace-content metadata inventory is complete for the enumerated current workspace persistence and SQL models, API-response models, and SSE event models. It is not a complete privacy-data inventory and excludes account authentication, billing, security and audit, abuse-prevention, and service telemetry domains; those domains are described non-exhaustively in the privacy policy. Metadata can itself be sensitive. Attachment ciphertext size usually reveals an approximation of the original file size.