In Perth, job descriptions (JDs) are operational documents that connect roles to Western Australian legal, safety & industrial realities. Done properly, they underpin lawful hiring, correct classification, safer work design, consistent performance, & clear workforce planning across metro, regional & FIFO contexts.

1) WA industrial relations: build JDs for the right system

Perth employers operate under two frameworks: most incorporated businesses follow the national system (NES, Modern Awards, Enterprise Agreements), while some unincorporated entities fall under WA’s state system. JDs must:

  • Name the applicable instrument (Modern Award/EA or state award) & the intended classification level.
  • Reflect duties, discretion, supervision & competency consistent with that level.
  • Flag allowances/penalties that may be triggered by hours, location, shifts, travel or on-call.
    For complex classification mapping or contentious duty statements, seek independent review from an HR Consultant Perth to validate levels, allowances & wording.

Perth reality to capture: split metro/regional operations, service windows tied to client SLAs, weekend trade, extended trading hours, & public holiday coverage.

2) Work Health & Safety: embed role-level duties

Under WA WHS laws, PCBUs, officers, managers & workers have defined obligations. Each JD should:

  • State role-specific WHS responsibilities (e.g., hazard reporting, permit-to-work, isolation verification, contractor oversight).
  • Document inherent requirements (physical, cognitive & environmental) such as heat exposure, manual handling thresholds, working at heights, driving long distances, remote or lone work, & dust/noise.
  • Specify mandatory competencies (e.g., first aid, LVR/CPR, confined space, gas test atmospheres), PPE, & authority to stop work where relevant.

Perth reality to capture: summer heat, bushfire risk periods, remote travel to regional clients, marine or port environments, & heavy-industry interfaces around Kwinana, Pilbara supply chains, or industrial estates.

3) Licences, checks & site access 

Only include what the role genuinely requires, & distinguish mandatory vs desirable:

  • WA White Card, high-risk work licences, HR/MC driver’s licence, Working With Children Check, National Police Check.
  • Site/industry passes (e.g., port or resources sites), medicals & fit testing.
  • Client or council inductions for public-facing or field roles.

Perth reality to capture: multi-client sites with differing induction rules, council depot access, utilities corridor access, & seasonal event rosters.

4) Privacy & equal opportunity in hiring

Keep recruitment data proportionate to the JD’s inherent requirements. Focus selection on capability & lawful criteria. For support, health, education & community roles, reference safeguarding obligations in the duties & behavioural expectations.

Perth reality to capture: community-facing work across multicultural suburbs, home-based service delivery, lone-worker protocols, & secure handling of client data.

5) JD structure that works 

Use a consistent structure so content maps cleanly to compliance, rosters & performance:

  1. Role purpose — one paragraph linking the role to Perth/WA service delivery.
  2. Key results (4–7) — measurable outcomes with targets & timeframes.
  3. Core duties — grouped by operations, stakeholder, compliance & administration.
  4. Decision rights — approvals, budget limits, vendor authority & escalation paths.
  5. Reporting lines & stakeholders — include client, council, contractor & regulator interfaces where relevant.
  6. Competencies & behaviours — aligned to your values/capability framework.
  7. Skills, qualifications, licences & checks — mark mandatory vs desirable.
  8. Tools, systems & equipment — list ERPs, CMMS, POS/CRM, mobile apps used locally.
  9. Inherent requirements — physical/cognitive/environmental demands, travel & driving.
  10. WHS responsibilities — worker/supervisor/manager accountabilities appropriate to WA practice.
  11. Work pattern & locations — hours, roster, overtime/on-call, metro/regional/FIFO, vehicle use.
  12. Industrial instrument & level — Modern Award/EA or state instrument, classification rationale.
  13. Version control — author, approver, date & next review.

6) Drafting standards 

  • Be outcome-led: “Resolve Priority-1 faults within 4 business hours, ≥90% compliance,” not “Assist with IT support.”
  • Match classification: Avoid inflating titles or duties that don’t occur in practice; classification must reflect real work.
  • State roster realities: Document evenings/weekends, split shifts, call-outs, travel time, & site access rules.
  • Name site risks & controls: Heat, remote work, driving, night work, port or construction constraints.
  • Use plain language: Clear verbs & metrics; multi-site, multidisciplinary teams need unambiguous instructions.

7) Lifecycle integration for Perth organisations

Workforce planning — Use JDs to model structures across CBD, suburbs & regional routes; define interfaces with contractors & councils.
Recruitment — Convert JDs into job ads, screening criteria & interview scorecards aligned to WA requirements.
Onboarding — Build checklists from JD sections: systems, inductions, licences, WHS training, route or site familiarisation.
Performance & reward — Tie KPIs to probation & review cycles; align to pay bands linked with the applicable instrument.
Learning & development — Extract competencies into training plans & licence renewal schedules.
WHS & wellbeing — Map tasks to risks & supervision levels; make lone-worker, fatigue & heat procedures explicit.
Change control — Update JDs after restructures, new client contracts, tech changes, incident learnings, or instrument updates.
Where internal capacity is limited, partner with an external HR company in Perth to maintain templates, version control & compliance updates.

8) Common Perth pitfalls & fixes

  • Vague scope: Replace “assist/support” with deliverables, volumes & timeframes.
  • Misclassification: Cross-check duties against the intended level before advertising or making offers.
  • Missing WHS detail: Insert role-appropriate WHS duties & inherent requirements; don’t rely on a generic clause.
  • No roster/location detail: Add work pattern, travel, vehicle expectations & site rules.
  • Stale systems: Remove legacy platforms; name current ERPs, CMMS, POS, field apps.
  • No review cadence: Assign an owner; set an annual review date & log changes.

10) Perth checklists you can apply today

Classification & compliance
☐ Correct IR system & instrument named
☐ Classification level matches duties & discretion
☐ Allowances/penalties consistent with roster & locations
☐ Licences/checks listed with mandatory vs desirable
☐ WHS responsibilities explicit for role level
☐ Inherent requirements stated & defensible

Operations
☐ Role purpose linked to local service delivery
☐ 4–7 KPIs with targets/timeframes
☐ Decision rights & escalation paths documented
☐ Systems/tools current & named
☐ Stakeholders, locations, travel & vehicle use captured
☐ Version control & review date set

Conclusion

A Perth-specific JD is a living document that reflects WA’s IR split, WHS duties, licences, rosters, site realities & community interfaces. When every section is written for Perth conditions, JDs improve compliance, reduce disputes, support safe work, lift performance & make recruitment, onboarding & reviews faster & clearer. Visit My HR Pro for more information.