Employment Lifecycle Stages

Overview

When an employment is created, it goes through different stages. These stages are referred to as "Employment lifecycle stages" and are indicated by the employment_lifecycle_stage field. Let's look at these stages in detail below:

Employment Lifecycle Stage	Description
`employment_creation`	This is the initial stage when required fields are still missing. Employment data can be submitted once using Create employment and later completed via Update employment . Once all required information is provided, the stage automatically advances to `employee_self_enrollment`.
`employee_self_enrollment`	At this stage, the employee or contractor must log in to the Remote platform and complete the necessary forms, which vary by country. Some information can be pre-filled with the Update employment endpoint. Refer to the API specification for details.
`right_to_work_check`	Remote verifies the employee's or contractor's work eligibility for the specified country. After passing this check, Remote will facilitate contract signing. There's no need for Remote API at this stage.
`contract_signing`	Once self-enrollment (and, the right-to-work check, if applicable) is complete, the employee remains in this stage until both parties sign the Employment Agreement Contract. This process takes place outside of the Remote API with Remote assisting as needed.
`remote_enrollment`	After contract signing is done, Remote handles benefits enrollment, payroll setup, and other administrative steps. No API action is required at this time. This is the final step before employment begins.
`onboarded`	The employee is officially ready to start work.
`offboarded`	The employment is archived, and the employee is offboarded.

The transition to the offboarded stage takes time, as it requires both the employment to be archived and the termination_date to be reached. Here are some of its edge cases:

Employee initiated resignation after provisional start date:
If the employee resigns through Remote's platform and their termination_date is after the provisional_start_date, the employment_lifecycle_stage remains onboarded until the termination_date is reached. Once the termination_date passes, the employment status changes to archived, and the employment_lifecycle_stage is updated to offboarded.
Termination or resignation before provisional start date:
If the employee is termination or resigns before their provisional_start_date and has not started onboarding, Remote will delete the employee without triggering any webhooks. After deletion, API calls to the employments endpoints for that employee will return a 404 response.

ℹ️ The employment_creation is the only step that requires data to be sent through the API. The other stages will move forward automatically based on the events that happen in the Remote platform or taken by any party—company, employee, or Remote.