Module · Arrivals & departures

every arrival follows a journey, not a lost checklist.

One template per journey type, tasks with an owner and a deadline, documents to provide and the contract signed from the employee's workspace. The newcomer goes through a welcome area until they sign, the departure runs through to archiving.

what changes when the arrival is prepared.

Nothing is forgotten

The arrival template lists everything: admin, equipment, access, training, documents, contract. Each task has an owner, office manager, manager or employee, and a deadline set from the arrival date.

The employee does their part

From their welcome area, without a password, they upload their documents, read their contract and sign it. Their full workspace opens as soon as the contract is signed.

The departure is clean too

The departure journey runs through equipment return, access revocation and archiving. The departed employee keeps their vault, read-only.

How it works

from the first day to the last.

  1. You add a newcomer

    From the employee record, you pick "New arrival" and the arrival date. The journey starts from the template, with deadlines computed from day 0.

  2. Everyone sees their tasks

    The office manager, the manager and the employee each have their tasks. Overdue ones are flagged, a reminder can be sent, and the history keeps who did what.

  3. The contract is signed online

    You upload the contract (PDF or Word), the employee reads it from their welcome area, ticks "I have read and accept" and signs. Full access opens right away.

  4. The departure follows its journey

    When the time comes, the departure journey starts: equipment, access, documents, then archiving of the employee. Their payslips and documents stay accessible read-only.

everything the module can do.

  • Two default templates, arrival and departure, adjustable at will
  • Tasks by category: admin, equipment, access, training, documents, contract
  • Owner per task: office manager, manager or employee
  • Deadline in days from the arrival date (day 0)
  • Task types: simple, document to provide, contract signature
  • Documents uploaded by the employee, sealed and filed in their vault
  • Contract uploaded as PDF or Word, read and signed from the employee workspace
  • Welcome area: access limited to arrival steps until signature
  • Tracking of ongoing journeys: progress, overdue tasks, reminders, history
  • Departure journey through to return, access revocation and archiving
  • Former-employee vault kept read-only
  • Employees already in place imported without a journey
Included with the core

The journey writes to the employee record.

Uploaded documents join the record's sealed documents, the signed contract too. The org chart provides the manager, the employee workspace provides the access. The module orchestrates, the core keeps.

  • Employee record, contract and sealed documents
  • Line manager and org chart
  • Employee workspace with no password
  • Former-employee vault, read-only
  • Email notifications at each step
  • Module setup assistant

questions about arrivals and departures.

what we get asked before switching the module on.

  • Do I have to build everything myself?

    No. On activation, the assistant offers two default journeys, one for arrivals and one for departures, with tasks already split by category, owner and deadline. You adjust them once, and every new journey starts from that template.

  • What is the welcome area?

    The reduced workspace a newcomer sees before signing: their tasks, the documents to upload and the contract to read. Once the contract is signed, the full workspace opens, with the company's active modules. An employee already in place is imported without going through it.

  • How is the contract signed?

    You upload the contract to the journey, as PDF or Word. The employee reads it from their workspace, ticks "I have read and accept my employment contract" and clicks "Sign my contract". The signature is timestamped in the journey history and the contract joins their sealed documents.

  • Which documents can be requested?

    Those you define in the template: ID document, bank details, proof of address, certificate, diploma. Each "document to provide" task expects a document category, the employee uploads it from their workspace and it is sealed in their vault.

  • And when an employee leaves?

    The departure journey lists what needs doing: equipment return, access revocation, end-of-contract documents. At the end, the employee is archived: they leave the team but keep read-only access to their payslips and documents.

  • What about employees already in place when I switch on eachr?

    You add them as "Already in place": they are imported directly, with no journey or welcome area. The arrival journey only concerns newcomers.

switch on arrivals and departures in one click.

14-day full trial, no card. The module is included in the price, with the six others.

ENFR