Pastoral care records and software for UK churches

Quick answer

Pastoral-care software can help a church remember a follow-up, coordinate a small authorised team and avoid losing an ordinary care request in an inbox. It should not become a general store for private conversations. Before choosing a product, agree what pastoral information may be recorded, why, who may see it, when it is reviewed and when it belongs in a safeguarding or emergency route instead. A supplier cannot provide pastoral confidentiality, safeguarding response, professional referral or data-protection obligations on the church’s behalf.

This guide is not pastoral, safeguarding, legal or data-protection advice. In a live concern, follow the church’s safeguarding procedure and relevant professional or statutory routes. Do not wait for access to a care system or use a routine pastoral note to delay a response.

Set a boundary for care records

Separate three kinds of information. First, ordinary operational information: a person asked for a call, a visit is planned, or a practical task has an owner. Second, pastoral information: a limited factual note necessary for agreed follow-up. Third, safeguarding, emergency, criminal, health or other highly sensitive material which needs the church’s specific procedure and appropriate advice. The boundary cannot be drawn by the product’s labels alone.

Church of England clergy guidance says that a person seeking pastoral counsel can expect confidential information not to be passed to third parties without consent or other lawful authority; it also says note-taking should be mutually agreed wherever possible.¹ The detail and applicability of that guidance varies by role and church tradition, but the operational lesson is sound: decide the purpose and sharing expectation before recording a note.

Write an approved statement for staff and volunteers. It should say what is not recorded, how a concern is escalated, whether a note is shared in a team, and who can seek advice. Never promise absolute confidentiality where the church’s safeguarding or legal obligations may require action.

Treat sensitivity and access as design constraints

Pastoral material can reveal religious belief, health, family circumstances, sexual orientation or other sensitive matters. The ICO lists religious belief and health among special-category data and explains that it receives additional protection.² Do not assume that a familiar church database makes every pastoral note suitable to store there.

Use the least-access model: only people with a clearly defined role should be able to create, read, correct, export or administer pastoral records. Test this with real role accounts, not a full administrator account. Ask whether access changes leave an audit record, whether a departed volunteer loses access promptly, whether exports can be restricted and whether a system administrator can read content unnecessarily.

Also reduce the data. A follow-up task may need a name, owner, due date and minimal factual context; it rarely needs a complete account of a conversation. The ICO’s data-minimisation principle requires data to be adequate, relevant and limited to what is necessary.³

Choose an operating model before comparing suppliers

There are several legitimate shapes, and they should not be compared as if they were identical:

A broad church platform may be sufficient for simple follow-up. A specialised tool may be justified for a larger, trained care team. Neither is automatically suitable for safeguarding casework. Do not use software categories as a substitute for a local policy decision.

Test a fictional care journey

Trial with invented names and a scenario that exposes the controls: a person requests a visit, the request is allocated, the original visitor becomes unavailable, the team reviews outstanding tasks, and a concern requiring escalation emerges. Check the pathway rather than trying to create a realistic private note.

1. Confirm who can create the request and the minimum data captured.
2. Allocate a follow-up without exposing it to unrelated volunteers.
3. Change the assigned role and check that the old user no longer has access.
4. Review overdue work without exporting unnecessary personal detail.
5. Test the distinct escalation route for a safeguarding concern.
6. Export a sample record and decide whether it is intelligible, proportionate and access-controlled.
7. Remove trial data and record how the supplier confirms deletion or return at contract end.

The trial should end with a decision record: the intended use, excluded uses, access owner, training requirement, review interval, retention approach and escalation contacts. If the church cannot write this clearly, it is not ready to load historic pastoral notes.

Implement with supervision, review and exit in mind

Train people in confidentiality, accurate factual notes, the boundary between pastoral and safeguarding work, and how to raise uncertainty. A polished interface does not give a volunteer authority to make a judgement or share information beyond their role. Arrange regular access reviews and a route for correction where a record is inaccurate or no longer needed.

For Church of England bodies, current records guidance directs users to a May 2026 record-retention schedule and record-keeping review process.⁴ Other churches should use the guidance and professional advice that applies to their own body. A product’s retention switch does not decide what a church must retain, archive or delete.

Plan exit before adding sensitive data. Ask for the current processor terms, a sample export, account-removal process, backups and return/deletion route. Retain only what the church is entitled and required to keep, in the appropriate controlled location.

Do not launch by importing years of unreviewed notes. Begin with the agreed live workflow, then decide case by case whether older material has a current purpose and an approved retention route. This reduces the risk that a new system simply makes historic uncertainty easier to search and share.

Software listings to explore

These directory profiles are research starting points, not endorsements or confirmation that a product is appropriate for sensitive pastoral records.

• ChurchSuite and iKnow Church are broad church-management profiles that may support limited follow-up workflows.
• ShepherdCare and ChurchBase are profiles to examine where care administration is a stated need.
• iKnow Safeguarding belongs in a separate safeguarding evaluation, not as a default pastoral-notes system.

Use the pastoral-care category together with the safeguarding category to keep that distinction visible.

Sources and research limits

This guide was researched and checked on 28 July 2026. It uses public authoritative material and does not determine a church’s lawful basis, special-category condition, retention period, safeguarding process or professional pastoral practice. Obtain appropriate denominational, safeguarding and data-protection advice before changing real records.