Church management

Questions to ask during a church management software demo

Don’t just watch a feature tour. Give every vendor the same sample data and tasks, score what they can actually do live, and write down every workaround, promised feature and export limit.

The Sanctuary teamSanctuary11 min read

How to run the demo

Ask the vendor to do your church’s real work live, using a small set of sample people and transactions. Don’t spend the hour watching a polished tour. Score each task from zero to three, write down every workaround and every promised feature, and ask for an export before the demo ends.

The product with the most features isn’t always the best. Look for the one that handles your critical work with the least risk and double entry, without needing special know-how or features that don’t exist yet.

Use one scorecard for every vendor

Pick the five workflows that matter most to you. Label each one critical, important or optional, and use the same scale in every demo:

  • 0: can’t do the task, or needs another product.
  • 1: possible, but only with double entry, a fragile workaround, custom development or a roadmap item they haven’t committed to.
  • 2: supported, but needs setup, training, an integration or a more expensive plan.
  • 3: done live, with sample data like yours, by the person who would own it at your church.

Multiply critical tasks by three, important tasks by two and optional tasks by one. Keep cost, migration risk, support and contract terms in their own columns. A product that fails a child safety or finance requirement shouldn’t win on an averaged feature score.

Give the vendor a small but tricky sample

Use made-up data, or carefully anonymized data, that looks like your hardest cases. Never send unprotected child, pastoral, medical, payment or donor data for a sales demo.

  • Two adults and two children in one household, with different last names and contact preferences.
  • Two people with the same name, plus one likely duplicate with an old email.
  • A guest who fills out a form twice and later becomes a volunteer.
  • A volunteer on two teams, away one weekend, who declines another request.
  • A donor whose payment email differs from the one on their household record.
  • A child with a pickup restriction, an allergy note and two authorized guardians.
  • Staff, ministry, finance, check-in and volunteer users who need different permissions.

People, households, forms and follow-up

  1. 1Import the sample people. Which fields, relationships, notes, consent records and history can’t be imported?
  2. 2Find and fix a duplicate without losing activity or giving history.
  3. 3Put people with different last names in one household. How do household messages and statements work?
  4. 4Submit a public form as an existing person. Does it update them, suggest a match or create another record?
  5. 5Create a follow-up task from that form, assign it, complete it, and show the history on the person.
  6. 6Find everyone who meets three conditions, save that list and use it without a spreadsheet export.
  7. 7Show who can see and edit sensitive notes, child details, contact information and consent.
  8. 8Export person, household, form, note, task and activity fields. Which related records or attachments are left out?

Volunteer scheduling and service planning

  1. 1Collect availability, then show that a request can’t go to someone marked away.
  2. 2Schedule one person on two teams. What warning or workload view does the leader see?
  3. 3Send a request, decline it as the volunteer, fill the open spot, and show the audit trail.
  4. 4Find everyone who hasn’t responded for Sunday and remind them, without messaging the people who already replied.
  5. 5Copy a service plan, change one week, and show that the change doesn’t rewrite the template or past services.
  6. 6Show what a volunteer can do on a phone without administrator access.
  7. 7How do training, age, qualifications or background check status limit who can be scheduled?

Giving, reconciliation and statements

  1. 1Record an online gift where the payment email doesn’t match the donor’s profile. Show how it gets matched and corrected.
  2. 2Split one gift across funds, refund it, and show the reports and donor history afterward.
  3. 3Reconcile gross gifts, processing fees, refunds and the expected deposit without fixing a spreadsheet.
  4. 4Move a gift credited to the wrong person or household, and show who can see the change.
  5. 5Generate a household statement, check how funds are handled, then correct and regenerate it.
  6. 6What happens to recurring gifts, saved payment methods, donor history and year-to-date totals during migration?
  7. 7Export transactions, funds, fees, batches, refunds, attribution and statement history in usable fields.
  8. 8List every platform, processing, subscription, messaging, statement, support and migration fee at the amount we expect to use.

Children’s check-in, attendance and safety

  1. 1Check in the sample family on the devices, printers, label sizes and network you plan to use.
  2. 2Register a new family at the station without creating duplicate adults or children.
  3. 3Show the allergy, room, capacity, guardian, pickup and custody controls that apply to your policy.
  4. 4What happens when the internet, the printer, a tablet or a volunteer’s login fails?
  5. 5Show secure check-out, a lost security code, an unauthorized pickup attempt and the audit history.
  6. 6Show that a check-in volunteer can’t browse giving, pastoral or unrelated household information.
  7. 7Export attendance and check-in history with dates, events, locations, rooms and person IDs intact.

Migration, data ownership, security and support

  1. 1Who does the migration, what formats do you accept, how many test imports are included, and what isn’t included?
  2. 2Which records can we export ourselves, in what format, and which need support or a fee?
  3. 3If we leave, who owns our data, backups, files, phone numbers, domains, processor relationship and integrations?
  4. 4How do you audit administrator actions, permission changes, exports, merges, financial corrections and views of sensitive data?
  5. 5What authentication, multifactor, backup, incident, deletion and retention controls do you have?
  6. 6Where is our data processed, which subprocessors are involved, and what agreements can we review?
  7. 7On our plan, what support channel and response time target apply if check-in or giving fails on a Sunday?
  8. 8What would need services, a partner, development work, an integration or a higher-priced tier?
  9. 9What does canceling involve, when does access end, and how long do exports stay available?

Answers that should lower the score

  • “It’s on the roadmap,” when there’s no released feature you can test.
  • “You can build a custom report,” when you need an everyday view for running things.
  • “Our implementation team handles that,” with no scope, price, sample output or owner.
  • “It integrates,” without showing which way data flows, how often, how records match, what happens when it fails, and which system owns the record.
  • “You can export your data,” without producing an export with related records and IDs that stay the same.
  • A workflow shown only from an administrator account that can do everything.
  • Security, support, pricing or cancellation promises that aren’t in written terms you can review.

Deciding after the demos

Cross off any option that fails a safety, finance, ownership or export requirement you can’t compromise on. For the rest, compare the weighted workflow score, three-year cost, migration effort, how much staff will have to change, support and contract risk. Write down why you gave each score while the demo is still fresh.

Ask the people who’ll use the system every week, and not just the buyer, which option they can rely on during a busy Sunday. Before you sign, do the most important tasks again yourselves. Get any promised exceptions, services, pricing and data terms written into the agreement.

About this guide

Sanctuary makes church management software and wrote this guide, so it isn’t an independent ranking. Use the same scorecard on Sanctuary. Ask us to show the hard cases, produce exports, explain our limits, and say clearly what works now and what’s planned. It only helps if every vendor is held to the same standard.

See how Sanctuary keeps the work connected

Sanctuary keeps people, serving and giving on the same record. Core is free, with no limit on how many people you keep in it.