Collaboration Etiquette

Writing a screenplay with someone else is rewarding and tricky in equal measure. Ensemble handles the technical side with real-time editing and colored cursors, but the human side needs communication and a few ground rules.

Writing Room Norms

Before you start writing together, talk about how you want to work. It does not need to be formal, but agreeing on a few things up front prevents friction later:

  • When will you write? Scheduled co-writing sessions where both people are online? Taking turns asynchronously? A mix of both often works well - synchronous sessions for creative breakthroughs, async for heads-down drafting.
  • Who writes what? Some teams divide by scene, others by character. Some pairs have one person draft and the other revise. There is no single right approach, but having one matters.
  • What is the creative chain of command? When you disagree on a story point, who gets the final call? In many teams, one person leads on particular sections or acts. Sorting this out early avoids stalemates.
Treat your first session as a planning session, not a writing session. Outline the story together, agree on character arcs, and divide responsibilities before anyone starts typing screenplay pages.

Communicating Changes

The most common source of friction in co-writing is surprise edits. You wrote a scene you are proud of, and the next time you open the script it has been rewritten. Even if the rewrite is better, the lack of a heads-up stings.

Some practices that help:

  • Do not edit someone else's scene without talking first. If you think a scene needs changes, tell your partner what you would change and why. Let them make the edits, or agree that you will handle the revision.
  • Use a separate communication channel. Ensemble is a writing tool, not a messaging tool. Keep a text thread, a Slack channel, a shared doc, or even a regular phone call where you discuss what needs to change and who will do it.
  • Leave notes for your partner. If you are writing asynchronously and you want your partner to review something, send them a message pointing to the specific scene. Something like "Take a look at the diner scene in Act Two, I'm not sure the ending lands" goes a long way.
  • Small fixes are fine without asking. Fixing a typo, correcting a character name, or adjusting formatting does not need a conversation. Rewriting dialogue, cutting a scene, or changing a plot point does.
Resist the temptation to "fix" your partner's work without talking to them first. What looks like a problem to you might be a deliberate choice. Ask before you edit.

Handling Conflicts

Creative disagreements are inevitable. Two writers will not always agree on the best direction for a scene, a character, or the story. How you handle disagreements determines whether collaboration makes the script stronger or wears the partnership down.

Separate the idea from the person. Critique the choice, not the writer. "I think the scene would be stronger if we cut the monologue" is constructive. "That monologue doesn't work" feels personal, even if you do not mean it that way.

Try it both ways. Stuck on two approaches? Write both versions. Seeing them on the page usually makes the better choice obvious. Export a JSON backup first so you can always go back.

Defer to the section owner. If you divided the script into sections or scenes, the person responsible for a section gets the final say on creative choices within it. Their partner can still offer feedback, but the section owner decides what to do with it.

Take a break if it gets heated. Step away from the script. Go for a walk. Come back to the conversation the next day. Most creative disagreements feel less urgent after some distance.

Version Control Tips

Ensemble does not have built-in revision history, but a few simple practices give you version safety:

  • Export a backup before major changes. About to restructure Act Two or cut a subplot? Export an Ensemble JSON file first. You can restore it if things do not work out.
  • Name your exports clearly. Use a naming convention like screenplay-title-draft-2-before-act2-rewrite.json so you can find the right backup later.
  • Export at milestones. Finished a draft, completed an act, or reached a version you both like? Export it. These snapshots are safe points you can return to.
  • Keep exports in a shared folder. Use Google Drive, Dropbox, or any shared folder so both writers have access to all backups. If one person has the only copy and their laptop dies, the backup is gone.
For writers who are comfortable with Git, Ensemble's Fountain export produces clean plain-text files that are easy to diff and version-control. Export to Fountain, commit to a Git repository, and you have a complete history of every draft.

Collaboration comes down to respect for your partner's time, their creative instincts, and the shared goal of writing the best screenplay you can together.