How AV Teams Track Revision Rounds Across a Dozen Docent Recordings at Once

Ask any AV coordinator prepping a museum opening how many docent recordings they have in flight at once, and the answer is rarely a comfortable number, it is usually somewhere between eight and twenty audio-guide videos, each one at a different stage of revision, each one owned by a different narrator or curator, and each one theoretically tracked on a spreadsheet that stopped being accurate sometime around Tuesday. We see this constantly with institutions gearing up for an opening: someone asks a simple question, which docent guides are actually locked and ready to load onto the handheld devices, and the honest answer is that nobody in the room actually knows for certain, because the spreadsheet says one thing and the shared drive folder says something slightly different.

The Spreadsheet Was Never Built for This

A shared spreadsheet works fine when you are tracking five things with two states, done and not done. It falls apart almost immediately once you are tracking fifteen docent recordings, each moving through four or five review stages, script approval, first recording pass, curator content check, final audio polish, and technical sign-off, with three or four people updating status by hand at different times of day. Someone finishes a revision, forgets to update the row, and now the spreadsheet is actively lying to the rest of the team about where things stand. We've watched this play out on a single Google Sheet with sixty or seventy rows once you count every revision round as its own line, color-coded cells that were supposed to mean something specific until three different people started using yellow for three different reasons, and by the second week nobody trusted the color coding enough to actually rely on it without opening the shared drive to double-check the file itself.

The catch here is that a stale spreadsheet is often worse than no spreadsheet at all, because it creates false confidence. A coordinator glances at a row marked "final," assumes the recording is ready to load, and only discovers three days before opening that the curator actually requested a content change two weeks ago that never got logged anywhere except a since-deleted email thread.

We hear a version of this same story from almost every AV lead we talk to who has run a large docent program before switching to a shared review system. One coordinator described her old process as "the spreadsheet is right until the moment someone forgets to touch it," which is basically the honest state of any manually updated tracker once more than three or four people are contributing to it. The spreadsheet is not the actual problem, right, the problem is that status living separately from the file itself always eventually drifts, because updating two things in two places at once is exactly the kind of small extra step that gets skipped when everyone is already stretched thin two weeks out from an opening.

What "At a Glance" Actually Needs to Show

For a docent recording program to feel manageable instead of chaotic, a coordinator needs to look at one screen and immediately answer three questions: which guides are locked and ready, which are still in active revision, and which ones have been sitting untouched long enough to be a scheduling risk. That is a genuinely different need than a general project management tool, because the unit of work here is a specific version of a specific audio or video file, not a generic task card.

We built PlayPause's project views around exactly this, a status that is tied directly to the file and its approval history rather than a manually updated label that someone has to remember to change. When a docent recording gets its final sign-off inside the review thread, the status updates itself, so the dashboard a coordinator glances at every morning is never more than a few minutes out of date.

Structuring a Dozen Recordings So Nothing Gets Lost

The teams who handle this well tend to set up each docent guide as its own tracked project within a shared workspace, so a curator reviewing gallery three's recording never has to wade through notes on gallery nine to find what they need, while the AV coordinator overseeing the whole opening can still see all twelve at once.

This mirrors how Multi Projects and Batch Uploads work together in practice, a coordinator can drop a dozen new recordings in at once as raw files come in from the narrator, and each one lands in its own tracked space automatically rather than needing to be manually filed and labeled one at a time.

Why Batch Handling Matters More Than It Seems

Docent recordings tend to arrive in waves rather than one at a time, a narrator finishes a session and delivers six files at once, or a curator sends back revision notes on four guides in the same afternoon. A workflow that only handles one file smoothly and turns into manual busywork the moment six files land at once is going to buckle right at the point in the schedule when volume is highest, usually two to three weeks before opening.

This is also where a smaller detail matters more than people expect going in, naming consistency. When twelve guides are each producing multiple revision passes, a loose file naming convention across a shared drive turns into a genuine liability fast, because "Gallery7_Final_v3" and "Gallery7_FINAL_v3_actual" can both exist at once with no way to tell which one a reviewer actually approved. Keeping every version of every guide tied automatically to its project, rather than relying on a human to name files consistently under deadline pressure, removes an entire category of avoidable mistakes.

When a Guide Needs a Language Pass Too

A detail that catches a lot of first-time opening coordinators off guard is that a single docent stop rarely means a single audio file. Bigger institutions running bilingual or trilingual programs are tracking an English guide, a Spanish guide, and sometimes a Mandarin or French guide for the same gallery stop, and each language version goes through its own recording and revision pass even when the underlying script barely changes. We worked with one institution prepping a touring exhibition that needed English, Spanish, and Mandarin guides across all fourteen stops, which meant forty-two individual audio files in flight at once instead of fourteen, and the team's first instinct was to track each language as a separate spreadsheet tab, which just multiplied the exact problem described above by three.

The fix that actually worked was keeping every language version of a given stop inside that stop's own project space rather than splitting by language across separate trackers, so a coordinator checking on gallery seven sees the English, Spanish, and Mandarin status side by side instead of hunting across three different files to piece together whether the whole stop is actually ready. It also catches a specific kind of mistake that's easy to miss otherwise, a curator approves an English script change but the Spanish translation never gets updated to match, and the stop goes out with two versions that say slightly different things. Keeping language versions grouped rather than scattered means that gap is visible the moment someone glances at the project, instead of surfacing three months later when a bilingual visitor mentions the discrepancy to a docent.

Telling Locked From Still-In-Revision Without Asking Anyone

At the end of the day, the entire point of a status system is that nobody should have to interrupt someone else's afternoon to ask "hey, is the gallery seven guide done yet." The answer should be visible without a Slack message, without a hallway conversation, and without waiting for someone to remember to reply to an email.

• Every docent guide has one current version, not three floating around with similar file names
• Status reflects actual sign-off, not a manually typed label someone forgot to update
• Revision history is visible so a coordinator can see how many rounds a guide has been through
• Reviewers assigned per guide so notes go to the right curator, not a shared inbox
• Locked guides are clearly separated from ones still awaiting a final pass

Handling Revision Rounds That Come From Multiple Directions

A docent recording rarely gets notes from just one source. Curatorial wants a factual correction, the AV lead wants a pacing adjustment, and sometimes accessibility flags that a described visual reference needs adjusting, similar to what we cover in how museums review audio description and captions for ADA-compliant exhibit video. When those three sets of notes arrive separately and get worked through in sequence instead of together, a single guide can burn through five or six revision rounds where two would have covered it if everyone weighed in on the same version at once.

We tell AV teams who ask us this to insist on parallel review from the start of a docent recording program, not sequential, because the time lost reconciling contradictory rounds of notes adds up fast across a dozen guides, and it is almost always avoidable with one shared thread instead of three separate ones.

Keeping the Whole Program on Schedule, Not Just Individual Guides

A single docent recording being a day behind is not a crisis. Four of them being quietly behind at the same time, discovered only when someone finally cross-checks the spreadsheet against reality a week before opening, is exactly the kind of compounding schedule risk that sinks an install week. Our related piece on the caption QC checklist museum AV teams run before a hard opening date covers a similar compounding-timeline problem on the caption side, and the underlying lesson is the same: the earlier a status gap gets caught, the cheaper it is to fix.

What We Tell AV Teams Who Ask Us This

Basically, the museums that get through a dozen-plus docent recordings without a chaotic final week are the ones who stopped trusting a manually updated spreadsheet the moment they had more than a handful of guides in flight at once. According to the Motion Picture Editors Guild, version control and clear review workflows have become as central to modern production as the creative work itself, and that holds just as true for a museum's audio guide program as it does for a feature film. We see this pattern repeat at almost every institution we talk to during opening prep: the AV team that trusts a real-time dashboard tied to actual file status walks into install week knowing exactly where things stand, and the team still relying on a spreadsheet is the one making frantic phone calls to confirm what should have been visible at a glance.

If you are tracking a dozen or more docent recordings across curatorial, AV, and accessibility reviewers and the spreadsheet is starting to feel like a liability, it is worth seeing what a status board tied to the actual files looks like. Explore PlayPause's pricing and get every docent guide's real status in one place before your next opening.