Write and Design a Treatment Together Without Losing the Current Version

The writer is still hunting for the right sentence at the moment the character hesitates. The designer has already given that moment a spread of its own and set the payoff on the next one. Both are making real progress. Neither one has the current version.

That happens because "the current version" was never defined as anything more than the file someone opened most recently. When the new sentence exists only in the layout, the copy file is wrong. When the accepted arrangement exists only in a message, the layout file is wrong. A week later the treatment has three plausible finals and nothing to choose between them except memory.

The fix is not identical documents. It is three things: each part of the treatment has a stable identity that survives being moved, each identity has exactly one current meaning, and every change has an agreed path back to that meaning. The arrangement below fits a short treatment — three or four units, not a production pipeline — and it uses an invented commercial as its example throughout. The spot is invented to give the lesson something concrete to hold. No collaboration tool or team workflow has been tested here, and the method is proposed rather than proven.

Identify the explanation before numbering the page

Page numbers lie. A spread gets added at the front and every page number after it shifts by one. Then the conversation has to start with "the page that used to be seven," which is four words doing the work that a name should do.

So name each unit by its job. In the invented spot, three units carry the whole commercial:

• Arrival. A kitchen at the end of the day. One lamp on. She comes in, drops her keys on the counter and fills the kettle.
• Hesitation. Close on her at the counter. She lifts the cup and then she sets it back down on the counter without drinking from it, and looks past the window at the street.
• Payoff. The street from her side of the glass: a car pulling in. She crosses to the front door and opens it. The two of them in the doorway, the lamp behind them.

Those names, not their positions, are what the writer and the designer refer to. The current text for each unit lives with the name. So do the reference notes that belong to it — a photo of the kitchen light, a note about how long the pause should feel, a line of voiceover if the spot has one.

A unit does not have to respect the page. The hesitation can open one spread and finish on the next. The arrival and the payoff can share a spread if the layouts are quiet. In this example, the designer later moves the hesitation so that it opens the final spread and the payoff finishes it, which means one spread now carries two units. That is a layout fact. It does not create a second hesitation, and it does not give anyone a reason to keep two copies of the same sentence.

Keep the system as small as the project allows. Three named units with one current text each will survive a treatment. A folder structure with eleven categories will not survive the second week, because nobody maintains a system that costs more than the work it protects.

Agree what each collaborator can change

Most version conflicts are not disagreements about quality. They are disagreements about what kind of change just happened.

It helps to separate three kinds, because they have different owners.

Wording. The sentences themselves. This belongs to the writer, mostly, but the boundary is not word count. Shortening "she eventually notices" to "she notices" removes one word and the whole point of the shot, because "eventually" is the delay the camera is waiting through. A change that small is a meaning change. Meanwhile "she lifts the cup, and then she sets it back down on the counter without drinking from it" can lose five words and keep every beat intact. Count is not the test. What happens on screen is the test.

Layout. Where a unit sits, how much air it gets, which spread it shares, how the type ranks against the image. This belongs to the designer, and it should stay there. A writer who insists on the page break is doing layout badly, and both people lose a day.

The film. The beat order, what a unit argues, whether a unit should exist. This is the writer's call, and it is the one kind of change that cannot be absorbed as an edit. The designer should still be able to raise it — more on that below, because in this example the biggest proposal of the week comes from the designer and it is the right kind of proposal to make.

Write down who accepts each kind before the parallel work starts. It takes one message and it prevents most of the collisions. It also keeps the designer from being treated as a destination for finished copy, which is the arrangement where the person closest to the material has no standing to question it.

Work one section through the complete return path

Before splitting the remaining work, take a single passage all the way around the loop: current copy into layout, a proposed change back, a resolution, and the accepted wording returned to the current copy.

In the invented spot, the passage is the hesitation. The designer sends two items together, both about that one named unit:

Hesitation. Two things back.

1. I moved it to open the final spread and let the payoff finish it. Reading order is now arrival, then hesitation and payoff together. The film's order does not change; you still see her hesitate before the car.
2. Trim in the cup sentence: "She lifts the cup, sets it back down without drinking, and looks past the window at the street."

Notice what the note does. It names the unit, so no one has to reconstruct which passage is meant. It says what changes. It says what decision is needed. It does not arrive as a redrawn layout with no explanation attached.

The writer's response separates the two. The move is a layout decision, the film's order is untouched, and it stands. The trim is a wording change, so it belongs to the writer — the designer had the useful idea, but the authority sits with the person who owns the sentences — and the writer accepts it as an ordinary line edit. Beats, screen time and meaning are all unchanged, so it needs no ceremony.

Then both accepted items land in the same current copy. The trimmed sentence goes into the text. The layout picks up its text from there. Nobody sends a revised file that contains half of the resolution.

Do this once, on one passage, and you find the real friction before it is spread across the whole document. What you are rehearsing is the handoff, not the wording. It should not take long, and it should not produce a new approval gate for every sentence that gets shorter. That is the failure mode at the other end: a process so careful that the ordinary edit needs two people and an afternoon.

Keep proposals visible without making them current

The designer also proposes cutting the hesitation. Kettle straight to car. That is a change to the film's argument, not to the page, and it cannot be absorbed as a line edit or a layout decision.

So it gets everything a real proposal needs and nothing else. It names the hesitation. It says what it would remove and why. It says what decision is needed and who makes it. And it lives somewhere that is not the sendable treatment — a proposals list, or a note copied into one once the conversation around it is settled.

Until that decision is made, the hesitation stays exactly as it is. The last accepted version is the current version even when someone has a good argument against it. This is the part people get wrong under time pressure: they leave the deletion marked up in the layout "just to see," and now the sendable file contains a proposal that looks like a decision.

Keeping that third item separate from the first two is not tidiness for its own sake. The move and the trim could be accepted on the day they arrived. If the deletion had been sent inside the same layout note as a change, all three would have been waiting on one conversation, and the paragraph about the cup would still be un-resolved because the argument about the structure wasn't finished.

Archive the rejected routes instead of deleting them. A treatment often comes back to an option that was wrong in March and is right in June, and the version that shows why it was set aside is worth keeping — outside the current copy, with enough of a note to say what happened to it.

Two housekeeping facts belong in this section, and both are about time rather than files.

First, agree review windows. "Send me anything, anytime" is not a working arrangement; it is a promise one person will eventually break. A treatment-sized project needs something like a stated turn-around on proposals and one point in the day when accepted changes get merged.

Second, put coordination in the assignment. Reading a layout, comparing it to the copy and writing a note about the difference is work. If it is invisible in the schedule, it happens late at night and badly. Parallel work does not mean permanent availability, and a short treatment is not exempt from that just because it is short.

Reconstruct the sendable treatment once

Before the treatment goes out, walk the units in their final order and compare the accepted text against the layout. This is a recovery check on one document, not an argument for document-control software. Most treatments need it once.

The check is not whether the filenames match. It is whether the altered claim and its image still agree. In this example, the trimmed sentence is current, so the spread's image note needs to still show the delay — the pause at the cup has to survive the trim without the words carrying it alone. And because the hesitation now opens the final spread instead of filling one of its own, the check is whether the move changed how the passage reads. Does the hesitation still register as hesitation, or does it now look like the first beat of the payoff? If the second thing is true, the problem is at its origin, in the layout, and it gets fixed there.

Here is the whole history of the invented spot. Three changes, one unit:

The arrival and the payoff have no entries. That is the point of keeping the list this small.

Now the test that matters. Hand the files to someone who was not in the conversation and ask them to write down the final wording and the final sequence. If they can do it, the arrangement works. If they find themselves choosing between three apparent finals — the long cup sentence, the trimmed cup sentence, and a version with no hesitation at all — then at least one of those three is sitting somewhere it should not be, and the fix is to move it rather than to explain it.

The three apparent finals are the whole risk, and none of them is wrong on its own. The long sentence was correct for a while. The trimmed sentence is correct now. The version without the hesitation might be correct in June. What makes them a problem is a single file that holds all three, so the reader has to guess which one the treatment means.

What one current version looks like

At the end, there is one document with the three units in order, the hesitation opening the final spread with the trimmed sentence inside it, and one proposal sitting outside the document waiting on a decision. The change path is short enough to read in a minute: one unit moved, one sentence shortened, one structural question open.

That is a finished state for a short treatment. It is not a finished method. The useful next step is to build this small history for one real treatment and then have a writer and a designer try to break it — specifically, to reconstruct the current version from the files alone, without the conversation. If they can, the return path is doing its job. If they cannot, the failure will point at exactly one of the three things above: a unit that was identified by its page, an authority that was never assigned, or a proposal that got comfortable inside the sendable file.

Frequently asked questions

Why do page numbers make version control worse in a treatment?

Page numbers shift as spreads are added or moved, so people end up referring to the page that used to be seven. Name each unit by its job instead, such as Arrival, Hesitation, and Payoff. The current text and its reference notes live with that name. A unit can cross a page break or share a spread without creating a second version of the same idea.

How should authority be split between writer and designer?

Wording mostly belongs to the writer, layout belongs to the designer, and the film itself belongs to the writer. The film includes beat order, what a unit argues, and whether a unit should exist. Count is not the test for a wording change; what happens on screen is. Shortening a sentence by one word can change meaning, while losing five words may preserve every beat. Write down who accepts each kind of change before parallel work starts.

How should a proposal to cut a unit be handled?

A proposal to cut a unit is a change to the film, not a line edit or a layout decision. It should name the unit, say what it would remove and why, state what decision is needed and who makes it, and live outside the sendable treatment, such as in a proposals list. Until the decision is made, the last accepted version stays current. Do not leave the deletion marked up in the layout just to see how it looks, because the sendable file then contains a proposal that looks like a decision.

What does it mean to work one section through the complete return path?

Take a single passage all the way around once: current copy into layout, a proposed change back, a resolution, and the accepted wording returned to the current copy. For example, the designer can send two items about the same named unit, separating a layout move from a wording trim. The writer accepts or rejects each according to its kind, and both accepted items land in the same current copy. Rehearsing this on one passage finds friction before it spreads across the whole document.

How do you know a sendable treatment is coherent?

Walk the units in their final order and compare the accepted text against the layout, checking whether an altered claim and its image still agree. Then hand the files to someone who was not in the conversation and ask them to write down the final wording and sequence. If they can do it from the files alone, the arrangement works. If they find themselves choosing between several apparent finals, at least one version is sitting where it should not be, and the fix is to move it rather than explain it.

Further reading

• Run a Director–Writer Session Around the Scene You Haven’t Solved — When a beat resists a line edit, this session format puts two filmable versions side by side and records the chosen action and its decision owner.