Every church office has a version of the same Friday-afternoon argument: does the youth retreat announcement go in the bulletin, on the website, in both, or neither? Nobody wants to leave someone uninformed, so the instinct is to print everything and hope. The result is a bulletin that has quietly grown to three pages of small type that almost nobody reads start to finish.
The fix is not a rule about paper being outdated. Paper still does something a website cannot: it reaches the person sitting in the pew who never opens a browser between Sundays. The fix is a clear test for which announcements need that reach and which ones are better served by a page you can correct after Sunday morning.
Why this decision keeps coming back
The tension is not really print versus digital. It is permanence versus correction. A bulletin is printed Thursday or Friday and read Sunday; whatever is wrong in it stays wrong until next week. A web page can be fixed the moment someone notices the typo, the changed room, or the sold-out class. Once you see the decision through that lens, most of the disagreement about “should this be in print” turns into a much easier question: how likely is this information to change, and how much does it cost if it does?
A one-time event this Sunday, at a fixed time, in a fixed room, is low risk. A multi-week sign-up with a cap, a price, or a date still being negotiated with a venue is high risk. Print the first kind freely. Point to a page for the second.
What belongs in print, almost every time
Some categories of information earn their spot on paper nearly every week, because they are read exactly once and need no correction:
- This Sunday’s specifics — sermon title, scripture, who is preaching, which rooms are in use for Sunday school or nursery.
- A name and a date, together — “pray for the Hendersons this week” belongs in print because it is time-bound and personal; nobody is going to look it up online.
- Anything that needs to be in someone’s hand, not their inbox— a giving envelope insert, a physical connect card, a printed order of service for a guest who is holding a bulletin, not a phone, during the service.
- A short headline with a QR code for anything longer — “Fall retreat registration is open, details and pricing at the link below” keeps the bulletin at one page while still pointing people somewhere accurate.
Notice what these have in common: none of them require an update after the bulletin is printed. That is the actual test, more than any assumption about who reads paper and who reads screens.
What belongs online only
The opposite category is anything that might change, that has more than two or three facts attached, or that benefits from being searchable weeks later:
- Registrations with a cap or a price tier — if the retreat sells out Tuesday, a page can say so; a bulletin printed Friday cannot.
- Anything with a phone number or an email someone will use later— contact information printed in September is still being read off an old bulletin in November. A web page is the version that stays current.
- Recurring class or small group schedules — a semester of small group meeting times fits far better on a page than reprinted weekly.
- Anything you might need to correct — a typo in a date, a changed venue, a canceled class. Correcting a web page costs nothing. Correcting a printed bulletin costs an announcement from the stage undoing what people just read.
If your church runs its calendar and registrations through SundayBridge, the gatherings calendar is the single place those dates live, so the bulletin headline and the online detail page never quietly drift apart the way they do when one lives in a spreadsheet and the other in a printed template from three months ago.
The one-page test
A useful discipline, independent of what technology you have: cap the bulletin at one page, front and back. Not because paper is expensive — it rarely is, at church scale — but because a one-page limit forces the actual triage decision every week instead of letting the bulletin grow by accretion. Once an announcement has run for three weeks with a QR code and nobody has complained, it has earned its place online-only. Once a new announcement shows up that changes week to week, it goes online from day one rather than getting a print slot out of habit.
Committing to a page limit also solves a subtler problem: bulletins that run long train readers to skim, and a skimmed bulletin serves the visitor and the older member worse than a shorter one they actually finish.
Where the website earns its keep
The instinct to distrust a website comes from real experience: church websites are often the last thing updated, a graveyard of a 2019 sermon series and a broken staff photo. That reputation is earned, but it is a maintenance problem, not an argument against putting time-sensitive detail online. The fix is not more printing. It is fewer, better-maintained pages — a calendar that is actually current, a giving page that is actually accurate, a class list that reflects who is actually teaching this semester.
Planning a church event from the calendar outward, rather than from the bulletin backward, tends to fix this on its own: if the event detail page is the source of truth and the bulletin only ever points to it with a headline, the page has to stay accurate because it is the only place the full information lives.
A weekly rhythm that keeps both current
The churches that do this well are not the ones with fancier software. They are the ones with a repeatable weekly habit: someone reviews what is happening in the next two to three weeks, decides what is date-specific enough for print, and updates the online calendar and detail pages at the same sitting rather than on separate schedules. If that review happens as part of a weekly church admin rhythm rather than as a scramble every Friday, the bulletin gets shorter and the website gets more accurate at the same time, because both are being maintained from the same source rather than reconciled after the fact.
The same logic extends past Sunday morning. What you do with a visitor’s card or a signup sheet after the service is a version of the same print-versus-system question: a paper card is the right tool in the moment, but following up after a big Sunday works better once that card’s information moves into a system someone actually checks, rather than staying a stack of paper on a desk.
A short list to run through this Friday
Before the bulletin goes to print, run each announcement through three questions. Will this be true, unchanged, on Sunday morning? Does it fit in two sentences? Does the reader need it in hand rather than in an inbox? Two or three yeses means print it. One or zero means give it a headline, a QR code, and a home online where it can be kept current without another print run.
None of this requires new software to start doing this week. It requires a five-minute conversation about which announcements have been running on autopilot in the bulletin for months, and moving the ones that have changed at least once since they first ran — a date, a price, a room — onto a page instead.