Multi-site sermon transcription: one library, every campus

Most multi-site churches we talk to are doing one of three things. Option A: each campus media director transcribes their own service in whatever tool they prefer (Otter, Descript, a paid Rev order), creating five different file formats and zero searchable archive. Option B: the central media team transcribes only the broadcast service, and satellite-campus services are simply not archived. Option C: a junior team member at central manually copy-pastes between tools every Monday morning. None of these scale past three campuses, and none produce a searchable archive across the network.

The clean pattern is: every campus uploads its weekend audio file to a shared folder (Drive, Dropbox, or directly to your central CMS) by Sunday evening. A single Sermon Transcription account ingests all of them overnight. Monday morning, the central media director reviews, tags by campus and series, and publishes. One library, one search index, one set of tags. Each campus then pulls captions, transcripts, and clips for its own social and website needs from the same source of truth.

Yes. The Multi-Site plan includes seat-based access with role assignment: central media director (full admin), campus media leads (upload + tag their own campus), and read-only volunteers (download captions and transcripts only). All sermon files live in a single library that everyone with permission can search.

Each upload gets two required tags at minimum: campus (Downtown / North / South / Online / Espanol) and service (8am / 10am / 11:30am / Saturday). Optional tags include series, preacher, scripture references, and language. Tagging once at upload powers every downstream filter, search, and report — including 'show me every sermon by Pastor Mike from the Downtown campus on Romans 8.'

Yes — that's one of the biggest wins for multi-site networks. When the broadcast campus airs the same teaching at every site, satellite campus media teams skip transcription entirely. They pull the central transcript, swap in their campus-specific intro and announcements, and publish on their site. We've seen this save 8-12 hours per week of duplicated work across a five-campus network.

Many multi-site networks let campus pastors preach their own message a few weekends per quarter (or every week, for the more decentralized models). Those campuses upload their own audio under their campus tag. The central library now has both broadcast and campus-original sermons, fully indexed and discoverable network-wide. Campus pastors love this because it makes their teaching visible to the rest of the network.

Sermon Transcription exports clean SRT, VTT, TXT, JSON, and DOCX. Every modern church CMS — Subsplash, Tithely, Aware3, Pushpay Resi, Brushfire, Ministry Pass, and custom WordPress setups — accepts at least two of those formats. For Subsplash and Resi specifically, we also support direct webhook posting on a published transcript so transcripts attach to sermon entries automatically.

It depends on average sermon length and total weekend services, but a typical five-campus network with one 35-minute message broadcast plus two unique campus sermons per weekend processes roughly 175 minutes per week, or 9,100 minutes per year. At Sermon Transcription Multi-Site pricing that lands in the $39-79/month range depending on review level. For context: hiring out the same volume from Rev.com (human transcription) costs roughly $1,090 per month.

Yes. Many networks add their podcast episodes, leadership team meetings, staff training, and special services (Christmas Eve, Easter, Good Friday) to the same library. As long as it's an audio or video file, it can live in the central transcript library. This becomes especially powerful as an internal search index — 'where did our lead pastor talk about generosity at the all-staff meeting?'

Two phone calls and 90 minutes total of work from central media. Call one: set up the account, define campus tags, create user accounts for each campus media lead. Call two: walk through the first weekend's upload-tag-publish cycle. After that, we send each campus media lead a 5-minute Loom video showing how to upload their campus audio. Most networks are fully running by their second weekend.