Events blueprint

Weekly church email, framed from the calendar

Each week the assistant reads what's coming up on the church calendar and builds the framework for your weekly email, so staff can finish it and send.

The problem

Every week someone stares at a blank email and digs through the calendar to remember what's coming up. Something always gets missed, or a sign-up goes out without a link.

What it does

Each week it reads everything coming up on the church calendar, plus the Planning Center calendar and sign-up forms if you've connected them, and builds the framework for the weekly email. Sections come in the same order every time: this Sunday, upcoming events with dates, times, and places, sign-ups with links, needs and serving, and reminders. If something is missing, like an event with no time or a sign-up with no link, it flags it instead of filling it in. Staff then finish the email in their own email tool. We use Flodesk.

Setup

  1. Connect the church calendar (read-only).
  2. List your standard email sections once.
  3. Give it one past email as a voice sample.
  4. Choose the day it runs each week.

Guardrails

Time saved

We're still tracking this honestly, so there's no number here yet.

Questions pastors ask

Does it send the email?
No. It builds the framework and hands it to staff. A person writes the final copy and sends it.
What if an event is missing a time or a link?
It flags it in the draft and asks. It won't guess.
Which email tool does it work with?
Any of them. It hands over a draft framework, and we finish ours in Flodesk.
What does it need to start?
Read-only access to the church calendar, your list of standard sections, one past email, and the day you want it to run.

Related blueprints

Read the ground rules every blueprint follows →