Email through your own Microsoft 365 tenancy, calls through Teams, sign-on through Azure AD — and more than fifteen national datasets syncing into your records automatically, from the Church of England’s CMS to Historic England and the Land Registry.
We’re not asking you to swap vendors — the platform sits on top of Microsoft 365 and the national Church systems you already run.
Outbound email sent and archived through your own M365 tenancy via Microsoft Graph. Click-to-dial from any contact record through Teams, with automatic call logs. Staff sign in with the Azure AD accounts they already have.
A two-way contacts and places bridge with the Church of England’s Contact Management System — the national record and the diocesan record stay in step without re-keying either.
Hierarchy and boundaries from the CofE ArcGIS layers, charity registrations, school records, heritage listings, land titles — synced on schedule, attached to the right parish, church or person automatically.
Every sync enriches the record it belongs to — so a church shows its listing, its risk register entry, its title, its EPC and its flood band without anyone visiting four websites.
Historic England’s National Heritage List matched by list entry number, the Heritage at Risk register with its priority categories, plus conservation areas, scheduled monuments and TPOs from planning.data.gov.uk. See church care →
HM Land Registry titles and INSPIRE polygons, OpenStreetMap footprints, OS Open UPRNs, and the brownfield land registers — you know exactly what land every record concerns.
The Charity Commission register matched and synced; DfE/GIAS school data including capacity and roll, with governors tracked as contacts.
ONS and Nomis census data, the 2025 Indices of Multiple Deprivation kept as its own vintage alongside 2019, age bands per parish, and ONS postcode geography for the joins underneath. See reporting →
The EPC register, the CofE Energy Footprint Tool, A Rocha Eco Church awards, Environment Agency flood alerts and risk bands, PVGIS and Open-Meteo solar estimates, live grid carbon intensity, and year-versioned government GHG conversion factors. See Net Zero →
National Lottery Heritage Fund and National Churches Trust grant awards; annual parish returns (SfM, RoPF, EFT) imported with validation — plus legacy-system bridges with reconciliation and audit tools for the transition years.
An enrichment that quietly guesses is worse than one that admits it has nothing.
Where a national dataset is reissued — deprivation indices, carbon conversion factors — each release is kept as its own vintage and the year used is recorded against the figure. Last year’s report still reproduces.
Where a source cannot answer for a record, the screen says it could not assess — never “no risk” and never a silent zero.
A church without a confirmed list entry number is described as not verified rather than not listed. They are different claims and the platform keeps them apart.
Every external sync is individually enabled, so a diocese takes the ones it wants and leaves the rest — including any whose licensing it needs to clear first for its own use.
Every import previews before it writes, and the preview genuinely writes nothing — no relying on a rollback that some table would ignore.
Records that match confidently are linked; near-misses go to a queue for someone to decide. Nothing overwrites your record on a guess.
Where the line sits between the national Contact Management System and your own.
Clergy, licensed ministers, churchwardens and the places themselves sync down from CMS. Everything CMS does not model is held locally and never written back. The line is agreed once during setup and then enforced by the software rather than by memory.
Places, people, postings and training run nightly, with a full reconciliation on demand. Dates of birth and training records come down the same channel, so retirement projections and safeguarding compliance rest on the national record.
Safeguarding training is matched to people from the national portal’s own exports and via CMS. Nobody needs to create a role in CMS simply to have somewhere to record a certificate, which is a common source of duplication.
A standing screen comparing your data against CMS in both directions: places in one and not the other, people whose posts disagree, records matching on name but not identifier. Data quality stops being an opinion and becomes a list with names on it.
A sibling screen reconciles your boundaries and church locations against the national ArcGIS layers, field by field, so you see which is stale before a map goes in a board paper.
On a live diocese this surfaced posts the diocese was funding that appeared in CMS holding nothing at all — not a report anyone can produce by eye.
We’re not asking you to swap vendors — we’re asking your existing Microsoft estate to do diocesan work.— From the DMS FAQ: “We already use Microsoft 365 — why something else?”