Recording received
Confirm the MP4 or approved church YouTube source before processing begins.
SermonOps gives the media team one visible handoff from the recording it received to the package an authorized person approves for publishing. Every checkpoint says what happened, who acts next, and what still needs attention.
SermonOps does not publish automatically. A church user with existing publishing authority must approve the final package.Confirm the MP4 or approved church YouTube source before processing begins.
Watch the proposed start and end, correct them when needed, then approve the cut.
Review the clean video, captions, metadata, clips, and study link; resolve any named warning.
An authorized church user chooses what to release. Existing channel approvals remain required.
The media team stays focused on publishing. The preacher and discipleship team can use the connected layers without making the Sunday workflow harder.
Find the sermon inside the full service, remove the long lead-in, and preserve a reviewable final cut.
Prepare titles, descriptions, chapters, clips, captions, hashtags, social copy, and reusable church defaults.
Attach a public study link and QR code so viewers can read, answer, save progress, and return without a paid subscription.
Carry the same sermon into evidence-based review, coaching, research, and the next message when the church is ready.
The main status names the owner and recovery step. Technical details remain available under More details for the person troubleshooting the failure.
The public study is separate from the paid ministry workspace. A visitor can preview the guide, enter a name and email once to save progress, receive a secure passwordless link, answer the 25 questions, and return to earlier studies from that church.
The operations engine: trim, package, publish, and attach the public study.
The preacher-intelligence layer: evidence, coaching, research, and better sermon creation.
The formation layer: private practice, study, follow-through, and consent-based care.
Use a real church service to evaluate the workflow, the public study, and the handoff your team would actually use each week.