Translate a Series Pitch Without Promising a Different Show

By pitch.dogFoundation13 min read20 September 2026

Television

The line that matters most in your pilot may be the one where nothing changes but the way someone is addressed. She has called him Tomas for twenty years. Then she calls him Officer Renn, and the words around it stay almost the same.

Translated plainly, that can arrive in English as Then I'm asking you — fluent, accurate-looking, gone. The English reader sees a woman repeat herself. They don't see a relationship close.

Translating a series pitch means making the same series understandable to an English reader, not quietly selling an adapted one. Three habits do most of that work:

Find the passages where the meaning lives in the relationship rather than in the words.
Write down what the wording does before you go looking for an English equivalent.
Keep any change to the show itself in a separate column, labeled as a proposal, and send it back to whoever owns the show.

None of this requires English to have the same machinery as your language. It usually doesn't. That's the job.

The pitch reader needs the show, not the performance

A pitch document is read. The series is performed. Those are different readers with different needs, and confusing them causes two opposite mistakes.

The first is writing sample dialogue as if it were a subtitle: every line polished to its final shape, nothing explained, the reader left to infer a social world they've never been inside. The second is the reverse — burying a scene under so much annotation that nobody can hear anyone talking.

The useful middle is dialogue rendered as dialogue, plus one short line telling the reader what the exchange is doing. Not a footnote on every name. One line, placed where the distinction actually turns the scene.

And there is no single English version that works for every reader. A line that lands for someone in London may sit differently for someone in Lagos or Manila. Choose for the reader you're actually writing to, and say who that is.

Mark the passages where the words aren't the meaning

Don't translate the whole pitch. Mark it.

Walk through the proposal and stop where a fluent English version would change something the series uses. In practice the list is short, and it concentrates in a few kinds of passage:

A form of address that shifts inside a scene.
A title or institutional role whose authority is specific — what the person can decide, what they're bound by, who they answer to.
A joke, and specifically who is being laughed at.
A formality level that tells you what these two people are to each other.
A description whose whole job is how something is said: an official's way of saying "we'll see," a mother's refusal to use a name.

Then separate the two languages you're actually working with. There's the language the show is performed in, and the language the pitch is read in. A pitch reader doesn't need a line an actor could say on set. They need to know what passes between these two people and how bad it is. Keep those jobs apart and you'll stop trying to make pitch dialogue carry a performance it can't, and stop apologizing for a pitch that reads better than a script.

Write the function before you choose the equivalent

For each marked passage, write four things before you touch English.

Who is speaking, to whom, and what were they a minute ago. Not "mother and son." Something like: she trained him, she fed him for two summers, he has used her first name since.
What the wording does. Names a distance. Invokes an office. Closes a door. Makes a group laugh at itself. Hands someone an obligation they can't refuse without insulting the speaker.
What the pitch reader must understand by the end of the paragraph — not the line, the paragraph.
What you would accept losing.

If you can't fill in the second one, you haven't found the passage yet. Keep walking.

This is also where a literal gloss earns its place and stops. A word-by-word rendering is honest working material: it shows you where the grammar is doing the work. It isn't the answer, because a reader outside the language can't feel a formal pronoun even with a tag explaining it. Glosses go in your notes. The function note is what the English gets built from.

One line, three renderings

Take the invented series I'll use through the rest of this piece. Call it Ninety Days, a drama about a district licensing office and the market it regulates. Yusra Bahri has held a stall permit for more than twenty years; she sells cooked food in the covered market. Tomas Renn is the district's licensing officer, and twenty years ago he spent two seasons working her stall, learning to cook from her. She has called him Tomas since.

Market permits are inspected on a ninety-day cycle. Yusra's stall has a drainage problem at its connection. Nobody thinks she's negligent, Tomas included. The licensed contractor's next available date is eleven days after her renewal date, and the committee that can note an extension meets monthly, after that. If renewal lapses, she applies again in the next annual allocation round. So the scene isn't about fault. The calendar is the antagonist, and Tomas is bound by it.

She asks him, the way she always has, to sign it anyway. He says he can't. Then she stops.

A literal gloss, kept exactly as the source has it:

YUSRA: Then I am asking [formal you], Officer Renn.

Everything is there, and a reader who doesn't know the language learns nothing from it. The tag tells them a rule exists. It doesn't let them hear the moment the rule gets used.

The smooth rendering, the kind an editor produces on a fast pass:

YUSRA: Then I'm asking you.

Clean, quick, and failing twice, for two separate reasons. The first is ordinary: the title is gone. English has titles, so that is a slip rather than a limitation of the language. Put it back — Then I'm asking you, Officer Renn — and the second failure is still there. She is still addressing him as you; the title hangs off the end of the request instead of doing the addressing. The reader gets a woman repeating herself with more emphasis. The switch hasn't happened.

A rendering chosen from the function. In English the distance doesn't live in the pronoun, because English doesn't have that pronoun. It lives in the name, and the name has to take over the address:

YUSRA: Then I'm asking Officer Renn.

TOMAS: Yusra.

YUSRA: Officer Renn.

With one line in the pitch to carry it: She has not called him Officer Renn in twenty years.

Nothing about the series has changed. Same relationship, same stakes, same refusal. English is simply carrying the register on a different part of the sentence, which is a translation decision, not an adaptation.

Notice which direction the switch runs. It would be tidier if the officer went cold and she stayed warm — the powerful party withdrawing. Instead the person with less power formalizes the relationship. It works as a rebuke and as self-protection at once: if he refuses her as Tomas, that's a betrayal; if he refuses her as the officer, that's a rule. Describe the scene to a translator with that direction backwards and the English will be coherent and wrong. It will read like a woman being turned away by a bureaucrat, when the scene is about her deciding to stop letting him be Tomas for the length of one sentence.

That rendering still costs something, and the cost belongs in your notes rather than in a smoother line. In some languages a switch like this also changes how the speaker talks about her own actions — she lowers herself in the same breath as she raises him. An English name can't carry that. If your language works this way, the English will preserve who is speaking to whom and lose the speaker's self-positioning. Say so in the brief rather than hoping nobody notices. Whether your language does this is a question for someone who reads it well; don't take it on faith from a general piece of writing, this one included.

One more caution about that explanatory line. A cue can become a way of explaining a scene instead of translating it. In a shooting script that would be a real problem; the dialogue should do the work. In a pitch it isn't, because the pitch exists to make the reader understand, and the reader will not be in the room when the scene plays. Put the cue in the pitch. Then put a separate note in the same brief saying how you expect the switch to land on screen without it. Two documents, two jobs.

A joke has a target, and the target is part of the premise

Among the traders in Ninety Days there's a running joke about the extension committee, and it's aimed at the traders themselves — at how long they have all been saying the same thing about it without once writing to it. It's the joke a group makes about its own habit. That's part of what makes the market feel like a place with an inside.

Now put that joke into English by turning it on the office — lazy officials, a committee that never meets. Funnier, probably. Also a different show. The office is now the butt of it, the traders are its victims, and the internal loyalty among them has evaporated. You kept the laugh and changed what the series believes about its own people.

Mark a joke's target the way you marked the address: who says it, who is in the room, who is supposed to wince. If the only English version that gets a laugh moves the target, that isn't a translation problem you solve by trying harder. It's a change you either accept with the creator's agreement or leave in the original.

Some proposed fixes are adaptations in costume

The most convincing suggestions in a translation pass are often not translation at all. Two show up again and again.

Swapping a role for one English readers know. Somebody will suggest that the licensing officer become a small-business lender, a city clerk, or a landlord. Each swap changes what the character can actually do. A lender has contractual discretion; if Tomas can simply say yes, the scene becomes about a hard-hearted man, and Yusra's problem is his character rather than a rule. The district officer's power is bounded in a specific way — a written cycle, a scheduled committee, a contractor's calendar — and that bound is the engine of the scene. Keep the role, and spend a sentence explaining the role instead.

Deleting the shared history. The other tempting fix is making Yusra a stranger: a cleaner scene, no twenty years to establish, and the switch becomes a formality between two people who never knew each other. Which removes the only reason the line hurts.

Neither suggestion is stupid. Both are changes to the series, and they need the person who owns the series to decide, not a translator trying to make a paragraph read well. That's the line the whole method exists to hold: fluency is not authority.

Keep the sample dialogue honest about what it is

When you put dialogue in a pitch, say what it's doing. One sentence buys a lot of freedom:

This shows the relationship and the turn in it. It isn't a subtitle, a dub, or the final script.

That sentence does two things. It stops a reader treating an English rendering as a locked creative choice, and it frees you to write dialogue that communicates instead of dialogue that could be performed. You're allowed to be clearer than the finished show will be, because the finished show has actors, timing, and a camera.

It also keeps your own team honest. Once a line is in an English pitch, it has a way of becoming the line — quoted in meetings, pasted into a deck, treated as settled. Labeling the sample costs nothing and prevents an accident.

The brief you hand over

Keep one document, and keep the columns apart. For each marked passage:

Passage. The source, or a description of it, in the form the creator has approved for reproduction.
Function. The four notes from earlier, compressed to a sentence or two.
Proposed English. The rendering, plus the cue if it needs one.
What it preserves. Who is speaking to whom, and what shifts.
What it costs. The thing English can't carry.
Status. Settled translation, or proposed adaptation.
Decision owner. Creator for anything touching role, relationship, setting, or joke target. Translator for register mechanics, in consultation.

The status column is the one people skip, and it's the one that matters. A brief where "translation" and "proposal" share a column will produce a show nobody decided to make.

Two habits keep the document usable. Review the paragraph after every edited line, not just the line, because a locally smooth phrase can quietly change the promise the surrounding page is making. And when one English rendering can't carry every function of the original, write down that it can't, along with who chooses which function matters. A brief that records a real disagreement is more useful than one that resolves it by accident.

What this method won't settle

It won't tell you what your own language is doing. That has to come from someone who reads and speaks it — ideally a translator who can explain their choices and not just deliver lines.

It won't give you one English version that works everywhere. There isn't one, and a pitch claiming otherwise will read as flat in exactly the places it tried to be precise.

And it won't settle rights, format approval, or a localization plan. This is about making your existing proposal legible to an English reader without moving the show. Whether the series travels, gets remade, or gets sold into a territory is a different job with different owners.

The whole thing comes down to the line where nothing changes but the way someone is addressed. If your English pitch still has Yusra saying Then I'm asking you, you translated the words and lost the scene. Put the name back. Put in the sentence about twenty years. Then hand the rest to the person who made the show, with the status column filled in and the proposed changes called what they are.

Frequently asked questions

How is translating a series pitch different from adapting the show?

Translating makes the same series understandable to an English reader; it should not quietly sell an adapted one. Changes to role, relationship, setting, or joke target are proposals for the person who owns the show, not translation decisions.

What should I write down before choosing an English equivalent for a marked line?

Write four things: who is speaking to whom and what they were a minute ago; what the wording does; what the pitch reader must understand by the end of the paragraph; and what you would accept losing. If you cannot fill in what the wording does, you have not found the passage yet.

Why can 'Then I am asking you' be a poor rendering even when it is fluent?

It loses the title and leaves her addressing him as you, so the switch has not happened; the reader sees a woman repeating herself. The chosen rendering moves the distance to the name: 'Then I am asking Officer Renn,' with a cue that she has not called him Officer Renn in twenty years.

What is the risk of making a joke funnier by aiming it at the office?

It changes the show. The original joke is aimed at the traders themselves about their own habit, which helps the market feel like a place with an inside. Turning it on the office makes officials the butt and traders victims, and the internal loyalty among the traders evaporates.

What can this method not settle?

It will not tell you what your own language is doing; that requires someone who reads and speaks it. It will not give one English version that works everywhere. It also will not settle rights, format approval, or a localization plan.