How to Hand Over a Locked Vertical Drama Script So Nothing Changes Without Your Approval

A locked script. A signed off series bible. Then the first episodes come back and a line of dialogue is different, a scene has moved from the office to a car, and the slap in episode nine is now a shove. Each change has a reason. The original location was hard to generate consistently. The line ran long for the shot. The slap read badly on a small screen. None of the changes were approved, and the commissioning team only found them by watching.

This is the most common source of friction between a commissioning team and a production partner, and it rarely comes from bad intent. Production teams solve problems as they meet them. Some of those solutions touch the story. If there is no agreed route for those decisions to travel back to the commissioning side, they get made on the floor and discovered at review, when they are expensive to undo.

The fix is not a stricter contract. It is a better handover. A script that arrives with clear rules about what can move, what cannot, and how a change gets requested is a script that comes back the way it was written. This piece sets out that handover in practical terms.

1. Decide What Locked Actually Means

Locked is a word that means different things to different people. To a writer it often means the words are final. To a production team it can mean the structure is final but the staging is open. To a commissioning executive it may mean the story beats are fixed while dialogue can be polished. Unless everyone agrees on the definition before handover, every party will act in good faith on a different version of it.

Start by writing down what is fixed. Most commissioning teams land on a version of the following. Story beats and their order. Reveals and their placement, including the paywall episode. Character names, relationships and core traits. Key dialogue lines, especially those used in trailers or tied to a cliffhanger. Episode count and the content of each episode ending.

Then write down what is flexible. Staging and blocking. Minor dialogue trims for length, provided meaning does not change. Background action. Location detail within an agreed setting, such as which corner of the office a scene happens in. This list gives the production team room to solve problems without needing approval for every adjustment, which keeps the work moving.

The grey zone

Some changes sit between the two lists. Moving a scene to a different location. Replacing a physical action with a different one. Merging two short scenes. These should default to needing approval. The cost of a quick message is low. The cost of discovering a moved scene after thirty episodes have been generated around it is high.

2. Build the Handover Pack Around the Script

A script on its own is not enough. It tells a production team what happens and what is said, but it does not tell them why, or which parts carry the most weight. The handover pack should wrap the script in the context that lets a production team make the same choices the commissioning team would.

A strong pack includes the locked script with a version number and lock date, a one page beat map marking every reveal and cliffhanger, a character sheet with fixed traits and relationships, a short list of protected lines, and a change policy that sets out the fixed and flexible categories from section one. Some teams also add a tone note, a few paragraphs on what the series should feel like, which helps the production side make small staging decisions in the right direction.

The direction brief is the piece that turns all of this into something a production floor can execute. A script describes the story. A direction brief describes the shots that tell it. If the commissioning team or the production partner writes one before generation begins, most of the ambiguity that leads to unapproved changes disappears. The guide to writing a direction brief a generation operator can execute without clarification covers how that document is structured.

Version numbers matter

Every script in the pack should carry a version number and a lock date on every page. If a revised version is issued later, it gets a new number and a short change summary at the top. This seems administrative, but it is the only reliable way to prove which version a production team worked from when a dispute comes up.

3. Check the Script Before It Locks

Many unapproved changes are not really changes. They are fixes to problems that should have been caught before the script was locked. A scene that cannot pass the content policy of the target platform. A location that will be extremely hard to keep consistent across forty episodes. A stunt that reads badly in a narrow vertical frame. When the production team meets these issues mid run, it has to solve them somehow, and the solution often lands on the page.

A short pre lock review with the production partner catches most of these. The partner reads the script for feasibility, not for taste. Which scenes will be difficult to produce consistently. Which locations repeat often enough to need a fixed reference. Which actions risk a content policy flag. The commissioning team then decides whether to adjust the script before lock or accept the risk with a known plan.

Content policy is worth a separate pass. Platforms differ on violence, self harm references, intimacy and depictions of minors, and a scene that is fine for one app may be rejected by another. Checking this before lock prevents the worst kind of late change, the one where a scene has to be rewritten after it was produced. The article on what a commissioning team should check against platform content policy before a script is locked sets out that check.

4. Set Up a Change Request Route

Even with a careful pre lock review, production will surface new issues. The question is not whether changes will be needed, but how they travel. A clear change control route gives every proposed change a single path from the production floor to the commissioning team and back.

The route does not need to be complicated. A shared log, a named approver on the commissioning side and a response window are usually enough. Each change request includes the episode and scene, the current script text, the proposed change, the reason, and the effect on anything downstream. The approver accepts, rejects or proposes an alternative. The decision is logged, and the script version is updated if the change is accepted.

The response window is what makes this work. If approvals take a week, the production team will either stop work or start making calls on its own. Same day or next day responses for routine requests keep the line moving. Larger changes, such as anything affecting a reveal or an episode ending, may need a short call rather than a written exchange.

Who approves

Name one approver and one backup. Not a committee. A committee produces slow decisions and conflicting notes, and the production team ends up choosing between them. The approver can consult internally, but the production side should receive one answer from one person.

5. Protect the Lines That Carry the Series

Not every line of dialogue matters equally. Some lines are the series. The line before the cliffhanger. The line in the trailer. The line a character says that defines who they are. If those lines drift, the series changes shape, even if every individual edit looked reasonable.

Mark these lines explicitly in the handover pack. A protected lines list of twenty to forty lines across a full series is typical. These lines cannot be trimmed, reworded or reassigned without approval. Everything else can be adjusted for length or timing within the flexible rules.

Protected lines also help the production team prioritise. If a scene is running long and something has to give, the team knows which lines to keep untouched and where to look for trims. This turns an ambiguous judgement into a clear one.

Translated versions

If the series will be produced or subtitled in more than one language, protected lines need protected translations. A cliffhanger line that lands in English can lose its edge in translation if a subtitler chooses a flatter phrasing. Agree the translations of protected lines before production, and treat them with the same change rules as the original.

6. Review in a Way That Catches Drift Early

Unapproved changes are cheapest to catch in the first episodes. A team that waits to review until the full series is delivered will find changes that have already been built on, and undoing them means redoing everything downstream.

Set the first review checkpoint early, after the opening episodes are produced. Review against the locked script line by line for these episodes. This is slow, but it shows the commissioning team how closely the production side is following the page, and it shows the production side what the commissioning team actually cares about. Most drift problems are solved at this checkpoint, because both sides recalibrate.

After that, reviews can shift to spot checks plus a full check of every episode containing a reveal, cliffhanger or protected line. This keeps the review load manageable without losing control of the parts that matter most.

Comparing against the script

When reviewing, compare against the script version the production team was working from, not the version in the head of the reviewer. If the change log shows an approved edit, the episode should reflect it. If the episode differs from the logged version, that is a genuine drift and should go back through the change route as a correction.

7. Put the Rules in the Agreement Without Making It Adversarial

The change policy, the approval route and the protected lines list should sit inside the production agreement as a schedule. This makes them binding and gives both sides a clear reference. It does not need to be written as a list of penalties. A schedule that describes how changes are proposed and approved is enough.

What the agreement should state clearly is the consequence of an unapproved change to a fixed element. Usually that is a correction at the cost of the production partner, within a set window. This is fair, and it gives the production team a clear incentive to route changes properly rather than make quiet fixes.

The broader structure of an agreement, including ownership of the delivered series, acceptance terms and payment milestones, deserves its own careful review. The guide to structuring an AI vertical drama commission for legal review covers how those pieces fit together.

What This Looks Like When It Works

A well handed over script produces a quiet production. Change requests arrive in the log, a handful per week at most. Approvals come back the same day. The first review checkpoint surfaces two or three small drifts that both sides learn from. After that, episodes come back looking the way the commissioning team pictured them, with staging choices that serve the story rather than reshape it.

The commissioning team spends its review time on quality, not on detective work. The production team spends its time producing, not guessing. And the series that reaches viewers is the series that was signed off, with a clear paper trail for every change that was made along the way.

This matters beyond a single commission. A platform or brand that has run one clean handover has a template it can reuse. The second series starts with a known change policy, a known approver and a production partner that already understands what locked means. That reuse is where commissioning starts to get easier.

Axis AI Studios Perspective

A script is a promise. Production should keep it.

Axis AI Studios works from the locked script as the source of truth. Feasibility questions are raised before lock, not discovered mid run. Every proposed change to a story beat, reveal, protected line or location goes through a logged request with a named approver on the client side. Staging and timing are handled within agreed flexible rules, so the production floor keeps moving without touching what the client has fixed.

The first review checkpoint is built into every schedule. It is where the production team and the commissioning team align on what the page means in practice, and it is where drift gets caught while it is still cheap. Every series is delivered with a change log that shows exactly what moved, why, and who approved it.

If a script is approaching lock and the handover rules are still undefined, that is the right moment to talk. Reach the team at business@axisaistudios.com.

FAQ

What should be fixed when a vertical drama script is locked?

Story beats and their order, reveals and their placement, the paywall episode, character names and relationships, episode endings and a list of protected dialogue lines. Staging, blocking, background action and small dialogue trims for length can usually stay flexible, provided meaning does not change.

How should a production partner request a change to a locked script?

Through a single logged route with a named approver on the commissioning side. Each request gives the episode and scene, the current text, the proposed change, the reason and any downstream effect. The approver accepts, rejects or suggests an alternative, and accepted changes update the script version.

When should a commissioning team first review episodes against the script?

After the opening episodes are produced. A line by line check at this stage catches drift before later episodes are built on it, and it aligns both teams on what locked means in practice. Later reviews can move to spot checks plus full checks of episodes that contain reveals, cliffhangers or protected lines.

Further Reading

For teams that want the script turned into something a production floor can execute without guesswork, the guide to writing a vertical drama direction brief covers the structure section by section.

For commissioning leads who want to avoid rewrites forced by policy rejections, the article on checking a script against platform content policy before it locks covers what to check and when.

For anyone putting the change policy into a production agreement, the guide to structuring an AI vertical drama commission for legal review covers how the agreement fits together as a whole.