A Subtitle Translation and Review Workflow for Teams

A single person translating a short video can keep everything in their head. Add a second translator, a reviewer, a deadline, and several languages, and the project quickly gets messy. Files named final, final2, and really-final-v3 pile up. Two people fix the same line in different ways. A name is spelled three ways across the film. Nobody is sure which version went to the client.

This guide describes a calm, repeatable workflow for subtitle projects with more than one person involved. It covers the roles, the stages, the documents you need, how to name and track versions, which checks to automate, and how to reconcile different people's changes without losing good work. It complements our article on comparing subtitle translations, which focuses on choosing between two versions of a line. Here the subject is the whole pipeline.

The stages of a subtitle project

Professional subtitle work usually passes through the same stages, whatever the size of the team.

  1. Preparation. Collect the video, script or transcript, and any reference material. Agree the style guide.
  2. Spotting and timing. Decide when each subtitle appears and disappears, either by creating a timed source-language file or receiving one.
  3. Translation. Translators render the text in the target language.
  4. Review. A second linguist checks accuracy and naturalness against the source.
  5. Quality control. A final check for technical and consistency errors, in a player, with the video.
  6. Delivery. Export the final files in the formats the client or platform needs.
  7. Feedback and archive. Handle corrections, and store the final files and decisions for the future.

Even a two-person project benefits from keeping these stages separate. The most common quality failure is to merge translation and review into one pass, so that the same eyes that wrote a mistake also check it.

Roles

Different projects use different job titles, but these functions need an owner.

Project owner. Decides priorities, keeps the schedule, and holds the master files. In a small team, this is whoever answers the client.

Translator. Produces the first target-language version.

Reviewer. Checks the translation against the source and the picture, and proposes changes. A reviewer should be a different person from the translator.

QC specialist. Performs the technical and consistency checks and the final playback review. In a small team, this can be the reviewer, but it should be a separate pass.

Terminology keeper. Maintains the glossary. Often the project owner or the lead translator.

One person can hold several roles on small jobs. What matters is that every function is performed on purpose, and that the final merge of changes has a single decision-maker.

The documents that prevent arguments

The style guide

A short written style guide settles hundreds of small disagreements before they happen. It does not need to be long. Cover:

  • Line length and lines per subtitle. For example, a maximum of 42 characters per line and two lines.
  • Reading speed and duration limits. See subtitle formatting best practices.
  • Italics rules: when to use them and when not.
  • Numbers, dates, and units. Write them out or use digits, and which format.
  • Dialogue dashes and speaker labels.
  • Punctuation and spelling variant. For example, British or American English.
  • Handling profanity, slang, songs, and on-screen text.
  • Whether to include sound descriptions. See captions vs subtitles vs SDH.

If a client supplies its own guide, follow that one, and add a note about anything it leaves open.

The glossary

List names, places, titles, product names, and recurring terms with the approved translation of each. Add notes such as "do not translate" or "use formal address". A glossary shared before translation starts prevents most consistency errors, and it saves the reviewer from repeating the same correction fifty times.

The reference pack

Give the translators everything that helps: a script, previous seasons or episodes, a description of characters and their relationships, and any prior subtitles. Context improves quality more than any tool.

Naming and version control

Most confusion comes from files, so name them with care.

A simple pattern is: project_episode_language_stage_version.srt, for example series_s01e03_es_review_v2.srt. Always include the language, stage, and a version number that only goes up. Never edit a delivered file in place; save a new version.

A few more habits:

  • Keep one master folder per language. Everyone works from the same location.
  • Keep stage files separate. The translator's version, the reviewer's version, and the final version are three different files. You will want to compare them.
  • Record decisions. A short change log, even a text file, saying what changed and why, makes later questions easy to answer.
  • Never work from email attachments. Attachments spread copies. Use shared storage.

Reconciling changes from several people

A review pass produces a second version of the file. Sometimes two reviewers each return their own. The question is how to merge them without losing good changes or accepting bad ones.

A side-by-side comparison does this efficiently. Load the base translation in the SRT Merger as File 1 and the reviewer's version as File 2. The tool aligns the two by timecode and shows you three kinds of rows: identical, different, and present only in one version. You skip the identical rows entirely, and go through the differences one by one, choosing the better line or editing it directly. Then save the result as a new version. To add a second reviewer, repeat with the saved file as File 1.

Some rules keep that process fair:

  • The project owner makes the final call when reviewers disagree.
  • Prefer the reviewer's version when it fixes a mistake, and the original when the change is only a matter of taste, unless the style guide says otherwise.
  • Add accepted terminology to the glossary immediately, so the same decision is not made twice.
  • Check timing after merging. A line chosen from one version may have different timing from its neighbours.

The same approach works to combine a human edit with an automatic first draft, as described in our guide to translating an SRT file.

Automated checks to run before delivery

A computer is better than a person at counting characters. Automate what you can, and leave the human attention for meaning.

Check for:

  • Lines longer than the limit, and more than two lines per subtitle.
  • Reading speed above the limit.
  • Durations that are too short or too long.
  • Overlapping cues and gaps that are too small.
  • Empty cues, duplicate cues, and numbering errors.
  • Invalid timecodes, such as an end before a start.
  • Characters outside the expected encoding, and double spaces.
  • Missing or unpaired formatting tags.
  • Inconsistent spelling of glossary terms, by searching the file for the wrong variants.

Subtitle editors include many of these checks, and a small script can do the rest. Run them after every merge, not only at the end.

The human review

Technical checks do not tell you whether a joke works. The reviewer's job is to compare the translation with the source and the picture.

A good review pass looks at:

  • Accuracy. Meaning, numbers, names, negatives.
  • Naturalness. Does it sound like something a person would say?
  • Register and character voice. Is each character consistent?
  • Cultural references. Are they carried across or explained?
  • Readability. Can it be read in the time?

Ask reviewers to give a reason for each change when it is not an obvious error. That feedback teaches the translator and prevents the same edits recurring in every episode.

The final QC pass

Do the last check in the same kind of player your audience uses, with the final video:

  1. Watch the first minute, a few scenes in the middle, and the ending.
  2. Check the first and last subtitle against the speech.
  3. Look for text that covers on-screen graphics.
  4. Confirm the files open in the target platform, and that special characters display correctly.
  5. Verify the file names, languages, and formats against the delivery specification.

Fix anything found, re-run the automated checks, and only then deliver.

Handling feedback after delivery

Clients and viewers will find things. Treat feedback as a short, simple loop.

  • Log every correction request in one place.
  • Apply it to the master file and create a new version.
  • Re-run the checks.
  • Update the glossary and style guide when the feedback reveals a gap.
  • Keep the previous version for reference.

Common problems and how to avoid them

Everyone edits the same file. Use separate files per stage and merge deliberately.

No shared terminology. Create the glossary first, and update it during review.

Review done by the translator. Use a second person whenever you can.

Quality checks only at the end. Run them after every stage.

Lost decisions. Keep the change log.

Overwritten files. Version numbers only go up, and delivered files are never edited.

Summary

A good subtitle workflow separates preparation, translation, review, quality control, and delivery, and gives each function a clear owner. A short style guide, a shared glossary, and consistent file names prevent most disputes. Automate the mechanical checks, reserve human review for meaning and tone, and use a side-by-side merge to reconcile reviewers' versions while the project owner keeps final say. With those pieces in place, a team can deliver consistent subtitles in many languages without the chaos.

Merge your own subtitle files

Compare two .srt files side by side and save the best lines as one file. It runs in your browser, so nothing is uploaded.

Open the SRT Merger