How does one sermon become a newsletter, a blog post and a study guide?
By being written seven times for seven places, from the same transcript, rather than once and pasted. A newsletter paragraph, a blog article, a caption, a study guide and a manuscript are different pieces of writing with different readers; the tool that does this well writes each one from the sermon, in every language the church serves, and then waits for a person to read it.
What a church writes from one Sunday
Count what the media volunteer actually produces in a good week, and the list is longer than anyone admits: a clean transcript for the archive, a summary for the people who missed it, something for the website, a paragraph for the newsletter, a caption for Instagram, questions for the small groups on Wednesday, and, for the person who asked, the whole message written out. Once for every language the church serves. Most weeks, most of it does not get written. That is not a failure of the volunteer. It is a working day, every week, for free.
Seven pieces, and what each is for
- A clean transcript: the record. Repeats and slips removed, punctuation added, in the language preached and in every language translated.
- A summary: for the person who missed it and the newsletter that mentions it. Short, with the scripture references.
- The full message: the sermon itself, written out under the preacher's own outline, for the person who wants to read it rather than a reminder of it.
- A small-group guide: a passage, four or five discussion questions grounded in what was said, an application, a prayer prompt. For the leader on Wednesday.
- A blog article: the message as a piece of writing for the website, with headings a search engine can read.
- An email newsletter: warm, short, ready to send, with the times of the next gatherings and an unsubscribe link that works.
- A social caption: one line that carries the sentence people took home, and the post ideas around it.
Written from the sermon, not from each other
The cheap way is to write the summary and then shorten it into a caption and lengthen it into an article. The result reads like what it is. Each piece should be written from the transcript for its own reader: the caption from the one sentence that landed, the article from the argument, the guide from the passages. And each language should get its own draft, not a translation of the English one, so that the Farsi newsletter is a newsletter and not a translation exercise.
The exception is the full message. That should be written once, in the language it was preached in, and translated section by section with the church's glossary, because a manuscript is a document and every language should carry the same outline.
What to check before anything goes out
The test that tells you most: take one real service and read the seven pieces beside the recording, in the language you know least. Ten minutes of reading says more than any feature list.
How Sanctavo does it
Every translated service becomes the seven pieces above, automatically: clean transcript, summary, the full message, a small-group guide, a blog article, an email newsletter and a social caption, each written from the transcript for its own reader, in every language the church chooses, with the church's glossary and memory. Every piece arrives as a draft for review and can be edited before it is published; the newsletter sends per language with a one-click unsubscribe; a church can let its listeners read and download the published pieces from the same link they listened on. A teaching series can go further into Sanctavo Press and become a study guide or a book draft. All of it is included in every plan. Because the system uses AI, errors remain possible, which is why the review step exists.