Growth changes the information problem
In a small church, leaders often know informally who is new, who is grieving, who has stopped coming, and who seems alone. Growth breaks that informal system. More people, more services, more groups, and more staff mean that important context becomes distributed across many relationships.
The answer cannot simply be “the pastor should know everyone.” Healthy pastoral care at scale requires a team and a way to surface where attention may be useful.
A ChMS organizes care work very well
Modern church management systems can assign follow-up, manage prayer requests, track attendance, store notes, create workflows, and route tasks to the right person. Rock RMS, Planning Center, Realm, and similar platforms are built to coordinate those operational processes.
That is indispensable. The limitation is not that these systems fail. It is that a workflow usually begins after someone or something has already been identified.
Relational visibility can help leaders notice earlier
A relational view asks different questions: Who appears to have no known connections? Which newcomers are still peripheral? Where are new communities forming? Is one ministry team carrying all of a person’s church relationships?
Those patterns can help a care team decide where a personal conversation might matter. They should never be treated as diagnoses. They are simply better prompts.
Privacy is part of pastoral care, not a competing value
More data is not always better. Private messages, confidential counseling notes, spiritual struggles, and personal disclosures do not need to be harvested to create useful relational visibility. In fact, collecting too much can undermine trust.
A healthy system should surface only what leaders need to ask better questions while leaving private conversations private. “Visibility for shepherds. Privacy for sheep.” is not just a slogan; it is a design constraint.
Pastoral care should remain human
A dashboard cannot pray with someone, sit at a hospital bed, make an introduction after worship, or notice the tone in a person’s voice. Technology is most useful when it gets the right human being into the right conversation sooner.
The standard should therefore be whether the system helps leaders act with greater attentiveness and context—not whether it produces more alerts.
Where Proximity fits
Proximity is a relational layer beside the ChMS. It can give authorized leaders a picture of connection health, zero-connection members, communities forming, and follow-up priorities without replacing the care workflows already in place.
That division of labor matters. Let the ChMS remain the operational system of record. Use Proximity to answer the narrower pastoral question: where might relational attention be needed?
Research basis
Rock RMS: church-management features include people management, attendance, prayer, workflows, communications, groups and connection processes.
CDC: social connection includes network size, diversity, support functions and relationship quality.
Barna Group (2025): relational connection is a meaningful part of church engagement and discipleship community.
This guide applies those findings to pastoral workflow design; it does not claim that software can diagnose spiritual or mental-health conditions.