Skip to content

Brief import

Brief import turns a written production brief into a ready-made CineFlow project: project details, scenes, shots, cast, crew, gear, shoot days, a draft schedule, and callsheets, extracted automatically.

Click New project and choose From a brief on the first step of the New project wizard. On a plan without brief import the choice shows a lock and Import with AI? with an Upgrade button, and choosing it opens the upgrade dialog. See Import a brief for the steps.

Up to 15 files of up to 15 MB each: PDF, DOCX, PPTX, TXT or MD. They become one project. A person, a scene, a shoot day or a piece of gear named in two files is created once. An image (PNG, JPG or WEBP, up to about 3.5 MB) can be imported on its own, not together with other files.

Each file is read as you add it and shows Ready. A row that cannot go into the import says why:

  • No readable text: the file has nothing in it to read, such as a scanned page with no text layer. A deck that is mostly pictures is still used for the text it has.
  • Couldn’t open. Remove and add it again.: the file could not be opened this time. That is not a statement about what is in it.
  • Over 15 MB, Image over 3.5 MB, Images go alone, 15 files at most, Can’t import this type.
  • Too much text together: the set holds more text than about three full length scripts. Remove that file, or split it, and continue with the rest.

Remove the file and Continue becomes available again.

  1. When you click Continue on Add your files., CineFlow reads the project’s details from your files: name, type, stage, shoot dates, director, DP and aspect ratio. The next steps of the wizard show them, each marked From brief, and you can change any of them. If the details cannot be read, the step says Couldn’t read these files. Try again. and Continue reads them again.
  2. When you click Create project, the project is created in your current workspace with the details as you left them, your files upload into its Documents (the wizard shows Uploading 3 of 11 while they do), and the import starts. What you set in the wizard is kept: the import fills in a detail from your files only where you left it empty, and it never renames the project.
  3. A quiet banner on the Project Overview reads Filling in from your files, with what has been read so far in counts, for example “26 scenes and a script so far.”
  4. The project fills in while you watch. Each part appears as it is read: the overview shows a part once it has something in it (Script, Scenes, Shots, Cast, Crew, Shoot days), never an empty section, and the Shot List, Cast and Crew, Schedule and Script pages fill in the same way if you open them. The project’s card on the dashboard shows that it is filling in, and its counts climb. If you rename the project while it fills in, your name is kept.
  5. When the import finishes, the banner says what was built, in counts, for example “26 scenes, 44 shots, 6 cast, 18 crew, 5 shoot days and a script.”, a toast says “Your project is ready.”, and you also get an email and a notification.

The import runs in the background, so you can leave the page.

Only information found in your brief is used, and every value is normalized to CineFlow’s own option sets:

  • Project details: type, stage, dates, director, director of photography and aspect ratio where you left them empty in the wizard, and the currency. The name is the one you confirmed in the wizard.
  • The script. A screenplay among your files becomes the project’s script on the Script page, through the same script import the Script page uses, with its title page and its scenes. It is not rewritten or summarised. A PDF script keeps its page breaks and the space above each scene heading, so with the matching page size under Display on the Script page it has the same number of pages as the PDF. Scripts imported before this keep their pages as they are; import the script again to get its layout. A PDF screenplay laid out as a script page (dialogue and character names in their own columns) is recognised and imported without asking, unless its file name says it is another kind of document, such as a call sheet or a shot list. Anything else that looks like a script is not guessed at: a text or Word file, or a PDF typed flush left. The overview asks, with Import as script and Read as a document. A project has one script: if you add two, the fuller one becomes the script and the other stays a file in Documents, and the overview names it with Kept as a file. When one of the two is a marked up copy, by its file name (for example “Marked Up Script”), the clean one becomes the script whichever is longer. The marks on a marked up copy are not turned into shots: shot markup reads marks made on the Script page.
  • Scenes and shots on the Shot List, with descriptions, shot sizes, angles, lenses, movement, and camera where the brief specifies them. When there is a script, its scenes are the Shot List’s scenes and the only ones: a shot list or call sheet that refers to a scene by its number lands on that scene, and a location column (“Hallway”, “Garrison Woods Dirt Path”) never becomes a scene of its own. A shot is its scene number and its shot letter as your documents print them, so 2C in your shot list is 2C in CineFlow, never renumbered. The same scene and letter in the master shot list, a day’s shot list and a call sheet’s shot schedule is one shot: the master shot list gives its description, and the day’s list and the call sheet add their lens, lighting, length and notes. Each row goes under the scene its own Scene column names. A row that names several scenes, such as “13, 14, 15” with shot A, goes under the first, numbered by the scenes it spans (13-15A) so it never takes another shot’s number, with the others in its notes. Reading a file again after it failed, or after an import stopped before it finished, adds what it says to the shots already there that it numbers: it fills only what they still lack, links the cast members it names that are in the project and that a shot is not linked to yet, and keeps any time or length you set on a shoot day. A shot it does not number that is already there word for word is left as it is, and is not put on that file’s day. A shot with a time that it adds to a shoot day that already has shots goes among the ones that have a time, by its time, or at the end when none of them has one, and the shots already there keep their order. In a project without a script, a scene is found by its name, so a file read again that names a scene differently makes a new scene.
  • Cast (with contact details where present) and cast links on the matching shots. There is one cast member per character, with the performer when a file names one, for example a call sheet that lists “DYLAN - Adam Lee”. What a file says about a character, such as an age or a costume, becomes a note on that cast member, never a second one. A character written by surname in one file and in full in another is one cast member, and two names written together, such as “Claus/Marsh”, are two.
  • Crew, marked confirmed, with email and phone when a crew list gives them, and rates when the brief states them. One person written two ways, with a nickname in brackets or without, is one crew member. When your call sheets list their crew, each shoot day gets the crew its own call sheet lists, with the job they do that day when it differs from their usual one. When no call sheet lists crew, everyone is assigned to every shoot day.
  • Gear, categorized and matched against the gear catalog.
  • Shoot days, only for the dates a call sheet, a schedule or a shot list names as a day of shooting, numbered Day 1, Day 2 and so on in date order. A project that runs from 3 to 11 August with call sheets for five of those days gets five shoot days, not nine. When a day’s shot list or a call sheet schedules shots, each shot is put on its own day in the order of its time there, with its length, so a day shoots only the shots its documents name. A shot’s length on a day is the one its day’s shot list gives and its time the one its call sheet gives, whichever file was read first, when the files are read together; a file read again keeps a length or time already on the day. When two day shot lists that place their scenes on their own day shoot the same scene on different days, each list’s day is a shoot day; a day shot list that does not place its scenes on its day can still lose that day. Otherwise scenes are assigned to days when the brief maps them. Either way the Schedule page starts populated. Each day takes its general call from its own call sheet, and the cast that call sheet lists, at the cast call or at their own call time when the sheet gives one.
  • Callsheets for described days, with call times and locations.
  • Locations. A place a call sheet names becomes a project location, and its shoot day is set at it. One place is one location, however each call sheet wrote its address (“2 Millers Rd” and “2 Millers Road”). A location whose address CineFlow can find gets a pin, and then its nearest hospital and nearest parking, the same way a location you add yourself does. These can take a minute to appear after the import finishes. A hospital printed on a call sheet is not read into the location: the one shown is the nearest one found on the map, marked as automatic, and you can replace it with your own.
  • A file that is not about the shoot. A file that tells the story rather than the shoot, such as a pitch deck, a treatment or a lookbook, or a file about another production, is kept in Documents and nothing is built from it. The overview names it with Kept as a file.
  • The original files, saved as documents in the project.

If you set no shoot dates in the wizard and your files state none, the project’s dates are its first and last shoot day. Dates you set are kept, and widened only if your files name a shoot day outside them.

Everything is a normal, editable CineFlow object afterward; nothing is locked.

An import never deletes anything. The project, everything that was read, and your uploaded files all stay, whatever happens.

  • One file could not be read, the rest could. The project is built from the rest. The overview banner reads Imported, with 1 file left to read and names the file, with Try again beside it. Try again reads just that file into the same project and adds what it holds; nothing already there is written twice. Leave it keeps the project as it is, and the file stays in Documents.
  • A file that looks like a script. When CineFlow cannot be sure a file is a script, it does not guess, because a call sheet or a shot list can look like one. The overview names the file and asks This looks like a script. Is it? Click Import as script to make it the project’s script, or Read as a document to have it read like the rest of your files. If the project already has a script with writing in it, that script is never replaced: the file is kept as a file and the overview says so.
  • Try again only reads files that are waiting to be read, and Try all again leaves a file that is asking a question for you to answer. To add new files to a project, use its pages.
  • No file could be read. The banner reads Your files could not be read yet and says nothing was lost: the project and the files are there, and each file has Try again. You can also build the project by hand.
  • The import stopped before it finished. The banner says so, and the files can be read again. What was already built stays.

A long file is read in parts, by its pages, so its length does not fail an import.

The redesigned onboarding has a step called Bring a project? that runs the same import, with the same file limits, on the files you already have: pitch decks, call sheets, crew lists, scripts. It is free once for every new account, on any plan. There the project takes its name from your files: the title they state, or the script’s own title page, and until one of those has been read, the name your files share. It is never “Untitled Project”.

  • Drop or Browse up to 15 files of up to 15 MB each: PDF, DOCX, PPTX, TXT or MD. They become one project. A person, a scene, a shoot day or a piece of gear named in two files is created once.
  • Each file is read as you add it and shows Ready. A file with nothing in it to read, such as a scanned page with no text layer, shows No readable text on its own row. Remove it and continue with the rest. A deck that is mostly pictures is still used for the text it has.
  • If a row says Couldn’t open. Remove and add it again., the file could not be opened this time; that is not a statement about what is in it. Remove it and add it again.
  • A set with a very large amount of text, more than about three full length scripts, shows Too much text together on the file that goes over. Remove that file, or split it into smaller files, and continue with the rest.
  • An image (PNG, JPG or WEBP, up to about 3.5 MB) can be imported on its own, not together with other files.
  • Click Continue. Your files upload into the new project’s Documents while CineFlow keeps filling the project in, and you carry on with the remaining steps.
  • On the last step the project’s card shows Filling in and its counts climb, and the line under it says what has been built so far. When it is ready the line says what was built, in counts. You can click Open at any moment: the project’s overview goes on filling in.
  • If a file could not be read, the last step names it, with Try again for that file. The rest of the project is there. If no file could be read, it says Your files could not be read yet. Your project and files are kept, and your free import wasn’t used., with Try again, which reads the files into the same project.
  • The free import counts as used once anything has been created from your files: a scene, a cast or crew member, a shoot day or a script. If nothing was created it is given back. An import can be read again twice. After several imports in a short time you may see Too many imports for now. Try again later.; wait an hour and try again.

Or click I’ll explore on my own to skip the import and open the Small Hours demo instead.

Brief import needs Team or higher; on Free and Solo From a brief is locked and the upgrade dialog opens instead. It also creates a project, so it counts against your plan’s project limit; at the limit the wizard’s last step shows Need more projects? with Upgrade instead of creating. There is no separate AI quota on top of that. See Billing and usage.