Directories solve an identity and contact problem
Modern ChMS platforms do this well. Realm Profiles and Directories, for example, store contact information, family relationships, serving data, custom fields, and communication preferences. Other church systems offer similar people records.
That is foundational infrastructure. Pastors and members need to know who someone is and how to reach them.
A roster adds context, but still not the relationship itself
A small-group roster tells you who enrolled. A serving-team roster tells you who is scheduled. An event registration tells you who signed up. Those are useful forms of association.
They do not tell you whether Samantha and Camila became friends, whether a newcomer has anyone to sit with, or whether a person in a large group has no close ties inside it.
The missing object is the connection between two people
Traditional databases are person-centered: each member has a record. Relationship visibility is edge-centered: it asks what exists between records. Who knows whom? Where are the bridges? Where are the isolated nodes? Which clusters never overlap?
That is a different data problem, which is why adding more fields to the directory does not fully solve it.
Directories are still part of the solution
This is not an argument against a directory. Contact information, household data, permissions, groups, attendance, giving, and workflows belong in the ChMS. They are the operational backbone.
Relationship data becomes most useful when it complements those records rather than trying to replace them.
Privacy matters even more when relationships are involved
A member directory already requires careful permissions. A relationship map requires even more restraint. The church should avoid exposing private pastoral notes, sensitive relationship labels, or unnecessary social information to other members.
Visibility for shepherds and privacy for members must be designed as separate concerns.
Proximity adds the connection layer
Proximity is designed to sit beside the directory and show the network the directory cannot. Members find people around shared interests; shepherds see aggregate and person-level relational patterns such as zero connections and areas of isolation.
The directory answers “Who is this?” Proximity is built to help answer “Who are they connected to?”
Research basis
Realm by ACS Technologies: Profiles & Directories, groups, Shepherd pastoral care and Connect community tools.
Rock RMS: people records, groups, Connections and engagement tools.
CDC Social Connection framework: social connection includes network structure, support functions and relationship quality.