Movie Magic Scheduling alternatives

Why look beyond Movie Magic Scheduling at all?

Movie Magic Scheduling has clear strengths — anyone switching should know what they are giving up:

• The stripboard implementation the industry standardised on
• Handles complex scripted schedules with many elements
• Output is recognised by every experienced 1st AD

Where teams hit limits

The search for an alternative almost always starts at one of these points:

• Desktop-first workflow with licence-bound installation
• The schedule is arranged manually; constraints are not computed for you

1. TillyGen — brief to shoot-ready plan

TillyGen produces a stripboard too, but derives it from constraints — daylight, travel, crew availability — rather than manual arrangement.

A fit for commercials, brand films, corporate and social work — anywhere a brief lands and has to become a plan a crew can actually shoot from, quickly.

Its file formats are a de facto standard, so exports usually travel well.

Other alternatives

Pure scheduling tools are strong when the schedule is the problem — and silent about everything upstream of it. They assume a finished breakdown: if the scenes are not yet in strips, there is nothing useful to open the stripboard editor for.

Depending on your bottleneck, these are worth a look — each with a different centre of gravity:

• Gorilla Scheduling: Independent narrative productions on a tight budget.
• Movie Magic Budgeting: Productions that must deliver budgets in a studio- or broadcaster-specified format.
• Filmustage: Teams that need a fast first-pass breakdown of a long script.
• Shot Lister: Directors and ADs who work from a phone or tablet on the floor.
• Boords: Animation and commercial teams whose approval process runs on boards.
• Milanote: The concept phase, before a production system takes over.

What the choice actually turns on

The useful question is not which tool has more features but where your process stalls today: writing the plan, distributing the paperwork, or getting sign-off. A tool that solves the wrong problem well stops being opened after three weeks.

Just as important is who is meant to work in it. A tool only the production office uses, while the director and DoP stay in spreadsheets, moves the problem rather than solving it — the paperwork then drifts between tool and spreadsheet instead of between two spreadsheets.

Before you migrate

Three things you can settle in half an hour beforehand, and that cost weeks if skipped:

• Export formats: does what comes out match what post, accounting and the client expect — PDF for the crew, CSV for downstream systems, API for anything automated?
• Existing data: do live projects have to move with you, or is a clean break between two jobs enough? The clean break is almost always the cheaper answer.
• Access: who on the crew needs read access, who needs write? Per-seat pricing gets expensive fast as the crew grows.