Onboarding should begin before the first-day checklist

The accepted-candidate handoff

Onboarding usually begins too late. The offer is accepted, the candidate is still sitting in the hiring tool, and the people team starts rebuilding context by hand. That creates avoidable gaps: wrong manager, missing start date, late access, or documents prepared from stale details.

A better onboarding path begins at conversion. The accepted candidate becomes a future hire, and useful hiring context is carried forward with appropriate boundaries.

Represent the future hire early

A future hire should exist before day one. The record can hold start date, manager, group, location, suggested work email, and pre-start tasks. This gives HR, the manager, and IT or operations a shared object to coordinate around.

Perelan Onboarding presents the core employee foundation as available and the automated workflow layer as Preview where runtime behavior should be validated.

Collect data once

The employee should not answer the same question in a form, a chat thread, and a document. Collect preferred name, contact details, address, emergency contact, and notes once where supported, then let the workflow use the resulting record.

Give each role different work

The employee, manager, and HR team do not need the same checklist. The employee might complete personal details and read policies. The manager might prepare team context. HR might validate documents, groups, and access prerequisites.

Use milestones and dependencies

Good onboarding is date-centered. Some steps happen before start, some at start, and some after the first week. Dependencies matter: a document should not be prepared before required details are collected, and account setup should not wait until the first day.

Continue into the first month

Onboarding should connect to goals, performance, time off, documents, and access. The first day is not the end of the process. It is the moment when the preparation becomes visible to the new employee.