Skip to content

Employment Contract Template (Casual)

Casual loading, no-firm-commitment wording, the CEIS and conversion rights — the four things this contract must get right.

What makes a contract genuinely casual

Casual employment in Australia turns on one idea: no firm advance commitment to continuing work. The employee is offered shifts, can accept or decline them, and is paid a casual loading in place of paid leave and other permanent entitlements. The Fair Work Act now defines casual employment by reference to the real substance of the relationship, not just the label — so a contract that says "casual" while the roster says "every Monday to Friday, indefinitely" is asking for trouble. The contract wording matters, but so does how you actually engage the person.

What the template must contain

1. Parties and engagement basis

The employing entity's legal name and ABN, the employee's details, and an explicit statement that employment is casual, engaged shift by shift, with no guarantee of ongoing or regular work and the right to decline shifts offered.

2. Award classification and casual loading

Name the covering Modern Award and classification, and state that the hourly rate includes the casual loading at the rate set by the award. Don't bake a percentage into the document — point to the award's current provisions so the contract survives rate changes. Itemise the loading separately on payslips; it matters if entitlement questions ever arise.

3. Rostering and shift arrangements

How shifts are offered and accepted, minimum engagement periods where your award sets them, and how cancellations are handled. Awards commonly set a minimum number of hours per shift for casuals — defer to yours rather than inventing a number.

4. The Casual Employment Information Statement

The contract should note that the employee has been given the CEIS, which the Fair Work Ombudsman publishes and requires employers to provide to every new casual (alongside the standard Fair Work Information Statement). Keep the current version in your onboarding pack and record that it was given.

5. Casual conversion

Include a clause acknowledging the employee's pathway to convert to permanent employment under the Fair Work Act's current casual conversion provisions. Don't paraphrase the eligibility rules in detail — they have changed more than once — just reference them and commit to following the process the legislation sets out.

6. Entitlements that still apply

Casuals miss out on paid annual and personal leave, but not everything: superannuation at the ATO's current guarantee rate, unpaid carer's leave, long service leave under state rules, and workplace protections all still apply. A short clause avoids the myth that casuals "have no entitlements".

7. Standard protections

Confidentiality, IP created during engagements, policy compliance (as directions, not contractual terms), and how the engagement ends — typically by either party ceasing to offer or accept shifts, subject to award notice provisions.

Using the template

  • Issue it before the first shift, with the CEIS and the tax and super forms in one bundle — our onboarding pack template covers the full set.
  • Revisit regular casuals periodically. If someone has settled into a steady pattern, review conversion obligations proactively rather than waiting to be asked.
  • Re-check the award every annual wage review — casual rates move with the base rates.

Common failure modes

  • Treating a de facto permanent employee as casual for years — the back-pay and conversion risk compounds quietly.
  • Absorbing the loading into a flat rate without documenting that it's included, and without checking the flat rate still clears the award.
  • Skipping the CEIS because "it's just a casual" — it's a compliance requirement with a paper trail.

Casual employment rules have been a moving target in recent years, so take this as general guidance and confirm the current requirements with the Fair Work Ombudsman or an adviser before rolling the template out. If casual admin is eating your week, that's usually a systems problem — see how a connected people function handles it.