Product features

One confidential workspace for care that cannot live in a memory.

Epimely gives churches the care-specific records a normal church database does not: requests, plans, notes, assignments, milestones, follow-ups, and auditability shaped around pastoral privacy.

People & families

A confidential directory for people, households, milestones, and care history.

Keep member, visitor, and household records in one place without turning every personal detail into an all-staff directory. Import from Planning Center or CSV, track relationships and milestones, and keep care context attached to the person who needs it.

  • Search and filter people by status, flags, membership details, and PCO profile state.
  • Track relationships, households, birthdays, baptisms, anniversaries, and bereavements.
  • Keep care requests, forms, care plans, tasks, and notes linked to the person record.

Care requests

A queue for prayer, counseling, visits, benevolence, and follow-up needs.

Receive, document, route, and close the loop on care requests. Assigners can triage incoming needs without seeing full personal information, while care workers see only the requests assigned or granted to them.

  • Assignment-scoped queues keep care work focused by default.
  • Confidential requests are sealed and visible only to pastors and above.
  • Status changes, notes, and access decisions are recorded in the audit log.

Care plans & notes

Structured ongoing care for needs that last longer than one conversation.

Turn a request into a care plan, apply templates, set goals, assign ownership, record SOAP-structured notes, and schedule follow-up tasks so care does not depend on memory or hallway conversations.

  • Use care-plan templates for common pastoral situations.
  • Write SOAP-structured notes and author-private notes where appropriate.
  • Review open plans, goals, resources, and next follow-up dates from one record.

Groups & teams

Small groups, classes, teams, and leaders connected to care records.

Groups help care teams understand who is connected to whom. Leaders and memberships can be managed inside Epimely, and membership changes become part of the person's visible context.

  • Track group leaders, members, cadence, and ministry-team membership.
  • Use groups as care context without broadening access to unrelated private records.
  • Keep group-linked people visible to the right staff within the same tenant boundary.

Milestones & tasks

Birthdays, baptisms, bereavements, anniversaries, overdue tasks, and next steps.

Pastoral care often depends on remembering at the right time. Epimely surfaces upcoming milestones and overdue tasks so the next call, visit, card, or check-in happens when it should.

  • See upcoming milestones on the dashboard and dedicated milestones list.
  • Assign follow-up tasks with owners, due dates, and linked people or requests.
  • Use queues to find assigned people who have not had recent contact.

Planning Center import

One-way directory sync from Planning Center Online into Epimely.

Planning Center can remain the church's directory source of truth while Epimely becomes the confidential pastoral-care workspace layered on top of it.

  • Import people, campuses, contact details, relationships, and key PCO metadata.
  • Use one-way sync so Epimely never overwrites Planning Center records.
  • Link incoming requests to PCO-matched people instead of creating duplicates.

Privacy built into the workflow

Features should not widen who can see pastoral care.

Every feature sits behind the same tenant-scoped, default-deny access model. A user can have permission to open a section and still only see rows assigned or explicitly granted to them.

Read the security overview

Encrypted at rest, per church

Each church gets its own encryption key. Sensitive records -- visit notes, intake answers, contact details -- are sealed in the database, never stored as plain text.

Default-deny, not default-open

Signing in grants almost nothing. Access is decided per person -- by role, assignment, and explicit grant -- not one master key that opens everyone's file.

Sealed confidential requests

Mark a request confidential and only pastors and above can open it. It's sealed at the database -- it won't even appear in anyone else's list.

Triage without exposure

An assigner can route incoming needs while names, emails, and phone numbers are redacted to initials -- on the server, not just hidden in the page.

See the workflow with real sample data.

Open the demo church and walk through people, requests, queues, forms, plans, and follow-ups.

View pricing