The calendar nobody asked for (until they did)

The problem was hidden in plain sight

When we first started talking to campus Christian Unions and student-led fellowships, we asked what they needed. 'Somewhere to post events,' they said. 'A way to let people know what's happening.' Standard stuff. We built that. But what we missed was the chaos underneath.

Campus fellowship is a strange thing to organise. You've got students juggling lectures, work, and a dozen other societies. People commit enthusiastically on Tuesday, then realise on Thursday they have an exam. Someone brings a friend. A venue changes. You need to know who's actually coming so you can book the right space, plan prayer, prepare for prayer requests. But the infrastructure for tracking that at a student level was everywhere and nowhere. A few people checking WhatsApp. The treasurer keeping a mental count. Someone writing numbers on a whiteboard.

The RSVP problem wasn't really a problem with RSVPs at all. It was a problem with friction. Every extra step (switching apps, sending a message, finding the right group chat) meant fewer people confirmed. Fewer confirmations meant worse planning. Worse planning meant worse events.

How we actually built it

When we set out to design the event calendar and RSVP system, we didn't start with a list of features we wanted to build. We started with real weeks in the life of real student leaders. One of them, Tom from a Cambridge fellowship, walked me through his Thursday. He'd post an event in the morning. By lunchtime, half a dozen people would RSVP via whatever channel was easiest for them. Some replied on Instagram. One person texted him. Two filled in a form he'd shared. He had to synthesise all that into a single answer: how many chairs do we need?

So we built RSVP to live right there in the app where students already are when they see an event. No extra step. You see something happening. You tap Yes, Maybe, or No. The numbers update in real time for whoever's running the event. Simple.

But here's what we didn't anticipate: students started using the calendar differently once RSVP was baked in. They began planning events further ahead. They started creating repeating Bible study schedules instead of posting one-off announcements. Small groups told us they were less anxious about turnout because they had real data, not guesswork. Someone at a large campus ministry said that being able to see which events were undersold and which were overbooked helped them think about what their community actually wanted to do.

The thing that surprised us most

What we didn't expect was how much the RSVP feature would change community discovery on campus.

When you can see an event and know how many people are going, and those people are other students from your campus, something shifts psychologically. You're not just joining an event. You're joining a room. You can see it has momentum. You can see who else is thinking about showing up.

A prayer group at Imperial told us that once they started using the RSVP calendar, they had more first-time visitors. Why? Because new students could see the event listed with real numbers. Not 'come to prayer group', but 'come to prayer group, and there's already eight people going'. That social proof matters, especially when you're new on campus and aren't sure if a society is actually active or just a dead entry in the student directory.

We also built member directories and cross-society discovery into Campus Fellowship because campus ministries operate as networks. You might be in one Christian Union, but there are five other prayer groups and Bible studies on your campus. The RSVP calendar works better when students can see the full calendar of events happening around them, not just their own group's events.

What it looks like now

The event calendar in Campus Fellowship is deliberately minimal. You see what's happening, when it's happening, where it is (if the organiser wants to share that), and whether there are spaces left. You can RSVP. You can see who else has said yes. You get a notification reminder if you want one. That's it. No required registration. No dark patterns.

For the person running the fellowship, there's a bit more. You can see confirmed numbers, maybes, and no-shows. You can edit an event if plans change. You can set capacity limits if you need them. For larger campus ministries running multiple groups across a university, you get visibility into what's happening across all your teams.

Some groups use it for weekly Bible studies. Some use it for one-off prayer meetings. One campus ministry uses it to schedule their monthly outreach events and track which students are interested in bringing mates. A chaplaincy we work with uses it to coordinate events between four different faith societies. The calendar doesn't care. It's flexible enough to work for however students actually organise their faith life on campus.

Why this still matters

I think a lot of the time, when software is designed for communities, it gets designed by people who've never actually had to run a community. They build what sounds good rather than what works on Wednesday afternoon when you've got thirty minutes before a prayer meeting and you need to know if you should order more tea.

That student leader from Durham still uses Campus Fellowship. She sent me a message a few weeks ago saying the RSVP calendar had saved her about three hours that month. Three hours she got back to spend actually preparing for events, talking to people, thinking about what her community needed. That doesn't sound like much until you realise how stretched student volunteers are. Those three hours are real.

The RSVP feature isn't clever technology. It's not complicated. It's just a calendar that knows numbers, tied to people who care whether anyone shows up. Building that required us to stop thinking about features and start thinking about weeks. What does a Wednesday look like for the person using this? What are they actually trying to do?