Service Tracker

Turning weekly services across three congregations into data that can be reviewed and compared.

Web In progress

Discuss this project

The Problem

Sabbath services and holy days were happening every week in Lagos, Benin and Owerri, but the information lived in scattered notes: who attended, who served, what changed, and what needed follow-up. Without a tracker, patterns were hard to see and decisions were based on memory instead of data.

The Solution

I built a Service Tracker that lets each congregation log services over time and quickly see what's happening: not just "we had a service", but who was there, who served in which role, and who needs a follow-up.

Structured records for Sabbath services, midweek services, prayer meetings and feasts.
Attendance, service roles and follow-ups attached to each service.
A Reports page to compare the three congregations.
Regional overseers see everything; congregation admins see only their own.

What I Focused On

The core of the system is clarity: a clean interface, obvious actions, and the right data in front of the right person, with no unnecessary complexity for people who just want to log what happened.

A global query scope plus policies, so a congregation admin can never see another congregation by accident.
Holy-day awareness: during the Feast of Tabernacles every congregation becomes visible, read only.
CSV exports and an attendance chart, built on a clean data model.
Demo mode with one-click role sign-in and an hourly reset.

Outcome

Instead of losing history in chats and paper, services are now tracked over time, making it easier to see who is active, how attendance is trending, and where support is needed.