Hand Over an Unfinished Treatment Without Making the Next Writer Start Blind

A clean page is the most misleading thing you can leave behind.

Picture the successor opening the file you sent. Every sentence is formatted the same way. The premise the client already approved and the paragraph you wrote at midnight to hear how it sounded look identical on screen. The paragraph you abandoned after two lines because the timing didn't work looks like everything else. The successor has no way to tell which parts are load-bearing and which are scaffolding, so they do the only safe-looking thing: they treat the whole document as a draft and start editing it. Sometimes they rewrite the one section that was already signed off. Sometimes they revive a route you killed last week and present it back to the director as a fresh idea.

None of that is the successor's fault. It's a failure of the handover, and the handover is the departing writer's job.

Here is the useful answer, before the particulars. An unfinished treatment handover should let the receiving writer tell three things apart: what is decided, what is only proposed, and what decision comes next. That means you transfer the reasons behind the current text, not just the current text. A polished page is not evidence of approval, and holding an assignment does not give you the right to forward every file attached to it. The note that does this well is not long. It is specific.

Identify the version the next writer should actually continue

By the time a treatment is mid-flight, most writers are carrying more than one version of it. There's the working document. There's an export from three days ago that still has the old ending. There's the branch where you tried a silent opening with no voiceover, and abandoned it. And there's the version somebody on the team started editing locally, which now disagrees with yours in a section nobody has reconciled.

Do not make the successor reconstruct which of these is real. Name the current document, and name it in a way that survives contact with a file system. State plainly which files it supersedes. Say what it is called, and say where its authority comes from — is this the file the director last read, or just the newest thing you happen to have saved?

Then summarize what changed most recently and which sections are still unfinished. Two or three sentences is usually enough: the premise is approved, the opening copy was rewritten once and is still tentative, the reveal is unresolved. That summary is the receiver's starting point. It is not a folder chronology. Nobody needs the order in which you created fourteen documents; they need to know where to begin reading and what to ignore.

There is one temptation to resist here, and it is strong. When you're leaving an assignment, you want to be tidy. You want to reconcile the conflicting notes, pick the sensible reading, and present a clean version that looks like a decision. Don't, unless you actually held the authority to make that call. If the director asked for one thing and the client's brand team asked for another, and nobody has ruled between them, say so. An apparent decision that the departing writer invented out of two live instructions is not a kindness to the successor. It's a trap they'll only discover when they present the "settled" version and get sent back.

The honest framing is: these two instructions disagree, here is who needs to resolve it, and here is what we know about each. That keeps the disagreement visible, which is exactly what the next writer needs.

Attach a state and a next decision to unfinished sections

The core skill of a handover is labeling. Every relevant section of the treatment should carry one of a small set of states, and the labels should be consistent from section to section so the successor can scan for the ones that are open.

An approved intention is a decision that somebody with the standing to make it has actually made. The comic premise of the spot is approved. The pack must be shot with its label legible at the reveal — that is not a preference, it is an approved constraint. When you mark something approved, you should be able to say who approved it. If you can't, it isn't approved; it's something you stopped worrying about.

A current proposal is the working direction you believe in but haven't gotten signed off. It might be strong, it might be plain, and it might even look finished. This is the state that fools readers most often, because a well-written proposed section reads exactly like an approved one. If the opening copy is tentative, say it is tentative. If the casting page is visually complete but nobody has approved the performer, mark it proposed, not approved. A beautiful page is not a decision.

An unanswered question is something the treatment genuinely cannot move past without a call from someone else. This is where most handovers go soft. "Casting needs work" tells the successor nothing. It sounds like a to-do item; it's actually a doorway with no handle. The useful version names the unresolved thing and who owns it: the reveal's action isn't chosen yet, the choice is the director's, and until it's made the casting page can't be locked — because one of the two candidate actions requires the performer to hold the pack through the beat and the other doesn't. That single sentence explains why casting is stuck, and it removes the temptation to just pick a performer and move on.

Pair each open question with the source material it depends on. If the question is about whether the label stays legible though a particular camera move, the material is the product guideline and the shot reference, not the whole client deck. Point to the exact thing. Then note who owns the answer. A successor who knows the question and the owner can do something. A successor who knows only that "casting needs work" will stall, or worse, guess.

Each state needs its own fields, and they differ. An approved intention needs the approver named, and the record of where that approval lives. A current proposal needs the writer who owns it and the draft it came from. An unanswered question needs the owner of the answer and the source material the answer depends on. Filled in, those fields are a usable handover for a section. It is also short, which matters — the successor should not have to read every discarded draft to find out what's actually open.

Preserve the reason a tempting route was rejected

You do not need to document everything you tried and dropped. Most of it deserves to stay dropped, and a handover that catalogs every dead end is just as useless as one that hides the live ones. Record the discarded routes that someone is likely to revive, and record the concrete reason they were set aside.

Here is a fictional example to make the distinction concrete. A kitchen spot has a product reveal built around the cook's hand. The earlier version had the cook holding the pack with the hand across the face of the label. It was rejected — not because anyone disliked the gesture, but because the label was obscured at the exact moment it needed to be readable. That's a product constraint, and it's a different kind of reason than "the room didn't love it."

The difference matters enormously to the successor. If a route failed a product constraint, they know the route isn't dead forever; it's dead as long as the constraint holds. If the client later relaxes the label legibility requirement, the hand-across reveal becomes available again, and the successor will know why it had been shelved. If instead you recorded it as "we didn't like the hand version," you've taught them something false — they'll treat a conditional setback as permanent creative law, and they won't bring back a good idea when the condition changes.

There's a second failure, the mirror image of the first. If you don't record the reason at all, the successor reviews the old drafts, finds the hand-across reveal, thinks it's clever, and presents it to the director as new work. Everyone who was in the last meeting watches it fail for the same reason it failed before. That is a genuinely demoralizing experience for the person who did it, and it's avoidable with one honest line: this was dropped because the hand covered the label; revisit only if the label requirement changes.

So the rule is narrow and useful. Keep the tempting route, keep the real reason, and keep the distinction between a constraint out in the world and a taste preference in the room. Don't dress a preference up as a constraint, and don't bury a constraint as a preference. The successor can argue with a preference. They cannot argue with a product requirement — but they can plan around it, if you tell them it exists.

Here is what a compact handover excerpt can look like, with all of the above folded together. It's invented, but the shape is the point.

Kitchen spot — handover excerpt (fictional)

Current document: kitchen_v7_treatment.md. Supersedes v5 and the "no-voiceover" branch. Anything in exports/ is older.

Last changes: comic premise approved by the client's brand lead at the Thursday review. Opening copy rewritten once; still tentative. Reveal unresolved.

Product reveal — open. The pack label must be legible at the moment of the reveal (product requirement, not our preference). Earlier version had the cook holding the pack with the hand across the label face; dropped for that reason. Director is choosing between two actions: the cook slides the pack label-out and the hand leaves frame before the hold, or the cook turns the pack label-out and holds with the hand in frame but clear of the label. Owner: the director. Needed to decide: which action the performance can carry.

Casting page — proposed, not approved. It reads as finished, but it isn't signed off and can't be locked until the reveal action is chosen — one action needs the performer to hold the pack through the beat, the other doesn't.

Notice what that excerpt does and doesn't do. It names the current file and pushes the exports aside. It labels the premise approved and the opening copy tentative. It keeps the rejected route and its real reason. It states the next decision and its owner. It flags the hidden dependency — casting waits on the reveal — that a successor would otherwise discover by accident, after committing to a performer. And it does all of that in a few lines, without asking anyone to reread the abandoned branches.

Transfer permitted material and walk through the first move

The text is only half the handover. The other half is the material, and the material has a boundary.

Before anything moves, confirm who the receiving collaborator actually is and what route is authorized to reach them. Having access to an assignment is not the same as having the right to forward every file attached to it. Client decks, brand guidelines, unreleased reference footage, and internal notes may be restricted for reasons that have nothing to do with how much you trust the successor. If you can't confirm a file is cleared for transfer, don't forward it. State the constraint it carries and let someone with the authority decide.

That's why the excerpt above points to the product rule rather than shipping the whole product deck. The successor needs to know the label must stay legible. They may not need the document that says so. Say the constraint; flag the source as available on request through the proper route. Link what you can link accurately, and name what you can't — unavailable material should be marked unavailable, not quietly omitted, so the successor doesn't spend an afternoon looking for a file that was never coming.

Then handle the loose ends honestly. If there's a credit question, it still belongs to the people who own it. A handover note cannot resolve authorship, payment, or permission, and it should not pretend to. Note that the question is open and who is holding it, and leave it there. The same goes for approval. You can report what was decided and by whom; you can't manufacture a decision that hasn't happened.

Finally, run a short walkthrough — a conversation, not a document. Ask the receiver two things: which section they'd work on first, and what's still unclear. Those two questions are surprisingly good at surfacing the dependencies you forgot you were holding. If they say they'll start with the reveal, that's a sign your note pointed them at the live decision. If they say they'll start with casting, you've just watched the hidden dependency fail to transmit, and you know to make it louder.

The walkthrough should expose remaining uncertainty, not manufacture agreement. You are not there to get the successor to nod along with your version of the treatment. You're there to find out whether the state of the thinking actually made it across. If something is still open, you want it to stay visibly open after the conversation, not get smoothed shut for the sake of a tidy ending.

Here's a way to test whether the note did its job. Ask the receiving writer to name the next decision and explain why the old reveal shouldn't simply be restored. A handover that works gets an answer like this: the next decision is the director's choice between sliding the pack or turning it, and the hand-across version stays retired because it hid the label — unless the label requirement itself changes. If the successor can say that without rereading every discarded draft, the handover is carrying the thinking, not just the text. If they can't, the note is missing a state, an owner, or a reason, and it's worth the extra ten minutes to add it.

No real assignment or transfer is described above, and the walkthrough result isn't a result — it's what a good one would need to produce. The point stands either way.

What the successor should be able to ask first

A successful handover makes unfinished thinking visible instead of disguising it as a finished document. It doesn't pretend the treatment is more settled than it is, and it doesn't bury the parts that still need a decision.

The clearest sign that you got it right is that the successor's first question arrives with an owner attached. Not "what should I do about the reveal?" but "the reveal needs the director to choose between the slide and the turn — is that still with them?" That question can only be asked by someone who knows what's decided, what's proposed, and what's waiting. Which means your note did the one thing a handover has to do: it handed over the state of the thinking, not just the last saved page.

Frequently asked questions

What three distinctions should a handover make clear to the next writer?

What is decided, what is only proposed, and what decision comes next. The handover should transfer the reasons behind the current text, not just the text. A polished page is not evidence of approval, and holding an assignment does not give the right to forward every attached file.

How should unresolved conflicting instructions be handled?

Do not reconcile them into an apparent decision unless you actually held the authority to make that call. State that the instructions disagree, name who needs to resolve the disagreement, and say what is known about each. An invented decision is a trap the successor discovers when they present the settled version and get sent back.

What labels can unfinished sections carry, and what does each need?

An approved intention needs the approver named and the record of where that approval lives; if no one can be named, it is not approved. A current proposal needs the writer who owns it and the draft it came from, and should be marked proposed even if it looks finished. An unanswered question needs the owner of the answer and the source material the answer depends on. Pairing the question with its owner lets the successor act instead of stalling or guessing.

Why preserve the concrete reason a tempting route was rejected?

It distinguishes a product constraint from a taste preference. A route dropped because the hand covered the label can return if the label requirement changes; if it was recorded as we didn't like it, the successor may treat a conditional setback as permanent law. If the reason is omitted, the successor may present the same old route and watch it fail for the same reason. Keep the tempting route, the real reason, and the distinction between a constraint in the world and a preference in the room.

How should permitted material be transferred and the first move checked?

Confirm who the receiving collaborator is and what route is authorized to reach them; access to an assignment is not the right to forward every file. If a file is not confirmed as cleared, such as client decks, brand guidelines, unreleased footage, or internal notes, do not forward it; state the constraint and let someone with authority decide. Mark unavailable material unavailable rather than omitting it. Then hold a short walkthrough, asking which section the receiver would work on first and what is still unclear. The test is whether they can name the next decision and explain why the old reveal should not simply be restored; if not, the note is missing a state, owner, or reason. No real assignment or transfer is described, and the walkthrough result is what a good one would need to produce, not a reported result.

Further reading

• Write in a Director’s Voice Without Inventing Their Convictions — When a draft must keep a director's judgments intact, this shows how to label her idea, your addition or an undiscussed gap, and why open questions stay open.