New Hire Onboarding Link
Fill in the new hire's details. The system generates a secure personal link and emails it automatically. Core team manage their own links; OCC admin has full oversight.
The link includes the Letter of Engagement pre-filled with the details above. It expires after the selected period or once the new hire completes all steps.
What the new hire completes
All 8 guided steps are completed from the worker's personal link, and the final document submission step sends one secure HR pack before Day 1. Preview email templates
- Letter of Engagement + Fair Work Information Statement
- Position Description - Disability Support Worker
- Code of Conduct Agreement (NDIS)
- Privacy & Confidentiality Agreement
- Conflict of Interest Declaration
- Private employee details, including bank details, are completed once in-browser. Tax and super are completed online-first through myGov / ATO, then the final submission sends the HR pack with identity documents, training certificate, and required compliance files.
- NDIS Worker Screening Check - required for all OCC workers
- Working with Children Check - required for roles involving children or young people
- National Police Check - required for all OCC workers
- NDIS Worker Orientation Module ("Quality, Safety and You") - required for all OCC workers
- Relevant training certificate (Certificate III or IV) - required with completion date
Start or open participant intake
Use the permanent participant file code and service start date. If that participant already has an active intake, the existing workspace opens instead of creating a duplicate.
Checking next participant code...
Participant Intake Records
Keep one row per participant using the permanent participant file code. Intake pack details stay in the JSON draft, signed packet, and SharePoint.
| Participant | Service start | Intake status | SharePoint | Actions |
|---|
Intake filing
Lean filing view. SharePoint remains the participant record.
Onboarding Submissions
Worker-submitted packs for review and filing. A submitted pack is not ready-to-work until OCC clears review, right-to-work, compliance evidence, and filing blockers.
| Name | Position | Pack View | Admin Next | Status | Actions |
|---|
Oversight
Filing gaps, unresolved completion blockers, and records that need admin follow-up before handoff.
Filing and Completion Blockers
Keep this visible. These are the items that can block closure or delay sending a staff portal link.
Diagnostics and audit trail Open only when investigating a problem, override, or support request.
Exceptions and Overrides
Participant onboarding exceptions, archive events, or revoke events. Useful for investigations, not daily workflow.
Recent Audit Activity
Newest system audit events. Use for spot checks after a support question or unexpected state.
| When | Domain | Event | Actor | Reference |
|---|
Recent Hub errors
Non-sensitive browser error metadata. Use only when something looks broken.
Staff Portal Access
Post-review staff portal tokens, grouped by worker. Use this after the pack is reviewed, filed, and ready for handoff.
| Worker | Portal Access | Activity | Actions |
|---|
Complete review and filing first, then send the Staff Portal invite from the worker row.