Somewhere in your bulletin is a line that has not been true for a while. The men's breakfast that quietly stopped meeting in the spring. The sign-up sheet for a mission trip that already happened. The small group that lost its leader and never told anyone to stop printing the invitation. Nobody put it there to deceive anyone — it was true once, and then the person who knew it stopped being true moved on, and the line kept getting copied forward.
This is not a design problem or a software problem. It is a maintenance problem, and it has a maintenance solution: a short, repeatable pass that asks one honest question of every recurring line, on a date somebody actually keeps.
Why stale announcements survive so long
Bulletin announcements decay by default, not by exception. Whoever builds the bulletin each week is usually copying last week's file and adding to it, not rebuilding it from what is currently true. That is a reasonable way to save time, and it is exactly how an announcement outlives the thing it describes. Nobody decided to keep running it — nobody decided anything. It just never got deleted.
The people who would notice usually are not the ones proofreading the bulletin. The volunteer who ran the men's breakfast knows it ended. The person copying last week's file into this week's does not, because nobody told them, and there was never a reason for anyone to tell them, because ending a small recurring thing does not feel like news.
How a line survives past its own truth
Watch it happen once and you will recognize it everywhere. A volunteer starts a Wednesday men's breakfast and asks for a line in the bulletin. Someone types it up: “Men's breakfast, Wednesdays at 7, fellowship hall.” For a season it is true every single week. Then attendance thins, the volunteer takes a new job with an early start time, and the breakfast quietly stops. The volunteer does not send a retraction — why would they, nobody sends a memo announcing that something small ended. The bulletin file gets copied forward again the next week, as it always has, and the line rides along inside it.
A year later, whoever assembles the bulletin has never been to a men's breakfast that did or did not happen. They have no reason to suspect the line, because it reads exactly the way it read when it was true. The only way it gets caught is if someone deliberately goes looking — and deliberately going looking is precisely what most churches never schedule time for. The line is not hiding. It is just never asked about.
The two-year test
Pull up your current bulletin and read every recurring line against one question: who told you this is still true, and when? Not “does this sound plausible” — a stale announcement almost always sounds plausible, that is why it survives. The question is whether a specific person confirmed it recently, and if you cannot name that person and roughly when they told you, treat the line as unverified.
Most bulletins have somewhere between two and six lines that fail this test outright. They are rarely dramatic — nobody is lying about a program that ended a decade ago. They are small and quiet: a sign-up deadline that already passed, a class that moved rooms three months back and never got corrected, a phone number for a ministry contact who left staff last winter.
Sort what is left into three piles
Once you have flagged the unverified lines, everything on the page falls into one of three groups, and the sorting itself does most of the work:
- Confirmed and current. Someone can vouch for it this week. Keep it running as is.
- Confirmed but ending. It is real, but it has a known last date. Print it with that date attached, so it removes itself instead of waiting for you to remember.
- Unverified. Nobody could confirm it inside a week of asking. Pull it. If it turns out to still be running, whoever owns it will ask you to put it back, and now it has an owner attached who will notice next time it goes stale.
That third pile is uncomfortable the first time. It gets easier once you notice how rarely anyone asks for the announcement back.
Give every recurring line an owner and a checkpoint
The reason an announcement survives its own relevance is that nobody's name is on it. Fix that going forward: every recurring line gets one person attached, and a date — quarterly is typical — when someone asks that person directly whether it is still true. Not a group email. A direct question, the same way you would check whether a volunteer is still on a serving team rather than assuming the roster from last year still holds.
This is the same discipline that keeps a directory your team actually trusts instead of one everyone quietly stops believing. A record with no owner and no checkpoint drifts. A record with both stays current because someone would notice if it did not.
Where the real facts should live
The bulletin is a printed snapshot, not the source of truth, and treating it like the source of truth is the root of the problem. The actual facts — who leads which group, who is on which serving team, what is really on the calendar this month — belong somewhere that gets updated as a byproduct of running the church, not somewhere that only gets touched when someone remembers to touch it.
If your groups and teams already live in SundayBridge, the pruning pass is mostly a matter of checking the bulletin against what the system already shows: a group with no members left probably should not have a bulletin line, and a serving team roster tells you whether that “volunteers needed” announcement is still accurate or quietly out of date. It will not write or send the bulletin for you — that is still a human job, and rightly so — but it gives you one place to check instead of five people to track down.
If your groups and teams still live in someone's head or an old spreadsheet, the pruning problem you are solving here is a smaller version of a bigger one. See moving your church off spreadsheets for the larger fix.
Build the pass into a rhythm, not a project
Pruning the bulletin once feels like a project: an afternoon, a list of awkward calls, a satisfying cleanup. Left there, it drifts right back to where it started, because the underlying habit that created the mess — copying last week forward without question — never changed. The fix is to fold the two-year test into whatever weekly or monthly rhythm already keeps your records current, so pruning becomes a five-minute check rather than a periodic overhaul.
A church running a weekly admin rhythm already has a natural slot for this: the same short pass that checks follow-up and the week ahead can carry one more question, asked of one recurring announcement at a time, until the whole list has been touched.
What a healthy bulletin looks like
It is shorter than you think it should be. Most churches, after a real prune, cut somewhere between a quarter and a third of their recurring lines and do not miss any of them. What is left reads faster, gets read more carefully, and earns back some of the trust a cluttered bulletin slowly spends. People stop skimming past the announcements once the announcements stop lying to them, even by accident.
The line that has been running for two years is not usually malicious and not usually anyone's fault. It is just what happens to any fact that nobody is responsible for checking. Assign the responsibility, set the date, and the bulletin stops accumulating the things that used to be true.
Start with the lines that cost the most to leave in
If a full prune feels like too much for this week, start with the announcements that do actual damage when they are wrong, not just the ones that are merely outdated. A stale contact number sends a visitor to a dead line. A sign-up sheet for an event that already filled or already happened wastes someone's Saturday morning. A “volunteers needed” line for a team that is quietly full makes the church look like it cannot keep track of its own people, which is a worse impression than simply having fewer announcements.
Rank the unverified lines by that kind of cost rather than by how long they have been sitting there. A line that has been wrong for three years but points somewhere harmless can wait another week. One that sends someone to the wrong door on Sunday morning cannot.