Open your shared Drive.
Scroll past “FINAL_v3_USE_THIS_ONE” and “Policy Pack (old).” Find the folder labelled Policies. Click in.
Now ask yourself, honestly: When was the last time a committee member opened one of those files before something went wrong?
If the answer is “never,” you’re not alone. I see beautiful policy libraries in tiny associationsprivacy, complaints, child safety, volunteer conduct, social media—all carefully downloaded from a template site in 2021 and never touched again.
Paperwork that nobody reads doesn’t protect your people. It just creates a false sense of calm.
Why policies die in folders
Three usual culprits:
They’re too long. A 14-page code of conduct for a volunteer-run hall committee will not be read. People will skim the first page and assume the rest is “lawyer stuff.”
They’re written for someone else. Corporate tone, interstate legislation references that don’t apply, or procedures that assume a paid HR team. Volunteers bounce.
Nobody owns them. There’s no annual review date, no induction that points to them, and no habit of using them when a real issue pops up. So they fossilise.
Fewer policies. Better ones.
You don’t need a policy for every imaginable scenario.
Start with what you actually need: how you treat people, how you handle money, how you keep kids and vulnerable people safe (if relevant), how complaints get heard, and how you protect personal information.
If a policy doesn’t change a decision or a behaviour, cut it—or merge it.
Aim for plain English and short sections. Headings that answer real questions: What do I do if? “Who decides…?” “Where do I report…?”
A two-page policy that gets used beats a twenty-page policy that gets filed.
Make them findable
“It’s in Drive somewhere” is not a system.
Use one folder. Clear names. A simple index at the top: Policy name → last reviewed → owner.
When you induct a new committee member, don’t hand them thirty PDFs. Hand them the five that matter for their role, and show them where the rest live.
If someone asks “what’s our process for X? and the answer takes more than thirty seconds to find, your filing is the problem—not their memory.
Use them when it counts
Policies earn their keep in awkward moments.
Someone complains about a volunteer’s behaviour. A conflict of interest turns up. A grant requires evidence you followed your own rules.
That’s when you open the document, follow the steps, and write down what you did. Not to be pedantic—to be fair. Consistent process protects the complainant, the accused, and the committee.
If you discover mid-crisis that the policy is nonsense, fix it after you’ve dealt with the immediate issue. Don’t invent process on the fly and pretend it was always there.
Review like you mean it
Put policy review on the board calendar once a year. Ten minutes each for a couple of policies beats a weekend “policy retreat” that never happens.
Ask: Still legal for our state? Still match how we work? Still understandable? Still needed?
Update the date. Note what changed. Move on.
Version control without the drama
You don’t need enterprise document software. You need one rule: one current version, clearly named, with a date.
Complaints-Policy-2025-11.pdf beats complaints FINAL FINAL (2) (1).docx sitting in three folders.
When you update a policy, move the old one to an Archive subfolder. Don’t delete history—just get it out of the way. In the current file header, note: approved by [board/committee], date, next review.
If two “current” policies disagree, you’ve created a governance trap. Pick one. Minute the decision. Retire the other.
And if a funder or insurer asks for a policy you don’t have, resist the urge to invent a twenty-pager overnight. Write the shortest honest document that matches how you actually work—then improve it on the scheduled review date.
If you’re staring at a graveyard of templates and want a clean, plain-English set sized for a small workplace or association, the Workplace Policy Pack ( https://plainsense.au/workplace-policy-pack ) exists for exactly that—or talk to me ( https://plainsense.au/appointment ) if you’d rather tailor than DIY.
A policy folder isn’t a museum. Its a toolkit. Keep the tools sharp, few, and where people can reach them.
All notes · Book a call
