A panel built around one week of a congregation, not around a feature list. The Sunday roster with who is serving where, a people directory, prayer requests that someone has to actually answer, and giving. Self-initiated and navigable, deliberately small.
01 / THE PROBLEM
Software for volunteers is not software for staff.
A congregation runs on people who are not paid to use your system. They open it on a phone, on Saturday night, once a week. Any tool built with the density of a corporate admin panel simply goes unused, and the roster goes back to a group chat.
The common failure is scope: a product that tries to do twenty things and does none of them well enough for a volunteer to bother. I built this one on the opposite bet.
02 / THE APPROACH
The home screen is next Sunday.
The panel opens on a date, not on a menu. Whoever arrives sees the coming Sunday, who is serving in each position, and what is still uncovered — the single question that matters on a Saturday.
Prayer requests get their own place because they are the part that is easiest to build and easiest to get wrong: a request with nobody assigned is worse than no feature at all. Here each one carries who picked it up.
03 / THE BUILD
Roster, people, requests, giving. Nothing else.
Roster by position. Each Sunday slot shows the person or the gap. Gaps are the interface's job to make loud.
People directory. Contact and what each person serves in — enough to fill a gap with two taps.
Requests with an owner. Every request shows who is on it, which is what stops the list from becoming a graveyard.
Giving. Contribution with PIX, because that is how it actually arrives in Brazil.
Four areas, done fully. The restraint is the design decision, and it is the one that would make it get used.
Screens
5
Built around
1 week
File
1 HTML
