Every church needs a small library of formal policies. Safeguarding. Data protection. Health and safety. A volunteer code of conduct. A complaints procedure. A trustees statement if you're a charity. None of these are optional, and trustees who don't have them on file are personally on the hook if something goes wrong.

And yet, in the average UK church, the policies live as Word documents on the office laptop. Nobody knows which is the latest version. Nobody can prove the kids' team has read them. The trustee who wrote them moved away in 2022 and the file is in their old email account.

We thought we could do better. The new Policies surface in ChurchLinker handles the whole life cycle, from draft to publish to acknowledgement, with the audit trail trustees actually need.

Start from a real starter library

We seeded ten policy templates inside ChurchLinker, written for UK churches, opening with a 'review before publishing' banner so nobody assumes the default text is final. The library covers Safeguarding (children and adults at risk), a Kids and Youth code of conduct, UK GDPR privacy notice, a data retention schedule, Health and Safety, a Volunteer code of conduct, a Complaints procedure, Trustee roles and responsibilities, Pastoral Care, and a Marriage policy.

When you take a copy, the church's name is substituted in for you, so the draft reads naturally from the first line. You then edit in a rich-text editor with bold, italic, links, headings, bullet points and quotes. No HTML, no Word-document weirdness, no formatting that breaks when somebody else opens it.

Publishing is a real event

We make publishing deliberate. You edit the draft, you click Publish, and we snapshot the body into an immutable version row with a timestamp, the publisher's email, and an optional change note ('Updated section 4 after the safeguarding training'). That snapshot is what every member sees. The next edit creates the next snapshot, and the old one is preserved in the version history so an audit can show exactly what was current on any given date.

Acknowledgements that mean something

Optionally, you can mark a policy as requiring acknowledgement. The next time each member opens the member app, they see a small amber banner: 'You have one policy to acknowledge.' Tapping through shows the policy, with an 'I've read this' button at the bottom. We record the acknowledgement against the specific version they read, not against the policy generally, so re-publishing forces re-acknowledgement. The church can prove the flock has read the current text, not a prior one, which is what the safeguarding paper trail actually needs.

Group restriction

Some policies apply to everyone (the GDPR privacy notice). Some only apply to a specific team (the Kids and Youth code of conduct only applies to people on the kids' team). For the second case, set 'Visible only to group' on the policy edit screen and pick the group. Members of other groups won't see it on their member-app policy list, and won't be asked to acknowledge it. Sensible default, no over-sharing.

Upload a signed PDF too

Some churches have an authoritative typeset version of a policy, signed by the trustees on a particular date. ChurchLinker lets you attach a PDF to the policy alongside the rich-text body. We snapshot the URL into each version at publish time so re-uploading a new PDF later doesn't quietly rewrite an already-acknowledged version. Belt and braces.

Why this matters

The Charity Commission keeps publishing case studies where churches got into trouble because they couldn't prove their volunteers had been briefed on safeguarding. Acknowledgement tracking is the missing piece. When the safeguarding officer asks who's read the latest update to the Children's Code of Conduct, you can show them a list with a date next to every name. That's not a CRM feature. That's a piece of evidence.

Available now

Policies, version history and acknowledgement tracking are on every plan. The PDF attachment is on every plan too. The seeded template library is bundled with the build, no extra setup. Group restriction is on every plan.

If you've been meaning to get the policies sorted, this is the afternoon's job.

Church policies your members actually read (and can prove they read)