
Review small business staff policies lightly once a year, and again whenever something changes: a new role, hybrid work, growth, or a complaint that exposed a gap. Age alone is not the problem. The risk is a policy that no longer matches how the business works, because it fails when someone relies on it.
Yes, a handbook untouched since 2019 is a problem. Not because of the date on the cover, but because the business you run today is probably not the one it describes. Roles have moved. People have left. Some of your team now work from home. The policy still says what it said, and it tends to let you down in the middle of a conflict, which is the worst time to find out.
This guide is written for owners and general managers of Australian businesses with no HR team. It covers the signs your handbook has drifted, how to test three key policies against a realistic situation, how to rewrite them in plain language, and a checklist you can work through this month. It also covers when it is worth getting someone outside the business to look at it.
Key Takeaways
- Do a light review of every staff policy once a year, plus a review whenever something material changes in the business.
- Trigger events include new roles, hybrid or remote work, growth, a restructure, and any complaint that showed a policy was unclear or silent.
- Test your grievance, bullying and code of conduct policies against a real scenario: who does the person go to, what happens next, and how long does it take?
- Plain language wins. Short sentences, numbered steps and a clear statement of who does what mean the policy actually gets used.
- Give every policy a named owner, a version date and a next review date, so reviews happen without anyone having to remember.
- You can't be neutral about your own people, and they know it. If you would be judging your own staff, bring in someone on nobody's side.
Summary Table
| Question | Short answer | What to do |
|---|---|---|
| How often? | Light review yearly, plus when something changes | Put the next review date on each policy |
| What triggers an early review? | New roles, hybrid work, growth, restructure, a complaint that exposed a gap | Treat each trigger as a prompt to check the affected policies |
| Which policies first? | Grievance, bullying, code of conduct | Walk each one through a realistic scenario |
| How should it read? | Plain language, short sentences, numbered steps | Name who does what at each step |
| Who owns it? | One named person per policy | Record owner, version date and next review date |
| When to get help? | When the owner would be judging their own people, or the policy needs a fresh set of eyes | Start with a triage call or HR guidance by the hour |
How often should small business staff policies be reviewed?

A sensible rhythm is a light review every year and a targeted review whenever the business changes in a way that touches how people work or how problems get raised. The yearly review keeps small drifts from piling up. The trigger reviews catch the big ones.
There is no single date that makes a handbook stale. What matters is the gap between what the document says and what actually happens. The same policy can be fine for three years and wrong in three months if the business changes quickly.
The yearly light review
Book it in the diary. Set aside a short block, once a year, to read every policy as if you were a new starter. Check names, titles, contact details and processes. Ask whether each policy still describes how the business runs. Fix what is obviously wrong. Flag anything that needs a deeper look.
A light review is not a rewrite. It is a read-through with a pen. Most years it will produce a handful of small corrections. That is the point.
Trigger events that justify an early review
Review the affected policies when any of these happen:
- New roles or a new reporting line. If a team leader layer appears, the grievance policy needs to say who a team member goes to now.
- Hybrid or remote work. Policies written for one site often assume everyone is in the same room.
- Growth. A business of 20 and a business of 120 do not raise problems the same way. What worked when the owner knew everyone does not scale.
- A restructure or a change of ownership. Names, titles and decision rights shift.
- A complaint that exposed a gap. If someone raised a concern and nobody was sure what the policy said, that is a free lesson. Use it while it is fresh.
- A change in the law or in an award or agreement that applies to you. Whether any policy or wording is legally required is a question for an employment lawyer. Conflict Services is not a law firm and gives no legal advice, so take that question to one.
The trigger list is the part most owners skip. A yearly review will not catch a complaint that landed in March and showed the grievance process did not work. You need to act when it happens.
Signs your staff handbook has drifted
A handbook has drifted when it describes a business that no longer exists. The clearest signs are assumptions about where people work, names of people who have left, a complaints process that points back at the person complained about, and language so dense that nobody reads it.
You can spot most of these in one sitting. Here are the four we see most often when we look at small business documents.
It assumes everyone works in the office
Search for phrases like "on the premises", "in the office" and "on site". If half your team now work from home some days, the policy may say nothing about how a complaint is raised by someone who is not in the building, or how a manager responds by video. A policy that ignores how people actually work gets ignored in return.
It names people who have left
If the handbook still lists a former HR contact, an old operations manager or a person who left two restructures ago as the place to take a concern, nobody is really holding the process. A staff member in a hard moment will not guess who has taken over. They will stay quiet, and quiet is where conflict grows.
The grievance process sends complaints to the person being complained about
This is the big one. Many inherited handbooks say a staff member should raise a grievance with their direct manager first. That works for small matters. It fails when the concern is about that manager. If there is no alternative path, the process quietly asks the person with the least power to confront the person with the most.
The language is dense enough that nobody reads it
Long paragraphs, legal-sounding phrases and sentences that run for five lines are a sign the policy was copied from somewhere else. If your own managers cannot explain it in two sentences, your team will not follow it. A policy people cannot read does not protect anyone.
Test your grievance, bullying and code of conduct policies against a real situation

The fastest way to test a policy is to run a realistic scenario through it and ask three questions: who does the person go to, what happens next, and how long does it take? If you cannot answer all three from the document alone, the policy has a gap.
Do not test a policy with an easy case. Test it with the awkward one, because that is the case it will be used for.
The scenario
Imagine a 60-person services business with no HR team. A team member, call her Priya, wants to raise a concern about her manager, Dan. Dan has been with the business for years and is a long-time friend of the owner. Priya has been asked to take on extra work that others are not, she feels spoken over in meetings, and she has stopped speaking up. She is not sure whether this is bullying, poor management or just a personality clash. She opens the handbook.
Walk the grievance policy through it
Who does she go to? The handbook says to raise a grievance with your direct manager, or the owner if that is not appropriate. Her direct manager is Dan. The owner is Dan's friend. Priya reads this and concludes that every route leads to someone who is not on her side. She may decide not to raise it at all.
What happens next? The policy says the matter will be "dealt with appropriately". It does not say who decides, whether Dan is told, whether Priya is kept informed, or whether there is a choice between a facilitated conversation and a formal process.
How long does it take? The policy gives no timeframe. Priya hears nothing for days. People in her position tend to react to the silence as much as to the original problem. The issue grows while the process sits still.
This is how small matters become large ones. The original concern may have been manageable. The delay and the sense of unfairness are what turn it into something else.
What a better grievance policy does
A clear grievance policy keeps the response calm, clear and early. In practice it does five things:
- Gives at least two places to take a concern, so nobody has to go to the person involved.
- Names an alternative contact when the owner or a senior leader is part of the matter.
- Commits to acknowledging the concern in writing within a set number of working days. Pick a number you can actually meet.
- Explains the options in plain terms. Not every matter needs the same process. Some need a management decision, some HR guidance, some coaching, some mediation and some an independent investigation.
- Says what happens to the person who raised the concern while it is being looked at, including that they will be kept informed.
On that fourth point, it helps to keep one distinction clear. Mediation asks what happens next. An investigation asks what happened. Mediation is voluntary, confidential and forward-looking, and the people involved own the outcome. An investigation establishes facts, makes findings and can lead to action. A good policy tells staff both exist and who decides which fits. Investigations are quoted after scoping, so the policy should not promise a fixed process or timeline either.
If you are facing a complaint right now and the policy review is not done, start with the first 48 hours guide. It covers what to do, in order, while you sort the document out.
Test the bullying policy
Use the same scenario. Does the bullying policy say what bullying looks like in plain terms, or does it only quote a definition? Does it tell Priya how to raise it, who receives it, and what she can expect? Does it separate a one-off disagreement from a pattern of behaviour, without telling her she is wrong to ask?
A good bullying policy treats a concern as information. It does not treat the person raising it as the problem, and it does not pre-judge the person it is about. Words like "allegation" and "offender" belong to a formal process once it is framed. In the early stages, "concern" and "complaint" are fairer and more accurate.
Workplace bullying has a defined meaning in Australian workplace regulation, and the regulators publish guidance on it. Check your policy against the material from Safe Work Australia and the Fair Work Commission listed below. If you want to know whether your policy meets a legal requirement, that goes to an employment lawyer.
Test the code of conduct
Run the code of conduct against the same story. Does it describe the behaviour you expect from managers as well as staff? Does it say what respectful disagreement looks like? Does it link to the grievance process, so a person reading it knows where to go?
Many small business codes of conduct are a list of prohibitions written for staff. A useful one also sets out what people can expect from leaders. If the code applies to everyone except the people who manage, your team will notice.
Rewrite your policies in plain language
Plain language means short sentences, numbered steps and a clear statement of who does what. If a new starter can read a policy once and explain it back, it is working. If they need to ask someone what it means, rewrite it.
The Australian Government's Style Manual is a good, free reference for writing in plain English. You do not need to become a writer. You need to cut, simplify and name people.
Five rules that fix most handbooks
- One idea per sentence. If a sentence has three commas and a semicolon, split it.
- Use active voice. Write "The owner will reply in writing" rather than "A written response will be provided".
- Name the role. Every step should say who does it. "The General Manager acknowledges the complaint" beats "The complaint will be acknowledged".
- Use numbered steps for processes. A grievance process is a sequence. Show it as one.
- Cut words that sound formal but add nothing. "Pursuant to", "in the event that" and "shall" can almost always go.
A before and after
Before: "In the event that an employee has a grievance relating to workplace matters, such grievance should in the first instance be raised with the employee's immediate supervisor, whereupon appropriate action will be undertaken."
After:
- Tell your manager or the General Manager about your concern. If it is about one of them, tell the other.
- We will reply in writing within the number of working days set out in this policy.
- We will talk with you about the options, so you know what could happen next.
- We will keep you informed until the matter is finished.
The second version is shorter, kinder and easier to follow. It also gives the reader an alternative if their manager is the issue. Plain language and fairness often arrive together.
Give every policy a named owner, a version date and a next review date
Every policy should carry three details on its first page: who owns it, the date of the current version, and the date it is next due for review. These three lines turn a one-off document into something that is kept alive.
Without them, a policy has no owner and no date, so nothing prompts anyone to look at it. Reviews do not fail because owners are careless. They fail because nobody was asked.
What each detail does
- Named owner. One person, not a team. In a business with no HR team, this is often the owner, the general manager or the operations manager. The owner is the person who answers questions about the policy and keeps it current.
- Version date. Staff and managers can see how current the policy is. It also helps when someone asks which version applied at a particular time.
- Next review date. A date in the diary makes the yearly review automatic. Add it to the calendar as well as the document.
A simple policy register
Keep a one-page list of all your policies with the owner, version date and next review date in three columns. Check it once a quarter. When a trigger event happens, you can see at a glance which policies it touches.
One caution: if the owner of the grievance policy is also the person most likely to be complained about, consider who the alternative contact is and put their name in the policy too. Ownership of the document is not the same as being the decision-maker on every complaint.
A checklist you can work through this month
You do not need a project team to do this. You need a few focused hours and a willingness to read your own handbook honestly. Work through these steps in order.
Week one: read and mark up
- Print the handbook. Read it as a new starter would.
- Mark every name, title and location that is out of date.
- Mark every sentence you had to read twice.
- Note which policies assume everyone works in the same place.
Week two: test three policies
- Write a short, realistic scenario for your business, including an awkward one where the person complained about is senior or close to you.
- Run the grievance policy through it. Answer: who do they go to, what happens next, how long does it take?
- Run the bullying policy and the code of conduct through the same scenario.
- Write down every question the documents could not answer.
Week three: rewrite
- Add a second route for raising a concern, so nobody has to go to the person involved.
- Rewrite the three policies in short sentences with numbered steps.
- Name the role responsible for each step.
- Say in plain terms what options exist after a concern is raised, and who decides which one fits.
Week four: set it up to last
- Add a named owner, version date and next review date to every policy.
- Build the one-page policy register.
- Tell your managers what changed and why, in a short conversation rather than an email.
- Put the yearly review and a trigger event reminder in the calendar.
If a question comes up during the checklist about whether a policy or clause is legally required, note it and take it to an employment lawyer. The checklist is about making your documents accurate and usable. It is not a legal audit.
When outside help is worth it
Outside help is worth it when you would be judging your own people, when the documents need a fresh set of eyes, or when a live matter is already running. You can't be neutral about your own people, and they know it. A reviewer who is not part of the business can see what you have stopped noticing.
Most owners can do the first pass themselves. The checklist above is designed for that. But some situations are better with someone else.
When you are the one being tested
Take the earlier scenario. If Priya's concern is about Dan, and Dan is a long-time friend of the owner, the owner cannot be the neutral person in that process. The same applies to a general manager who hired the person involved, who has already given advice to one side, or who will make the final decision. The staff member knows this. So does Dan. Neutrality is not only about what you intend. It is about what the people involved can reasonably see.
In that case, bringing in someone on nobody's side is not a sign of weakness. It protects the process and the people in it.
Choosing the right help
Not every matter needs the same process. Choosing between a management decision, HR guidance, conflict coaching, mediation and an independent investigation is often the hardest part. If you are unsure which fits, a short conversation sorts it faster than guessing.
That is why we start with a triage call. It is 45 minutes with Shiv Martin, a nationally accredited mediator, for $290 ex GST. You then get a short email of next-step recommendations. There is no obligation to go further.
If what you need is the documents themselves, our policy review service is $290 ex GST an hour, with no retainer and no lock-in contract. You pay for the time it takes. You can also use HR guidance by the hour for specific questions as they come up, without signing up to ongoing support.
If you are ready, you can book a triage call and we will match the matter to the right person on our panel, not just whoever is free. Sessions and calls run by video anywhere in Australia.
Write the policy for the awkward case, not the easy one
Most handbooks are written for the case where everyone gets on and the process is never really tested. Our view is that a policy should be designed for the worst-placed person in the building: the staff member whose concern is about someone senior, close to the owner, or hard to challenge.
Here is the test we suggest, and it is one you will not find in most checklists. Take the longest-serving, best-liked person in your business. Imagine a newer team member has a concern about them. Now read your grievance policy from the newer person's chair. Not as the owner who wrote it, but as the person who has to use it.
If the policy only works when nobody important is involved, it does not work. It will survive until the first time someone relies on it.
This connects to something we believe about conflict more broadly. Conflict is not a bad word. It is usually a sign that something important needs attention. Most workplace conflict starts small, with an issue everyone decides to manage around. By the time it surfaces, people are reacting to the silence, the delay and the sense of unfairness as much as to the original problem. A policy that gives a clear, early route for a concern does not create conflict. It gives people somewhere to put it before it grows.
Calm, clear and early is usually better than perfect and too late. A grievance policy does not have to be perfect. It has to tell people who to go to, what happens next and how long it will take, and then the business has to keep to it.
The contrarian part is this. Many owners believe a good manager can sort out any dispute between their own staff, and so they write policies that route everything back through the manager. We disagree. Someone who manages the people involved, has advised one side or will decide the outcome is not neutral. A good policy builds in the exit for that case, in plain words, before it is needed.
References
Questions
Other questions people ask
- How often should a staff handbook be updated?
- A light review once a year is a practical minimum for most small businesses. Add a targeted review whenever the business changes in a way that affects how people work or raise concerns, such as new roles, hybrid work, growth or a complaint that exposed a gap. The aim is to keep the document matching what actually happens.
- Is a staff handbook a legal requirement in Australia?
- Whether a particular policy, clause or wording is legally required for your business depends on your industry, size and any award or agreement that applies. That is a question for an employment lawyer. A handbook that people can read and use is more helpful than one that sits in a drawer.
- What should a grievance policy include?
- At a minimum: more than one person or route for raising a concern, so nobody has to go to the person involved. It should also set out how and when the concern will be acknowledged, what options exist for dealing with it, and how the person raising it will be kept informed. Write it as numbered steps with a named role at each one.
- Who should review HR policies if we have no HR team?
- Give each policy to a named owner, usually the owner, general manager or operations manager, and do a first pass in-house. Where the person reviewing would be judging their own people, or you want a fresh set of eyes, bring in an outside reviewer. Conflict Services policy review is $290 ex GST an hour, with no retainer.
- How do I make HR policies easier to read?
- Use short sentences, one idea at a time, active voice and numbered steps. Name who does each step by role. Cut formal phrases that add nothing. A good test is whether a new starter can read the policy once and explain it back in their own words.
Written by
Conflict Services
Mediators, an investigator, a leadership coach and HR and governance specialists, matched to the matter.
General information only, not legal advice. Conflict Services provides mediation, HR guidance and policy review.







