Care ministry

How to start a church prayer chain

To start a church prayer chain, name one coordinator, agree in writing what may be shared and who decides, choose how requests travel (a phone or text tree for urgent needs, or a schedule where people claim time slots to cover the hours), recruit a small group of people who will actually pray, and close every request with an update. Start small, protect people's privacy, and grow the list once the first few requests have gone well.

Most churches already have a prayer chain of some kind, even if nobody calls it that. Someone hears that a member is going into hospital, tells two friends, and by Sunday half the congregation knows and the other half feels left out. A prayer chain is simply a way of doing that on purpose: the right people hear quickly, they hear what the family is happy to share, and someone tells them how it turned out.

This guide walks through starting one from nothing, or restarting one that has drifted. It works the same whether your chain runs on phone calls, a group text or an app.

What is a church prayer chain?

A church prayer chain is a group of people who have agreed to pray when a need comes in, and a simple route for getting the need to them. The classic version is a phone tree: the coordinator calls two people, each of them calls two more, and within an hour everyone on the list has heard.

There is a second kind that many churches now use alongside it: the scheduled prayer chain. Instead of everyone praying at once, people claim a date and a time slot, so that a surgery, a night in intensive care or a day of prayer is covered hour by hour without gaps. Our glossary entry on prayer chains has the short definition.

You may want both. The tree is for "please pray now". The schedule is for "please help us cover the next twelve hours".

Step 1: name one coordinator

Every prayer chain needs one person who receives requests and sends them out. Without that, requests arrive from five directions, some get passed on twice and some never at all.

A good coordinator:

  • Is easy to reach by phone and text, including in the evening.
  • Keeps a confidence. This matters more than anything else on the list.
  • Will ask before sharing. They check with the person or family what may be passed on.
  • Follows up. They chase the update a week later and close the request.

In a small church this is often a deacon, an elder's spouse or a long-standing member of a care team. Name a backup for when the coordinator is away, and tell the church who both of them are.

Step 2: write down what gets shared, and who decides

This is the step most churches skip, and it is the one that causes the trouble later. Before the first request goes out, agree a few rules with your pastor and put them on one page:

  1. The person decides. Nothing about someone goes on the chain unless they, or a close family member when they cannot answer, have agreed. If you cannot ask, share less: "Please pray for a family in our church facing a hard diagnosis" is still a real request.
  2. Share what helps people pray, not the whole story. First name, the need in one or two sentences, and any time that matters ("surgery at 8 a.m. Thursday"). Leave out test results, family conflict and anything the person would not say from the front on Sunday.
  3. The chain is not the church. Requests go to people on the list, not to the whole congregation, unless the family asks for that.
  4. No forwarding. Members of the chain pray and may reply to the coordinator, but do not pass requests to friends, other churches or social media.
  5. Some things go to the pastor only. Abuse, crime, self-harm and anything that may need a safeguarding response goes straight to the pastor, not to the chain.

Read the page to everyone who joins and ask them to agree to it. It feels formal for a prayer list, but it protects the people you are praying for, and it protects the chain from becoming a gossip line.

Step 3: choose how requests travel

Pick the simplest route your people already use. You can change it later.

RouteGood forWatch out for
Phone treeOlder members, urgent needs, people without smartphonesMessages change as they pass along; one missed call breaks the branch
Group text or chatSpeed, reaching everyone at onceReplies pile up; details can be forwarded with one tap
Email listLonger updates, people who read email dailySlow for urgent needs; easy to miss
Scheduled time slotsCovering the hours of a surgery, vigil or day of prayerNeeds a sign-up sheet or app and someone to share it

If you use a phone tree, keep each branch short (no more than three people deep) and give the person at the end of each branch the job of calling the coordinator back to confirm the message arrived. If you use a group text, ask people to reply to the coordinator directly rather than to the whole group, so a request does not turn into forty messages of "praying!".

For a scheduled chain, the sign-up can be as simple as a sheet with one row per hour and a space for a name. Share it with the people closest to the family first, then the wider chain. A free version of this kind of sheet is part of the meal train sign-up sheet; swap meals for time slots and it works the same way.

Step 4: recruit the right people

Ask people personally rather than announcing a sign-up from the front. You are looking for people who:

  • will actually pray when they say they will,
  • can keep a confidence,
  • are reachable during the day, or are willing to say when they are not.

Eight to fifteen people is plenty to start in a small church. Include some who are home during the day (retired members are often the backbone of a prayer chain) and some who are up late. Ask each person how they want to be reached: call, text or email. Write it down.

Once the chain has carried a few requests well, invite more people. A chain that grows slowly keeps its trust.

Step 5: send a request well

A good request is short and the same shape every time. For example:

Prayer request from the church: Please pray for Margaret, who has heart surgery at 8 a.m. Thursday. She asked us to pray for the surgeons and for peace for her husband, Tom, while he waits. The coordinator will send an update on Friday. Please do not forward.

Notice what it includes: who, what, when, what to pray for in the person's own words, when the next update comes, and the reminder not to forward. Notice what it leaves out: diagnosis, hospital ward, anything Margaret did not ask to share.

For a scheduled chain, add the link or sheet and the hours you are trying to cover: "We are covering 8 a.m. to 8 p.m. Thursday in one-hour slots. Please claim one."

Step 6: close the loop

The fastest way to kill a prayer chain is to never hear how anything turned out. People stop praying for requests that seem to vanish.

Within a week, the coordinator should send a short update, again only with the person's agreement: "Margaret's surgery went well and she is home. She and Tom are grateful for your prayers." If the news is hard, say so simply and say what the family needs next. That is often the moment to start a meal train or to ask a deacon to visit.

Then close the request. Keep a simple list of open requests, and once a month go through it and close anything that has been resolved or gone quiet. Long-term needs (a chronic illness, a family member overseas) can stay open, with a fresh update every month or two.

How do you restart a prayer chain that has drifted?

If your church has a chain that nobody quite trusts any more, do not just send a new request to the old list. Start again:

  1. Name the coordinator and backup, even if they are the same people as before.
  2. Write the one-page rules from Step 2 and share them.
  3. Ask everyone on the old list whether they still want to be on it. Remove anyone who does not reply.
  4. Send the next request in the new shape, with an update promised and delivered.

Most chains that drift do so because requests stopped being closed, or because something was shared that should not have been. Fixing those two things fixes most of the rest.

Is there a simpler way than a phone tree?

A phone tree and a group text work, and for many small churches they are enough. They get harder when the chain grows past a few dozen people, when the same few people are carrying every request, or when you want to cover the hours of a long surgery without someone sitting on the phone filling gaps.

Churchory Care runs prayer chains as part of a care train for a person or family: people claim a date and time slot until the hours are covered, or you can use a simpler prayer wall. The same care train can hold a meal train with dietary notes and drop-off instructions, and a public share link lets relatives and neighbours sign up without an account. Only people whose role includes Care can see care requests, so you can give access to your coordinator and care team and no one else. Follow-ups are assigned to a named person, so "someone should check on them" becomes one person's job.

Care is $25 a month or $250 a year on its own, with a 45-day free trial and no card required, or it comes with every other product in Churchory One. Churchory Core, the free people directory every product works from, is free forever. You can see how a care train works, step by step, on the Care tour.

If your prayer chain is eight faithful people and a phone list on the fridge, keep it. It works. The tools only matter once the list outgrows the fridge.

Churchory products in this guide

Try Churchory free for 45 days

Pick only the products you need. No credit card, no contract, and help from the people who build it.

Start your free trial

Questions

Frequently asked questions

What is a church prayer chain?

A prayer chain is a group of people in a church who agree to pray when a need comes in. Traditionally it was a phone tree, where each person called the next. Many churches now also run it as a schedule, where people claim a date and time slot so the hours of a surgery or a vigil are covered without gaps.

How many people should be on a prayer chain?

Start with the people who will reliably pray and keep a confidence, often eight to fifteen in a small church. A short list of faithful people is better than a long list where nobody is sure who has heard. Add people once the chain has handled a few requests well.

Who should decide what goes on the prayer chain?

One coordinator, working with the pastor. The person the request is about, or their family, should always agree to what is shared and with whom. If you cannot ask them, share less.

How do you keep a prayer chain confidential?

Share only what the person agreed to, keep medical and family details to the minimum needed to pray, send requests to the chain rather than the whole church, and ask members not to forward them. Close each request with an update so old details do not keep circulating.

Can a church run a prayer chain in an app?

Yes. Churchory Care lets a care team run a prayer chain where people claim a date and time slot until the hours are covered, or a simpler prayer wall, alongside meal trains and follow-ups. Only people whose role includes Care can see care requests.

Who is Churchory for?

Churchory is for small and mid-size churches, and especially for the pastors, church administrators and ministry leaders who run them with a few staff and a lot of volunteers. Nothing in it assumes a full-time IT person: the kiosk, the sign-up links and the apps are built for the volunteer who was trained once and is standing at a table at 9:58 on a Sunday.

Who can see what? We have volunteers.

You decide, with roles you name yourself. Each role is a grid of 23 areas, each set to one of four levels (none, view, manage what you're assigned to, or manage everything), so a group leader can manage their own group and nothing else, and a kids volunteer never sees a giving record. Church settings and billing are administrator-only and can't be granted through a role at all.

See every question churches ask us

45 days free

Try it on a real Sunday.

Pick the products you need and they’re yours free for 45 days. Add another during the trial in one click. No credit card, no contract.

No credit cardNo contractHelp from the people who build it

Just need a directory and announcements? Start free with Core, free forever.

Start your free trial45 days free · no card