If it's public, it's on the calendar

Here's a setup we see at a lot of churches. A couple of small care groups are on the website calendar. A large weekly Bible study, one of the biggest things happening in the building all week, isn't. It lives only on its ministry page.

You'd think the people who need the study would find it there. Some do. But many won't. When some groups are on the calendar and others aren't, people assume the missing ones aren't happening.

That assumption is the whole problem. People don't read a church calendar as a sampler of what's going on. They read it as the list. When something is missing, they don't think "they must have forgotten to add it." They think it isn't happening, or they stop believing the calendar and start emailing staff instead.

As Tanner Moushey, our founder, puts it: "I think it's worth the effort to make sure that there's full visibility. Otherwise people lose trust in what's being displayed on the website."

Why half a calendar is worse than none

If you have no calendar, people know to look elsewhere: the bulletin, the ministry page, a staff member. A partial calendar removes that instinct. It looks authoritative, so people rely on it, and it quietly misleads them.

The damage spreads past the calendar, too. Once someone gets burned by a missing event, they wonder what else on the site is out of date. Service times, staff pages, the nursery info. A calendar is often the most visibly "live" part of a church website, so it sets the tone for how much people trust the rest.

Newcomers feel this most. Someone who shows up in October has no idea your Wednesday night program started in September. If Wednesday night isn't on the calendar every week, it might as well not exist for them.

The rule: if it's public, it's listed

One communications team we work with settled on a simple test that we like a lot: if a fifth grader or a senior adult could attend it, it goes on the calendar. That covers the weekly studies, the recurring care groups, youth nights, and the one-off events alike. It leaves out staff meetings, elder meetings and anything invite-only.

The point of a test like that is that nobody has to make a judgment call. Staff don't debate whether an event is "big enough" for the calendar. Size and importance are handled elsewhere (more on featuring below). The calendar's only job is to be complete.

Start with an audit

You can do this in an afternoon, and it's useful even if you never touch your website's design:

• Open each ministry page and list every recurring gathering it mentions: day, time, location.
• Check each one against the calendar. Mark what's missing.
• Do the same with your bulletin and announcement slides for the next month.
• Hand the list of missing events to whoever does data entry. A clear spreadsheet is a good intern project.

The audit tends to surface other useful things. Seeing every ministry's schedule in one place is often the first time anyone notices, for example, that fall programs all start on different weeks. Whether that matters is a staff conversation, but it's worth knowing.

Design for 2,000 events, not 200

Here's the catch. A complete calendar is a much bigger calendar. Most church event pages were designed around the handful of events comms chose to promote. Add every weekly study and group for a semester and you can go from a couple hundred entries to a couple thousand. If the design doesn't change, the page becomes an endless scroll of the same Tuesday study repeated fifteen times.

What helps:

• Collapse recurring events. In list views, show each recurring series as one card for its next occurrence. Craig Van Korlaar, our UX lead, said it plainly when we worked through this: "I do think that most of this problem is mitigated by simply having the collapsed view for the recurring thing." Month grids are the exception: they need to show every occurrence, because that's the point of a grid.
• Add a Featured / All events toggle. Default to a short, curated set, with one tap to see everything. Who decides what counts as featured deserves its own policy, written before the requests start coming in.
• Keep the weekday visible. People decide by day of the week ("I'm free Thursdays"), not by date.
• Put filters at the top and cap card height. Truncate descriptions so the first sentence has to work as a summary, and write it that way.
• Build a mobile calendar that works. A full month grid is unusable on a phone, and a plain list means endless scrolling. A compact month view where you tap a day to see its events, with dots marking busy days, has worked well for us.

Show events where people already are

Many church sites give events a nav slot and stop there. But most people looking for a youth event start on the youth page, not on a general calendar.

A better pattern is to pull a filtered list of upcoming events into each ministry page, with a link to the full calendar already filtered to that ministry. Pages stay fresh without anyone editing them, and every event has more than one way to be found. Label those links clearly. "View all events" on the student page reads like all church events; "View all student events" doesn't.

One trade-off to watch: once the calendar is full, weekly studies can crowd a ministry page's "upcoming" block and push out the one-off retreat people need to hear about. Since the weekly rhythm is already described on the page, it's reasonable to leave recurring series out of that preview while keeping them on the calendar. Just apply the rule evenly. Showing one weekly study and hiding another implies a ranking you didn't intend.

Decide who owns entry

A full calendar stays full only if someone owns it. Pick one place where events originate and one person or team responsible for getting them on the site. For some churches that's a request form that comms processes. For others it's the church management software syncing events to the site, which is a bigger topic we'll cover separately. Either way, avoid keeping the same event in two places by hand. Duplicates drift apart.

Expect a second wave of work, too: more events means more "the room changed tonight" messages. A clear cutoff for website changes, such as 24 hours' notice, saves a lot of scrambling, as long as you hold to it from the start.

The test is simple

Pick a regular gathering at your church and try to find it on your website the way a newcomer would. If you can't, someone else already couldn't either. If you'd like a second set of eyes on your calendar or the site around it, we're happy to talk.