Workflow rules a diocesan administrator can build: triggered by record events, schedules, form submissions or key dates — a DBS expiring, a visa ending, a role handover — and acting through a library of templated steps, with every run logged for audit.
A trigger, an action, and a picture of the whole thing your team can actually read.
Record events, schedules, form submissions, inactivity — and the key dates that matter in a diocese: DBS expiry, visa expiry, licence end, role handover. The system notices so nobody has to.
Send templated email, create tasks (one, or one per team member), notify users, open pipeline items, enrol in campaign sequences, update fields, apply tags, record notes — and an AI-decision step for the judgement calls. How the AI step works →
Every rule rendered visually, plus a friendly no-code builder for composing new ones — the automation estate is legible to the people who own it, not just the person who built it.
Start from a library, approve in chains, and wrap the genuinely complex processes in guided run-throughs.
Pre-built workflow templates you can preview and instantiate — the common diocesan patterns, ready to switch on.
Configurable approval chains with every decision recorded — expenses, changes, requests, each with the right sign-offs in the right order.
Guided, repeatable run-throughs for complex processes — a vacancy, an onboarding, a scheme — so the tenth time is as reliable as the first.
Recurring review tasks generated and chased automatically — the annual checks stop depending on someone’s calendar reminder.
Every execution logged: what fired, what it did, what it touched. Automation you can audit is automation you can trust.
Outbound webhooks when workflows fire — so the systems around the platform hear about changes the moment they happen.
Live screens from the platform.
The best diocesan automation isn’t clever — it’s the reminder that went out on time, every time, with a log to prove it.— Triggers, actions and audit — the same pattern across all 25+ operational areas