The diocesan operating system that joins up Church House staff and parishes — over 25 operational areas, 32 pre-built dashboards, 170+ metrics, all on Microsoft 365 you already pay for. Live across UK dioceses today.
It isn't a generic CRM bent into a diocesan shape. It was built around how dioceses actually work — and around the cross-team coordination problem the OPP described.
A unified record of every parish, contact, role and interaction. The cross-team panel surfaces what other Church House teams are doing on the same parish — ending "many versions of the truth" the moment two teams open the same page.
A back-office for Church House staff and a parish-facing portal for churchwardens and treasurers, sharing the same database. A churchwarden's submission lands on the archdeacon's dashboard before the kettle has boiled.
Calls through Teams, email through Graph, AI through Azure OpenAI, SSO through Azure AD. Subject Access Requests treated as a workflow with a tracked deadline — not patched on later. One vendor boundary.
Different people in a diocese need radically different views — and radically different things hidden from them. The platform is built around the role, not the seat licence.
Subject Access Requests as a workflow, not a panic. Layered role-as-job-category permissions. One vendor boundary. Funder-ready PDF reporting in two clicks.
The same parish appears the same way to the archdeacon, the safeguarding officer and the area dean. Succession planning stops being anecdotal. Cross-team work stops getting tangled.
Parish share goes live with a year-on-year change log defensible to PCCs and auditors. DIP/SDF programmes on one RAG dashboard. Audit-actions linked to purchase orders.
Open a parish, see every team's interaction with it side-by-side. File the Form C return online, and let the system chase the DBS that's coming up for renewal.
Every DBS dated. Required training derived from job category. Allegations register with case management. Workflow emails the right people 90 days before it matters.
Sign in, do your declaration, book the visitation, submit the meter reading, sign the Gift Aid declaration, file the APCM — all in one place, on your phone.
Every cycle, every cadence and every role-holder a diocese touches. The list below is a representative sample; the platform covers more. The whole thing is one platform, not a set of modules sold separately.
A handful of screens from a live diocese. Mock data shown; the same layouts run against real CMS data once you’re onboarded.
Three of the seven before/after stories on the case-studies page. Each is short enough to read in 20 seconds — and grounded in something that has actually happened.
On a Wednesday, the Stewardship team emails a benefice to discuss giving. The same morning, Mission & Pastoral are visiting that benefice about a reorganisation. The vicar feels the diocese is uncoordinated — and says so.
When Stewardship opens the benefice page, the cross-team panel shows that Mission & Pastoral logged a meeting yesterday and have another booked next week. The email is paused for a fortnight. The vicar gets one diocese, not two.
A children's worker's DBS lapses. Nobody knows for three months. A safeguarding incident exposes the gap.
The system sees the expiry coming 90 days out. A workflow rule emails the parish, creates a task for the safeguarding administrator, and surfaces it on the DBS Expiring Soon dashboard. The DBS is renewed before it lapses.
DIP/SDF programme reporting is a quarterly assembly job: status reports written by hand, copied into PowerPoint, sent to the funder. RAG ratings are a judgement call no-one will defend.
Project leads update directly. The portfolio RAG dashboard is live. The funder gets a two-click PDF that already exists. The board paper writes itself.
Diocesan trust is earned over years, not signatures. Every line below is a quotable defence.
Laravel + Nova + PostgreSQL. No proprietary runtime, no bespoke language, no orphan-vendor risk.
The platform sits inside your existing Microsoft compliance boundary — it doesn't drag you into a new one.
Live at the Diocese of Leeds in anger across multiple teams. This is not a slide deck.
Back-office and parish portal weren't bolted on later — they were architected together. No "phase two for the portal" risk.
Subject Access Requests, right-to-erasure, retention policy and PII redaction are first-class features.
Standard schema, standard exports, well-documented data model. You take your data with you if you ever leave.
Four short reads for the questions that come up before a board paper.
The platform end-to-end — what we replace, where we sit, what your teams see.
24+ self-service tools for churchwardens, treasurers and PCC secretaries.
Phase 0 to Phase 4: what a roll-out actually looks like, by quarter.
The ten questions diocesan secretaries actually ask — with candid answers.
"Before DMS we had five different systems and a person whose job was effectively to copy data between them. That role doesn't exist anymore. She's doing actual work now."— Diocesan Secretary · UK Diocese · 2025