Quick answer: A copy package is every piece of communication one announcement needs, generated together from a single input — social posts, text messages, stage announcements, a newsletter, an email campaign, a blog post, FAQ answers, ad copy, volunteer recruitment, a press release, and a timeline for when each piece ships. Churches usually write these one at a time in separate places, which is why the details stop matching.
The problem nobody names out loud
A church decides to run a fall serve day. What happens next is predictable.
Someone writes a paragraph for the bulletin. Someone else writes a shorter version for the stage. A volunteer writes the Instagram caption from memory. The newsletter gets a slightly different date because the plan changed on Wednesday. The text reminder goes out with last year's link.
No single person did anything wrong. The work was simply spread across six documents, four people, and three weeks, with no shared source. Small differences accumulate until the congregation quietly stops trusting the details.
That is the problem a copy package solves. Not writing speed — consistency across channels.
What goes into a complete package
A ChurchCopy copy package is built in three groups.
Core copy
- Social media posts — written separately for Facebook, Instagram, and X, because each feed reads differently.
- Text messages — short enough to land in a single SMS, with the action up front.
- Announcements — including stage announcements written to be spoken out loud, not read silently.
- Newsletter — the section that goes into your weekly or monthly send.
- Description — a clean block you can paste straight into an email, a registration page, or an event listing.
Bonus copy
- Email campaign — a sequence, not one send: announce, remind, last call.
- Blog post — the long-form version that search engines and AI assistants can actually find.
- AI FAQ answers — direct answers to the questions people ask about this event.
- Meta ads copy — for Facebook and Instagram promotion.
- Google Ads copy — headlines and descriptions that fit search ad limits.
- Volunteer recruitment — the ask, written to invite rather than guilt.
- Press release — for the things local media would genuinely cover.
Resources
- Comms timeline — when each piece ships, editable so you can move dates as plans change.
- Images and videos — the visual assets attached to the package.
You will not use all fourteen every time
This is the part people get wrong. A complete package is not an assignment to publish everything.
A midweek prayer gathering needs a text, a stage announcement, and one social post. A fall series launch needs nearly all of it. A building campaign might need the press release. A guest night needs the ads.
Having every piece generated means you choose what to use instead of deciding what you have time to write. Those are very different decisions. The second one is why the volunteer recruitment ask never gets written until two days before.
Why generating them together matters more than generating them fast
Speed is the obvious benefit and the least important one.
When all fourteen pieces come from one input, the date is the same everywhere. The audience is described the same way. The name of the event does not drift from "Fall Serve Day" to "Serve Saturday" between the bulletin and the text. The tone matches, because everything was written against the same tone of voice setting rather than by four people's individual instincts.
And every piece was written after reviewing your mission, values, statement of faith, and AI policy — not from a blank prompt where whoever is typing has to remember to explain your church again.
Everything is editable
Generated copy is a starting point, not a finished product. Every item in a package can be edited directly — type over it, cut a sentence, change the date.
There is also a rephrase control on each item. Use it to make something shorter, longer, more casual, or to suggest a different angle. You are not stuck choosing between what the AI wrote and rewriting from scratch.
What you should never skip is the human read. A person who knows your church should read every package before anything ships, which is what the review and approval step exists for.
Recurring things are duplicated, not rebuilt
Churches repeat almost everything. Monthly newcomers lunch. Quarterly baptisms. The same serve day every fall.
You do not create those from scratch each time. Build the package once, duplicate it, and change what actually differs — the date, the location, the specific need. Most of the time that is a five-minute edit instead of an hour of rewriting.
Over a year, that difference is the reason recurring events either stay well-communicated or slowly degrade into a line in the bulletin.
The timeline is the piece teams underuse
Every package includes a comms timeline: when each piece should ship. Four weeks out, the blog post and first email. Three weeks out, the first social push. Two weeks out, volunteer recruitment. The week of, the text and the stage announcement.
You can adjust every date. And because packages feed into the communications calendar, you can see the timeline next to everything else happening that month — which is usually when someone notices that three ministries are all asking for sign-ups on the same Sunday.
What changes for your team
Before: someone writes copy in a doc, pastes it into six places, chases approval by text, and hopes the version on the screen Sunday matches the one in the newsletter.
After: one input creates one package, the package holds every channel, a reviewer approves it in one place, and the timeline says what ships when. Your dashboard shows what is pending, what is approved, and what is scheduled.
The output is not just faster communication. It is communication your congregation can trust, because the details finally agree with each other.
Who touches a package, and when
A package is not just content. It is a small workflow, and naming the steps removes most of the friction teams feel.
- Intake. Someone submits the need with confirmed details — the date, the audience, the action.
- Generate. The package is created from that input, all channels at once.
- Edit. The communicator trims, adjusts, and deletes the pieces this particular announcement does not need.
- Review. A second person reads it, comments on specific items, and approves.
- Ship. Each piece goes out on the timeline date.
Most churches already do all five. What they lack is a single place where the steps are visible, so work sits in someone''s inbox for two days and nobody knows whose turn it is.
What packages fix that a document cannot
Teams often ask why a shared document would not do the same job. It can hold the text. It cannot hold the state.
A document does not know which items are approved, which are still drafts, who commented, or what ships Thursday. A package does, and every item carries its own status. That is why the same content in a package behaves differently than the same content in a doc — you can see what is done.
It also means nothing gets published twice by accident, and nothing sits finished but unsent because the person who wrote it assumed someone else was scheduling.
Try for free — seven days, no credit card, unlimited free viewers.