Subtitle Delivery Package: What a Client Actually Needs

A complete subtitle handoff identifies the matching video, language, review status and intended destination for every file. Agree on whether the client needs a clean video, burned-in version, timed-text sidecar or editable project. Delivering several vaguely named files is not the same as delivering a usable localization and accessibility package.

Documentation basis: Premiere caption workflow; W3C WebVTT specification. The recommendations below are editorial analysis and original teaching exercises, not a hands-on product benchmark or a forecast of search performance.

What should be agreed before captioning starts?

Confirm language, transcription versus translation, sound descriptions, speaker labels, format and destination. Ask who approves names and specialized terms. These decisions affect the work and should not be discovered after a styled video has already been exported.

How should files be named?

Use a consistent project identifier, video version, language and deliverable type. Keep draft and approved outputs separate. The client should be able to identify the correct caption file without opening every file or guessing which of several final versions is current.

What should a delivery manifest contain?

List each file, its purpose, the matching video and any known limitation. Note whether captions are burned in or selectable and whether styling must be recreated elsewhere. Include the approval status and reviewer rather than implying unreviewed automatic text is final.

How do you verify the package before sending?

Open the video and each requested text format outside the authoring tool. Check the beginning, middle and end, plus difficult names and long cues. Test an import in the destination when possible. Confirm that no private working files or unnecessary source material are included.

What happens after a late video revision?

Assess every caption derivative against the new cut. A small inserted intro can shift the entire file; a removed sentence can create local mismatches. Update the manifest and version names together so the client does not combine the new video with old subtitles.

A practical exercise

Package a clean MP4, a captioned MP4 and one approved subtitle file with a short manifest. Ask a colleague to identify which files belong on a website and which belong in a social post. If they need clarification, improve the names and purpose descriptions before delivery.

Before you decide

• Agree on deliverables early.
• Tie every file to a video version.
• Verify the package outside the editor.

Sources and scope

Sources checked October 24, 2026. Follow the current documentation for your exact model, application, account and destination.

• Premiere caption workflow
• W3C WebVTT specification
• W3C caption guidance

SUBTITLE DELIVERY PACKAGE: WHAT A CLIENT ACTUALLY NEEDS
Original Creator Lane decision worksheet | 2026-10-24

TASK
Audience / project:
Required outcome:
Current workflow and its specific limitation:
Options actually available without a new purchase:
Source material and permission:

DECISION QUESTIONS
What should be agreed before captioning starts?
Your evidence / answer:
Unresolved detail / owner:

How should files be named?
Your evidence / answer:
Unresolved detail / owner:

What should a delivery manifest contain?
Your evidence / answer:
Unresolved detail / owner:

How do you verify the package before sending?
Your evidence / answer:
Unresolved detail / owner:

What happens after a late video revision?
Your evidence / answer:
Unresolved detail / owner:


PRACTICE BRIEF
Package a clean MP4, a captioned MP4 and one approved subtitle file with a short manifest. Ask a colleague to identify which files belong on a website and which belong in a social post. If they need clarification, improve the names and purpose descriptions before delivery.

ACCEPTANCE CHECKS
[ ] Agree on deliverables early
Evidence:
[ ] Tie every file to a video version
Evidence:
[ ] Verify the package outside the editor
Evidence:

RESULT LOG
Option / exact version / account or interface:
Date / source URLs checked:
Input / settings / output version:
What was actually tested (leave blank if not tested):
Accepted results / failures / correction time:
Actual charges, if any (do not estimate as measured):
Privacy / permissions / delivery checks:
Decision and main limitation:
Next action / owner:
Recheck trigger:

REFERENCES
Premiere caption workflow: https://helpx.adobe.com/premiere/desktop/add-text-images/insert-captions/about-captions.html
W3C WebVTT specification: https://www.w3.org/TR/webvtt1/
W3C caption guidance: https://www.w3.org/WAI/media/av/captions/