Table of contents

 

Source Material Provided	Dubbing Script (DS) SoW
Dialogue List (DL)	Requirements	Episode Title Treatment
Dialogue list events	Dubbing Script required content in TTAL format	Main Title Treatment
	Dubbing Script delivery
	Timeline expectations
	Validations
	Dubbing Script redelivery

 

 

Defining Scope of Work (SoW)

This Dubbing Script Scope of Work (SoW) outlines Netflix’s expectations and requirements when commissioning the creation and delivery of As Recorded Dubbing Scripts by Dubbing Studios. 

 

Source Material Provided

Along with the video, Netflix provides a Dialogue List (DL) to assist in authoring the dubbing scripts.

 

Dialogue List (DL)

The DL is a script of the original content. It contains a transcription of the audio and other elements of the content, all timed to match the video. If the content’s original language is not English, the DL also includes an English translation of the content. In such cases, it is referred to as Pivot Language Dialogue List (PLDL). 

In this Scope of Work, the terms Dialogue List and DL are used to refer to the script of the original content, regardless of its source language. 

You can download the Dialogue List in TTAL format from the script authoring request page in the Authoring tool. It’s also available in Excel format in Backlot under the Download Materials tool of the assigned source request.

 

Dialogue list events

Each section in the DL delimited by in and out timecodes is called an event. Events appear as rows when viewing the DL in Excel, as shown in the screenshots below.

 

For more information about the dialogue list, see DL Style Guide.

We encourage all NP3 dubbing studios to familiarize themselves with the DL/PLDL style guidelines as they define what these assets should look like.

 

Dubbing Script SoW

 

The As-Recorded Dubbing Script (ARS) is a transcription of the audio and Forced Narratives (FN) in the target language of the secondary audio. 

The ARS includes all discernible audio and text elements needed for viewers who watch the dubbed version in the target language to understand and follow the story.

Netflix considers the as-recorded dubbing script to be a live asset—it's actively used and updated, not just stored for reference—for each secondary audio. We require delivery in the TTAL format, which is a structured format.

For more details about the requirements for Forced Narratives in dubbed content, please refer to the articles Forced Narratives Guidelines and Style Guide for Dubbing and Forced Narratives Linguist Guide.

 

Requirements

• Dubbing script format: You must deliver dubbing scripts in TTAL format.
• Timing: Make sure all events in the dubbing script match the timing in the final video. 
  • Matching duration: The duration of events should match the duration of the audio corresponding to the event's text.

 

 

• Event’s in and out timecodes: Each event's timecodes (start and end times) should be timed to the first and last spoken word the event transcribes. 
• Pauses in dialogue: Whenever there is a pause in the dialogue that lasts around two seconds or more, always use a new event when the dialogue continues. Reactions and efforts count as dialogue pauses.

 

 

•  Voice-over and Polish Lector styles: Time the events to the original dialogue heard in the dubbed audio. Use the timing of the Dialogue List as a reference.
  
  

• Transcription of audio: The written version should match the final audio word for word.
  • Discernible dialogue in a foreign language not meant to be understood by the audience should not be included in the as recorded script.
• Spelling and Punctuation: The dialogue in the events should be written correctly in sentence case and with proper punctuation, even if a sentence is split across multiple events. 
  • Do not use ALL CAPS.
  • Typographical errors: The text in the events should not have any spelling or typing errors unless they are intentional and match the audio.
  • Symbols in the event: Intentional symbols used to indicate pause or other instructions can be present in the event as long as they are one of the symbols listed here:
    • Backward and forward slashes ( '/' and '\' )
    • Circumflex symbol ( '^' )
    • Less-than and greater-than ( '<' and  '>' )
    • Pipe symbol (‘|‘)
  • KNP names should be spelled correctly as per the KNP. If phonetic spelling is needed, enclose it in parentheses ( ) or brackets [ ] next to the properly spelled name.

 

• Episode Title (ET) treatment 

When the episode title appears on screen or is mentioned in dialogue, translate it according to the guidelines below.

• • First, check Terminology to ensure that there isn’t already an approved episode title for your language. You should use it if one exists.
  • If there is no translation in Terminology, or the translation doesn’t work for lip-sync (ET is mentioned in dialogue):
    • Translate the ET freely after watching the episode to gain a deeper understanding of the episode's context.
      • If the episode title is redundant (i.e., no translation needed) in your language, delete the event before delivery. 
    • If watching the episode doesn’t provide sufficient context for accurately translating the ET, preserving the original intent, request the original episode title rationale from the Netflix representative.
    • Important: If you need to retranslate the ET for lip-sync requirements, flag it to the Netflix representative.
    • Ensure all events with the episode title are correctly tagged in your dubbing script.
      • The tags should have been carried over from the DL. However, it’s still your responsibility to ensure they are present in your ARS file as needed.
        • On-Screen Text - Episodic Title: Use it when the ET appears on screen.
        • Episode Title in Dialogue: Use it for any instance of episode title usage in dialogue.
          • Use this tag only when the full episode title is mentioned. Do not tag partial matches.
    • You don’t need to enter your episode title translation in the KNP. The new ET translation will be added automatically to the KNP after it has been reviewed.
  • For non-English titles, the English translation of the ET should be present in the PLDL when the ET appears on screen or is mentioned in the dialogue.
    • English dubbing studios should utilize the English ET from the PLDL, adapting it if needed for lip-sync (when mentioned in dialogue).
    • If the episode title isn’t translated in the PLDL, English dubbing studios should check for the approved episode title in Terminology and implement it accordingly. 
      • Do not freely translate episode titles into English.
    • Dubbing studios of all other target languages should reference the English ET from the PLDL when translating the ET into their language or the Terminology tool for the approved English episode title.

• Main Title (MT) treatment

  When the main title appears on screen or is mentioned in dialogue:
  • • Do NOT translate the main title freely. Always use the approved MT translation found in Terminology.

• Forced Narratives (FN): Events that need forced narratives should be tagged correctly, and their on-screen position should be identified. Refer to the Forced Narratives Linguist Guide for instructions.
  • Translating content for Forced Narratives: Events that translate content for the dubbed audio's FN file should follow the FN style guide for Dubbing and the target language FN style guide (if one exists).
  • Selecting events for FN: If project-specific instructions are available, refer to them when identifying events for the FN file.
• Non-essential events: Events should not be empty, redundant, or unnecessary. 
  • Remove from the dubbing script events that aren't necessary.

 

 

• Reactions and efforts: Any reactions and efforts that are included in the event’s dialogue field must be enclosed in parentheses ( ), brackets [ ], or curly brackets { }. There are no exceptions to this rule.
  • Anything that is not heard or seen on-screen, such as instructions and explanations, should be in the annotation field or enclosed in parentheses, brackets or curly brackets.
  • Time the events with reactions and efforts to dialogue: Do not time events to begin or end with a reaction or effort. Events should be timed based on the first and last words spoken.

 

 

• Character name (SOURCE column): Each event should represent the dialogue of one individual character.
  • Do not list multiple characters in the same event.
  • Every event should be attributed to the correct character.
  • The character name NONE should be used only for on-screen text events.
  • Polish Lector character: Scripts created in the Polish Lector style should attribute the events to the lector voicing the words. Events selected for forcing (not voiced by the Lector) should be attributed to NONE (as indicated above) if they’re on-screen text or to the character voicing the dialogue.
  • Dialogue events selected for forcing (foreign dialogue, archival, songs) should be attributed to the character speaking the dialogue.
    • Polish Lector: See the previous bullet point.

 

• Crowd/group sound design (WALLA): If you're recreating sounds from a crowd or group from the original version, always use the character name WALLA when the dialogue is indistinct. 
  • WALLA represents the indistinct murmuring noise of a crowd.
  • The character name should start with WALLA, even if this term isn't used in your language.
  • You can add other words to WALLA to help identify the type of crowd or group sound you need. But you must separate WALLA from other words using a dash ( - )  or colon ( : ): 

 

• Discernible dialogue: Dialogue that the audience is clearly meant to understand should be attributed to the character that speaks it (not WALLA).
• Unison dialogue or chants: When named characters speak or chant together discernible dialogue, don't attribute it to WALLA. Use the characters’ names instead.
  • When multiple characters say the same dialogue simultaneously, duplicate the event, once for each extra character, and attribute the new events to each character voicing the dialogue.

 

Dubbing Script delivery

The final dubbing script should deliver to the As Recorded Dubbing Script source request in Backlot, and can be done in two different ways:

• Direct upload of a TTAL file to fulfill the source request.
• Using Netflix’s Script Authoring tool.

To learn more about authoring Dubbing Scripts in Netflix’s Script Authoring tool, see:

Script Authoring Tool User Guide

CLP | Dubbing Script Authoring Workflow (requires sign-in)

 

Timeline expectations

Fulfillment of the As Recorded Dubbing Script source request is expected three calendar days before the secondary audio. 

If the dubbing partner cannot meet any of the due dates for any reason, they must notify Netflix immediately.

 

Validations

Scripts created in or uploaded to the Authoring tool are checked during their authoring and proofing steps. Each step can’t complete until all validation blockers are resolved.  

Dubbing scripts uploaded directly to Backlot are automatically inspected to ensure they comply with the TTAL requirements and don’t have major problems. If a file fails these checks, it must be fixed and redelivered. 

Dubbing partners should use the TTAL Validator on any files that need to be redelivered. This tool will show a list of problems found in the files. All of these issues must be fixed before a file can be uploaded to Backlot and for the As Recorded Dubbing Script source request to be considered fulfilled.

For a list of errors and possible solutions, refer to the  As Recorded Dub Script Validation Guide in PHC.

 

Dubbing Script redelivery

If changes are needed to the Forced Narrative (FN) file or if the content of the script doesn’t meet the requirements listed in this document, the as-recorded script will need to be updated and redelivered. 

These changes might be due to Quality Control (QC), customer complaints, creative changes, or any other reason to give the best experience to the viewers.

No matter which tool was used to create the as-recorded script or how it was first delivered, any updates or corrections must be done in Netflix's Script Authoring tool.

 

For information, see Forced Narratives Linguist Workflow Guide.

 

 

 

Change log

2025-09-24

• Added the Episode Title and Main Title treatment section.
• Removed the sections: Dubbing Script required fields in TTAL format and the Appendix section.

 

2024-09-17

• Updated the timeline expectations from five calendar days to three calendar days.

 

2024-02-08

• Added note about dubbing script and as-recorded dubbing script meaning the same thing at Netflix.
• Reformatted requirements for clarity.
• Added a few extra requirement bullet points for clarity and avoid misinterpretation.
• Added screenshot examples for some requirements.

2023-11-06

• Explicitly called out the use of dash ( - ) when creating walla characters to help indicate that the event is walla.

2023-10-17

• Expanded the Appendix section with more examples. 

2023-07-14

• Requirements: 
  • Clarified metadata and added bullet points on reactions and efforts.
  • Expanded the explanation on the use of the character WALLA.
• Updated the required content in TTAL section.
• Added Appendix section

Was this article helpful?

15 out of 21 found this helpful