Building something
with AI?
Whether it's an idea, automation, dashboard, bot, website or full application, we want to know what you're building.
Your project could go further than your expression.
The AI Training Programme did what it set out to do: AI adoption is now decentralised across the network. Teams are building. Some of those solutions have started touching member data, carrying the name of the church, and becoming load-bearing for ministry operations.
That progress creates a new responsibility. Innovation at this level must be matched with structure — not to slow it, but to protect it and to multiply it.
You are encouraged to innovate
Every expression is encouraged to use approved AI tools in daily ministry work without seeking permission. Everyday use needs no form at all.
The AI Ministry wants to know what is being built
Not to approve every keystroke — to hold one clear picture of what exists across the network, who owns it, and what data it touches.
Good projects can be refined and replicated
A solution that meets a real need in one expression should not stay local. Registered projects are assessed for wider deployment — and the team that built it is credited and invited into the work.
Governance protects people, the church and the project
It protects the members whose information you hold, the church whose name you carry, and you — so the thing you built does not quietly become a risk you own alone.
Not every use of AI requires reporting.
Three tiers decide what is expected of you. Most everyday work sits in Tier 1 and needs nothing at all.
Everyday AI Use
- Drafting
- Research
- Summarising
- Flyer design
- Image and video generation
- Sermon preparation support
- Social media content
Operational Tools
- Recurring automations
- Workflows
- Dashboards
- Bots
- Shared templates
- Team tools
- Tools processing attendance, first-timer or unit records
Applications & Systems
- Web applications
- Mobile applications
- Databases
- Member-facing portals
- Integrations
- Systems storing member data
- Solutions carrying The Elevation Church name
- Solutions other expressions will depend on
Regardless of tier, always report
These five things are reported whatever tier your work sits in.
- Any solution that stores, transmits, or processes member personal data
- Any solution that is member-facing or carries The Elevation Church name, logo, or domain
- Any solution built or maintained by an external party, vendor, or volunteer outside the expression
- Any incident, data exposure, or AI-generated output that caused or could have caused harm, offence, or doctrinal misrepresentation
- Any recurring cost, subscription, or hosting arrangement entered into for an AI solution.
Every AI project is measured against seven principles.
They apply from the first line of a prompt to the last day a system is in service.
Ministry First
Technology serves the mission; it does not set it. Every solution must answer a real ministry need and be able to state it in one sentence.
Stewardship of Trust
Members entrust the church with information given in confidence. That trust is a pastoral obligation before it is a technical one, and it governs every decision about data.
Human Oversight
AI output is a draft, never a final word. Anything teaching, counselling, pastoral, doctrinal or member-facing is reviewed and approved by a responsible human before release.
Truthfulness
AI-generated content must be verified for accuracy. Scripture, quotations, statistics and attributed statements are checked against source before publication.
Named Accountability
Every project has a named human owner and a named Resident Pastor sponsor. No solution goes live owned by 'the team'.
Transparency
Where members interact with an AI system, they are told so. Automated communication is not passed off as personal pastoral contact.
Built to be Shared
Solutions are documented and built so that another expression could adopt them. What solves a problem in one place should be able to serve the whole.
Information members give the church is given in trust.
Four classifications decide how each category may be handled with AI tools — and they apply to every tier of use, including everyday Tier 1 activity.
No restrictions
Published sermons, service times, public events, published social content, general teaching material.
May be used freely with approved AI tools.
Church-managed accounts only
Rosters, planning documents, aggregated/anonymised figures.
May be used with approved AI tools using church-managed accounts. Remove names before submitting.
Access-controlled systems only
Names, phone numbers, addresses, emails, attendance, first-timer records.
Only within approved, access-controlled systems. Must not be pasted into public or personal AI accounts.
Written approval required
Counselling notes, prayer requests, giving/financial records, health, family, welfare, safeguarding and disciplinary information.
Must never be entered into any AI tool, of any kind, under any circumstance, without explicit written approval from the AI Ministry and the responsible pastor.
Sensitive pastoral data
Counselling notes, prayer requests, giving and financial records, health, family, marital or welfare information, safeguarding matters and disciplinary records must never be entered into any AI tool, of any kind, under any circumstance, without explicit written approval from the AI Ministry and the responsible pastor.
Reporting is deliberately light.
For most projects it is a single form and a short conversation. The full seven stages apply to Tier 3; Tier 2 projects complete Stage 1 only.
Register
Tell us what you are building.
Review
We read it properly and come back to you.
Build
Build it against the agreed scope.
Pre-launch Check
A short readiness confirmation before go-live.
Launch & Log
You go live and join the network register.
Report
A brief quarterly update. Incidents immediately.
Replication Review
Could this serve the whole church?
Acknowledged within 3 working days
Every submission is acknowledged, whatever its tier.
Tier 3 decision within 10 working days
From a complete submission. Where a decision will take longer, we say so and give a date.
Pre-launch check within 5 working days
A short readiness confirmation before you go live.
What solves a problem in one place should be able to serve the whole.
A solution that meets a real need in one expression should not remain local. Registered projects travel a defined pathway — and where a solution is adopted network-wide, the expression and team that built it are credited and invited into the standardisation work.
Initiative is to be honoured, not absorbed quietly.
Local
Built and running in one expression.
Reviewed
Assessed by the AI Ministry for wider value.
Recommended
Shared with the network as a proven pattern.
Standardised
Refined into a supported network solution.
Global
Deployed across the global church.
Have something in mind?
Tell us what you're building. We'll help you make it safe, sustainable and shareable across The Elevation Church.
About 15 minutes · You can save and finish later