If you’re running a business with 20 to 250 people, HR can look “fine” for a long time.
People get paid. New starters turn up. The team mostly gets along. Issues get handled… kind of.
Then one day you’re staring at a complaint, a performance issue that’s gone stale, a workplace injury, or a Fair Work change you didn’t catch. And suddenly HR isn’t admin. It’s time, risk, reputation, and a leadership week you don’t get back.
This is the hidden cost of patchy HR systems. Not because you don’t care. Because HR outgrew the ops desk and no one sent a calendar invite to mark the moment.
In this edition you’ll spot the early warning signs, and grab our downloadable HR Health Checklist (SME Edition) to pressure-test your foundations. For SMEs, it’s the fastest way to identify people risk before it turns into a formal complaint, a Fair Work problem, a safety issue, or a leadership time sink.
Why HR looks fine right up until it isn’t
Most SMEs don’t have “no HR.” They have informal HR.
It lives in a few places:
- A contract template someone found years ago
- A manager who’s good with people (until they’re not)
- A policy folder that hasn’t been opened since the last resignation
- A payroll process that works, but no one wants to touch
This setup survives on goodwill and momentum.
And that’s why it feels fine.
Until you need to prove you were fair. Or consistent. Or compliant. Or that you followed your own process.
That’s the shift.
HR stops being what you do.
It becomes what you can defend.
The 4 moments that expose patchy HR
Different industries, same pattern.
1) A complaint lands and suddenly everything needs to be documented
You can be a fair employer and still be exposed if you can’t show:
- what the expectations were
- what happened
- how you responded
- whether you followed a reasonable process
The stress isn’t just the complaint. It’s the scramble to reconstruct the story.
2) A performance issue goes from annoying to formal
Performance rarely explodes overnight. It drips.
A few missed deadlines. A manager avoiding the conversation. A team quietly carrying someone.
Then you finally act, and realise you’re missing:
- a clear position description
- documented expectations
- consistent feedback records
- a process that’s fair and workable
Now it’s not just “manage performance.” It’s “manage performance without stepping on a legal landmine.”
3) A workplace injury or incident triggers WHS and workers’ comp pressure
When something goes wrong, the question isn’t only “what happened?”
It’s also:
- were you compliant
- did you train properly
- did you have the right reporting and incident process
- did you manage return to work sensibly
If the answer is “we do it, but it’s not written down,” you’re relying on memory under pressure
4) A Fair Work or Award change quietly makes you non-compliant
This one is brutal because you can be doing your best and still miss it.
If your agreements, classifications, pay conditions, or policies are out of date, the risk doesn’t announce itself politely. It shows up when:
- someone questions their pay
- you terminate employment
- you get audited
- you have a dispute
The Hidden Cost Equation (ForgeHR’s view)
Most people think the cost of patchy HR is legal risk.
That’s part of it.
The sneakier cost is leadership bandwidth.
Here’s the equation we see in real businesses:
Patchy HR + normal human behaviour = leadership time leak
And when the market feels unsteady, time leaks hurt more. You don’t have spare capacity for avoidable mess.
A simple example:
- You’re dealing with a performance issue.
- It’s taking your Ops Manager 6 hours a week.
- It’s dragging down the team.
- It’s creating resentment.
- You still haven’t had the hard conversation.
That’s not an HR issue.
That’s a management cost.
An audit is the fastest way to stop guessing where the gaps are.
What to do if you find gaps (without spiralling)
If you scan your current setup and think, “Okay… we’ve got some holes,” good.
That’s not failure. That’s information.
The mistake is trying to fix everything at once, then doing none of it because the business is busy and HR feels like a side quest.
Here’s the order that actually works.
1) Triage the risk. Start with anything that could hurt you quickly if challenged.
- Employment agreements that don’t match reality
- Award/classification uncertainty
- Pay conditions that haven’t been checked in a while
- Anything you’d struggle to defend if an employee questioned it
If you’re not sure what’s “high risk,” that’s the point. You need a clear call, not more guessing.
2) Fix the repeat offenders. These are the gaps that create the same mess over and over.
- Onboarding that’s inconsistent
- Role clarity that lives in someone’s head
- Managers handling performance differently depending on who they like
These don’t always look like compliance problems. They look like turnover, resentment, and leaders spending their week in awkward conversations.
3) Make it easy for managers to do the right thing. If your process is too complicated, it won’t get followed. Simple beats fancy.
- A basic performance conversation guide
- A documentation habit that takes five minutes, not an hour
- Clear “if this happens, do this” steps for complaints and conduct issues
4) Put an owner on it. Not “HR owns it.” A real person. If HR is everyone’s job, it becomes nobody’s job.
Once you’ve got the top 3 priorities, you’ve got momentum. And momentum is what stops HR drifting back to “we’ll deal with it later.”
Before the next issue chooses you
If any part of this felt uncomfortably familiar, don’t wait for the complaint, the claim, or the awkward termination to test your systems.
You don’t need a 12-month transformation plan.
You need clarity on where you stand, right now.
Download our HR Health Checklist and pressure-test your current setup. Check what you think, you’ll see:
- Where you’re exposed
- What’s solid
- What needs tightening before it costs you time, money, or reputation
Strong businesses don’t assume their HR is fine. They verify it.
To verify you your systems and processes:
Further info:
Fair Work Ombudsman Fact Sheets

Fine, fine, fine?