Onboarding Bridge
When an offboarding reaches Completed status, PurpletGo can spin up an onboarding record for whoever replaces that employee. It carries over the role and department from the departing employee and seeds a standard onboarding checklist, so HR isn't starting from scratch.
Onboarding Bridge is available on the Team and Enterprise plans.
How it works
The Bridge only shows up on offboarding records that are already Completed - you'll find it as a card on the employee's detail page. Starting a bridge creates a new onboarding record pre-filled with the departing employee's role and department (you can change either before saving), plus a start date, manager, and notes if you want to add them.
PurpletGo then seeds a default checklist of 15 tasks covering admin/paperwork, IT provisioning, culture/orientation, and role milestones (1:1s, 30/60/90-day check-ins). A handful of extra tasks get added automatically based on keywords in the role title or department - for example, mentioning "engineer" or "developer" (or a department containing "engineering"/"tech") adds tasks like repo access setup and an architecture-docs review; "sales," "account," or "marketing" adds CRM access and customer intro calls; "hr" or "people" adds an HRIS walkthrough task.
This is a static, keyword-matched checklist, not a live read of the departing employee's actual system access or asset inventory. It doesn't inspect Okta groups, GitHub org membership, Slack workspace access, or which assets were assigned - it just picks from a fixed task list based on role/department text matching.
Starting an Onboarding Bridge
Open the completed offboarding
Go to the employee's record from Employees or Offboarding - the Onboarding Bridge card only appears once the offboarding's status is Completed.
Click "Start Onboarding"
This opens a dialog pre-filled with the departing employee's role and department.
Fill in the new hire's details
Enter the incoming hire's name (required), email, role, department, start date, manager email, and any notes. Role and department default to what the departing employee had, but you can overwrite either.
Save
Saving creates the onboarding record and seeds the default checklist described above. There's no separate draft step - the record and its tasks are created together.
Creating or editing an onboarding record requires the HR or admin role (or superadmin); deleting one requires admin or superadmin.
Tracking progress
The onboarding record shows a progress bar based on completed vs. total tasks. Each task has a category (admin, IT, HR, culture, or role), an assignee label (HR, IT, Manager, or Ops), and a due offset in days relative to the start date - some tasks are even due before day one (for example, provisioning equipment two days early). Tasks can be checked off, reassigned, renamed, or have their due offset adjusted from the record.
An email goes out to the org's superadmins, admins, and HR users when a bridge is created, summarising the new hire and task count - it does not go to the new hire themselves, since at bridge-creation time they may not even have an account yet.