Church pastoral platform
Tend helps leaders notice who is drifting, while giving members a simple way to ask for support before they slip through the gaps.
"In scaling churches, pastoral connection is too often gated by personality and initiative rather than genuine need or access."
Core design insight behind Tend
What Tend does
Tend surfaces the pastoral relationships that need attention before people slip through the gaps. It gives leaders and members the right tools to act on what they see.
Separate experiences for pastoral leaders and church members, built around what each side actually needs. Both people in a pastoral relationship have a place in the platform.
Automatic prompts at weeks 3, 6, and 10 of no contact mean no one goes unseen, even in a church of hundreds across multiple sites.
Leaders log pastoral notes privately. Status signals are visible only to the pastor who logged them and the senior pastor. Members never see their own status.
Designed for churches with multiple sites and layers of pastoral structure. Role permissions mean the right people see the right information across every site.
All conversations stay inside Tend's permission structure. Leaders can reach out naturally. Members can start a conversation without having to find a WhatsApp number first.
Health scoring is built from signals that people log themselves. No GPS. No passive tracking. The dignity of every member is built into how the system works.
Built for both
Whether you're a pastor overseeing a congregation or a member trying to find your footing, Tend is built around where you actually are.
A pastoral dashboard that gives you visibility over the people in your care, flags who needs attention, and makes it easy to act before someone quietly disappears.
A welcoming space for members to find out who their pastoral team is, request a conversation, and stay connected without having to know the right people first.
The member side
One of the clearest findings from primary research was that people don't always know how to initiate contact with a pastor. Especially when they're new. Especially when they're going through something.
The meeting request screen removes that barrier. A member can say what's on their mind, suggest a time, and add a short note, without having to track down a phone number or work out who the right person even is.
The options are deliberately gentle. "Just want to catch up" sits alongside "I'm going through something." There is no wrong answer and no pressure attached.
Member surveys showed that people who didn't feel connected often cited not knowing how to initiate contact with a leader as one of the main reasons. The problem wasn't a lack of care on either side. It was a missing mechanism.
Pastoral observation
Tend gives leaders a simple, private way to note where each person is without that information going anywhere it shouldn't.
Observation notes are only ever visible to the pastor who logged them and the senior pastor. They shape how someone is cared for. They don't become a data dashboard.
Engaged, connected and flourishing. Keep up regular check-ins and celebrate what's going well.
Some signs of drift or difficulty. Gentle proactive contact is worth making soon.
A real pastoral need has been identified. Direct contact and active support should be prioritised.
Observation statuses are only ever visible to the pastor who logged them and the senior pastor. Members never see their own status.
The nudge system
Tend tracks how long it's been since a leader made contact with someone, and prompts them before absence becomes something harder to reverse.
A gentle prompt appears in the leader's dashboard. A soft check-in is suggested.
The nudge returns with more weight. The leader is encouraged to reach out directly.
After ten weeks of silence, the senior pastor is also notified and a priority flag is set.
A logged interaction clears the nudge. Pastoral care continues with full context preserved.
Messaging in Tend
This is what the nudge system leads to. Gemma saw Marcus flagged after six weeks of no contact. She reached out through Tend. He replied. A coffee is being arranged.
That conversation happened inside a closed platform with proper permissions in place. Not a WhatsApp group. Not an email thread. A secure space where the context was already there before the first message was sent: six weeks without contact, keep an eye on, Penarth.
Prototype
The prototype covers both core journeys end to end: a leader noticing pastoral drift and acting on a nudge, and a member requesting support through the app for the first time.
Why Tend exists
A friend from church mentioned she had never spoken to the senior pastor. She had been attending for over a year, serving visibly every week, known by the people around her. But not by leadership.
That was not a criticism of anyone's care. It was a structural problem. If someone that visible could remain unknown to senior leaders for that long, the system for connection clearly was not working. Not for her, and likely not for a lot of other people too.
Tend is the response to that moment. Not an app for people who can already work the room, but a platform built for the people who currently get missed.
"If you have no way of connecting in the first place, you'll slip the net."
Core insight, Tend project logbook
Getting known at church still depends too heavily on confidence, extroversion and being willing to put yourself forward. People who are new, introverted, or going through a hard time are the ones most likely to fall through the gaps.
Tend makes pastoral care structural rather than personal, so people don't have to be bold or lucky to be known by their church.
A growing context
Christianity is not declining globally. It is growing faster than the world's population. That growth creates a real problem: the bigger a church gets, the harder it becomes for leadership to maintain genuine relational visibility over the people in their care.
Growing churches face a real tension. The bigger they get, the harder it becomes to notice who's drifting. Pastoral intent doesn't diminish with scale, but pastoral visibility does. Tend exists to restore that visibility through design rather than relying on effort alone.
Designed for privacy
Most churches use consumer messaging apps for sensitive pastoral conversations. That is not just a UX problem. It is a legal one. Under UK GDPR, church congregation data is classified as Special Category data because religious affiliation can be inferred from membership. That means it requires stricter handling, controlled access and documented consent. Tend is designed around that standard from day one.
UK GDPR note: Church congregation data is Special Category personal data because religious affiliation can be inferred from membership. It must be handled with higher security, stricter access controls and explicit consent. Consumer messaging apps were never designed with this in mind. Sources: ICO (2024); Parish Resources GDPR Guide (2023); Baptist Union Data Protection FAQs (2026).
Built on evidence
Tend was not designed from assumptions. Every feature decision traces back to primary and secondary research across pastoral leaders, church members and the wider church technology market.
Two pastoral talks from the Discipleship Pastor and Spiritual Life Pastor at VCC Penarth were analysed for how the church naturally talks about care, community and belonging. Because these talks were not produced for the project, they offered a more natural view of how pastoral care is already understood inside the church. They shaped the tone, architecture and privacy model of Tend.
Separate Qualtrics surveys for pastoral leaders and church members mapped how connection currently happens, where it breaks down, and what both groups actually need. The findings validated the nudge system, the two-sided model and the GDPR requirement.
Research across ChurchSuite, Planning Center, Breeze, Elvanto, TouchPoint, Notebird and CareNote confirmed that no existing platform combines leader visibility with a designed member experience in one system. That gap is where Tend sits.
Integration layer
Tend is designed to sit alongside the tools churches already use. ChurchSuite handles rotas, giving and events. Tend handles the pastoral relationship layer that sits on top of all of that.
Churches may ask, "why not just use ChurchSuite?" The answer is that ChurchSuite was built to organise church operations. Tend was built to help leaders notice, follow up, and genuinely know the people in their care. The two are not competing. They are doing different jobs.
Rotas, giving, events, attendance records and church admin. The operational backbone.
Service planning, volunteer scheduling and team communication. The production layer.
Pastoral relationships, connection health, nudge escalation and member access. The care layer.
Where Tend sits
Church Management Software handles rotas, giving and events. Pastor side PRM tools help leaders track care. Neither has a designed experience for the member. That is the gap Tend fills.
Church Management Software
The Care Layer
Pastoral Relationship Management
This positioning shaped three core design decisions.