# Onboarding: joining and leaving, against your shared people records

> Onboarding and offboarding as tasks against the person record, so access, equipment and introductions are tracked in the same place the person already exists.

Source: https://www.cordango.com/capabilities/onboarding/
Language: en

[Home](https://www.cordango.com/) [Capabilities](https://www.cordango.com/capabilities/) Onboarding

PEOPLE

# Onboarding

A first week that is a checklist against a real person record. Available as a ready-to-use Cordango capability.

[See Cordango in action →](https://www.cordango.com/contact/) [How it runs →](https://www.cordango.com/capabilities/onboarding/#how)

Onboarding People

ON

A first week that is a checklist against a real person record

## What it builds on.

Onboarding goes wrong in the gaps between departments. IT does not know about the start date, facilities does not know about the desk, and the manager finds out when somebody arrives without a laptop. All three are working from different lists.

Here there is one list, hanging off the person record everybody can already see. The start date is a field, not an email, and the tasks reference the same person that Equipment and PTO reference.

-   USES People records, start dates, teams and managers
-   USES The permission model, so access ends when the record closes
-   USES Automation, so a task can open when a date arrives

[The People foundation →](https://www.cordango.com/people/)

Available from the start Onboarding

-   PLAN Task templates per role, team or location
-   OWN Each task owned by a named person, not a mailbox
-   TRACK What is done, what is late, before day one
-   EXIT The same list in reverse when somebody leaves

## How it actually runs.

1 

#### A start date is set

The person record exists before day one, with a role, a team and a manager.

2 

#### The checklist opens

Tasks are generated from the template for that role and assigned to the people who own them.

3 

#### Equipment and access follow

A laptop assignment and an account both point at the same person, so nothing is issued to a name that does not exist.

4 

#### Leaving runs the same way

Offboarding reuses the structure in reverse. Return the equipment, close the access, and there is one place that says whether it happened.

## What you can change.

Use the standard version where it fits. Change only the parts where your company is genuinely different.

DATA 

### Task templates

A different list for a developer, a field engineer and a working student. Build the ones you need.

RULES 

### Timing

Two weeks before, day one, end of first month. Tasks open when they should rather than all at once.

STATES 

### Task states

Open, blocked, done, not applicable. Match the way your teams actually report progress.

VIEW 

### Per-role views

IT sees only the access tasks. The manager sees the whole plan. The joiner sees their own.

MORE

## What it works with.

-   [**PTO & Absence** Absence requests and approvals on the people you already have](https://www.cordango.com/capabilities/pto/)

NEXT

## One foundation. Everything on top of it.

Onboarding does not create a shadow list of new starters. Tasks, owners and dates attach to the People record that HR, Equipment and PTO all already use.

[See Cordango in action →](https://www.cordango.com/contact/) [All capabilities →](https://www.cordango.com/capabilities/)