marketing off
What it is:
Promotion planning for churches. The schedule is generated from the size of the event. $29 a month per church.
The assistant answers from what this site says and nothing else.
Anything it cannot answer: contact@engine.church
/ask
Ask what it costs, what it connects to, or what the assistant does.
Playbook · Serving teams
A training night is for the people already on serving teams, which is a list the church has, and the promotion is a reminder with a time, a room and the content. Nothing about it concerns anyone else, which is the definition of the framework's smallest level: three pieces over two weeks, and no newsletter mention, because the newsletter goes to everyone.
A handful: 3 pieces over 3 weeks. Dated for Sunday, January 17, 2027, the next occurrence after the day this page was built.
The size
A handful. The serving teams and their leaders, a room, and a head count for the meal if there is one. Three pieces over three weeks.
10 pieces · 6 weeks
Everybody should know. 5 channels.
6 pieces · 4 weeks
A ministry or an age group. 4 channels.
3 pieces · 3 weeks
The people already involved. The level this event is on.
The schedule
For Volunteer training night on Sunday, January 17. Publish is the day a piece goes out. Due is the day it has to exist, which is the publish date less the channel's lead time: 1 day for Social, 1 day for Sunday Announcements, 3 days for Website.
| When | Channel | Piece | Publish | Due |
|---|---|---|---|---|
| 2 weeks before | Website | Put the page up | Monday, December 28 | Dec 25 |
| 1 week before | Social | Social post | Friday, January 8 | Jan 7 |
| The day | Sunday Announcements | Announce it | Sunday, January 17 | Jan 16 |
Move the event and every unfinished piece keeps its weekday and its lead time. A piece in the event's own week that would land after the event is moved to the week before; the day-of post counts from the date itself.
What each piece carries
What the 3 pieces above have to say for Volunteer training night, channel by channel.
One post the Friday before, in the serving teams' own group rather than the public account, with the time, the room and the RSVP.
The announcement on the Sunday before, made to the teams at their huddles rather than from the stage, with the time and the room.
The page, or the team's own channel: date, time, room, what is covered, who must attend, the meal, and an RSVP. Published two weeks out.
How it is built
Three inputs: the event's date, the level, and the church's framework. The framework is the one above until a church edits it.
Channels with a default weekday and a lead time, levels with a rule for each piece: which channel, how many weeks out, which day. A church edits the defaults to match how it publishes, and every schedule after that follows the edited rules.
Enter the event, pick the level, and the pieces are written with a publish date and a due date each. Each piece is assigned to a person, who sees it on their own list and in their own calendar, with the brief and the copy attached.
Change the date or the framework and the unfinished pieces move to the new dates. Finished pieces, assignments, notes and the copy already written stay where they are. Nothing is published or sent by the software; a person presses every button.
Other playbooks
The same schedule arithmetic, for the events a church runs through the year.
Set your church up, enter the event and pick the level. $29 a month per church. Free for 15 days, no card.
Promo Engine keeps your theme and the other choices you make on this site in your own browser. No tracking cookie and no advertising. What is stored