From one YouTube sermon to reviewed social posts: the full workflow

A Monday content meeting can go wrong with one sentence: "We need five posts."

That puts the quota ahead of the sermon. A better question is, "What does this sermon support, and who can review it?" Now the team has permission to make fewer posts, repair the source, or stop.

A sound sermon-to-social workflow moves through five gates: authority, source, scope, draft, and approval. Export comes last, and the church decides what passes each gate.

Church Media Kit follows that order for static social posts. The workflow begins with a public YouTube sermon and ends with files your team has chosen to export. A YouTube link does not create permission. Captions are not flawless, and the product does not approve a post for the church.

The workflow at a glance

1. Confirm the church has authority to use the sermon.
2. Check that the YouTube source and its captions are usable.
3. Choose the voice, copy length, and post types the sermon can support.
4. Generate source-based drafts and let the automated checks run.
5. Review the message, wording, details, design, and accessibility.
6. Record approval, edit the final pages, and export only what passed.

If a required check fails, stop there. Moving a weak draft forward does not make it stronger. It only makes the error harder to catch.

Gate 1: confirm authority before pulling captions

Start with a public YouTube URL for a sermon your church owns or has permission to repurpose. In Church Media Kit, the person submitting the URL must confirm that authority before the caption check begins.

That confirmation is a statement from the church, not an independent rights investigation. The submitter still needs to know who owns the recording, whether the speaker agreed to the use, and whether the service includes material that should not become a social post.

Use a simple source record:

• sermon title and public URL
• speaker and service date
• person who confirmed authority
• any restrictions, such as a guest speaker agreement or a pastoral-care story that should stay out of social media

This is also the right place to catch privacy problems. A public livestream can contain a testimony, prayer request, image of a child, or identifying detail that your church should not reuse.

The USCCB social-media guidelines advise church personnel to respect copyright and confidentiality. They also tell church personnel to get other people's approval before using their material. Your own church policy should name the person who handles that check.

Stop here when no one can confirm authority, the source contains sensitive material without clear permission, or the URL does not identify the intended sermon.

Gate 2: inspect the caption source

Church Media Kit checks for captions already available with the YouTube video. It does not promise to transcribe captionless audio.

Available captions are the strong source path, but "available" does not mean "verified." YouTube says automatic captions can misrepresent speech because of accents, pronunciation, background noise, overlapping voices, and other conditions. YouTube tells creators to review automatic captions and correct mistakes.

Before generating drafts, inspect the passages most likely to become public copy:

• the sermon's main claim and the sentences around it
• names, places, dates, and numbers
• Scripture references and the translation used
• exact quotations
• event details and calls to action

Listen to the recording when a word is unclear. This is especially important for an exact quote. A caption track is a useful index into the sermon, not a substitute for hearing what the speaker said.

If captions are missing, the current workflow should stop. A URL proves where the sermon lives, but it does not supply the sermon's words. Fix or add the caption track in YouTube, then retry. If that is not possible, work conservatively outside the automated path from a transcript or notes that a responsible person has verified against the recording.

Stop here when captions are missing, the caption language is wrong, the sermon and URL do not match, or the passages you plan to use cannot be checked against the recording.

Gate 3: choose the job before generating the posts

Once the source is usable, decide what each post should do. Do not ask the tool to make every available format.

Church Media Kit's content mix starts empty. Your team can select Quote, Big Idea, Teaching, Announcement, Prayer, Question, Devotion, Testimony, Sermon Recap, or Stat Impact. The source may support only two of those. That is fine.

A practical selection note can fit in one row per proposed post:

Classify the treatment before drafting:

• Exact quote. Preserve the speaker's words. Check the recording, punctuation, and surrounding context.
• Paraphrase. Restate a point without quotation marks. Make sure the meaning and limits remain intact.
• New application. Write a prompt, invitation, or question based on the sermon. Review it as new church copy, not as something the pastor said.

Then choose a voice direction and length. The current choices are Warm and Pastoral, Bold and Convicting, Reflective and Quiet, or Uplifting and Joyful. Copy can be short, balanced, or rich. These settings guide the draft. They do not override the sermon or your church's judgment.

Stop here when the team cannot explain a post's job, the selected format needs evidence the sermon does not contain, or no qualified person can review the treatment.

Gate 4: let generation prepare drafts, not decisions

After intake, the generation job may move through queued, running, needs-attention, and recovery states. Do not build your handoff around an instant-output promise. A section that needs attention is unfinished work.

The workflow prepares source evidence, plans the selected post types, writes draft copy, and pairs that copy with static page designs. Automated checks can catch defined problems such as an exact quote that does not match the supplied evidence, missing primary copy, unsupported event details, or text that does not fit a design's content budget.

Those checks matter, but their scope is narrow. They cannot decide whether a paraphrase is pastorally wise, whether a joke should leave the room where it was told, whether a prayer prompt suits the church's tradition, or whether a call to action is the right next step.

Treat every generated item as a draft even when the automated checks pass.

Keep its source note attached. A reviewer should not have to search the whole sermon to discover where a line came from. For each draft, preserve the source moment, treatment type, and any warning raised during preparation.

Stop here when a section fails and cannot be repaired, a source note is missing, the tool turns a paraphrase into a quotation, or the draft introduces a fact the source does not establish.

Gate 5: run two human review passes

A small church may have one person perform both passes. Keep the jobs separate on the checklist even if the same name appears twice.

Source and pastoral review

The first reviewer protects the message.

Check each draft against the sermon and recording:

• Does an exact quote match word for word?
• Does a paraphrase preserve the sermon's point and its qualifications?
• Is the excerpt still honest without the sentences before and after it?
• Are the Scripture reference, wording, and translation correct?
• Does the application fit what the sermon actually taught?
• Should any personal story, pastoral detail, or image stay private?

The answer can be "do not publish." That is a successful review outcome.

Communications and accessibility review

The second reviewer protects the public handoff.

Check the details the sermon alone cannot approve:

• Is the intended audience clear from the first lines?
• Does the caption say what the graphic cannot?
• Are event dates, locations, links, and contact details current?
• Does the call to action lead somewhere the church can support?
• Is the visual treatment readable and suitable for the subject?
• Does the image alternative describe the useful content without repeating the caption?
• Has the team checked consent for identifiable people and sensitive settings?

W3C's image alternative decision tree recommends a brief description when a simple image contributes meaning. If the image only decorates the page or repeats nearby text, the alternative should not make a screen-reader user hear the same information twice.

This is also where the team checks the church's visual system. Automatic Brand Kit styling is not part of the current workflow. Review fonts, colors, imagery, spacing, and marks instead of assuming the draft is already on brand.

Stop here when the source reviewer rejects the wording, a detail is stale, the visual depends on missing permission, the page is hard to read, or the final approver has not been named.

Use a review rhythm your team can sustain

There is no universal schedule. A church with a full communications staff and a church with one volunteer should not pretend to have the same handoff.

A workable rhythm is role-based:

1. One person prepares the source record and selects the proposed post types.
2. The teaching reviewer checks source fidelity before design polishing.
3. The communications owner edits the approved copy, design, details, and accessibility.
4. The named approver records "approved," "revise," or "do not publish."
5. The exporter selects only approved pages.

Set a cutoff that matches your real capacity. If approval is not complete by the cutoff, move the post or drop it. Do not skip the review to protect a calendar square.

Edit and export only the approved pages

Approved static pages can move into Studio for final editing. The church still decides the wording, page order, visual treatment, and which pages leave the editor.

The current export paths are image-based. A single-page document can export as JPEG. A selected page can export as PNG. Several selected pages can export as a ZIP containing PNG files. A 9:16 Story JPEG path also exists. This is not a video or PDF workflow.

Before export, compare the selection with the approval record. A polished unapproved page should stay behind.

Use a compact final record:

That record is intentionally plain. It tells the next volunteer what was checked, what was approved, and what they are allowed to publish.

The real finish line

The finish line is not "the tool generated posts." It is "the church can explain why each exported post is faithful, current, accessible, and approved."

Church Media Kit can prepare source-based drafts, run defined checks, and give your team editable static pages. It cannot supply permission, pastoral judgment, current event facts, or final approval. A documented source, named reviewers, and a recorded approval decision show what the church checked before export.