Multi-site sermon transcription: one library, every campus

Multi-campus networks have a transcription problem most single-site churches never see. Five campuses, three services, two languages, one broadcast feed, and a media director trying to keep a searchable sermon archive across all of it. This page is the playbook.

Why multi-site networks need a central transcript layer

One archive, every campus searchable

Network leadership can search every sermon ever preached across every campus from a single library. "Where did we teach on generosity last year" becomes a 10-second query instead of a three-day email thread.

Broadcast and campus content side by side

Broadcast sermons and campus-original sermons live in the same library, tagged by campus and preacher. Satellite campuses skip re-transcribing the broadcast. Original campus sermons get the same indexing love.

One account for central + campus teams

A single shared account keeps every campus in the same library while central media oversees the whole archive. Campus leads contribute audio through a shared folder; volunteers pull captions and downloads from the output.

The multi-site weekly transcript workflow

A six-step rhythm most multi-site media teams can run with one central director and one part-time helper per campus.

1

Each campus uploads its weekend audio by Sunday evening

Campus media leads drop the raw audio or video file into a shared Drive/Dropbox folder named for the campus, or upload directly via their campus-tagged Sermon Transcription account. File naming convention: YYYY-MM-DD-campus-service. Example: 2026-06-08-downtown-1030am.mp3.

2

Central library ingests everything overnight

Whether you have three campuses or fifteen, all uploads route to the same central transcript library. Overnight processing means Monday morning the central media director walks in to a queue of finished transcripts ready for review, not a queue of files waiting to start.

3

Central media tags, reviews, and publishes

Each transcript gets tagged: campus, service, series, preacher, scripture, language. Review takes 5-10 minutes per transcript (proper nouns, names of regular attendees, ministry-specific vocabulary). Publish pushes the transcript to the network library and optionally to each campus website.

4

Satellite campuses pull from central for broadcast services

When the broadcast campus airs the same message at every site, satellite campus media teams skip transcription entirely. They pull the central transcript, swap in campus-specific intro/announcements, and publish to their own site. 8-12 hours per week saved across a five-campus network.

5

Campus-original sermons stay in their campus folder, network-visible

Campus pastors who preach unique messages on certain weekends upload to their own campus tag. The central library indexes them just like broadcast content. Other campus pastors can search and learn from each other's teaching.

6

Network leadership uses the library as a teaching index

Senior leadership uses the central library for sermon planning ('what have we already taught on the parables this year?'), for content repurposing ('pull our top three Easter messages for a book project'), and for compliance ('what did Pastor Sarah say on this topic three years ago at the East Campus?'). One archive, infinite questions answerable in seconds.

Three multi-site models, three transcription patterns

How the workflow shifts depending on whether your network broadcasts, distributes video, or runs decentralized campus preaching.

ModelWho preachesFiles transcribed/weekLibrary benefit
Live broadcastOne lead pastor across all campuses1 per weekendOne transcript, distributed to every campus website
Video venuePre-recorded teaching + occasional campus pastor1-2 per weekendBroadcast + occasional campus original, all searchable
Decentralized teachingCampus pastors preach their own message most weekends3-7 per weekendCross-campus teaching index, sermon planning across network

Most multi-site networks blend models — a broadcast lead pastor most weekends, with campus pastors preaching during sermon series breaks, summer schedules, and special services.

One upload, every campus output

Each weekend sermon produces the artifacts every campus needs, automatically, from a single source of truth.

Weekend audioCentral transcript libraryCampus ASite + captionsAuto-publishCampus BSite + clipsAuto-publishOnlineSRT for streamAuto-publishCentralIndexSearch

Frequently asked questions

How do multi-site churches typically handle sermon transcription today?+
Multi-site churches generally land on one of three arrangements. 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.
What does a centralized multi-site transcription workflow look like?+
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.
Can multiple campus team members access one account?+
Yes — the simplest pattern is one shared account run by the central media team. Campus media leads drop their audio into a shared Drive or Dropbox folder, and whoever runs the account uploads and organizes everything in one place. Because the $19/month Church Plan is unlimited, adding campuses never changes the bill.
How do you tag transcripts by campus and service?+
Use a consistent file-naming convention before upload: campus (Downtown / North / South / Online / Espanol), service (8am / 10am / 11:30am / Saturday), plus series and preacher — e.g. 'downtown_10am_romans8_mike_2026-08-02.mp3'. The transcript keeps the name, so a plain folder search answers questions like 'show me every sermon by Pastor Mike from the Downtown campus on Romans 8.'
Can satellite campuses use the broadcast campus transcript for their own publishing?+
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.
What about campuses that have their own unique sermon?+
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.
Does this integrate with our church CMS or media platform?+
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, so attaching a transcript to a sermon entry is a copy-paste or file upload away.
How much does it cost for a five-campus church?+
A flat $19/month, same as a single-campus church. A typical five-campus network with one 35-minute broadcast message plus two unique campus sermons per weekend processes roughly 175 minutes per week, or 9,100 minutes per year — all covered by the unlimited Church Plan on one shared account. For context: hiring out the same volume from Rev.com (human transcription) costs roughly $1,090 per month.
Can we transcribe non-sermon content too?+
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?'
What's the onboarding process for a multi-site church?+
About 90 minutes of setup work from central media, all self-serve. Step one: create the account and set up a shared folder structure with a tag convention (campus, service, series). Step two: walk the campus media leads through the first weekend's upload-and-publish cycle — a 5-minute screen recording is usually enough. Most networks are fully running by their second weekend.

Run one transcript library across every campus

Centralized sermon transcription for multi-site networks. Two onboarding calls, one weekend rhythm, every campus searchable.

Start Free