The Bible study group manager nobody asked for (until they did)

Last February, we got a message from a campus ministry leader at a Russell Group university. She was managing four separate Bible study groups across her campus using a shared Google Sheet, a WhatsApp group chat, and three separate prayer request documents. 'I spend more time herding information,' she wrote, 'than I do actually leading.'

The spreadsheet problem

When we first started building Campus Fellowship, we focused on the obvious gaps: a calendar where students could find events without asking their mate on the group chat. A prayer board so you didn't feel alone at 2am on a Tuesday. A member directory so newcomers could actually find someone to sit with.

What we didn't anticipate was the administrative chaos beneath the surface.

Student-led Christian Unions and campus ministries operate differently from traditional churches. They're flatter. Decisions are made fast. A Bible study might meet in three different rooms depending on the week. Leaders rotate. Sign-ups happen the day before. And every leader we spoke to was essentially running their own custom system, cobbled together from whatever apps happened to be available.

One group at a London university was using a shared document to track which students had led which studies. Another was sending attendance lists via email because they needed a record for their chaplaincy report. A third had simply given up and was doing everything from memory, which meant when the main leader graduated, half the institutional knowledge left with them.

Why generic church software doesn't fit

We looked at what was already out there. General church management platforms exist. They're built for parishes with budgets and paid staff and a physical building that doesn't change location. They're built for 9am Sunday services and evening rotas and fundraising drives.

None of them understood that a campus ministry might have a weekly Bible study on Tuesday night, a prayer group on Wednesday morning, a social event on Thursday, and a larger gathering on Sunday afternoon. That leaders graduate every year. That attendance is genuinely unpredictable because exams happen. That everything runs on volunteer energy and the willingness of students who have essays due next week.

The feature request that stuck with us came from a chaplaincy coordinator at a Cambridge college. She needed to see across multiple student-led groups on the same campus without controlling them. She needed leaders to be able to manage their own studies without her stepping in every week. But she also needed basic visibility: which groups existed, who was leading them, how many students were actually engaging.

That's when we realised we weren't building a church app. We were building a coordination tool for a uniquely decentralised, student-centred form of Christian community.

What actually got built

The Bible study group manager ended up being simpler than we expected, which is usually a sign we got the design right.

A leader can create a study, set the passage they're covering, pick when and where it happens. Students can see it on the calendar and sign up. Attendance tracking is optional, but it's there for leaders who need to report back to their chaplaincy or keep records as the leadership team changes hands.

What made the difference was the cross-campus visibility. On a big campus, a student might not realise there are three different Bible study groups running. With Campus Fellowship, they see all of them. Leaders can see what other groups are doing without any of the proprietary control that would exist in a traditional hierarchical church structure.

We also built it so that groups can run entirely without signing in. A lot of campus ministries are already stretched. They didn't want another password requirement. So if a leader wants to share a public link, students can show up and find out where the study is, what's being covered, and whether there's space for them.

The thing we didn't expect

Once we launched it, something unexpected happened. Leaders started using it to pass the baton.

A third-year at Edinburgh who'd been leading a study group for two years suddenly had a structured way to document what she'd been doing, which passages they'd covered, how the group worked. When she stepped down, the incoming leader could actually see the continuity. No institutional knowledge loss. No starting from scratch.

One group message we received was from a student who found three different Bible studies on her campus through the app and chose one. 'I wouldn't have known they existed otherwise,' she said. 'I would have assumed my college just didn't have one.'

That's closer to what we were hoping for than any number of sign-ups or feature adoption rates.

Who this is actually for

The Bible study group manager matters most to student-led faith societies and campus ministries that are growing beyond the point where WhatsApp and memory can hold everything together. If you're running two or three groups on a campus, it probably feels like overkill. If you're running five, or if you're a chaplaincy trying to stay connected to multiple student-led initiatives, or if you're a campus ministry with real governance responsibilities, it's the thing that lets you actually scale without hiring more staff.

Free for student-led groups; we offer a premium tier for larger campus ministries that need cross-group visibility and reporting. Because scaling a volunteer organisation shouldn't require a budget overhaul.

We built Campus Fellowship to solve the problem of students not being able to find their faith community on campus. The Bible study group manager solved a different problem: how that community doesn't fall apart when people graduate. Which problem is keeping your leaders up at night?

Want to try Campus Fellowship?

Visit Campus Fellowship →