Writing Role Descriptions That Actually Describe the Role
Most small-business role descriptions are written once, for a job ad, and never touched again. They list duties (“answer phones, manage inbox, general administration”) without ever saying what the role is for. Then six months later, owner and employee disagree about whether something is “their job” — and both are right, because the document describes neither the job nor the boundary.
A role description should let a stranger answer one question: if this role is done well for a year, what is true about the business that was not true before?
A structure that works
- Purpose — one sentence. Why the role exists. “Keep every customer job scheduled, invoiced and followed up so nothing falls through the cracks.”
- Outcomes — three to five. The measurable or observable states the role owns. Outcomes survive tool changes; duty lists do not.
- Core responsibilities. The recurring work, grouped, each pointing at the procedure that documents it. The role description should not duplicate procedures — it should index them.
- Decision rights and boundaries. What the role decides alone, what it recommends, what it never touches. This section prevents most role friction and almost nobody writes it.
- Reporting and cadence. Who they report to, what they report, and when.
From job ad to role description
The advertisement and the role description are different documents doing different jobs. The ad sells the role to strangers; the description governs it day to day. Write the description first and extract the ad from it — never the reverse. Outcomes make strong ad copy anyway, and starting from the description means the person who accepts the job arrives to find the same role they applied for.
Example outcomes for an office administrator role: every job invoiced within its agreed window; the owner's inbox at zero actionable items daily; supplier accounts reconciled monthly with no unexplained variances; every procedure the role runs reviewed on its schedule. Four lines, and the shape of a year's good work is visible.
Roles, not people
Write the description for the role, not for whoever holds it today. When a document is shaped around a particular person's strengths, it stops being reusable: the next hire inherits a role defined by someone else's habits, and comparisons at review time become personal rather than structural. Keep the role stable and let people bring their own methods to it — the outcomes section defines success, and how someone reaches those outcomes is exactly the flexibility good people value. When a person consistently outgrows the role, that is the trigger to redesign the role or create a new one, deliberately, on paper, before the payroll conversation.
Keep it honest and keep it current
Review each role description at the same time as the person's review. Roles drift — the document should follow reality, not the other way around. If a role has quietly absorbed responsibilities, write them in and acknowledge the growth; if something was dropped, take it out and decide who owns it now.
For employees, remember that a role description does not override legal obligations: awards, enterprise agreements and minimum entitlements still apply regardless of what the document says. The Fair Work Ombudsman publishes current award and entitlement information worth checking when a role changes materially.
FAQ
How long should a role description be?
One to two pages. Shorter than that usually means missing decision rights; longer usually means procedures have leaked into it.
Do contractors get role descriptions?
Contractors work to a scope of services in their agreement rather than a role description — and maintaining that distinction matters for how the relationship is characterised. See the ATO and business.gov.au guidance on contractor arrangements.