Writing a script#

Applies to v0.10Last reviewed

In short

The Production Book holds a production's scripts as structured data: scenes, typed beats and links to the entities in your production bible, so later stages such as the board and the continuity check can read a script instead of parsing one.

The Production Book is where a project's writing lives. It opens as the Script tabThe tabs above the work areaA map of the Zymcos workspace. The five tabs above the work area, marked 1 to 5, are Home, Script, Bible, Viewport and Files.1Home is the first tab: the production at a glance.2Script is the Production Book, where the writing lives.3Bible sits between Script and Viewport: a list on the left and the entry you choose on the right.4Viewport is the stage, where the take you chose is shown.5Files is the last tab: every file in the production.A map of the Zymcos workspace, drawn from its layout. Your screen has more on it. of the canvas — a paper page inside the dark workspace, because a script is prose you read and re-read for hours rather than something you look at.

A script here is structured data, not a document. Scenes are records, beats inside them are typed, and the entities a scene involves are real links into your production bible. That is what lets later stages — the board, the shots, the continuity check — read a script instead of parsing one.

The Script page#

The page is laid out so the scene you are working on has the room:

  • A two-row header. The first row says what the script is: its title (click to rename), whether it is a draft or locked, its version, its format, about how long it runs (a clock for a commercial or a short, pages for a screenplay), and which script, on the right, when there are several. The second row says what to do: the next step on the left, and the actions on the right. Outline with CODA and Co-write are buttons; Board puts the scene board in the page's place once the script has a scene; everything else (the brief, adding pages, the breakdown, the table read, revisions, locking and unlocking, and export) is under More. What a script with no scenes cannot do yet is not shown until it can.
  • The scenes on the left, one row each: a small picture (the scene's chosen still, else the first take it has, else an empty frame that says no picture), its number, its heading, a dot for what the scene board says (green when nothing is missing, amber when something is, grey when it has no shots yet; point at it for the words) and about how long it runs. + New scene at the top of the list adds one. The list scrolls on its own however many scenes there are. Click a row, or use Up, Down, Home and End, to open a scene. The button above the list turns it into a filmstrip: the same pictures, larger. The open scene's row has the same outline as any other thing you are looking at, and a scene whose picture is a ★ chosen one has a ★ in the picture's corner. A scene's chosen still is the newest ★ still of its first shot that has one, and its chosen clip the same for clips; "chosen" is a ★, not an approval. The Gallery button in the header shows every scene as one tile with its chosen still and chosen clip side by side (each tagged Still or Clip, or an empty frame that says No still or No clip), its counts, a ★ and an outline when it has a chosen still, and the takes that are in no shot as one last tile, so "which scenes have no picture yet" is one look; a tile opens its scene. Your browser remembers which you chose. The page fits the space it has, so it widens when you collapse the right column: where the canvas is narrow the rows shrink to their numbers, and where it is narrower still the list is a menu above the page.
  • The open scene as a page, one scene at a time, with Previous and Next at its foot. A scene's link opens that scene, so you can send someone straight to scene 7. A commercial, a short or any other picture and sound format reads as a two-column table, picture and sound, with a time ruler down the left saying when each row starts and, when you point at it, about how long it runs. The times are estimated from the words, never timed, and the ruler says so.
  • The scene's details in the right column. On the Script tab the right column opens on Scene: the production's progress, the script's details (logline, genre and tone; an empty one reads + Add logline), the scene's comments and approval, its shots, and the takes no shot holds yet. History is the next tab, as it is elsewhere.

Where you are, and what comes next#

The next step lives in one place, the right column's Scene tab, so the Script page's header does not repeat it. It says the first concrete thing to do, such as Next: Make a still for scene 2. Point at it for why, and click it to open the step: the Bible on that entry, a scene, a shot's editor, or, when the step is done right here (adding a scene, making a shot), the box or button that does it, which briefly lights up so you can see where it is. When the step is not the earliest scene that has work, it says why: Scene 1 has its clip to do too: your order does every scene's still first. Before there is a script, the same step is one line at the top of the page. At the top of the right column's Scene tab, Progress counts the stages done out of six (2 of 6 done, always six), shows them as a bar (point at a segment for its stage; a stage that is not applicable yet is greyed and says not yet), and holds the next step. Show me opens it, All stages lists the six stages with their counts, and Hide puts it away for the session. When CODA tells you what to do next, it is this step, or it says plainly that it is suggesting a different order and why.

The next step is for the scene you are on. With scene 2 open, Progress says Next · scene 2 and the step for scene 2, not the production's first gap; under it, a quieter line gives the whole production's next, with its own Show me. A scene with nothing left to do says so and names the nearest scene that still has work. Each scene in the list also carries four small marks (shot, cast, still, clip), each in its stage's colour: filled when it has it, a ring when it does not, a faint dash where casting is not yet possible. Point at them, or read them aloud, for the words.

Phases. The tabs along the top are in the order of the work (Home, Script, Bible, Viewport, Files) and carry no headings over them; the Sequence below is the post-production step. A phase names where you are in the work without limiting what you can open. Ask CODA "which phase are we in?" and it answers from the same place the Progress strip does: pre-production until the Script and the Bible stages are done, production while shots, casting, stills and clips are being made, and post-production once every stage is done.

Each stage has its own colour, the same on every screen, and the shape says how far it is, never a second colour: a filled mark is done, a half-filled one is under way, a ring has not begun, a dash is not yet applicable. The segments of the Progress bar follow the same rule, and every state is also written in words.

The six stages are the order the work builds in, each worked out from what is actually in your production, and counted over scenes, so Stills 1 of 3 means one scene of three has a still:

  1. Script: done once there is a script with a scene to make shots from.
  2. Bible: done when every entry has reference pictures, is locked, is unedited since its lock, and has its rights affirmed. An entry with no pictures is named first, because a lock is refused while any entry has none.
  3. Shots: done when every scene has a shot.
  4. Cast: done when every shot that needs someone is cast. A shot whose "must look the same" is set to no does not need anyone, and undecided still does. Not yet applicable until something is locked.
  5. Stills: done when every scene has a still, whichever take you have chosen.
  6. Clips: done when every scene has a clip.

Your way of working orders the next step, and nothing else. By default Progress asks for every scene's still before any clip, because the storyboard comes before production. It can instead finish a scene (still and clip) before the next, or go straight to clips without stills. Choose it under Settings → How you work, for yourself or for one production. If you say it in the chat ("I'd rather do all the stills first"), CODA puts up a card and nothing changes until you click it. The order changes what is recommended; it never stops you doing anything and never changes what is true or what a stage counts.

It guides and never stops you: nothing is disabled because a stage is not done, and you can generate before casting (a take made before casting is not measured against anyone). It never asks you to lock the script, because a locked script takes no new shot for its scenes; locking is yours to do when the writing is finished. When every stage is done it reads Ready to generate. You can also ask CODA "what should I do next?"; it answers from the same place, and if it names a step that is not the real next one the reply is corrected with the real one.

Scripts#

A production can hold several scripts: drafts, alternates, a version for a different cut. The header's Scripts button opens the Scripts page: one card per script, each with its title, format, draft or locked, version, how many scenes it has and how many are approved, and when it last changed, so two scripts with the same title are still told apart. Open shows that script. Duplicate makes a new draft named Title (copy) with the same scenes (never locked, never approved), to try a different cut without touching the first. New script offers the same three ways in as a production's first script, and a script made anywhere, CODA included, arrives as a new card. Each one carries a title, a logline, a genre and a tone, plus a kind that names its production format — screenplay, commercial, live selling, music video, brand content, social short, event hosting or immersive.

Logline, genre and tone are in the right column's Script section, edited in place: click, type, click away. They are not decoration: CODA reads all three when it works on the script, so a logline that says what the film is about changes what you get back. A locked script shows them as text.

Formats#

A script's kind decides what it may hold and how it reads. Pick it when you make the script, and the editor offers exactly what that kind uses.

KindReads asLength is counted in
ScreenplayThe standard page: one column, dialogue under its characterPages (about a minute a page)
Commercial, Live selling, Music video, Brand content, Social shortPicture on the left, sound on the rightSeconds
Event hostingThe standard page, as a run of showSeconds
ImmersiveThe standard page, by place and momentPages

Screenplay scenes are numbered as scenes; every other kind numbers its scenes in sequence. The length of a scene is an estimate (spoken lines at speaking pace, what is only seen at reading pace), and is called an estimate wherever it is shown.

Scenes and elements#

Scenes are ordered. Each has a heading, an optional summary, and a list of elements, the typed pieces the scene is made of. Every kind has these three:

  • Action: what happens.
  • Dialogue: what someone says, carrying the character's name.
  • Transition: how the scene leaves.

Each kind adds the others it uses: parenthetical, voice-over (a name is optional), narration, on-screen text, super, lower third, music, sound effect, shot, B-roll, call to action, section and note. A screenplay offers parentheticals, voice-over, music, sound effects, sections and notes; a commercial offers voice-over, narration, text, supers, lower thirds, music, sound effects, shots, B-roll and a call to action. A note is for you and your team: it is never part of the pages you hand on.

Elements are validated on every save, so a malformed one never becomes part of a stored script. Dialogue without a character is refused, and so is a character name on an element that cannot have one. An element a kind does not use is refused too, with the kind named. Every element has a name of its own behind the scenes, which stays with it when you edit around it, so a comment or a revision can point at it later.

Scene numbers come from scene order. There is no separate number to maintain: reorder the scenes and the numbering follows. Ordering moves by the up and down controls on the open scene rather than by dragging. A new scene's heading goes in the box under the list of scenes.

A scene can also reference the entities that appear in it, linked to your project's bible entries rather than retyped per script.

Bringing a script in, and taking it out#

A script you already have does not need retyping. It arrives as Fountain, the plain-text screenplay format that Final Draft, Highland, Fade In, Celtx and WriterDuet all read and write, as a Final Draft .fdx file, or as plain text. You see what was found, how many scenes and elements and about how long, and anything that was changed on the way in, before anything is written. Importing adds the scenes after the ones already there, as one edit; it never replaces a script, because shots may already be made from its scenes.

Fountain's everyday syntax is read: a title page, scene headings, action, character cues with their dialogue and parentheticals, (V.O.) voice-overs, transitions, sections, synopses (kept as a scene's summary) and notes. Text before the first heading becomes a scene called Opening. An element a kind does not use arrives as action, with its words. A very long passage is split into several elements, and a scene with more than 200 elements into two, and the report says so.

Plain text reads a line starting INT., EXT. or Scene 3 as a new scene, NAME: words as dialogue, MUSIC: words (and the other element names) as that element, and everything else as action.

A Final Draft file is read for what a script is made of: scene headings, action, characters with their dialogue and parentheticals, and transitions. Formatting, revision marks and page layout in the file are not carried over, and a file that is not a Final Draft script, or that tries to load anything from outside itself, is refused with a sentence and nothing is written.

Export (under More) writes the script as Fountain, plain text, Final Draft (.fdx) or a PDF, named after its title. What Fountain has no line for, such as a super or a call to action, is written as an action line that begins with its name in capitals, and reads back into the element when the same kind imports it. A script exported and imported again comes back as the same scenes.

The PDF is the page a screenplay prints on: 12-point Courier on US Letter, the margins and columns the industry uses, a page number from the second page, and, for a script in production, the scene numbers in both margins. Its title page carries the title, the logline, the genre and tone, the format and the brief's target length, the version and date, and the production's name, and only what the script has. Each scene's synopsis prints under its heading (an outline CODA wrote is its synopses, so a first draft is no longer a list of bare headings), and a scene with nothing in it says so. Notes are never printed. Export is greyed out only when there is no scene to print, and it says so under the item. The PDF uses the standard Courier font, which holds Western European characters; a character outside them (a script in another alphabet) prints as ?, the download tells you how many, and Fountain or Final Draft carry the full text.

Starting a script: three ways in#

A production with no script opens on Start a script. Choose the format first (it decides what the script may hold and how it reads), then the way in:

  • Write it myself. A title, then the editor.
  • Develop it with CODA. Give your idea and as much of a brief as you have, and CODA drafts an outline for you to approve. A solo creator may bring one sentence; an agency may bring a whole client brief.
  • Bring mine. Paste or choose a Fountain or plain-text file and see what was found before anything is made (see the section above).

The brief#

A script can carry a brief: your idea, the audience, the tone, where it runs, how long it should be (in seconds), what it is about or selling, what it must never claim or show, and what the viewer should do at the end. Every field is optional. CODA reads the brief whenever it drafts, and the length is what a draft is measured against. Open Brief under More to read or change it; a locked script keeps its brief as it was.

CODA drafts, you decide#

Outline with CODA (in the header) and Draft with CODA (the sparkle on the open scene) ask CODA to write one stage: an outline (a logline and the scenes in order) or one scene's elements. Either way:

  • A draft is a proposal. It waits in CODA's drafts, under the header, and nothing in your script has changed until you approve it. An outline adds its scenes (each with its heading and a line of what happens, ready to be drafted next). A scene draft is shown beside the scene as it is now, with its estimated length, and Use this scene replaces that scene's elements.
  • Approval is one edit. It is the same edit as typing, so if the script changed in the meantime you are asked to reload, and if the scene itself changed after the draft was written, the draft is set aside rather than written over your words. A locked script takes no draft.
  • It fits the format. CODA writes only the elements your format uses, and an answer that does not fit is asked for once more and then reported, never half-applied. If CODA cannot be reached, the draft says so and nothing was changed; Try again asks again.
  • There is an allowance. Drafting is on Zymcos's bill, within a daily allowance for your workspace, counted in characters written. Before you ask, the panel shows about how much the stage will write and how much of today's allowance is used, and it will not start a stage that would pass it.

You can also ask in chat: "draft an outline for me", "draft scene 2 with more tension". CODA queues the stage and tells you it will appear in the Script tab; it never says it is done or applied, because only you approving it makes it so. "What is the state of my draft?" is answered from the drafts themselves. If there is no script yet, CODA creates one first and then queues the draft. Asked to "make a shot for scene 1", CODA makes the shot in that scene, and offers its first take after; it does not put up a picture with no shot to hold it.

From the script to the Bible and the shots#

Breakdown (under More) reads what the script says it needs and shows it as cards. Nothing is added until you press a button.

  • Who and where. The characters are the names on dialogue and voice-over (with (V.O.) and the like taken off), and the places are the scene headings that name one (INT. LIGHTHOUSE - NIGHT). Each shows the scenes it is in. Anything already in your Bible is matched without regard to case and marked, and one that is in the Bible but not yet linked to its scenes is offered again for the links. Add to the Bible adds the ticked ones as draft entries and links them to their scenes: no pictures and no rights yet, and the Bible asks for pictures next. Doing it twice adds nothing twice.
  • Shots. Each scene that has none shows the shots it might be broken into, with a length, a framing and, where someone speaks, that the character must look the same. A scene is cut into shots of about six seconds (between three and ten, which the video models take) between its elements, and a scene written with explicit shot calls gets one shot per call. A long moment is one shot at most ten seconds, and the shot editor is where to cut it further. Break into shots makes one scene's shots; Break all makes every proposed scene's.
  • It is only what you pressed. If the script changed since you looked, nothing is added and you are asked to reload; a locked script takes none. Props and looks are not found here, because they are an inference: ask CODA.

The scene board: what each scene has, and what it is missing#

Board (in the header) puts a table of every scene in the page's place: every scene against what it has: what is written (elements and about how long), the entries it names and how many are locked, its shots and how many have someone cast, and its takes, how many are video and how many are starred. The last column says what the scene is missing, in words: "Maya has no pictures yet", "1 shot needs someone cast", "No shots yet", "1 shot has no video yet". A scene that is missing nothing is marked complete; a scene's heading opens it on the page, and Board again puts the page back.

It guides and never stops you: a scene with gaps is a scene with gaps, and nothing is blocked because of what it says. The same words are what the path and CODA use, so asking CODA "what is missing, scene by scene?" gives you the board's answer, and if CODA says a scene has no shots, has a number of shots, has no video or is finished when the board says otherwise, its reply is corrected with what the board says.

Two more columns come from the same script. Estimate is what it would cost to make that scene's shots once: for each shot, a still and the video of the shot's length, at the quality you choose under the table (draft or production quality), worked out the way the ledger does when you actually generate. It is the cost of the pictures and video and nothing else (not a crew, not retries), and the line under the table compares the total with the cap CODA proposes for an autopilot run. A part that has no price in the catalogue is not counted and not free: the figure then reads "at least", with a "≥" beside the scenes affected, and the line says which part has no price yet. Approval says whether someone approved the scene and whether that still stands (see below). Neither changes whether a scene is complete.

When the script changes after things were made from it#

Every scene has a revision that moves when its elements or heading change, and not when only its summary, its entries or its order change. A shot remembers the revision of its scene that it was made for, and so does each take made for a shot, so when you rewrite a scene the things made from the old words say so: the shot's strip shows Script changed since this was made, the scene board lists "1 shot was made for an earlier version of the scene" and "2 takes were made for an earlier version of the scene", and CODA is told when you are working on that shot.

It is information, never a gate. Nothing is deleted or blocked, and the continuity marks are untouched (a score always names the version it was measured against). You can regenerate, let it stand, or press Keep as is: one act that confirms the shot and its takes against the scene as it now reads, and clears the note. A take you placed in a shot by hand has no revision to compare, so it is never called out of date on a guess, and everything made before this was added counts as current until the scene is next changed.

The open scene's shots#

The right column's Scene tab shows the open scene's shot strip: its shots in board order, each a card with its number, a line of what it asks for ("medium close-up · push-in · 3 s", or "no requirements yet") and its take count — "Shot 4 · 2 takes" — and its takes as thumbnails, each marked Still or Clip. A ★ marks the circled take, and the chosen one of each kind has a warm outline (the take you are looking at has the brand-coloured one). All / Stills / Clips above the cards shows only the stills or only the clips. The strip is a view of the same files the Viewport shows, so the two never disagree about what a take is called or which one is circled.

Click a take to put it on the stage. The canvas switches to the Viewport, the take is shown, and History and the other panels follow — it is the same selection every surface shares, so the browser's Back returns to what you looked at before. The takes wrap inside their card when a shot has more than fit, on a phone as on a desktop.

A scene with no shots says so and offers Add a shot, and one that has shots offers Add another shot. Either adds one shot to the end of the board, belonging to that scene; the script is implied. On a locked script the control is disabled and says so. A shot made with no scene can be put in one later: ask CODA ("put Shot 1 in scene 1"). When CODA makes a shot it says which scene it is in, and it asks which scene when the script has more than one. To assign a take to a shot, use the stage's controls, or drag the take from any strip onto the shot you want: while you drag, each card offers assign here. A locked script offers no drop.

A take made for several shots at once appears in the strip of each of them, under the name that says so ("Shots 2–3 · take 1").

At the end of the script an Unassigned strip gathers what the board has not placed: takes made for no shot ("Unassigned take"), and shots that belong to no scene. When there is nothing of either kind it says so rather than disappearing. The strips are cut from the takes loaded so far; if older ones exist, the Unassigned strip says that Load more in the Viewport's strip brings them in.

The Sequence: your frames, in order#

The strip at the bottom of the window is the Sequence: every shot you have made, as a frame, in the order your script reads (the scenes in their order, a scene's shots in theirs, and any shot no scene claims last). Collapsed, it says how many frames there are, how long they run together and how many have a still. Expand it for two views of the same frames:

  • Storyboard: a card per frame, grouped under its scene, with its picture (the chosen still, else the first take, tagged Still or Clip), its place in the sequence and how long it lasts. A frame with no picture yet says so. Click a card and that shot opens in the Scene panel. The first frame has no Earlier and the last has no Later.
  • Timeline: the frames along a ruler in seconds, each as wide as it lasts. Switching between the two changes nothing, because they are one sequence. Under the pictures, a Text lane shows your script's on-screen text, supers and lower thirds over the scene they are in, and a Voice lane shows its spoken lines from the scene's start, in script order. A spoken line is solid when it has speech, dashed while it is waiting for speech, and outlined in a warning colour when it cannot be spoken yet (point at it to see why: no voice recorded, no rights basis, or no speaker named). A line with no speech lasts as long as its words take to say, and is shown in italics to say so. These come from the script, so you change them in the script, and the storyboard shows how many each scene has beside its name. Making the speech is still the table read's card, because it spends.

You can move a frame by dragging its card (a line shows where it will land; drop on a scene's Last in this scene box to put it last), or from the keyboard: select it, then Alt+Left and Alt+Right, or the Earlier and Later buttons under it. Moving a frame inside a scene reorders that scene's shots; moving it across a scene's edge puts the shot in the other scene, so your script and the sequence never disagree. A selected card also has a Length box (in seconds). Undo and Redo at the top right of the strip reverse the last edit; each edit, yours or CODA's, is one step. A locked script's shots can't be moved directly, and the strip says so and offers Ask for this change, which holds the move for a person with the approve right to accept (The Sequence); once a script is locked, Undo and Redo of a move are refused the same way, so a lock really does hold the order.

You can also ask CODA in the chat: "move frame 3 before frame 1", "move frame 1 into scene 2", "swap frame 1 and frame 3", "remove frame 3", "make frame 2 five seconds long", "undo that", "save the storyboard as a version called Client round 1". CODA names frames by the number on their card. When your own message asks for the edit and names the frame (both frames, for a swap), it is done at once and CODA says what it did to the order; when CODA suggests an edit itself, you get a card to confirm, and the Undo button reverses either. A swap puts two frames in each other's places, and in each other's scenes if they are in different ones, and one Undo puts both back. CODA can also tell you which versions are saved and what has changed since the newest, and "present the storyboard" (or "present version 2") gives you a Present card to click, since Present takes over the whole screen. Saving "a version" without saying the storyboard is a different thing: that locks the Bible. A frame is a shot, so removing one deletes its shot, and only when the shot holds no takes: takes are never deleted, so a frame with a take in it stays and CODA says why. A locked script's frames can't be removed here either. Getting a version approved, the strip's menus, zoom and voice are on The Sequence.

Versions. Save version (top right of the strip) keeps the sequence exactly as it stands: every frame, in order, with its scene, its length and its picture, and which version of the Bible it was made on. Give it a name or let it number itself (Storyboard v2). The chip beside it says which version is newest and how much has changed since (v2 · 3 changes since; point at it for "1 frame added, 2 moved"), and its list shows who saved each. A saved version never changes, whatever you edit afterwards; it is how you show a client the storyboard as it was.

PDF. PDF (top right of the strip) downloads the storyboard as a sheet you can send or print: landscape A4, six frames a page in script order, each with its picture, its number, its length and its scene, and a footer with the production, which version it is and the date. Each saved version in the list has its own PDF, which draws the storyboard as that version kept it. A frame with no picture yet, whose latest take is a clip, or whose picture cannot be read prints as a labelled empty box, so a gap is never hidden. The sheet holds stills only, shrunk to fit the page and without the original's embedded information, and its text uses the standard Western European alphabet, so a character outside it prints as a question mark. A storyboard of more than 300 frames is not exported in one sheet.

Present. Present (top right of the strip) shows the sequence full screen as an animatic: each frame's picture is held for the length the frame has, with its scene and place underneath. Space plays and pauses, the arrow keys step, Escape leaves. A frame with no picture yet shows an empty frame, so a gap is never hidden. Open a saved version's list and choose Present beside it to show the storyboard as it was when you saved it.

A frame lasts as long as its shot's duration. A frame whose shot has none is counted at three seconds and says (default); set the shot's duration and the frame follows. There is no separate order to keep in step with the script: moving a shot or a scene moves the frame.

Setting up a shot#

Each shot in a strip has an Edit button. It opens the shot editor, a panel beside the script that does not block the screen: the chat stays open next to it, so you can ask CODA how to fill a field while the field is in view, and Escape (pressed in the panel) or its close button puts it away, where you say how the shot is made: its length in seconds, its framing (from extreme wide to extreme close-up), a camera move, the light, the aspect ratio and resolution, whether anyone speaks, and whether a character must look the same. Every one of them starts as Not decided, and that is a real answer: a shot can exist before anyone has decided how it is shot, and you can return any field to Not decided.

A camera move that takes an amount asks for it in its own unit. A pan, tilt or orbit asks how far it turns, in degrees (negative turns left or down). A push in or pull out asks how tight or wide it ends, as a multiple of the first frame (1.5 ends 50% tighter). Tracking and static take none, and the sheet does not ask. A move also takes a time of its own, which cannot be longer than the shot.

What these do today. The sheet says it at the top, and it is exact: the requirements are recorded for checks and routing. The length sets what a video of the shot costs, and whether a character must look the same decides whether the path above asks you to cast the shot; the rest does not change the picture yet. They are still worth setting: they are the record that cost estimates, routing and the continuity checks read as they arrive, and CODA reads them when you talk about the shot.

Save sends only what you changed. If something is wrong, for example a move longer than the shot, the sheet says exactly what and that nothing was saved, and your edits stay for you to fix. If CODA or another tab changes the shot while the sheet is open, your edits are kept, the sheet shows the new values for everything you did not touch, and it tells you the shot moved. Closing with unsaved changes asks first. The cast is shown on the sheet and is held to the Bible's locked versions.

You can ask CODA for the same things in plain words: "make shot 3 six seconds", "give this a close-up with an orbit", "move shot 3 to the front", "add a shot to this scene". CODA does these at once, says what it did, and offers Undo on the line, but only while the shot still holds what it set. It names a shot by its number ("shot 3") or by the shot open in the editor, and asks if it is not sure which; it never guesses.

CODA casts a character only if you named them. "Put Maya in shots 1 and 3" is done; "put her in shot 3" gets the question "which entry do you mean?", and nothing changes. It counts your own last few messages, or the entry you have open in the Bible. A first name is enough while only one character has it; if two share it, say the full name.

Deleting a shot. Delete this shot is always on the sheet, and asks first. A shot with takes can be deleted: the confirmation shows the takes, says These 2 takes move to Unassigned. Nothing is lost: their history and scores stay on the record, and the takes wait in Unassigned to be put in another shot. For 30 minutes after a delete a bar offers Undo, which brings the shot back with the takes that are still in Unassigned (a take you put somewhere else meanwhile stays there). The one thing that stops a delete is a shot that holds a final: replace the final through a request first, and the sheet says so. History lines that say a take "moved from" a deleted shot will no longer name it. If you ask CODA in your own words to delete a shot that has no takes ("delete shot 3"), it deletes it and says so. For a shot with takes, or if CODA suggested the deletion and you answered "ok", you get a confirmation card to click instead, and the card says what moves.

Locking a script#

A script is either a draft or locked. Locking says the content is a commitment that later stages build on. What that means depends on the format.

A screenplay locks the way a production script does: the scene numbers are frozen and every later change is tracked, not refused. See A locked screenplay: revisions below. Every other format keeps the simple lock: a locked script refuses edits to its scenes and beats with a reason the editor shows you.

Lock the script and Unlock the script are under More. Unlocking exists and is recorded. Locking again is how you re-commit after a change. Lock the script opens the lock's check: one row each for the script's state, its scenes, its shots, which scenes are approved and the requests open against it, each marked fine, open or stops it, with the names and a Show me link where something is open. Under it is what the lock means (the script's words close, and shots and takes stay free), then one button: Lock script when nothing is open, Lock anyway when something is. That button is the confirmation, and Cancel locks nothing. Deleting a scene asks too, because content is destroyed. While a script is locked, every control it closes stays on the page, greyed, with the reason on it, and a note above the scenes says what the lock means and offers Unlock the script. Everything else — heading, summary and beat edits — simply saves.

A lock files a copy. The moment you lock, an exact snapshot of the script at that version is written into the Script folder of the Files tab. It is the record of precisely what everything generated afterwards was based on — so if you rename the script, or unlock and keep writing, the snapshot does not change with it. That is what makes it evidence rather than a shortcut back to the editor.

If the snapshot cannot be written for some reason, the lock still happens. You will see the Script folder without that version in it, and locking again writes it.

A locked screenplay: revisions#

When you lock a screenplay, its scene numbers stop moving, the way they do on a production: scene 12 stays scene 12 whatever is cut or added around it. The script is then in the white revision (the script as locked), and it still takes changes. Each change belongs to the current revision set, and the sets run in the industry's colours: white, blue, pink, yellow, green, goldenrod, buff, salmon, cherry, and round again.

  • The first change after the lock starts the blue revision. Every later change belongs to it until you choose Revisions under More, then Start the next revision, which begins pink and so on. A set with no changes in it cannot be followed by another; the panel says so.
  • A scene you insert takes an A number. Use the + on a scene to add one after it and it becomes 12A (then 12B); a scene added at the end takes the next whole number.
  • A scene you remove is omitted, not deleted. Its number stays, it is marked OMITTED with its words kept, and Restore brings it back under its own number. Nothing is destroyed once numbers are frozen.
  • A revised scene carries its colour. The scene shows a chip in the colour of the last set that changed it, and a PDF prints a page that holds such a scene on that colour of page, headed with the revision's name and date, with an asterisk in the margin against its lines.
  • The Revisions panel lists the sets, newest first, and what each changed (the scene's number and what was done to it, never its words), so you can see who changed what, and when, without opening the script.

A shot can be made for any scene of a locked screenplay, because the lock no longer means the scenes are closed. A scene whose words change still marks the things made from it as out of date, as before.

Screenplays that were already locked when this arrived became "locked, white revision, numbers as they are": the first change you make to one starts the blue revision, and nothing before it is called a change.

Hearing the script: the table read#

Table read (under More) lists every spoken line of the script, by scene, against the speech made for it. A line is dialogue, or a voice-over that names who speaks it; directions (parentheticals), narration and calls to action are not lines here.

  • A line is spoken when a speech take exists of exactly its words in its speaker's voice, whoever or whatever made it: a CODA card you approved, an autopilot run or your own click. The ★ take stands for the line, otherwise the newest. Two identical lines share one take. Change the words and the line goes back to to speak, because the old take says something else; change the speaker's voice in the Bible and the lines go back to to speak in the new voice.
  • A line to speak has a Speak button. It does not spend anything: it puts a card in CODA with the line's words and the speaker's voice, priced, and your click on the card is the one spend, as for every generation. The summary line says how many characters are waiting and about what they would cost at draft or production quality. If the speech model has no price in the catalogue it says so instead of showing a figure.
  • A line that cannot be spoken yet says why, in words: "There is no character called GHOST in the Bible", "Mara has no voice recorded", "Mara has no rights basis, which a voice may not be used without", "Name who speaks this voice-over". A voice needs a rights basis before it may be used, as everywhere in Zymcos.
  • Play the table read plays the standing takes in script order and highlights the line being read. A line with no take is skipped, and a take whose file cannot be loaded is skipped and said so; the table read never fills a gap with a different voice.

The table read uses the voices your Bible entries already carry; it adds none.

Writing together, live#

Co-write (in the header) lets several people type in the same script at the same time, each seeing the others' words appear as they are typed. It is off by default: a script is written by one person at a time, with the version check that tells you when someone else saved first, until a person turns co-writing on for that script. Where your workspace's deployment has not enabled it, the panel says so and offers no switch.

  • Turning it on makes you the script's first editor. You then invite members of your workspace, one at a time, each as an editor (types), a commenter or a viewer (both read along live; commenting stays on the scene). Nobody outside the workspace can be invited, and a member you did not invite cannot join. Remove takes someone out at once: their connection closes within a second.
  • While it is on, a scene's heading, summary and elements are boxes you type into in place, with no Save. Two people typing in the same element both keep their words. Each scene shows how many others have it open. Which elements exist, their order, their kind and their speaker still change the usual way (adding, removing or moving a scene works as before); the words of a scene can no longer be changed from anywhere else, including by CODA's drafts, and you are told why.
  • What you type is saved into the script a moment after you stop, when you press Save now, when the last person leaves and when co-writing is turned off. It is saved as an ordinary edit: the scene's version moves, shots made from the old words say so, the board and the exports read it, and in a locked screenplay it belongs to the current revision. The panel says whether everything is saved, and if something cannot be (a heading cleared to nothing, an element that is blank or too long) it says what, and the script keeps its earlier words until it is fixed.
  • Turning it off saves everything first. If some typed text cannot be saved you are shown what, and can fix it or turn co-writing off and discard that text. A script cannot be locked while it is being co-written: turn it off, which saves what was typed, and lock then.
  • If the connection drops, what you type is kept and shared when it comes back. If you are removed, or co-writing is turned off, you are told so.

Live cursors are not shown; who has a scene open is.

Review: comments and approvals#

The open scene's Comments button and approval line are in the right column's Scene tab.

  • Comments are notes on the scene, or on one of its elements. Write one, answer one, and Resolve a thread when it is dealt with (resolved threads fold away and Reopen brings one back). You can delete your own comment; deleting the first comment of a thread deletes its answers with it. A comment is a conversation about the script and is not part of it: writing one never changes the script, never makes a shot out of date and is never shown to CODA or used to write a draft. If the words a comment was about change, the comment stays with its scene and says "The words it was about have changed". In the Script tab's scene list an approved scene is tinted and says Approved, and one edited since says Approved, then edited, so the approval shows without opening the right column.

The scene's name, its approval state (Not approved, Approved or Changed since approved) and its Approve and Comments buttons share one row at the top of the Scene panel; point at Approved to see who approved it.

  • Approve records that you looked at the scene as it reads now and it is right. The approval names the scene's version, so you can only approve what you saw: if the scene changed while you were reading, you are told to read it again. An approval stands while the scene's elements and heading are as they were; the moment they change it reads Changed since approved and can be given again. A change to the summary, the entries linked or the order does not undo it. Withdraw approval takes it back, and the record of who approved what and when is kept either way. An omitted scene cannot be approved.
  • The scene board shows each scene's approval and how many scenes are approved. An approved scene is not thereby complete: approval is a person's judgement, completeness is what the scene has.
  • Approving and commenting are not edits, so a locked script takes both.

For now, writing a comment or an approval needs the same permission as writing the script. Reviewers who may only comment, and live co-writing, come later.

When two people (or you and CODA) write at once#

Every edit carries the version of the script it was based on. If the script moved underneath you, the write is refused and you are shown the current version with one action: reload.

The editor does not attempt to merge, and does not pretend to have merged. Losing a sentence you thought was saved is worse than being asked to reload.

What CODA can and cannot do#

CODA, the built-in creative assistant, can work on the script with you from the chat rail. It can create a script, read the current one back (every scene's words, or one scene in full when a script is long), edit the title and other metadata, add a scene, and edit an existing scene. Its edits go through exactly the same validation and the same version check as yours, and each one appears in the conversation as an activity line, so you can see what it did and not only what it said.

CODA cannot lock, unlock, or delete. A lock is a commitment later stages build on, and a deletion destroys content — both stay yours, made in the editor. Ask CODA to lock a script and it will say so and point you at the editor rather than failing quietly. (For the Bible, she runs the check and puts up the lock card for you to press; she never locks, even on autopilot.)

CODA also takes at most three actions in a single reply. If it is still working at that point, the turn ends with a visible note rather than continuing silently. A step CODA got wrong and corrects itself (a script kind that doesn't exist, say) doesn't use up one of the three; if it gets a step wrong a third time in one reply, it stops and tells you in plain words, with nothing more changed.