Turn a repeatable process into a tracked program
- 1
Create a program and draft its first version.
- 2
Add ordered or parallel stages.
- 3
Add tasks, choose who completes each one, and set dependencies, approvals, and whether the person can see the task.
- 4
Publish the version so it can be assigned.
- 5
Assign it to an approved applicant, a member, a role, or an email address.
- 6
Track progress, approve submissions, and handle blocked steps.
- 7
Publish a new version for future assignments without changing people already in progress.
Choose a step-by-step task guide
Each guide includes prerequisites, exact actions, verification, and troubleshooting—not just a feature summary.
Module capabilities
- Programs with published versions that never change an in-progress person’s path
- Ordered or parallel stages and task dependencies
- Ten task types: uploads, certifications and licenses, questions, general tasks, account creation, background processes, scheduling, profile/contact data, gear and uniform issue, and resource acknowledgements
- Tasks for the person or for staff, with a visible-to-person switch
- Reviewer approval and rejection of submitted work
- Connected steps: Time Clock face enrollment, real Quartermaster gear requests, and Resources acknowledgements
- Credential vault with encrypted temporary passwords, audited reveals, and printable password sheets
- Code-based portal for new people, completion reports, and an optional one-way Google Sheets mirror
Before your department relies on it
- 1
Map the real process and owners before building stages.
- 2
Decide which tasks the person should see.
- 3
Use dependencies only where work truly cannot start early.
- 4
Require approval for documents or answers that must be verified.
- 5
Turn on the Quartermaster and Resources task types only when those modules are in use.
- 6
Publish changes as a new version instead of changing expectations for people already in progress.
Portal destinations
These destinations appear only when the module is enabled and your roles grant the required access.
| Area | Portal path |
|---|---|
| Onboarding overview | /onboarding |
| Programs | /onboarding/programs |
| Program builder | /onboarding/programs/:id |
| People | /onboarding/people |
| Person progress | /onboarding/people/:id |
| Reports | /onboarding/reports |
| Settings | /onboarding/settings |
| My Onboarding | /onboarding/my |
| Applicant onboarding | /applicant/onboarding/:personId |
Associated modules
Required modules must be enabled first. Related modules exchange data or extend the workflow when both are available.
Dependencies
RequiredCoreWorks especially well with
Works withRecruitingWorks withResourcesWorks withQuartermasterWorks withTime ClockAnswers before you get stuck
Why doesn’t an assigned person see a task I just added?
People are pinned to the version they were assigned. Publish a new version for future assignments.
Is Recruiting required?
No. Onboarding can be assigned to existing members as well as approved applicants.
Does converting an applicant start onboarding automatically?
No. Assign the program after conversion.