Job board — hire without a separate ATS
The job board is for employment and recruitment. The shift board covers unfilled roster coverage for existing or outreach workers. Both stay inside your organisation — HealthOS does not employ workers or broker cross-org hiring.
Ask
Ask
End-to-end workflow
- 1HR / hiring manager
Create and publish a vacancy
Draft a role in HRM → Job board with program, employment type, site, and description. Publish when ready and optionally tick “Advertise on public job board”.
- 2HealthOS
Snapshot requirements & list publicly
The system stores compliance requirements for the role, shows the vacancy in your internal queue, and — when you opt in — adds an anonymised public listing (suburb, employment type, provider contact).
- 3Job seeker
Browse and apply on HealthOS
Candidates browse public vacancies on the HealthOS website and submit an application with contact details and optional message. Applications land in your HRM job board queue — they are not auto-hired.
- 4HR / hiring manager
Review, interview, and hire
Move applications through stages (submitted, review, interview, offer). When you hire, onboarding continues in your existing HRM and roster flows — same organisation boundary and audit trail.
Public job board listings
Any registered provider can enable public job listings in Settings → Claiming. HR then ticks “Advertise on public job board” when publishing — the same vacancy, visible on the website for job seekers.
Published on public listings
- ✓Role title, program, employment type, suburb/state
- ✓Sanitised role requirements (no participant names or street addresses)
- ✓Provider name, optional NDIS registration number, contact email/phone
- ✓Role description and closing date when supplied
Never published
- ✗Participant names, DOB, or medical information
- ✗Full street addresses or person file details
- ✗Internal applicant pipeline notes or salary bands unless you choose to include them in the description
Applicants submit through the HealthOS apply form or contact the provider directly. Your HR team reviews applications in the portal — public listings are for recruitment outreach, not shift coverage.
Compliance requirements published on each vacancy
Requirements are computed from the role, program, and organisation settings at publish time — then shown to applicants before they apply.
Role requirements
- ✓NDIS Worker Screening current and not refused (NDIS roles)
- ✓First aid certification when recorded for support worker roles
- ✓AHPRA registration current for allied health clinical roles
- ✓Right-to-work and program-specific credentials as configured
Organisation readiness
- ✓Public job listings enabled in organisation preferences
- ✓Contact email or phone for applicant enquiries
- ✓Role description reviewed before publish — no participant-identifying content
At hire
- ✓Hire action uses existing HRM onboarding where configured
- ✓Posting moves to filled when a candidate is hired
- ✓Compliance checks continue through your standard worker onboarding
Application pipeline
The job board uses the same staff accounts, organisation boundary, and HRM permissions as recruitment — not a separate product or external login.
Submitted
New applications in one queue
Every public apply creates a job application record tied to the posting. HR and the posting creator receive notifications — same queue whether the candidate came from the website or was entered manually.
Pipeline
Stage through to hire
Move candidates through review, shortlist, interview, and offer. Rejected and withdrawn applications stay auditable. Phase 2 links promoted candidates into your existing applicant onboarding flow.
Same sign-in, same organisation
Internal job board posts are scoped to your organisation. Public listings use a read-only API — no login required to browse vacancies, but only your HR team can publish or close them.
Role-based actions
HR officers and managers create postings, review applications, and update stages. Org admins enable public job listings and set contact details in Settings → Claiming.
Program and site context
Vacancies inherit program type (NDIS, Home Care, Allied Health), site, and region context. Public listings show suburb parsed from the site address — not participant locations.
Privacy by design
Participant-specific compliance lines are stripped from public requirement text. Closed or filled vacancies disappear from the public job board automatically.
How it fits your existing flows
The job board extends HRM recruitment — it does not replace shift board coverage or bypass compliance.
Complements shift board outreach
Use the job board for employment vacancies and ongoing recruitment. Use the shift board when you need someone to cover a specific unfilled shift — different products, different candidate expectations.
HRM stays the source of truth
Postings, applications, and hire actions live in HRM → Job board. Public listings are a read-only channel — edits and stage changes happen in the staff portal.
Compliance before hire
Published requirements snapshot role expectations at publish time. Final hire still runs through your worker onboarding and credential checks.
One provider, many roles
Publish multiple vacancies across programs and sites. Each posting has its own application queue and closing date — no mixing with shift board posts.
Included across NDIS, Home Care & Allied Health
- ✓Create and publish employment vacancies in HRM
- ✓Published role requirements on every posting
- ✓Optional public listing on the HealthOS job board
- ✓Application queue with stage tracking
- ✓Public apply form with provider notification
- ✓Org-level opt-in for public job listings
- ✓Distinct from shift board — employment, not roster coverage