A case that outlives three officers. A policy every PCC has to adopt. A document somebody will need in twenty years, and one that must be destroyed in seven. A question from a churchwarden at half past four. None of it belongs to a module — which is exactly why it goes missing.
These are the areas people forget to ask about in a demo, and the ones they miss most in year two.
A long-running piece of work — a difficult parish, a building project, a wellbeing concern — opened against whatever it actually concerns: a person, a parish, a church, a school. Status history, notes and documents stay with it when the person who started it moves on.
Diocesan templates rendered into each parish’s own version with their names and contacts filled in, then tracked through adoption, review and evidence. “How many PCCs have adopted the current safeguarding policy?” is a number, not a survey.
Multi-step approval flows for the things that need a second pair of eyes — spend, grants, data changes, access — with each decision recorded against the request rather than lost in an inbox.
The plumbing that decides whether the rest of the platform is used or worked around.
Files held against the record they belong to, versioned, with types and links — not a shared drive nobody can search.
Retention policies applied to the material they govern, with a floor under safeguarding records that a well-meaning tidy-up cannot shorten. GDPR & audit →
Letters, certificates and statutory forms generated from the record, so the details in them are the details you hold.
Articles and categories for the answers staff give repeatedly, with the history of how the answer changed.
Requests from parishes and staff, with categories, macros and response targets — and the asker’s own record beside the question.
Online forms and surveys whose answers land on the record they concern, rather than in a spreadsheet export nobody reconciles.
Events, sessions, venues and bookings — attendance recorded against the person, so training, courses and gatherings all count.
Shifts and assignments for the duties that recur, held beside the people who cover them.
Tasks and task processes attached to the case, scheme or post they advance — with dependencies, so “what is blocking this?” has an answer.
Clergy announcements and internal notices sent to defined lists, recorded as sent — the trail survives the mail merge.
Periodic campaigns that ask an owner to confirm who should still have access to what, with the answers kept. Security →
What a committee asks for during a meeting is logged as it is said, straight into the backlog — which is also how we take requirements from you. How we work →