How to Write SMART Goals for Performance Reviews
Most Australian performance reviews go sideways for the same reason: the goals set at the last review were too vague to assess at this one. "Improve communication", "be more proactive", "support the team better" - they sound reasonable in the meeting and tell you nothing six months later.
SMART goals fix that. Done properly, they turn a performance review from an opinion exchange into a structured conversation about what was agreed, what happened and what comes next. For HR managers and business owners running teams between 200 and 2,000 people, that consistency is what makes a performance program defensible, fair and actually useful.
This guide explains what SMART goals are, how to write them for an Australian workplace and how the right hr software australia platform turns them into a workflow your managers will actually run.
Note on facts: The SMART acronym attribution and Fair Work references below were checked on 16 June 2026 against the original 1981 Management Review article by George T. Doran and current Fair Work Ombudsman guidance on managing performance. Always confirm current Fair Work guidance directly before relying on it for a decision.
What SMART goals actually are
The SMART acronym was introduced by George T. Doran in the November 1981 issue of Management Review ("There's a S.M.A.R.T. way to write management's goals and objectives"). The wording has shifted over the years, but the modern version most HR teams use is:
- Specific - clear about what is to be achieved
- Measurable - quantified so progress and completion are observable
- Achievable - realistic given the person's role, capability and resources
- Relevant - connected to the role and to broader team or business outcomes
- Time-bound - with a defined deadline or review point
The point is not the acronym. The point is that every goal in a review cycle should be unambiguous enough that a third person - a new manager, an HR business partner, an internal reviewer - could read it and tell you whether it has been achieved.
Why vague goals create real problems
Vague goals are not just a productivity issue. Under the Fair Work Ombudsman's guidance on managing performance, employers are expected to give employees a clear understanding of what is required of them, regular feedback, and a reasonable opportunity to improve before any formal action.
A goal like "be more proactive" fails that test on day one. It cannot be measured, the employee cannot demonstrate they have met it, and the manager cannot fairly say they have not. If the same goal later appears in a performance management process, it is the employer - not the employee - who carries the weakness.
A SMART goal removes that risk by being verifiable on its own terms.
Writing SMART goals that hold up in an Australian workplace
The mechanics are simple. Take any draft goal and rewrite it so each of the five tests is satisfied.
Specific
Name the outcome, not the activity. "Complete training" is an activity. "Complete the Cert IV in Workplace Health and Safety" is specific.
Ask: could two reasonable people interpret this goal differently? If yes, tighten it.
Measurable
Define how completion or progress is observed. That can be a number (calls per week, NPS, ticket close rate), a deliverable (a written policy, a finished migration), an event (a passed exam) or a behaviour observed against a defined rubric.
Ask: how will I know this has been achieved without a debate?
Achievable
The goal has to be possible inside the person's role, capability and available resources. A stretch is fine; an impossibility is demoralising and, if used in a performance process, indefensible.
Ask: do they have the time, authority, tools and support to do this?
Relevant
The goal should tie to the role and to a wider team or business outcome. A goal that has nothing to do with the person's job is a hobby, not a performance objective.
Ask: what changes for the team or business if this goal is achieved?
Time-bound
Every goal needs a date. "By the end of Q3", "by the next review on 30 September", "within 90 days of role commencement" - pick a deadline and write it in.
Ask: when does this goal stop being open?
Worked examples by function
Vague drafts on the left, SMART rewrites on the right.
People & culture
- Draft: Improve employee engagement.
- SMART: Lift the engagement survey "I would recommend us as a place to work" score from 68 to at least 75 in the November 2026 cycle by running three quarterly listening sessions and closing the top issue from each.
Operations
- Draft: Reduce errors in dispatch.
- SMART: Reduce dispatch error rate from 2.1% to under 1% by 30 September 2026, measured monthly via the existing WMS exception report.
Sales
- Draft: Sell more.
- SMART: Close $480,000 in new business from named target accounts by 30 June 2026, with at least 60% from accounts not on the FY25 customer list.
Finance
- Draft: Tidy up month-end.
- SMART: Reduce month-end close from 9 to 6 working days by the August 2026 close, by automating the three reconciliations identified in the May process review.
Healthcare and aged care
- Draft: Stay on top of compliance.
- SMART: Maintain 100% currency of mandatory training and AHPRA renewals for the direct team across each monthly compliance dashboard report through to 31 December 2026.
The same shift applies in any role. The test is always the same: a third person should be able to read the goal and tell you whether it has been achieved.
Common mistakes that drain a review cycle
- Too many goals. Three to five well-written goals beat ten weak ones. People deliver against what they can hold in their head.
- Goals that measure activity, not outcome. "Run 12 toolbox talks" is an activity. "Reduce reportable safety incidents by 20%" is an outcome.
- Goals owned by no one. If a goal depends on three other teams, the person being reviewed cannot own it alone.
- Goals set once and never revisited. Business priorities shift. A goal that is no longer relevant should be retired or rewritten in a check-in, not stretched into the end-of-cycle review.
- Goals copied from job descriptions. "Manage the team" is a duty, not a goal.
Tying SMART goals to development and business outcomes
A SMART goal is more useful when it sits inside a wider performance and capability picture. The pattern that works in most mid-size businesses:
- Business goals for the year, owned by the leadership team.
- Team goals that ladder up to the business goals, owned by each manager.
- Individual SMART goals that contribute to one or more team goals, set with each employee.
- Development goals that build the capability the individual needs for their current or next role.
Reviewed quarterly, this structure means the November review is a summary of what already happened in three check-ins, not a single high-stakes event.
Where the HR system earns its keep
SMART goals on a Word doc work for a team of ten. They do not scale to 500 or 2,000. At scale, a useful performance management software australia module needs to:
- capture each goal against the employee's profile, not in a shared drive
- prompt managers and employees for scheduled check-ins
- record progress, comments and evidence over time
- support self-, manager- and 360-style feedback where used
- roll up completion and ratings into reports HR and the leadership team can actually use
- keep a defensible history that holds up if a performance issue escalates
workit's performance reviews module does this natively. Goals are written and tracked against the same employee record used by onboarding, compliance and leave, so a manager has one view of the person, not five tabs across four tools.
Connecting performance to the rest of HR
The reason performance reviews fail in many businesses is not the review itself. It is the disconnect between the review and everything else HR holds about the person. The goal set in a Word template never finds its way into a development plan, the development plan never connects to a capability matrix, and the capability matrix never connects to credentials or compliance.
An all-in-one hr management software platform closes that loop. The same employee record that holds their goals also holds their qualifications, credentials, leave, policies and documents. When a manager opens a review, they are looking at the full picture - not a goals form in isolation.
For regulated sectors, that integration matters even more. A hr compliance for healthcare team can tie SMART development goals directly to the credentials a clinical role requires, so professional development is something the system reminds you about, not something that quietly slips.
A short SMART goal template you can reuse
Drop this into your next review prep:
- Outcome: What specifically will be different when this is done?
- Measure: How will we observe it? (number, deliverable, event, rubric)
- Resources: What does this person need to make it possible?
- Connection: Which team or business outcome does this support?
- Deadline: By when?
- Check-in cadence: When will we review progress?
Five lines, every time. The discipline is in using it, not in the wording.
Where workit fits
workit is an Australian-built human resource software platform that runs performance reviews as one connected module alongside onboarding, HR core, compliance, leave, forms and reporting. SMART goals are captured against the employee's record, tracked through scheduled check-ins, summarised at review time and reportable across teams and sites from one dashboard.
If you are reviewing how to make performance reviews work in a mid-size or large Australian business, the performance reviews page covers exactly what the module does, the HR software buyer guide covers how to choose a platform that supports it, and the HR metrics to track blog covers the measures worth reporting alongside completed goals.
