Onboarding and leave

Onboarding checklists links a person to the work around onboarding, offboarding, transfer or rehire. Its type, start date, target completion and status show where the transition stands. Onboarding tasks gives each item a category, assignee, due date, status and optional evidence. The categories cover practical work for IT, Facilities, Payroll, HR, Manager, Buddy, Training and the employee. This gives Admin a shared place to follow the preparation surrounding an employee move.

Leave requests records the employee, leave type, start and end dates, status, reason and approver. Leave balances holds accrued, taken and pending amounts for a named employee and leave type at an as-of date. Leave types supplies the policy category, country, accrual method and documentation setting. An employee can enter a leave request; the named approver decides the outcome and Admin records it.

• Checklist. The transition has one visible container with a type, person and target completion date.
• Task. Each assigned item has its own due date and status, so a blocked item is visible.
• Absence. The request dates and leave type sit beside the employee’s current balance record.

Choose which transition types the HR team will use, who assigns the checklist tasks and what evidence is useful for completion. The task assignee is an employee reference; make sure the person understands what to report to Admin. Agree how Admin responds to Blocked and Overdue work before a start date. A completed checklist should reflect completed individual work, rather than a status chosen in isolation.

For leave, define leave types and accrual rates by the relevant country and employee class. Identify the approver for each request and confirm what documentation is needed. Employees can enter their own leave requests, while the approval person is named on the request. Admin should compare the requested dates with the balance as of the appropriate date. The record keeps pending and taken amounts distinct, which helps explain why available leave changes.

A candidate accepts an offer for a position with a planned start date. HR Business Partner creates the employee context; Admin creates the onboarding checklist. Admin records task updates from the assigned owners as in progress, Completed or Blocked. Admin checks the open items before treating the transition as ready. After the employee begins, the person submits a leave request for a later date. The request names its leave type, start and end dates and approver. The approver decides the outcome, and Admin records Approved or Rejected and compares the record with the leave balance.

Rehearse a transfer checklist and a leave request that crosses a reporting change. The team should know who owns unfinished tasks and which approver is responsible for the requested absence. Preserve the dated record when plans change.

• New employee checklists — Admin sees pending, in-progress and overdue transitions.
• Assigned onboarding tasks — Admin tracks work by assignee and due date.
• Leave schedule — CHRO / VP People reviews requested and approved dates together.

Use employee transition for start and move cases and ongoing people operations for leave.