On a funded production the plan is held by twelve people. On an indie film it is held by one person who is all twelve departments at once. The four artefacts that survive that, and the rhythm that keeps them true.

Category
Filmmaking
Author

Justkay
Documentary Filmmaker & Founder at Storyflow
Topics
2026-08-26
•
17 min read
•
FilmmakingLook at how a studio production is organised and the striking thing is not the software. It is the division of labour.
The 1st AD holds the schedule. The line producer holds the budget. The production coordinator holds the paperwork and the contacts. The location manager holds the permissions. The script supervisor holds continuity. Each of them has a specialised document, a routine for updating it, and, critically, nothing else to think about that day.
Now look at an indie film. One person, or two if you are lucky, holds all of it. The same head that spent the morning rewriting a scene is in the afternoon working out whether the location is available on the 14th, and in the evening chasing a sound recordist who has not replied.
That switching is the actual cost, and no tool removes it. What a good system does is make each switch cheaper: you come back to the schedule after six hours of writing and the schedule tells you where you were, instead of you having to reconstruct it.
Three things follow, and they explain why so much indie film organisation advice misses.
Advice built for crews does not transfer. Call sheet software, stripboard scheduling, and departmental workflows all assume somebody whose job is that document. On a five-person shoot, adopting studio paperwork means one person doing twelve people's admin, and it collapses in week two.
The system has to survive being ignored. Indie films go quiet for months. A system that requires weekly upkeep is a system that will be wrong when you come back to it, and a wrong system is worse than a rough one because you trust it.
Updating has to be cheap. If changing a shoot date means editing four documents, it will get changed in one and the other three quietly become lies. This is the single most common way indie film plans fail, and it is a structural property rather than a discipline failure.
Across the indie productions I have run and watched, the systems that survive to the shoot are almost always the same four artefacts. Not twelve. Four.
One: a project home. One place where the film lives. Treatment, look, structure, references, and the current state of things. It is what you open when you come back after two weeks away and cannot remember where you were. Most indie films do not have this, and that absence is why the first hour of every return session is spent reconstructing.
Two: a live schedule. Not a Gantt chart. A dated list of what happens when, with the fixed things marked as fixed. Shoot dates, availability windows, deadlines that come from outside you. The value is that it is one document and it is true.
Three: a folder structure agreed on day one. Where footage goes, where audio goes, where documents go, and the naming convention. Decided before there is anything in it, because deciding afterwards means renaming four hundred files. This is the most boring item on the list and the one that saves the most time.
Four: a contacts sheet. Every person, their role, their number, and what they agreed to. On a small film the cast and crew agreements live in text messages, and a single sheet consolidating them prevents the most avoidable failure in indie production, which is somebody not turning up because nobody confirmed the date in writing.
Everything else is optional. Shot lists, storyboards, breakdowns, budgets, and call sheets are all genuinely useful and all downstream of these four, and none of them survive if the four are missing.
| Artefact | What works | What does not | Free option |
|---|---|---|---|
Project home | A canvas or board per film (Storyflow, Milanote, Notion) | Scattered docs, a chat thread | Milanote free tier, Notion free |
Live schedule | One shared calendar or one dated sheet | Four documents with dates in them | Google Sheets, Google Calendar |
Folder structure | Agreed naming, cloud sync, one root | Deciding later, per-person conventions | Google Drive, Dropbox free tier |
Contacts and confirmations | One sheet with a confirmed column | Text messages and memory | Google Sheets |
Shot list | Sheet or board, ordered by setup | Ordered by script order | Google Sheets |
Call sheets | StudioBinder if you shoot often | Making them by hand every time | A template document |
Prices and free tiers change; check before committing. The pattern that matters more than the tools: one artefact, one home, one update.

An indie film project home on a Storyflow canvas holding the treatment, look, structure and current state in one place
Indie films go quiet for weeks, and the first hour back is spent reconstructing where you were. Storyflow's AI reads the whole board, so a project home can tell you what state the film is in rather than making you reread it. Paid-only during early access; Milanote's free tier and Notion cover the same four artefacts for nothing.

Organisation on an indie film is not a state, it is a habit with a frequency, and the frequency matters more than the tooling.
Daily during production, ten minutes. At the end of each shoot day: what got shot, what did not, what moved, what broke. Ten minutes into the schedule and the project home. Skipping this is how a shoot ends with nobody sure whether scene 14 was covered.
Weekly during pre-production, thirty minutes. Walk the schedule forward, chase whatever is unconfirmed, and update the project home with what changed. This is the session that catches the location that quietly stopped answering.
On every return after a gap, first thirty minutes. Do not start work. Read the project home, update it to reflect reality, and only then continue. Indie films have long gaps, and the temptation to jump straight back into the creative work is exactly how the plan drifts from the truth.
Once, at the start: the folder structure. Fifteen minutes, before there is anything to file.
That is the whole system. Roughly ninety minutes a week during prep, ten minutes a day during production, and one boring decision on day one.
Adopting a studio system. StudioBinder, Movie Magic, and full stripboard scheduling are excellent and they assume somebody whose job is that paperwork. On a small film, the setup cost is paid by the same person who has to write, direct, and produce, and the abandonment rate is close to total. Buy them when you shoot often enough that call sheets are a bottleneck, not before.
Building the system during pre-production and abandoning it during production. The most common failure, and it is predictable: the system is designed when you have time and used when you do not. If an update takes more than ninety seconds, it will not happen on a shoot day.
Keeping the plan in a chat thread. Decisions in messages are unfindable within a fortnight and there is no version that is current. The thread is where things are agreed and it cannot be where they live.
A separate document per department. A schedule, a budget, a shot list, a contact sheet, and a location list, each maintained separately, means five things to update when one date moves, so four of them become wrong.
Trusting memory during a gap. Indie films pause. After six weeks, what you remember is a summary of a summary, and the details that got lost are precisely the ones that cost money later.
Organising instead of making. The mirror-image failure and it is real. Some filmmakers use system-building as a legitimate-looking way to avoid the harder work of writing or asking somebody for a location. Four artefacts, ninety minutes a week. If you are spending more than that, you are hiding.
It helps with the return. Coming back after a gap, having something that can read your whole project and tell you what state it is in saves the hour you would spend rereading. That is the single most useful application here, and it is why keeping the project home on a canvas the AI can read is worth something. Storyflow, which we make, is built around exactly that, and it is paid-only during early access from $7.99 a month annual, with the Free plan landing before the end of 2026.
It helps with mechanical conversion. Turning a scene list into a setup count, or a setup count into a day estimate, is tedious and rule-based.
It helps with the chase list. Asking what in this project is unconfirmed is a question about your own material, and it catches the location nobody followed up.
It does not know your constraints. No model knows that your lead has an unreliable car, that the location's neighbour complains about noise after 6pm, or that your DP has a day job on Thursdays. Those are the facts that actually determine a schedule.
It does not make the phone call. Most indie film organisation is chasing people, and no tool does that. The system's job is to tell you who has not replied; the calling is yours.
Indie film organisation is discussed as a software question and it is a division-of-labour question. On a funded production, twelve people each hold one thing and think about nothing else. On an indie film, one person holds all twelve and switches between them all day, and every switch drops something.
No tool fixes that. What a good system does is make the switches cheap, which is why the four artefacts that survive are the ones you can update in ninety seconds and read in five minutes: a project home, a live schedule, a folder structure agreed before anything exists, and a contacts sheet that records what people actually agreed to.
Studio paperwork will not transfer, because it assumes a person whose job it is. Elaborate systems built during pre-production will not survive production, because they were designed when you had time and are needed when you do not.
And the rhythm matters more than the tooling: ninety minutes a week in prep, ten minutes at the end of each shoot day, and thirty minutes of reading before you start again after a gap. That is a small enough commitment to actually keep, which is the only property of an organising system that has ever mattered.
Four artefacts, not twelve: one project home where the film lives, one live schedule with the fixed dates marked, one folder structure agreed before there is anything to file, and one contacts sheet recording who confirmed what. Everything else, including shot lists and call sheets, is downstream of those and does not survive without them.
It varies far more than the marketing suggests. Common combinations are a board or canvas for the project home (Milanote, Notion, or Storyflow), Google Sheets or Calendar for the schedule, Google Drive or Dropbox for files, and StudioBinder only once shooting is frequent enough that call sheets are a bottleneck. Plenty of good films have been organised in a spreadsheet and a folder.
Once you shoot regularly with real crew, yes, because breakdowns and call sheets in the format crews expect save meaningful friction on the day. For a first short or a film that shoots twice a year, it is production paperwork software being maintained by somebody who also has to write and direct, and it usually gets abandoned. Start with a template document.
Assume gaps, and build for the return rather than for the day you set it up. One project home that tells you where you were, updated whenever something changes rather than on a schedule, and a rule that the first thirty minutes back is reading and correcting before any new work. The systems that fail are the ones that require weekly upkeep during months when nobody is looking.
Keeping the same information in several places. A date in the schedule, the call sheet, the contact thread, and the shot list means four updates every time it moves, so three of them become wrong and nobody knows which. One artefact, one home, one update is the whole principle.
Decide the folder structure and the naming convention on day one, before anything exists, and write it somewhere the whole crew can see. Root folder per project, then footage, audio, documents, and exports, with a date-and-scene naming pattern. Deciding this after two shoot days means renaming several hundred files, which nobody does, so the convention never happens.
If you can get one, it is the highest-value addition to a small production, because the core problem is one person switching between twelve departments. A producer removes the switching rather than adding a tool. Where that is not possible, the four artefacts are the substitute, and they work by making each switch cheaper rather than by eliminating it.
Roughly ninety minutes a week during pre-production, ten minutes at the end of each shoot day, and one fifteen-minute decision about folders at the start. If it is taking substantially more, the system is too elaborate for the size of the production, or it is being used to avoid harder work.
The folder structure and the project home, in that order, before any creative work goes anywhere. It takes half an hour and it is the difference between a project you can return to and one you have to reconstruct. Then the contacts sheet as soon as a second person is involved.
For the return after a gap, genuinely: something that reads your whole project and tells you what state it is in replaces an hour of rereading. It also handles mechanical conversion, like turning a scene list into a setup count. What it cannot do is know your real constraints, and it will not chase the people who have not replied, which is most of the actual work.
Not during early access. Storyflow is paid-only right now, from $7.99/month annual, with the Free plan launching before the end of 2026. Anyone a paid member invites to a board joins free, so a director on a paid plan can bring the producer and the DP on at no cost to them. For a free setup, Milanote's free tier or Notion plus Google Drive covers all four artefacts.
Reduce the number of artefacts rather than the discipline. On a one or two person shoot you need the project home, the schedule, and the folder structure, and the contacts sheet collapses into the schedule. What does not change is the ten minutes at the end of each shoot day, which matters more with fewer people because there is nobody else who noticed what got missed.
Not the tools, the gap length and the number of confirmations. A short can be held in one person's head for a week. A feature cannot be held in anybody's head at all, and it runs long enough that everything gets confirmed, unconfirmed, and reconfirmed. The four artefacts are the same; on a feature, the contacts sheet and the discipline of writing decisions down do far more work.
Table of Contents
Skip the blank canvas. Open one of these filmmaking boards in Storyflow and the AI builds on the structure that is already there, from research through the shot list.
A visual AI workspace where every feature lives inside one canvas. No tab-switching, no context lost.
Build your entire board from a single message
Type what you need in the AI chat at the bottom of your canvas. The AI adds cards, headings, and structure directly onto your board.
Use expert frameworks as AI context
Type @ in the AI chat and choose any Tactic. The AI tailors every response to that framework instead of giving generic advice.
Turn your board into a mind map in seconds
Ask the AI to restructure your canvas as a mindmap. It connects your ideas into a visual hierarchy so you can see how everything relates.
Storyflow actually began as a personal tool while working on creative and research projects.
We kept running into the same problem: ideas were scattered everywhere: notes, documents, and whiteboards.
Nothing helped us see how everything connected.
So we started building a workspace designed around how ideas actually grow.
→ Read how Storyflow was created
Justkay
Documentary Filmmaker & Founder at Storyflow
Published: 2026-08-26
Transform your creative workflow with AI-powered tools. Generate ideas, create content, and boost your productivity in minutes instead of hours.