What happens automatically when you hire

The handoff from candidate to employee is the bridge between the Hire arc and the Develop arc. It runs as a single transaction, so either everything happens or nothing does. Knowing what the transaction touches makes it easier to reason about what is auto-created (and what is therefore safe to lean on) versus what you need to set up manually.

What the transaction does

When you click Hire and confirm, the following happen atomically:

• The Person.status flips from CANDIDATE to EMPLOYEE. The same Person record is preserved — so all of their CV-derived competencies, screening narrative, interview ratings, and notes carry forward into their employee profile.
• The Person.roleId is set to the role they are being hired into, with startDate as you specified.
• The Role.status flips from OPEN to FILLED. Other open candidates remain in the pipeline; the role's public job page closes to new applications.
• A GrowthPlan is created and linked to the new employee. The plan's targetRoleId is left null (you set it later in conversation with the employee) and it starts with no milestones — you add them once you and the employee agree on a development direction.
• A User record is created for the new employee, with role EMPLOYEE and locale matching their application's preferred language.
• A welcome email is sent.
• An ONBOARDING notification is created on the new employee's record, ready in their bell at first login.
• A CANDIDATE_HIRED notification is fired to the workspace's HR administrators and to the assigned line manager.

What the transaction does not do

• It does not auto-assign any assessment. (Assessments are assigned earlier, during CV screening in the hiring pipeline.) If you want a specific assessment for the new hire, you assign it manually after the handoff.
• It does not connect the new employee to any team beyond the line manager you set. Wider team membership is set in the line manager's team scope.
• It does not import any data from external systems. If you have a legacy HRIS, the new employee record is created from the candidate record only — payroll, benefits, equipment, all live in their own systems.
• It does not notify the rest of the company. There is no auto-announcement.

Why a single transaction

Two reasons:

• Consistency. A hire that was half-applied — the role marked filled but no growth plan created, or the candidate marked employee but no welcome email sent — would leave the workspace in an inconsistent state. Atomicity removes that class of failure.
• Auditability. Every record created by the handoff carries the same transaction reference. If you need to trace what happened on the day someone was hired, one query lists everything.

Rolling back

There is no automated rollback after the transaction commits. If a hire falls through, the unwinding is manual: mark the employee as FORMER_EMPLOYEE, reopen the role from FILLED → OPEN, optionally archive the growth plan and the assessments. The records are preserved for audit; you do not delete them.

A rollback workflow with a one-click Undo hire button is on the v0.6 watch list.

Next

The hire is complete. From here, the platform's centre of gravity shifts from acquisition to assessment. Section IV — Assessing and developing opens with the five assessment types and walks through assigning, taking, and reading them.