ChatGPT Prompts for Churches: 10 Admin Jobs, No Sermons

Ten prompts cover the office: a weekly notice sheet, event announcements in three lengths, a rota pattern, hall-hire replies, council agendas and minutes, an annual admin calendar, a quote comparison, a plain-English document brief, and a welcome email for visitors. None writes sermons or touches member data.

That line is drawn on purpose. Sermons, prayers and pastoral advice belong to the church leader, and a church's member list, prayer requests and giving records reveal people's beliefs and circumstances, which data-protection law such as the GDPR treats as especially sensitive. Every prompt below works from facts you type about the church, its rooms and its calendar, never about its people.

Follow me on Instagram@sagnikteaches

Each job has a prompt, a made-up example with the kind of output to expect, and a check to do before anything leaves the office. If you want the wider picture of where AI fits in a church office, AI for church administration: rotas, notice sheets and room bookings covers it. And for the line between office work and pastoral work, see admin versus pastoral care.

Connect on LinkedInSagnik Bhattacharya

The office rules, and what never goes into ChatGPT

Put these rules in a ChatGPT Project's instructions, which apply only inside that project and override your global custom instructions, or paste them above each prompt. The guide to customising ChatGPT with Projects, instructions and files shows the set-up.

Subscribe on YouTube@sagnikteaches

CHURCH OFFICE RULES
You help the office of a small church with administration. Warm, plain English, short sentences, the spelling we use in our notices, no jargon.
Never: write sermons, prayers, devotions or pastoral advice; give theological or legal opinions; invent dates, times, prices, names or room availability.
Never ask for or use personal details about members or visitors. Where a person is needed, use [first name] or a code such as V1.
Use only the facts I give you. If something is missing, write [CHECK: what is missing].

Now the list of what stays out. Names, addresses, phone numbers and email addresses of members and visitors. Prayer requests and pastoral notes. Giving records. Safeguarding concerns, which belong in your safeguarding process and nowhere else. Anything that reveals someone's health or family circumstances. Photos of children. And rota availability tied to named people, which the rota prompt handles with codes. Article 9 of the GDPR lists "religious or philosophical beliefs" among the special categories of personal data, and its exception for religious not-for-profit bodies comes with conditions, including that the data is not disclosed outside the body without consent. Whether a cloud AI tool counts as disclosure is a question for your data-protection adviser. Keeping the data out removes the question.

On a personal ChatGPT plan, switch off "Improve the model for everyone" under Data controls before the office starts; business plans such as ChatGPT Business do not train on business content by default. For a one-off draft, Temporary Chat stays out of your history, creates no memories and is not used to improve models while it stays temporary, though OpenAI says it may keep a copy for up to 30 days for safety. If volunteers will use the tool, agree a policy first: the sample one-page church AI policy is a starting point, and your wider church body may have its own guidance.

Job 1: Turn rough notes into a one-page weekly notice sheet

The weekly sheet is where small errors collect: a time copied from last week, an event listed twice, a deadline hidden mid-paragraph. This prompt keeps your facts fixed and changes only the shape, and it makes the model list anything unclear instead of resolving it quietly.

Task: turn these rough notes into this week's notice sheet.
Format: one A5 page, about 300 words. Sections: Sunday services, This week, Coming up, Thank-yous, Contact the office.
Rules: keep my dates, times and places exactly. Put anything with a deadline in bold, with the date. Merge duplicates. Do not add events I did not mention. List anything unclear under CHECK at the end.
Rough notes: [paste]

With these made-up notes pasted in, the office gets the sheet below.

Sun services 9.30 and 11.15. tea after both in hall.
Tues coffee morning 10-12 hall, all welcome, bring friends
toddler group Thurs 9.30-11, volunteers needed for the rota, ask the office
Christmas fair Sat 28 Nov 10-2 hall, cake stall, crafts, need cakes by Fri 27 Nov, drop at office
Church council Thurs 12 Nov 7.30pm meeting room
thanks to everyone who helped with the hall clean last Sat
office closed Mon 2 Nov

Notices for [church name], week of Sunday 1 November. Sunday services: 9.30 am and 11.15 am, with tea and coffee in the hall after both. This week: Tuesday coffee morning, 10 am to 12 noon, in the hall; all welcome, so bring a friend. Thursday toddler group, 9.30 to 11 am; we need volunteers for the rota, so please ask the office. The office is closed on Monday 2 November. Coming up: Church council, Thursday 12 November, 7.30 pm, meeting room. Christmas fair, Saturday 28 November, 10 am to 2 pm, in the hall, with a cake stall and crafts. Cakes needed by Friday 27 November, dropped at the office. Thank-yous: to everyone who helped with the hall clean last Saturday. Contact the office: [phone], [email]. CHECK: which rota do the toddler group volunteers join? What date was "last Saturday"?

Check before printing: compare every date, weekday and time with your diary, one by one, because a tidy sheet makes a wrong time look official. The CHECK list is the model being honest about gaps; resolve each item rather than deleting it. And read the sheet aloud once, since a page that sounds fine to the ear is usually one that makes sense to a visitor who has never seen last week's.

Job 2: One event, announced in three lengths

An event needs an email, a social post and something the leader can say from the front, and they should carry the same facts at different lengths. The common mistake is to write the long version and then shorten it by hand, which is how the date ends up different in each place. This prompt writes all three from one fact list.

Task: write announcements for this event in three forms: an email under 120 words, a social post under 60 words, and a spoken announcement of about 90 words that a leader can read aloud in about 40 seconds.
Facts: [event, date, day, time, place, cost, who it is for, how to book, deadline, office contact]
Rules: lead with date, time and place. Say what to do and by when. Explain any church term a newcomer might not know. No emojis. The spoken version must be easy to say aloud: no brackets, no abbreviations, no "see below".

Made-up facts: Christmas fair, Saturday 28 November, 10 am to 2 pm, church hall, free entry, cake stall and crafts, all welcome, cakes wanted by Friday 27 November at the office. The spoken version might come back like this, with the social post close behind it.

Spoken: Our Christmas fair is this Saturday, the twenty-eighth of November, from ten in the morning until two in the afternoon, here in the church hall. Entry is free, and everyone is welcome, so please bring a friend or a neighbour. There will be a cake stall and a craft stall. If you can bake, we would love your cakes by Friday the twenty-seventh; just drop them at the office. Come for the cakes, stay for the tea, and say hello to someone you have not met.

Social: Christmas fair at [church name]: Saturday 28 November, 10 am to 2 pm, in the church hall. Free entry, cake stall, crafts and tea. Everyone welcome. Baking cakes? Drop them at the office by Friday 27 November.

Check before sending: the spoken version runs to about 85 words, and at roughly 150 words a minute that is about 35 seconds, inside the 40 you asked for. Count and time yours. Then compare the dates across all three versions, because the point of generating them together is that they match, and verify the line about cakes in particular, since it is the only one that asks someone to do something. Two slips in this sample are worth catching. Both versions mention tea, which was not in the fact list, so either confirm there will be tea or cut it. And the spoken version says "this Saturday": read out on Sunday 1 November, as the notice sheet in Job 1 would have it, that sends people to the hall on the 7th, three weeks early. Give the model the date the announcement will be read, and ask for the full date instead of "this" or "next".

Job 3: A volunteer rota pattern built from codes, not names

A rota is a puzzle of counts and constraints, which suits a language model, and a list of volunteers' names and availability, which does not suit sending anywhere. The answer is to ask for the pattern and keep the people in your own spreadsheet. Give each volunteer a code, keep the key to the codes in the office, and put only the codes into the prompt.

Task: draft an 8-week rota pattern for welcomers.
Slots: 2 welcomers each Sunday for 8 Sundays.
People: 8 volunteers coded V1 to V8. Names stay in my spreadsheet.
Constraints: everyone serves exactly twice; nobody serves on consecutive Sundays; V3 and V7 are unavailable in weeks 3 and 4.
Output: a table with week, welcomer 1, welcomer 2. Then a count of how many times each code appears, and one line per constraint saying met or broken.
Rules: if the constraints cannot all be met, say which one fails. Use no names.

A first draft can arrive with a quiet slip, such as a code in a week it was marked unavailable, while the summary still says "all constraints met". This corrected pattern meets all three.

Check it yourself rather than trusting the model's "met" lines, which are claims, not proof. The maths first: 8 weeks times 2 slots is 16 slots, and 8 volunteers serving twice is 16, so it can close. Then count each code down the columns (V1 appears in weeks 1 and 4, V7 in weeks 5 and 8, and so on), scan the rows for any code in adjacent weeks, and confirm V3 and V7 are absent from weeks 3 and 4. Then paste the pattern into your sheet and look the names up from your key. A code is not anonymous in your hands, but it means ChatGPT never learns who anyone is. When someone drops out, ask for a revised pattern for the remaining weeks with the new constraint, still without names.

Job 4: A hall-hire reply built only from your own hire rules

Hall enquiries arrive vague ("are you free on the 12th?") and tempt a quick, wrong yes. The safe pattern is to paste your own rules and rates and forbid anything outside them. Here are made-up rules, standing in for yours.

HIRE RULES
Main hall: up to 60 people, $25 an hour. Small room: up to 20 people, $12 an hour.
Deposit $50, returned if the room is left clean and undamaged. Kitchen use: $10 flat.
Hours: 8 am to 10 pm. No alcohol. Events over 50 people need the hirer's own liability insurance.
A booking is confirmed when the booking form and deposit are received.

Task: reply to this hall-hire enquiry using only the hire rules above.
Enquiry (first name only): "[message with personal details removed]"
Output: an email under 150 words. Answer what was asked, quote the relevant rates exactly, show the sum, list anything missing that we need to know, and say how a booking is confirmed.
Rules: do not offer a discount or a date. Do not say the hall is free on any day. Write [CHECK] for anything not in the rules.

The made-up enquiry: "Are you free on the 12th for a child's birthday party? About 25 children and 6 adults, 2 pm to 5 pm. What do you charge, and can we use the kitchen?" A good reply runs as follows.

Hi [first name], thanks for asking about the hall. For about 31 people you would need the main hall, at $25 an hour. For 2 pm to 5 pm that is $75, plus $10 if you use the kitchen, so $85 in all, with a $50 deposit that we return if the room is left clean and undamaged. Could you tell me which month you mean? I can't confirm any date until I have checked the diary, and I will do that as soon as I know. A booking is confirmed once we have the booking form and the deposit. No alcohol is allowed in the hall. [name], [church name] office

Check before sending: the sum, which is 3 hours at $25 for $75, plus $10 for the kitchen, giving $85, and then $50 on top as a refundable deposit, so $135 changes hands at booking. Check the capacity against the headcount (31 is within 60). Notice that the model asked for the month, which is why the prompt says to list missing details. And look for any sentence implying the date is available; the diary decides that, not the draft. Any rule the draft mentions must be one that is in your paste, so read it against your real hire agreement.

Job 5: A council agenda built from last meeting's action list

The raw material for the next agenda is already written: the actions from the last meeting, the standing items, and whatever has come in since. The prompt arranges them, puts overdue actions first, and makes the timings add up. Use roles, never names, for who introduces each item.

Task: draft the agenda for the next church council meeting. Length: 90 minutes.
Last meeting's actions (roles, not names): [action, owner's role, due date, done or not]
Standing items: [list]
Items raised since: [list]
Output: a numbered agenda as a table: item, purpose (for decision, discussion or information), paper needed, who introduces it (by role), minutes. Put overdue actions first. The minutes must add up to 90; show the total.
Rules: do not add items I did not list. Flag any item that needs a decision but has no paper.

Made-up inputs: the treasurer's roof inspection report is overdue; the warden has collected three quotes to redecorate the hall; the church leader has drafted Christmas service times; and the warden wants to review the hall hire rates but has not written anything yet. Standing items are the finance report and safeguarding and policy review dates. A sensible output is below.

Check before circulating: add the minute column yourself (5 + 10 + 10 + 10 + 20 + 15 + 10 + 5 + 5 is 90), because a model can write "total 90" above a column that adds to 85. Notice the flag on item 8, which has no paper, and either supply one or drop the item. Confirm the overdue item really is overdue, and that nothing on the agenda is a pastoral or safeguarding matter in disguise; item 7 lists review dates only, and the concerns themselves never appear in a drafting tool.

Job 6: Minutes that copy every resolution word for word

Council minutes are a formal record, and a resolution's wording matters. Language models tidy as they go, and tidying a resolution can change what was agreed. The fix is to mark the exact wording in your typed notes with double braces and tell the model to copy it character for character.

Task: write formal but plain minutes from my typed notes.
Rules: wherever my notes put wording between {{ and }}, copy it word for word and do not tidy, shorten or rephrase it. Record the vote result exactly as I typed it; if I gave none, write [VOTE RESULT?]. Use roles, never names. Do not add anything that is not in my notes.
Sections: Resolutions, Actions (action, role, due date), Reported for information, Deferred.
Notes: [paste]

Made-up notes: "Item 5 hall redecoration. Three quotes seen. {{That the hall walls and ceiling be redecorated by Contractor A at the quoted price of $4,200, with a deposit of not more than 25%.}} Proposed treasurer, seconded warden. For 7, against 1. Carried. Warden to confirm start dates with Contractor A by 20 Nov. Item 6 Christmas services: leader to bring final times next meeting, deferred." The output, trimmed:

Resolution 5.1. "That the hall walls and ceiling be redecorated by Contractor A at the quoted price of $4,200, with a deposit of not more than 25%." Proposed by the treasurer, seconded by the warden. For 7, against 1. Carried. Action: confirm start dates with Contractor A, church warden, by 20 November. Deferred: item 6, Christmas service times; the church leader will bring final times to the next meeting.

Check before filing: copy the resolution from your notes, search for it in the minutes, and confirm it matches exactly. A typical slip turns "the quoted price of $4,200" into "a price of around $4,200", which changes a firm figure into an estimate in the formal record. Confirm the vote numbers match your count of hands, check there is no "unanimously" you did not type, and send the draft through your usual approval at the next meeting, as you would any set of minutes.

Job 7: A twelve-month admin calendar from your own list

Every church office has recurring jobs that live in someone's head: the insurance renewal, the annual meeting, the weekly alarm test. Write them down, with the month and who is responsible by role, and the prompt turns the list into a calendar with a reminder of what to prepare the month before. The important rule is that it adds nothing to your list and states no legal requirements, because it does not know which ones apply to you.

Task: build a 12-month admin calendar from my list of recurring jobs.
Jobs: [job, how often, month or trigger, who (role), notes]
Output: a table by month, January to December: jobs due, who (role), and what to prepare in the month before. Then a list of any job with no month given.
Rules: do not add jobs that are not on my list. Do not state legal requirements or deadlines. If I wrote "check", keep the word "check". Use roles, never names.

Made-up jobs: buildings insurance renewal each June (treasurer, "get two comparison quotes first"), weekly fire alarm test (warden), annual church meeting in April (secretary, "notice period: check"), accounts prepared for review in February (treasurer), hall deep clean in January and August (warden), and an electrical safety check every five years with the next date unknown. The output, trimmed to the interesting rows:

Check before using: every job in the table appears on your list and nothing else does. A tidy-minded model may add "fire risk assessment review" because most calendars have one, and that is exactly the sort of requirement you must source from your insurer or your wider church body, not from a drafting tool. Judge each "prepare" line on its lead time: two insurance quotes in a month may be optimistic, so move the prompt earlier if your renewals take longer. Then load the dates into a shared calendar, since a table nobody sees will not remind anyone.

Job 8: A like-for-like comparison of three contractor quotes

Three quotes rarely cover the same work, and the cheapest one is often the one that left something out. The prompt builds the comparison table, shows the sums, and writes the questions to ask each contractor. It is told not to recommend anyone, since the council decides. Quotes are business information, so they can go in, but remove any individual's mobile number or home address first.

Task: compare these three contractor quotes like for like.
Quotes: [paste Quote A, Quote B and Quote C, personal contact details removed]
Output: a table with total price, what is included, what is excluded, deposit and payment terms for each. Then the price of each quote adjusted to the same scope, with the sums shown. Then questions to ask each contractor so the quotes can be compared. Do not recommend a contractor.
Rules: if a quote does not say whether something is included, write [CHECK] instead of assuming.

Made-up quotes for redecorating the hall. A: $4,200 for walls and ceiling, two coats, materials included, the church moves the furniture, 25% deposit. B: $3,650 for walls only, two coats, materials included, ceiling extra at $700, the contractor moves the furniture, 50% deposit. C: $5,100 for walls, ceiling and woodwork, two coats, materials included, 12-month guarantee, the contractor moves the furniture, 20% deposit.

Adjusted to walls and ceiling: A is $4,200. B is $3,650 + $700 = $4,350, which is $150 more than A. C is $5,100 but includes woodwork that A and B did not quote, so it cannot be compared until C prices walls and ceiling alone. Deposits: A 25% = $1,050; B 50% = $1,825, or $2,175 with the ceiling; C 20% = $1,020. Questions: A, who moves the furniture and how long does it take, and what if the walls need filling? B, is the $700 ceiling price final and does it include materials, and why a 50% deposit? C, what is the price for walls and ceiling only, and what does the guarantee cover?

Check before it reaches the council: redo the sums, since $3,650 + $700 is $4,350 and half of that is $2,175, and confirm each total covers the same scope. The cheapest headline, B at $3,650, becomes the dearer of A and B once the ceiling is added, which is the whole point of the exercise. Watch for a recommendation sneaking in despite the rule ("A looks like the best value"), and cut it, because the council weighs trust, references and insurance as well as price. Ask the contractors the questions in writing and run the comparison again with their answers.

Job 9: A plain-English brief of a long document for the council

Insurance renewals, hire agreements and grant guidance arrive as dense pages that council members do not read. A one-page brief helps, provided it quotes every number and date so they can be checked. Remove any personal details first (a claims history that names someone, for instance) and paste the text.

Task: write a one-page brief of this document for council members who have not read it.
Document: [paste the text, personal details removed]
Output: what it is and who it is from; what we must do and by when; what it costs; what has changed (only if I paste last year's version too); three questions to ask the provider; then a list of every number, date and name in the document, quoted exactly.
Rules: use only the pasted text. Mark anything unclear as [CHECK]. Give no legal or insurance advice, and do not say whether the cover is adequate.

Made-up renewal letter, summarised. The output reads: this is the renewal notice for the church's buildings insurance, from the insurer; reply by 15 May for the policy renewing on 1 June; the premium is $1,860, up $220 from $1,640, which is 13.4%; the excess rises from $250 to $500; a new condition asks the church to keep a log of weekly fire-alarm tests. Questions: why has the premium risen by 13.4%? Is the cover limit unchanged? What evidence of the alarm log does the insurer want?

Check before the council sees it: tick every figure in the brief against the letter, using the quoted-numbers list at the end, and recompute the percentage yourself ($220 divided by $1,640 is 0.134). The brief says nothing about whether the cover is enough, and it should not; that is a question for the insurer, a broker or your wider church body. With a long PDF, ask the model to state how many pages it read and to quote the last sentence, which shows whether it reached the end. Notice how this ties back to Job 7: the new alarm-log condition belongs in the admin calendar the same week.

Job 10: A welcome email for first-time visitors, merge fields only

A message the week after someone's first visit is one of the kindest things an office can send, and easy to forget. The trick is to write a template once, with two merge fields, and let your email tool fill in the names. The visitor list itself stays out of ChatGPT.

Task: write a welcome email template for people who visited us for the first time, and a short text version.
Merge fields: [first name] and [date visited] only.
Facts: service times [...]; what to expect, in our words [...]; refreshments [...]; parking and access [...]; who to contact and when [...]; one open invitation [...]
Output: an email of about 120 words and a text of about 40 words. Warm, no pressure. Do not assume why they came or what they believe. Explain any church term in a few words. No emojis.

With the made-up facts filled in, the email comes back like this.

Subject: Good to see you on [date visited]
Hi [first name], thank you for joining us on [date visited]. It was good to have you with us. If you would like to come again, our services are at 9.30 am and 11.15 am on Sundays, with tea and coffee in the hall afterwards. A service lasts about an hour, and there are activities for children during it. For parking and access, [parking and access detail]. If you have any questions, the office is open [office days and hours] on [phone]. There is also an open invitation: come for a cup of tea after any Sunday service, with no commitment at all. [your name], [church name]

Check before it goes into your email tool: every fact in it matches reality this month, especially the line about children's activities, which belongs only if there is a rota to run them every week; if not, "most weeks" is honest. Read the tone as a stranger would, because a welcome that assumes they are searching for faith or ready to join is presumptuous. Send it only to visitors who gave their email address for this purpose when they gave it, and use your mail tool's merge feature rather than pasting any visitor details into ChatGPT.

One reader, one recount: the office habits behind all ten jobs

The same routine sits under every job. One named person reads every output before it leaves the office. Anything with numbers or dates (the rota, the agenda, the minutes, the quote comparison, the calendar) gets a second pair of eyes or a recount. Every edit you make more than twice becomes a new line in the office rules. And the rules block is reviewed each term, since staff, volunteers and tools change.

Start with Jobs 1, 2 and 7. They carry little risk, the facts are yours, and you will see the result in a day. Add 4 and 10 once you are comfortable with the rules block. Leave 6 and 9 until you have tested them on a past example whose right answer you already know: last year's minutes, last year's insurance letter. If the output matches what you filed, the prompt is ready for a live one. If it does not, you have found out cheaply.

The line stays where it started. These ten jobs exist so that the people who write sermons, lead prayers and sit with the worried have more of their week for it. A prompt that drifts into any of that, or that needs a member's name to work, has left the office, and it should come out of the set. For the shared rules on staff and volunteer use, the guide to church data rules and ChatGPT covers what member data must never go in, and the check on OpenAI's nonprofit programme explains how to find out whether a church qualifies for any discount.

Questions church offices ask about these prompts

Can ChatGPT write a sermon or a prayer for us?

It can produce text, but these prompts deliberately leave it out. Sermons, prayers and pastoral advice are the church leader's own work, and a tool that has met nobody in your congregation cannot do that job for you. This tutorial stays with the office: notices, rotas, bookings, agendas and letters.

Is it safe to paste volunteers' names and availability?

Avoid it. Use codes such as V1 to V8 in the prompt and keep the key linking codes to names in your own spreadsheet. A code is not anonymous in your hands, but ChatGPT never sees who anyone is, and in a church a name list can also reveal belief.

Does data-protection law apply when we use AI?

If you handle personal data, yes, whichever tool you use. Data-protection law such as the GDPR treats information revealing religious belief as special-category data, with extra conditions even for religious bodies. Ask your data-protection adviser or wider church body what applies to you. Keeping member data out of ChatGPT avoids most of the question.

Which ChatGPT plan does a church office need?

All ten jobs work on the free plan, which has usage limits that change. A paid personal plan such as Plus ($20 a month list price in USD) gives more room, and a Project can store your office rules. OpenAI's nonprofit rate for ChatGPT Business Standard seats is $8 a user a month billed annually, with eligibility checked by Goodstack, so check whether your church qualifies first.

Further reads

• ChatGPT Prompts for Nonprofit Organisations: 10 for Admin and Donors — The wider nonprofit version: ten prompts for admin and donor letters.
• ChatGPT for Nonprofits: Volunteer Recruitment Posts and Rota Messages — Recruitment posts and rota messages for volunteer teams.
• AI Chatbot for Churches: Weddings, Baptisms and Hall-Hire Questions — What a chatbot can answer on weddings, baptisms and hall hire.
• AI Receptionist for Churches: Office Phone Cost and Pastoral Call Rules — Office phone cover and the pastoral call rules it needs.
• AI Church Website Builder: Wix, Squarespace or GoDaddy Airo Compared — Choosing a website builder for a small congregation.
• Community Centre Volunteer Form: AI Sign-Ups and Rota Reminders — Volunteer sign-up forms and rota reminders that run themselves.
• Church Translation With AI: A Test to Run Before You Pay a Vendor — A two-evening test with a bilingual checker that shows whether AI can translate your notices, newsletters and live services, and what to ask vendors.
• AI Tools and AI Development: The Complete 2026 Guide — the AI hub, including every tutorial in the AI-for-business series.

Sources: OpenAI help pages on Projects, Temporary Chat and OpenAI for Nonprofits; the text of Article 9 of the GDPR on special categories of personal data; ChatGPT plan details from OpenAI's help pages (October 2026). All names, dates, prices and quotes in the examples are invented.