TV series pre-production software, built for a season rather than six films

The difference is not length, it is repetition. On a feature, every set, every role and every constraint exists once: you break it down, you schedule it, you pay for it. On a series the same elements come back across different scripts, often written by different writers, and rarely delivered all at once. Three consequences follow, and they are what should drive the choice of a tool. The breakdown has to feed a shared inventory rather than six parallel lists. The schedule has to be able to break episode order to group locations. And the budget has to exist at two levels, episode and season, without either being a hand-typed sum of the other.

A series breakdown produces a mass of elements, much of it recurring: standing sets, series regulars, picture vehicles, running props. If each episode builds its own list, production ends up with “Claire's apartment”, “Claire apt” and “APT – CLAIRE” counted three times, so budgeted three times and scouted three times. In Soldum the AI breaks down each episode separately — the right unit of work, since scripts arrive one after another — but matches recognised elements against the inventory already built by earlier episodes. What is new shows up as new; what recurs is proposed as a match, and production decides.

This is the economics of a series in one idea. If the lead character's apartment appears in episodes 1, 3, 4 and 6, it does not get built four times: the scenes set there are shot together, whichever episode they belong to. Cross-boarding is exactly the operation feature tools handle badly, because they only ever know one script at a time. In Soldum the grouping runs across every episode currently available: the schedule gathers scenes by location, time of day and availability, and shows for each shoot day which episodes it covers. When a script is rewritten or an episode lands late, the grouping is recalculated instead of rebuilt.

A series is financed across a season and controlled per episode, so both views are needed — broadcasters and streamers think in cost per episode, production runs against one overall envelope — and accounts do not behave the same way at the two levels. A set built once for ten episodes cannot be charged like a location rented for a day; a DP's weekly rate covers several episodes at a time. In Soldum the budget is held at season level, with the per-episode split derived from the shoot days actually allocated to each episode by the schedule. Dividing the total by the number of episodes, the usual shortcut, gives a wrong figure the moment episodes carry different shooting weights.

On a feature, an actor's availability is checked over five weeks. On a series it has to hold over four to six months, with guest cast appearing in only some episodes and therefore not needing a continuous hold. That combination — a few long engagements plus many short ones scattered across the calendar — is precisely what a spreadsheet loses. In Soldum each person carries their episodes and their availability windows, the schedule flags conflicting days before a contract goes out, and moving a block surfaces the clashes it creates. The tool does not arbitrate; it makes the clash visible while it still costs a phone call.

The direct consequence of cross-boarding is that a series shoot day often contains scenes from two or three different episodes. The crew therefore needs to know not just which scene is up, but which episode it belongs to — that drives costume, hair and make-up, continuity, and sometimes the performance itself. In Soldum the call sheet is produced from the schedule, one per day, and carries that information. It goes out by personal link rather than as an attachment, nobody has to create an account, each person confirms attendance in one tap, and production chases only those who have not. When a day changes the version changes and the link does not, so nobody turns up at the call time printed on a stale PDF.

Three ways of prepping a series coexist, and they are not separated by feature count. They are separated by what happens at episode six. A spreadsheet holds up fine through episode two; past that the set lists diverge and nobody knows which one is authoritative. A feature tool used once per episode does each episode correctly, but cannot group locations across episodes or consolidate a season budget — two operations it has no concept of. A chain built for series keeps the shared inventory, the cross-boarded schedule and both budget levels in one place. Disclosure: Soldum publishes one of the solutions described here.

Worth knowing before you open an account. No tool decides the shooting order: cross-boarding proposes, directing and performance decide, and there are days when you accept rebuilding a set to protect an actor's progression. No tool writes or rewrites an episode, and none replaces the continuity notes kept by the script supervisor. Soldum does not assemble your financing plan either — it tracks it. And nothing is changed in the project without your approval: AI suggestions go through a review queue, with their impact shown before they are applied. One point if you shoot in France or co-produce with a French partner: rates are checked against the French industry collective agreements, the sector-wide rate cards that set minimum pay. What the software removes is the retyping between episodes and the drift between schedule and budget. The rest is the job.