What year one
looks like.

We map your team's terminology onto the platform's data model, identify which sources you'll migrate and which you'll keep external, and assess your Microsoft tenancy posture.

• Vocabulary mapping — your terms onto our entities (deanery, benefice, post, tenure type, scheme).
• Data-source inventory — what migrates, what integrates, what retires.
• Microsoft tenancy review — Azure AD groups, Graph permissions, Power BI estate.
• Stakeholder map — who needs what dashboard, who has what permission.

The diocesan record (parishes, benefices, deaneries, contacts, job roles) is loaded. Azure AD SSO is wired up; back-office staff log in for the first time. The cross-team panel becomes the first thing anyone notices changed.

• Diocesan hierarchy loaded — archdeaconries, deaneries, benefices, parishes, churches.
• Contacts and job roles loaded — with role-as-job-category permissions live from day one.
• Azure AD SSO configured — staff log in with their existing diocesan account.
• First two dashboards live — typically Bishop's Overview and Archdeacon Overview.
• Cross-team panel switched on across every parish page.

DBS data lands and expiry workflows fire. Annual returns ingestion (SfM, RoPF, EFT) is configured. The keenest team writes their first email templates and workflow rules.

• DBS records imported — expiry workflow live with 90/60/30-day reminders.
• Statistics for Mission, Return of Parish Finance and Energy Footprint Tool ingestion configured.
• Email templates written, versioned and deployed by an admin user (no developer needed).
• First workflow rules go live — typically DBS expiry and roles ending soon.
• Parish policies templated and rendered for every PCC.

The portal goes live for a friendly cohort of parishes — typically a single deanery. Churchwarden Declaration and Form C move online. The portal expands across the diocese as confidence builds.

• Pilot deanery onboarded — magic-link emails, 2FA, interactive tour.
• Churchwarden Declaration and Form C move online — visitation booking direct to the archdeacon's diary.
• Meter readings, Gift Aid declarations and APCM submissions go online.
• Public-facing parish share view, church directory and "What's on" calendar published.
• Portal rolled out diocese-wide once the pilot deanery is steady.

DIP/SDF programmes are loaded. Net Zero is wired through to schools, houses and church estate. Power BI integration (embed and/or data-mart) is delivered. Power users start building their own dashboards on the visual report builder.

• DIP / SDF / Barnabas programme tracking live — portfolio RAG, two-click PDF export.
• Net Zero unified across churches, schools and clergy houses.
• Power BI integration delivered — embed existing tiles or refresh from the OData feed.
• Visual pivot builder and report builder rolled out to power users.
• AI assistant fine-tuned on the diocesan corpus and switched on for staff.

Once the platform is in, the requests change shape. They stop being "can we do X?" and start being "could we extend X?". The diocese's own roadmap takes over.

• Mobile PWA for field use — visit logging from a parish car park, even without signal.
• Inbound email-to-engagement — replies threading back onto the contact timeline automatically.
• AI assistant fine-tuning on diocesan corpus continues; new tools added as the team finds them useful.
• Whatever the diocese discovers it wants once it has the platform.