Shoot out of order
without breaking the story.

Lay the scenes out in story order rather than shooting order, because continuity is a property of the order the audience sees and you will almost never shoot in that order. For each scene, record the state of every tracked element: not the jacket but the jacket unbuttoned with the left sleeve rolled, not the glass but the glass two thirds empty. Then mark which day each scene shoots and look for adjacent story scenes that shoot far apart, since those are the pairs at real risk. Photograph every setup on the day and attach the photos to the scene card, so that when you return to that costume in three weeks you are matching against an image rather than a memory. The discipline that matters most is recording state, because the error is almost never the wrong object.

For planning continuity, it is a strong fit. For logging it live on set, it honestly is not, and you should know that before choosing it. A dedicated script supervision tool like ScriptE handles timecode, lined scripts, and editor reports, and a paper log book in a competent script supervisor's hands is still faster on the day than any app. Storyflow's advantage is in prep and in the gaps between: laying the story order out against the shooting order, finding the dangerous jumps before you get to them, keeping reference photos attached to scenes, and having all of it beside your shot list and schedule. Many productions use both, and that is the right answer rather than a compromise.

Not during early access. Storyflow is paid-only right now, with plans starting at $9.99 a month, and a Free plan launches before the end of 2026. Anyone a paid member invites to a board joins free today, so your departments can read and update the plan without paying. If you want something free this minute, a notebook and a phone camera is the classic answer and remains genuinely effective, which is worth saying plainly.

Because state has to carry forward in story order while production happens in shooting order, and the two are almost never the same. A scene that follows on directly from another might be filmed two weeks later at a different location with a different crew on shift. Everything that was true at the end of the earlier scene, the tear in the sleeve, the half-eaten meal, the wet hair, has to be recreated from information rather than from the situation. If that information was never written down in a form tied to the scene, it gets recreated from memory, and memory is where continuity errors come from.

Photograph more than feels necessary, because storage is free and reshoots are not. At minimum, take a wide of each actor showing the full costume, a detail shot of anything with a specific state such as a rolled sleeve, an open button, a wound, or a stain, and a shot of the set showing where key props are positioned. Take them at the start of the setup and again if anything changes during it. Then attach the photos to the scene card rather than leaving them in a camera roll, because a photo you cannot find in three weeks is the same as no photo.

No, and any tool claiming otherwise is overselling. The AI can lay out your scenes in story order, build the structure for the elements you want to track, and give you a starting grid from a script description. It cannot see your footage, does not know what was on the monitor, and cannot tell whether the jacket was buttoned. Catching the mismatch is a human job. What the board does is make it far more likely that a human looks in the right place at the right time.

Yes, with one caveat about formats. Paste your script text onto the canvas or drop a PDF onto the board and the AI can work from it to lay out scenes in story order and suggest which elements need tracking. Storyflow does not import Final Draft, FDX, Word, or Fountain files directly, so export to PDF or plain text first and then paste or upload. From there you fill in the state notes, which is the part that needs a human reading the scene carefully.

Yes, and that is often the biggest practical gain. Share a view-only link and costume, props, makeup, and the script supervisor all read the same state notes in a browser with no account. A large share of continuity failures are not mistakes by any one department but a gap between two of them, where costume knew about a change that props did not. One shared board closes that gap. Live multi-editor presence with cursors is on the Max plan.

Yes, and it is one of the stronger reasons to use a canvas rather than a dedicated tool. The continuity board can sit beside the shooting schedule, the shot list, the wardrobe plan, and the props list on the same surface. That adjacency is what lets you notice that moving a scene to a different day has just created a continuity risk, which is the sort of connection that gets missed entirely when the schedule and the continuity notes live in different applications.