How to keep track of church prayer requests

It is Tuesday, and the church office is trying to reconstruct what was prayed for on Sunday.

The requests came in through five doors. One on a card dropped in the offering basket. One as a text to the pastor's personal number at eleven at night. One as a comment under the announcement post, three replies deep. Two names in the margin of a service sheet now in a bag in the back of a car. And one said out loud in the meeting, remembered afterwards by four people in four different versions.

None of that is neglect; it is what happens when a church collects something important without deciding where it goes. And prayer is the easiest thing in the world to collect carelessly, because asking for it is an act of trust and nobody wants to answer trust with a form.

What actually breaks

The list becomes a graveyard. A prayer list that is never cleared is read once and then skimmed forever. By month three it carries a surgery that went fine in March, a job search that ended in April, and a marriage nobody is sure is still in difficulty. The stale entries are not clutter; they teach the reader that none of it is current.

The person who asked never hears anything. They put something frightening into the church's hands, and then silence. They do not need a report; they need to know it did not vanish.

And the request is sitting wherever it happened to land. A basket, a phone, a thread — not one of them chosen as the place to keep something sensitive. Nobody decided who could see it, whether it could be asked without a name on it, or when it would be cleared.

The part that is not a software problem

A prayer request is usually two sensitive things at once. Under EU data protection law, processing personal data revealing "religious or philosophical beliefs" is prohibited, and so is processing "data concerning health" — both sit in the same list in Article 9(1) of Regulation (EU) 2016/679. A request about a diagnosis is both at once.

Article 9(2) sets out conditions that lift the prohibition, and two describe exactly what a church is doing. Point (a) is the data subject's "explicit consent to the processing of those personal data for one or more specified purposes." Point (d) covers a not-for-profit body "with a political, philosophical, religious or trade union aim," processing "in the course of its legitimate activities with appropriate safeguards," about its own members, former members, or people in regular contact with it — on the condition that the data are not disclosed outside that body without consent.

That last condition is the one a public post fails, and it fails it instantly.

The same regulation names a second principle worth borrowing anywhere. Article 5(1)(e), "storage limitation," requires personal data to be "kept in a form which permits identification of data subjects for no longer than is necessary for the purposes for which the personal data are processed."

A church outside the EU and UK is not bound by either article, but together they are the clearest short statement of careful handling: ask before you collect, keep it inside the body, do not keep it longer than needed. (Both read 22 October 2026 — Article 9 and Article 5.)

A checklist for your church, whatever you run it on

1. Decide who can see a request before you collect one. The answer can be "the whole congregation" — it just has to be a decision somebody made and can say out loud.
2. Give people a way to ask without their name on it. Some of the most urgent requests in any church will never be made otherwise.
3. Set a retention period, and say it before they post. Thirty days is a reasonable default. Telling people in advance makes clearing the list an act of care rather than a deletion.
4. Close the loop. Some signal back to the person who asked that others actually prayed. A number is enough; silence is the one answer that does damage.
5. Keep the detail out of anything public. "Pray for the Mensah family this week" carries the request. The diagnosis does not need to travel with it.
6. One place, not five. The doors in the opening paragraph are the problem; any single place beats four good ones.

None of that requires software, and a church that does only it is already ahead of most.

What this looks like inside Harvest

Harvest's prayer wall is on every plan, including Forever Free — the unpriced bottom of the ladder.

Members post from a 200-character share bar, as themselves or as Anonymous. Others pray with one tap; the count is live and can be toggled back off. Requests can be filtered by Today, This Week or This Month. A member can delete their own request at any time, and an admin can delete any request.

And every request carries a 30-day expiry from the moment it is posted — stated up front, before anyone writes anything. That is the checklist's third point built into the product rather than left to somebody's discipline: the wall stays current because it clears itself, and nobody is surprised when it does.

Why it belongs where your member list already is

Consider what gets assembled instead: a prayer-wall app or a group chat for the requests, a church management system for the member list, a separate giving tool behind the donation page. Three subscriptions, three member lists drifting apart from the day they were set up, and — the part that quietly decides whether any of it gets used — a new login issued to every member for each one.

A prayer wall punishes that worst: it only works if ordinary members open it on a Thursday, and one more password is exactly the friction it cannot survive. Which is also the problem with anything resting on one determined person.

In Harvest, the wall is a tab in the app your people already have. The same app carries the Bible and the mobile app on every plan including Forever Free; courses on every plan; the community feed, the donation page and the member record in the CRM from Church up; and QR check-in on Ministry. One member record, not three lists.

Church, the first paid plan, is $30/mo, or $300/yr — two months free, which the pricing page shows as $25/mo, billed as $300 every 12 months. Harvest's fee on donations is 0% on both paid plans; it takes no cut of a gift. What a church's own payment provider charges is a matter between the church and that provider, under its agreement with them — what you pay Harvest is the subscription, and nothing else.

What a church is actually buying is not a prayer wall. It is one subscription, one member record, one login — and a Tuesday where somebody can still tell you what the church prayed for. The full ladder, free tier included, is on the pricing page.