Expert guide

Church Membership Database in Microsoft Access

Know your people: households, attendance, groups, volunteers and giving in one place

Short answer: structure the database around People linked to Households, with separate tables for Attendance (per person per service or group meeting), Groups and memberships, Volunteer roles and rotas, Pastoral care (restricted access) and Giving. Reports then give attendance trends, people who have stopped attending, volunteer schedules, and year-end giving statements. We build these as custom Access databases for churches and community organisations.

Many churches keep members in one spreadsheet, the rota in another, attendance on paper and giving in the treasurer's workbook. Nobody can easily answer "who used to come every week and has not been seen for a month?" or "which families have children in the youth group and are not on the newsletter list?". A single Access database answers those questions while respecting that some information, particularly pastoral care notes, must stay private.

The Tables

TableKey fieldsNotes
tblHouseholdsHouseholdID, MailingName, Address, PhoneOne per family or address
tblPeoplePersonID, HouseholdID, Name, Role in household, DOB, Email, Mobile, MemberStatus, JoinedOnOne per individual
tblServicesServiceID, Date, Type (Sunday AM, Midweek, Youth, Event)Each gathering
tblAttendanceServiceID, PersonIDOne row per person present
tblGroups / tblGroupMembersGroup, Leader, MeetingDay; PersonID, Role, JoinedOnSmall groups, choirs, ministries
tblVolunteerRoles / tblRotaRole; Date, Role, PersonIDWho serves when
tblPastoralPersonID, Date, Type, Note, RecordedByRestricted access
tblGiftsPersonID or HouseholdID, Date, Amount, Fund, MethodTreasurer access

Fast Attendance Entry

  • A check-in form listing regular attenders with tick boxes, filtered by service type.

  • A search box to add visitors, creating a new person and household in one step.

  • Headcount-only option for large services, with named attendance for groups and children's ministry.

  • Children's check-in with guardian and allergy notes visible to leaders only.

The Most Useful Report: Who Has Drifted?

qryRegularsNotSeen:
SELECT p.PersonID, p.Name, p.Mobile, Max(s.ServiceDate) AS LastSeen,
       Count(a.ServiceID) AS VisitsLast6Months
FROM (tblPeople AS p
      INNER JOIN tblAttendance AS a ON p.PersonID = a.PersonID)
      INNER JOIN tblServices AS s ON a.ServiceID = s.ServiceID
WHERE s.ServiceDate >= DateAdd("m", -6, Date())
GROUP BY p.PersonID, p.Name, p.Mobile
HAVING Count(a.ServiceID) >= 10
   AND Max(s.ServiceDate) < Date() - 35
ORDER BY Max(s.ServiceDate);

People who attended at least ten times in six months but not in the last five weeks. Share the list with pastoral leaders weekly; a phone call from someone who noticed means a great deal.

Other Reports Leaders Ask For

ReportPurpose
Attendance trend by serviceAverage per month, year over year
First-time visitors and returnsHow many visitors came back within six weeks
Group participationMembers not in any small group
Volunteer coverageRota gaps in the next eight weeks, people serving too often
Birthdays and anniversariesPastoral and welcome team prompts
Giving statementsAnnual statement per donor

Volunteer Rotas

Store availability and preferred frequency per volunteer, then build the rota as rows of date, role and person. A query flags gaps and people scheduled more often than they asked. A report per volunteer, emailed monthly, reduces the "I didn't know I was on" problem.

Emailing personalised schedules from Access is shown in sending email from Access with Outlook VBA.

Privacy and Permissions

  • Split the database and give different front ends to the office, pastoral team and treasurer.

  • Keep pastoral notes and giving in tables only certain front ends can open, or in a separate back end with restricted folder permissions.

  • Record consent and contact preferences, and respect them in every mailing query.

  • Store children's data minimally, and follow your safeguarding policy.

  • Back up regularly and keep backups secure.

Where AI Can Help a Church Office

  • Drafting welcome messages to first-time visitors from the check-in details.

  • Summarising volunteer availability replies into the rota format.

  • Writing the weekly notices from a list of events.

Personal and pastoral information should not be sent to public AI tools; keep AI use to drafting and administrative text, or consider a private local model. The giving side shares much with our nonprofit donor tracking guide, and the attendance structure with school attendance tracking.

FAQ

Church membership database FAQ

People, attendance, groups and giving

Yes. Access is a practical choice for churches and faith communities that want to track members and households, attendance, groups and ministries, volunteers, pastoral care and giving without a monthly church management subscription, especially when a volunteer or staff member is comfortable with Office.

Individuals linked into households, membership status and key dates, contact preferences, attendance at services and groups, ministry and volunteer roles, pastoral care notes with restricted access, and giving with year-end statements. Keep sensitive pastoral notes in a separate table with limited access.

Use a Households table for shared address and mailing name, and a People table where each person has a HouseholdID and a role (head, spouse, child, other). Mailings go to households; attendance, groups and volunteering are recorded per person.

Record attendance per person per service or group, then run a weekly query listing regular attenders who have not attended in the last four to six weeks. That list gives pastoral teams a gentle prompt to reach out.

Yes. With gifts stored per person or household, a report produces annual giving statements for each donor, which can be printed or saved as PDFs and emailed. Statement wording should follow the requirements that apply in your country.