Owns drafts, version history and publication without a personal Drive folder.
PP · Club OS module
Policies should be current, owned and acknowledged — not a PDF from 2019.
Policies & Procedures is where Club OS publishes the rules and working methods the committee expects people to follow: policies, procedures, roles and responsibilities, handovers, acknowledgements and approval workflows. EquippedAI can draft, rewrite and gap-check so the club starts from a usable document instead of a blank page.
The job
What Policies & Procedures is for.
Give secretaries and presidents a controlled way to draft, approve, publish and acknowledge club policies — with role handovers that survive the AGM and files that still live in Documents & Vault.
Who uses it Secretary President Welfare / compliance lead Role holder Incoming committee
Built around real club roles.
Runs committee approval and knows what is currently in force.
Needs child safety and related policies acknowledged by the right roles.
Reads what the job expects and completes handover when they leave.
Inherits current policies and role packs instead of hunting old email.
Inside the module 01 02 03 04 05 01 02 03 04
The functionality committees actually run.
Policies, procedures and approvals
Write once, approve properly, publish with a date the club can defend.
Policies and procedures as club records
Each policy has an owner, status and effective date. Superseded versions stay findable so the club knows what was in force last season.
Committee approval workflows
Draft, review, approve and publish with a trail. Policies should not go live from one person’s laptop the night before the AGM.
EquippedAI draft, rewrite and gap-check
Start from a prompt or an old document: draft language, tighten wording and flag gaps against what the club already requires. Humans still approve before publish.
Stored with Documents & Vault
Published files and supporting packs sit where Library and Vault already work. Policies are not orphans in a side folder.
Announce through club channels
When a policy changes, Communication & Social Media can carry the notice to the roles who must read it.
Roles, handovers and acknowledgements
People should know what the job is — and confirm they have read what applies to them.
Roles and responsibilities
Define what each committee and volunteer role owns. Responsibilities attach to People & Teams roles, not to a shared inbox nickname.
Role handovers
Build a handover pack: key policies, procedures, contacts and first-month tasks. Club Meetings can brief the incoming officer against the same pack.
Policy acknowledgements
Require named roles to acknowledge child safety, codes of conduct or season policies. Outstanding acknowledgements stay visible.
A trail for disputes and audits
When someone says they were never told, the club can show the version, the audience and the acknowledgement time.
How it runs
A path volunteers can repeat.
01 · Draft or import Start from EquippedAI, an existing file or a blank policy the club must write.
02 · Approve in committee Run the approval workflow until the document is ready to publish.
03 · Publish and acknowledge Put the policy in force, store the file, and collect acknowledgements from required roles.
04 · Hand over the role Attach procedures and packs so the next volunteer inherits the job, not a rumour.
What it replaces
The hidden systems clubs already have.
- Policies in a president’s email
- FINAL_policy_v7.pdf on a USB
- Acknowledgements on a clipboard
- Handover as a car-park chat
- Blank-page drafting the week before AGM
Connected modules
This work does not sit alone.
See Policies & Procedures in a walkthrough.
We will show the working screens, the volunteer path, and how this module connects to the rest of Club OS for your club.
Ready when your committee is
Give the club a system that outlasts the season.
Start with the workflows causing the most pressure, then grow into a full Club Operating System.