Planning Center is one of the most widely used church management platforms in North America, and for good reason. It does services scheduling well, it does check-in well, it does giving well, and the People module gives a church a respectable shared database of members and households. Most churches that adopt Planning Center stay on it for years, and most of them are happy with the bulk of what they get. The one place the platform quietly stops carrying its weight, for a lot of teams, is pastoral care.
This post is about that gap. Not as a complaint about Planning Center, which is a serious tool built by people who understand churches. As an honest description of what the platform was designed to do, where the design starts to creak when you push it into care work, and how a small or mid-sized church can keep using Planning Center for everything else while adding a thin layer that finally answers the questions a deacon chair or care pastor actually needs answered.
What Planning Center Actually Gives You for Care
The relevant pieces are inside the People module. You get a household record, a contact record per person, custom fields you can configure for care-related attributes, lists you can build by query, and Workflows that can route a person through a defined sequence of steps with assigned owners. You also get Notes, which can be tagged and filtered, and which become the closest thing Planning Center offers to a contact history. For a church just trying to know who is a member and what household they belong to, this is plenty. For a care team trying to make sure no family in the congregation drifts past their attention, it starts to feel thin in predictable ways.
The thinness is not because Planning Center got pastoral care wrong. It is because Planning Center was built to be a general-purpose database that any reasonably configurable team can shape to its needs. Care work, when you do it for long enough, turns out to need a more specific shape than the general one. The shape is a coverage view by family, a contact history that survives staff turnover, a queue of overdue or at-risk households, and a set of follow-ups that hold across meetings. None of those are first-class objects in Planning Center People, and that is where the friction lives.
What Most Care Teams Try First
The first thing a care-minded team does on Planning Center is set up custom fields and start using them seriously. A field for assigned deacon. A field for last contact date. A field for care status, with values like active, watch, hospital, hospice. The team meets, agrees on the schema, and for the first two months everyone fills the fields in. The lists look right. The reports run. The chair feels like the team finally has a system.
The drift starts somewhere around month three. A new deacon joins and is not trained on the schema. A field gets renamed. A list breaks. Two members of the team start logging contacts in Notes instead of touching the fields. The last-contact date drifts because nobody remembers to update it after a phone call. By month six the data is uneven enough that the chair is no longer confident pulling a coverage report in front of the elders. The team is still doing real shepherding work. The database just stopped reflecting it accurately.
Why the Workflows Module Almost Helps
Workflows is the part of Planning Center that gets the closest to pastoral care without quite landing. A workflow defines a sequence of steps, each with an assigned owner, and routes a person through the steps with reminders and a queue. For new member onboarding, baptism follow-up, and visitor connection paths, it works very well. For ongoing pastoral care, it works for the first iteration of a relationship and then runs out of room.
The reason is that pastoral care is not a finite workflow with a defined end. A deacon does not finish his assigned families. The relationship continues indefinitely, the contact rhythm needs to repeat without forcing the family into a new workflow card every quarter, and the history of contacts needs to accumulate in one place that the next deacon can read in five minutes when the assignment changes. Workflows can be coerced into doing this, but the team ends up rebuilding the same workflow every few months and copying notes across cards by hand. The work the platform was supposed to save them ends up consuming the evening it was supposed to give back.
The Coverage Question Planning Center Cannot Answer
The single question that exposes the gap fastest is the coverage question. On a given Sunday, can a deacon chair or care pastor open Planning Center, look at a single view, and see which families in the congregation have not been contacted by anyone on the care team in the last sixty or ninety days. Almost no Planning Center installation can answer that question without a series of list filters, manual exports, and at least one careful piece of mental arithmetic. The data is technically in there. The view is not.
That matters because the coverage question is the one that catches drift before it becomes loss. A family that has not been contacted in ninety days is rarely in active crisis. They are just becoming invisible. The team that sees that family before a fourth missed Sunday gets a chance to do something small and timely. The team that does not see them until the family has fully disappeared spends six months trying to repair a relationship that could have been protected with a fifteen-minute phone call in week ten. The back door audit walks through that pattern in more detail if you want a closer look at how it shows up in a typical congregation.
Where the Notes System Quietly Slips
Notes in Planning Center are good for what they were designed for, which is recording information about a person on their profile. They are not built to be a contact log read across a care team. There is no clean way to see, in one screen, the last five contacts across an entire assigned-family list. There is no notion of an overdue contact based on the gap since the last note. There is no easy way to filter Notes by care status across a household rather than just a person. Teams that try to use Notes as the pastoral care log usually end up with a record that is technically complete and practically unreadable.
The deeper problem is that the people most likely to be reading and updating those notes are part-time, unpaid, and not particularly inclined to learn the filters and views needed to make Notes function as a care log. A deacon wants to log a phone call in ten seconds while he is walking back to his car. He does not want to scroll a profile, click into Notes, choose a category, and type a paragraph that nobody will ever read in context. The tool does not match the moment. The contact goes unrecorded. The history thins out a little more each week.
How Teams Bridge the Gap Without Leaving Planning Center
The pragmatic answer for most churches is not to leave Planning Center. The platform still handles services, check-in, giving, and the membership database better than any care-specific tool would. The right move is to keep Planning Center as the source of truth for who is in the church, and to add a thin layer on top that handles the care-specific job. The care layer reads the household and member list from Planning Center, lets the team make family assignments, captures contacts in seconds from a phone, surfaces overdue families, and gives the board a coverage view it can rely on.
That layer is not a replacement. It is an addition shaped specifically for the care job. The team still opens Planning Center for everything else. They open the care tool when they need to know who has slipped through the gaps, when a deacon wants to log a visit, and when the board wants the coverage picture. Pairing a general-purpose ChMS with a focused care tool tends to work better than trying to make one platform do both jobs.
What a Care Layer Should Actually Do
A care layer worth adding to Planning Center has a short list of jobs. It should treat the family or household as the primary unit, because most pastoral care is carried at the household level rather than the individual one. It should let the team make and adjust assignments quickly, including reassigning a family when a deacon rotates off the board. It should let any team member log a contact from a phone in well under a minute. It should expose a coverage view that opens to the overdue families instead of making the chair go looking for them. And it should keep an open follow-up queue that survives the gap between meetings so the team is not retracing the same conversations every month.
What it should not do is try to replace Planning Center. It should not duplicate the giving record. It should not become the membership database. It should not chase services planning or check-in. The discipline of staying inside the care slice is what keeps the tool light enough for a small team of volunteers to actually use. The moment a care tool starts adding general ChMS features, it stops being the thing that loads in five seconds on a phone while a deacon is sitting in his car after a visit.
The Honest Question for a Planning Center Church
The question for a church already on Planning Center is not whether the platform is good. The platform is good. The question is whether the care team can currently answer, in under thirty seconds, which families in the congregation have not been contacted in the last ninety days. If the answer is yes, the existing setup is working and there is no reason to add a tool. If the answer is no, and the chair has been promising herself for six months that the team will finally fix the schema and rebuild the lists, the right move is probably to stop trying to fix Planning Center for a job it was not built for and add a small care layer alongside it. A short comparison of the main pastoral care options can help frame the choice if you want to look at more than one.
What This Looks Like in OurChurchCare
OurChurchCare was built to sit beside the church management system rather than replace it. For a Planning Center church, that usually means importing the household and member list once, making the family assignments in OurChurchCare, and then letting the care team log contacts and follow-ups in the tool while Planning Center keeps handling services, giving, and the general membership record. The home screen opens to the families ordered by who is overdue or drifting. Tapping a household shows the assigned shepherd, recent contact history, any open follow-ups, and a single button to log a new contact in under thirty seconds from a phone.
Pricing is flat, the trial does not require a credit card, and the tool intentionally stays inside its slice of pastoral work. If your team has been trying to make Planning Center carry the care job and the data is no longer giving you an honest coverage picture, start a free OurChurchCare trial. Import your member list, make your assignments, and watch the coverage view build itself over the next few weeks of normal shepherding. Planning Center keeps doing what it does well, and the care job finally has a home shaped for it.