One Treatment Writer, Two Competing Bids: Can the Work Stay Separate?

The second email is the easy one to answer, and most people answer it with a filing system. Keep Ana's pitch in one folder, Ben's in another, never open them in the same window, and the work stays clean.

The folder isn't where the work lives. The work lives in your head, and by the time the second email arrives, your head already contains a shared brief, one director's private solution, and a couple of pages you wrote from it. None of that sorts into directories. Some of it you can't even locate reliably, because the ideas you generated last Tuesday don't come with provenance labels attached.

So the question isn't whether you can keep the material separate. It's whether you can keep the work separate, and those two questions are answered by different evidence. Separate files are a fact about your laptop. Independence is a fact about your decisions.

The practical answer, up front: settle permission and independence before the second team's creative material arrives. If it has already arrived, your first job changes. You're no longer deciding whether to accept exposure. You're managing exposure that has happened.

The brief is a question, not a shared secret

A pitch brief is usually circulated to more than one team. That's the design. Two directors get the same document, and a writer can be approached by both without anything improper having occurred yet.

The confusion comes from treating a shared document as shared thinking. The brief is the question. A treatment is an answer. Knowing the question tells you nothing about anyone else's answer, and "we all got the same brief" is not a license to move anything else across.

Three streams of information arrive in the same week, and it helps to separate them by their origin rather than their arrival:

The brief itself. It came from the commissioner — an agency, a producer, whoever is running the pitch. You can work with it. It may still be confidential to that commissioner, which is a different constraint and worth noticing.

Each director's private interpretation. A scene, a structure, an ending, a "what if she drives home past her own customers." This is the valuable material, it arrived to you privately, and it does not travel. Ever. Not to the other director, not to a friend who might be a good fit for the job, not into your own draft for the other pitch in a slightly different form.

Your own ideas. Generated while holding the other two streams. This is the hard case, and it's where the folder theory gives way entirely.

One practical check before any of it: verify that "the same brief" is actually the same brief. Read both copies. Look for a private addendum, a client call that only one team had, a note that came after the document went out. Small differences in what each team knows are exactly the kind of thing that gets discovered later by someone else.

Permission is a gate. Independence is a test.

These get treated as one question. They aren't.

Permission is external. Someone with authority has to be able to say yes, and the someone is usually more than one person, because the questions have different owners. The commissioner who circulated the brief may be able to speak to whether multiple responses were contemplated. The company that engages you has something to say about your engagement terms. The director has authority over her own material and nothing else. An agency's yes is not automatically the production company's yes.

Read the actual terms. I'm not going to interpret them for you, and this article won't decide what any clause permits — where the language admits two readings, that's a question for whoever is qualified to read it, not a question for a writer at 11 p.m. with a deadline.

Here's the part people miss: asking the question has a footprint. The smallest honest version names no one and describes nothing — does my engagement on this pitch allow me to contribute to another response to the same brief, and under what conditions? That still tells the commissioner that a writer is being approached by more than one team, which is itself information. It's usually a smaller disclosure than the alternative, which is an arrangement nobody authorized, but it isn't zero. Decide to make it deliberately rather than discovering you made it.

And don't route the request through a director as if her nod settles it. She can speak to her own material. She can't consent on behalf of a team she's competing with, and a permission given by someone who can't see what it covers does very little work. If she says "sure, go ahead," you've learned something about her mood, not about your obligations.

Independence is the other half, and it's internal. The test is narrow and unforgiving: could you have arrived at this decision without the other engagement? Not "did you copy anything." Not "would anyone notice." Could you have gotten here on your own, in a world where the other pitch didn't exist.

Folders don't touch that question. Time does. Memory does. Method does. And a permission, however clean, doesn't turn an answer of "no" into a "yes."

Case file: Ana, Ben, and the attachment you shouldn't have opened

What follows is invented. It doesn't describe a real pitch, a real permission, or a real conflict determination, and it isn't a report on what the industry does. The particulars are fixed so the decision points are visible.

A regional bank has briefed a 30-second film. The problem stated in the brief is that customers don't believe the bank is local. The agency has asked two directors, Ana and Ben, to respond. They have the same document.

Ana engaged you two weeks ago. On a call with just the two of you, she gave you her working solution: the film opens on a branch manager locking up, and she drives home past her own customers. That's Ana's idea. It's not in the brief. You've drafted two pages from it.

Now Ben emails. Same job, same brief. Would you write his treatment?

Variant one. The email is one paragraph. There's no attachment. Ben hasn't described how he'd approach it. What you hold is the brief, Ana's private scene, the two pages you wrote, and the fact that Ben is interested.

Variant two. Same email, except it has his draft attached, and you opened it before any of this registered as a question. Ben's version ends with a customer recognizing the manager in a car park.

What separates these two variants is not a slope. It's a step. Before the attachment, your cleanest move — take Ana's, decline Ben's, say nothing to anyone about anyone's private material — is fully available. After the attachment, declining Ben is still available, but "take Ana's and don't worry about it" isn't, because the duty has flipped direction.

That's the thing worth sitting with. Before you read Ben's draft, your risk is Ana's idea leaking out to Ben. After you read it, your live risk is Ben's idea leaking into Ana. Reading the second team's material doesn't just make your future work for them suspect. It puts the assignment you already had under a new obligation. Your two pages from before the email aren't retroactively tainted — they predate the exposure. Everything you write from that point forward is a different situation.

Which is why exposure never adds options. It only removes.

Three arrangements, priced honestly

Suppose, for the exercise, the agency answers that a writer may contribute to more than one response to this brief, provided each team's material stays with that team and the writer can confirm that it does. That answer is invented. A real one would come from the actual commissioner and the actual terms, and it might be narrower, or slower, or silent.

With that stipulation in hand, the three arrangements look like this.

Take one assignment. You give up the second fee, the second relationship, and whatever the second director might have hired you for next year. What you get back is a single confidentiality duty, a schedule that fits in one head, and no ongoing self-policing — but only if the timing holds. Those benefits are cleanest when the second team's creative material hasn't reached you: before Ben's draft, before you've read anything you can't unread. If it has reached you, taking one assignment still narrows the work, and it still isn't the same move. The received knowledge stays where it is. Ben's ending is in your memory either way, and if a beat in Ana's treatment later turns out to be one you can't certify as independently arrived at, the disclosure that follows still happens. Declining the second job answers who you work for. It doesn't answer what you know. You're choosing between assignments now, not between being exposed and not being exposed.

You can still decline the other without explaining. I can't take this one on is true, complete, and carries nothing, and you don't need anyone's permission to say it. Don't route the decline through Ana. She has no business knowing Ben called, and an unnecessary conversation about it creates exactly the record you were trying to avoid.

An expressly permitted separate arrangement. This needs four things, not one. An answer from someone who can actually give it, plus a written version of what it covers if you can get one. Genuinely distinct development for each piece — different phase, different material, real gaps in time. Enough calendar for two real pieces of work, checked against both schedules rather than assumed. And an escalation route in advance, because "we'll figure it out if something comes up" is how the something comes up.

Then apply the independence test as a working check: can you state how the two treatments differ without describing anything you learned privately from either team? If explaining the difference requires Ben's ending or Ana's opening, you haven't separated them. You've just moved them further apart in the file tree.

One more requirement, easy to skip: you should not be the only person checking the two outputs for overlap. The person best positioned to notice that your work has drifted toward someone else's idea is the person who knows that idea — and that's the person you can't talk to. Your own check is the least reliable one available, because the contaminating idea is the one that already feels like yours.

And note what that stipulated yes does in variant two: nothing about Ben's ending leaves your memory. A permission makes the arrangement legitimate; it doesn't reach the knowledge you already received. Whether the arrangement is workable is now a separate question from whether it's allowed.

Decline, or refer. Referring is the option most likely to be botched, because a referral feels like a neutral act and it isn't. Two consents are inside it. Nora needs to be willing to have her name passed along, and Ben needs to be willing to have his project mentioned to her. Without both, you've made a decision on someone else's behalf.

The handoff is contact, not content. You don't brief Nora on the job. You don't tell her what Ana is doing, or what Ben's approach is, or really anything about the pitch beyond what Ben is free to send her himself. Ben may be looking for a writer, here's his address — and let the two of them work out the rest.

The overlap you find at the end of the draft

Three weeks into Ana's pitch, one week after Ben's email, you're writing the closing beat. You draft: the manager's car pulls into a driveway, and on the porch is a customer whose account she opened last spring. You read it back and something snags. You have read Ben's ending, in which a customer recognizes the manager in a car park. You cannot determine whether the porch came from you or from him.

That inability is the finding. Not a nuisance standing between you and finishing. The actual answer to the independence question.

So: don't fix it by rewording. A synonym doesn't unlearn anything, and it does something worse — it removes the visible evidence that the problem exists. Anyone reviewing the finished piece later, including you, will see a sentence that reads like yours because it's been sanded into looking like yours.

Don't delete the draft, and don't delete the email. Erasing the source doesn't restore your independence; it just destroys the record you'll need when someone asks what you received and when.

What you do instead is smaller and more uncomfortable. Stop the affected passage. Securely note what you received, from whom, and on what date — for your own clarity, not as legal proof. Then take the problem to someone with authority over it, at the minimum level of description that lets them act. Not here's Ben's ending. Something like I've drafted a beat I can't certify as independently arrived at, and I think it came from exposure outside this assignment. That's truthful, it carries nothing private, and it gives the owner enough to direct you.

This may mean telling more than one party, and which parties depends on whose material is at issue and who governs the engagement. That's a question to ask rather than to settle privately. You are not a licensed arbiter of your own contamination, and no one becomes one by wanting the deadline to hold.

What you're actually deciding

Most of these decisions get made in the twenty minutes before you reply to the second email, and they're usually the smallest of three moves. Take the one you can do cleanly. Or take both under a permission you can point to and a method you can name, with somebody on each side able to see the outputs. Or decline, and pass along a name only if both people agree to the introduction.

None of that requires a universal rule, and I'd be suspicious of anyone offering one. Writers do this all the time and writers never do this are both claims about an industry neither of us can check from here. The usable answer is local: what your terms actually say, what a person with real authority actually says, and what you can actually make.

Here's the distinction to carry out of this, and it stays uncomfortable on purpose. Authorization can be necessary without being sufficient. A yes from the right person is the gate — you need it, and without it you have nothing. It isn't the work. You can be fully permitted and still unable to produce two pieces independently, and when those two things come apart, the permission is what you'll want to point at while the independence is what you actually needed.

Stop conditions, then. Stop the affected work if you can't say where an idea came from. If you can't describe how the two pieces differ without describing private material. If the schedule has narrowed to the point where one treatment gets made out of the other's leftovers. If the permission's scope no longer covers what you've been asked to do. If the terms need a reading you have no way to get.

If the fix is a synonym, you haven't separated anything.

Frequently asked questions

What is the difference between keeping material separate and keeping work separate?

Separate files are a fact about a laptop. Independence is a fact about decisions. The test is whether you could have arrived at a decision without the other engagement, not whether you copied anything or whether anyone would notice. Permission is external; independence is internal, and a clean permission does not turn a no into a yes.

Can one director give permission for a writer to work on a competing pitch?

No. A director can speak to her own material, not consent on behalf of a competing team. Permission must come from someone with authority over the relevant obligation, and that may be more than one person, such as the commissioner, the company engaging the writer, or both. An agency's yes is not automatically a production company's yes.

What changes if the writer has already opened the second team's draft?

Before reading it, the live risk is the first team's idea leaking out to the second. After reading it, the live risk is the second team's idea leaking into the first. Declining the second job is still available, but taking the first and not worrying about it is not, because the duty has flipped direction. Anything written after the exposure is a different situation, though earlier work is not retroactively tainted.

What does an expressly permitted separate arrangement require?

It needs an answer from someone who can actually give it, plus a written version of what it covers if possible; genuinely distinct development for each piece, with different phases, material, and real gaps in time; enough calendar for two real pieces of work checked against both schedules; and an escalation route in advance. The independence test is also a working check: you should be able to state how the two treatments differ without describing anything learned privately from either team.

What should a writer do if a drafted beat cannot be certified as independently arrived at?

Stop the affected passage. Do not fix it by rewording, and do not delete the draft or the email, because erasing the source destroys the record. Securely note what was received, from whom, and on what date. Then take the problem to someone with authority over it, at the minimum level of description that lets them act, rather than settling privately whether it counts as contamination.