Guidelines International Moves 32-Language Production Off One Person’s Desktop With Files.com

Guidelines International Ministries has been on the air since 1963, when it launched the first daily five-minute program in Christian radio. That program is still running, which makes it the longest-running five-minute commentary in the field, and the ministry built around it now produces audio and video devotionals that broadcast partners air in more than 100 countries. The reach is deliberate: Guidelines aims its programming at the places conventional missions cannot go, including warzones, refugee camps, and regions where the native church is small or absent.

Reaching those listeners means reaching them in their own language, and Guidelines does not translate in-house. English scripts and audio masters go out to regional production partners across Africa, Eurasia and Central Asia, and Europe. Each partner translates, records, and produces a local-language version, then sends the finished program back. Guidelines then distributes that programming to the radio stations and networks that air it.

Nothing the ministry makes reaches a listener until it has left the building, been remade by an outside organization, and come home again. That round-trip is the ministry's entire supply chain, and it used to run by hand.

With Files.com as the hub, Guidelines replaced a hand-carried exchange with a loop that partners and stations drive themselves. Thirty-two languages are in active translation at once, with three media assets in simultaneous multi-language production, all on one platform administered by one person.

The Middleman Was the Security Model

The library of .wav audio masters and English scripts lived on an on-premises server, and files moved when someone at Guidelines moved them, using desktop transfer tools such as Cyberduck. Every outbound script, every returning translation, every program delivered to a station passed through one person's hands.

The obvious fix, giving partners direct access, was the dangerous one. A translation partner cannot deliver finished work without write access, and unscoped write access to a shared library is the ability to damage it: overwrite a master, or delete another language's finished programs. With 19 regional partner organizations on three continents, some producing ten or more languages each, an open server would have put every partner one mistaken upload away from another partner's work. Hand-carrying the files was slow, but it was also the access control. The bottleneck and the security model were the same person.

The ministry was adding languages and putting multiple media assets into production at once, with a stated goal of translation into 100 languages within two years. A roster heading toward triple digits cannot pass through one person's desktop.

What replaced the manual exchange had to do several things at once. It had to give every partner and station direct access from anywhere in the world, over a browser or a standard SFTP client. It had to show each partner only the languages it owns, with write access scoped to exactly those folders. It had to split the largest partners further, so an organization producing ten languages holds region-specific credentials rather than one master key. And it had to keep an archival copy current without anyone maintaining it. Guidelines selected Files.com to be that hub.

One English Source Folder, a Folder for Every Language

The library came off the on-premises server, and Files.com became the primary repository. A Files.com remote server sync now pushes everything to SharePoint, so the archival copy maintains itself.

The round-trip runs through a single structure. English masters and scripts sit in one curated source folder that every production partner can download from. Each language has its own folder, and a partner uploads finished productions into the folders for its languages and nowhere else. Radio stations and networks log in and pull finished programming straight down to their own systems.

Files.com user groups and folder-level permissions are what make that structure safe to open up. Brandon Neal, the ministry's Director of Media Services, built the groups and permissions himself: each translation partner is scoped to see and write only its own language folders, and the largest partners are segmented by region, so a ten-language organization holds several narrow logins instead of one broad one.

“It limits the potential issues they can cause, because if someone is uploading content, they have to have writing ability, which also means they can hose a lot of things if they choose to.”

Partners and Stations Drive the Loop

• Partners and stations read close to 3,000 files a day from the platform, peaking above 3,200. Because they pull those files themselves, nobody at Guidelines pushes a single one of them.
• A partner uploading a finished translation can touch only its own language folders, so an accident is contained to the work that partner already owns and can never reach another language or another partner.
• Adding a language is a folder and a permission, and adding a partner is a scoped login. The stated path from 32 languages toward 100 asks for no new infrastructure and no new staff.

Designing Access Instead of Carrying Files

Neal's work is designing access rather than carrying files: partners take the English masters, return the translations, and stations collect the finished programs, each inside a boundary that makes the mistake they might have made impossible.

A ministry built to speak to people in their heart language found that a many-to-many translation loop did not need a bigger team. It needed each partner's write access scoped to exactly the folders that partner owns, and Files.com is where that boundary is drawn.