How it works
One week, start to finish.
The product runs on a fixed weekly rhythm. Here is exactly what happens, on which day, and where your team steps in.
- MondayDraft
Your draft is waiting.
Events sync from your connected calendars and the week’s bulletin is drafted. Your team gets an email that it’s ready.
- Calendars synced
- Draft generated
- Staff notified
Men’s CoffeeVictory YouthYoung AdultsDrafted from 3 calendar sources.
- WednesdayIn review
One last check before the weekend.
Calendars sync again. Anything that moved since Monday is reconciled, conflicts are surfaced, and your team gets the final preview.
- Re-synced
- Changes reconciled
- Preview sent
Men’s CoffeeVictory YouthWed · 6:30 PMWed · 7:00 PMYoung Adults1 time changed since Monday — needs review.
- Thursday & FridayPaused
Nothing moves behind your back.
Automation stops completely. No syncing, no regenerating, no surprises in the two days when nobody wants any.
- Automation paused
- No changes applied
Men’s CoffeeVictory YouthYoung AdultsAutomation paused until Saturday.
- SaturdayPublished
Approved. Published. Verified.
The bulletin your team approved publishes on schedule — and the system checks the public page actually responds.
- Published
- Public URL verified
Men’s CoffeeVictory YouthYoung AdultsPublished · public page responding.
Setting up
Four things once, then it runs.
Setup is the only part that takes real attention, and it happens one time.
Connect a calendar
Paste a Subsplash URL, an ICS or RSS feed, or a SnapPages calendar. This is the only step that touches anything technical, and it happens once.
Set your times
The Monday, Wednesday and Saturday times are yours to choose, in your church’s own timezone. The defaults are sensible; most churches never change them.
Add your team
Invite the people who write and the people who approve. Give them a role, and restrict them to a ministry if that’s how your church works.
Then leave it alone
From the following Monday the rhythm runs itself. Your job becomes reviewing rather than assembling.
The awkward questions
What happens when something goes wrong.
What if we need to stop everything?
There’s an emergency pause that stops all automation for your church immediately — no syncing, no drafting, no publishing — until you turn it back on.
What if nobody reviews it in time?
Nothing publishes that hasn’t been approved. An unapproved draft simply stays a draft; Saturday publishes the approved version or nothing at all.
What if an event changes on Friday?
It won’t change the bulletin. Automation is deliberately frozen Thursday and Friday, so the thing your team approved on Wednesday is the thing that goes out. You can still edit by hand at any time.
What about daylight saving?
Times are stored against your church’s timezone, not a fixed offset, so a 7:00 AM Monday stays 7:00 AM through the clock change.
Monday is coming either way.
Open the week with a draft instead of a blank page.
No card required.