What production coordinators actually need from scheduling software

In this guide

• What coordinators actually do day-to-day
• The PDF problem
• The version control nightmare
• What good scheduling software looks like from a coordinator's perspective
• What coordinators don't need
• How Planner fits into the production timeline
• What Planner doesn't cover
• Common questions

What coordinators actually do with a schedule, day to day

The production coordinator's relationship with the schedule is fundamentally different from the 1st AD's. The 1st AD builds it. The coordinator maintains it - and that maintenance is a constant job.

A typical day for a coordinator involves receiving updates from the 1st AD or line producer about scenes that need to shift, timings that need adjusting, cast requirements that have changed. Then you're making those changes in whatever system holds your schedule. Then you're re-exporting or regenerating the current version. Then you're emailing that updated version to the relevant departments. Then you're tracking which version each person or department has been sent, because if the schedule changes again tomorrow, you need to know who needs the new version and who still has the old one. And in between all of that, you're fielding calls from departments asking if the schedule has changed, cast asking when they're needed, locations asking about site access times, and production trying to confirm logistics for the next location move.

The coordinator is the central hub of schedule distribution and communication. They're the person everyone goes to when they need to know what's happening next.

The PDF problem

Most production schedules live as PDFs. They have to - PDFs are portable, they work on any device, they don't require software, and they're the universal format for distributing documents across a film or TV unit.

The problem is that a schedule that exists as a static PDF is out of date the moment something changes. It's not a technology limitation - it's a fundamental property of paper-like documents. You email schedule_v7_FINAL_USE_THIS.pdf to the unit at 5pm. By 6pm, something's changed. But most of the recipients still have the 5pm version, and they're now working from information that's no longer correct.

Most productions operate in an endless cycle of revised PDFs. Version control becomes a nightmare. Is everyone reading from the same document? Has the director seen the latest one? Is the transport captain working from yesterday's location plan or today's? Did the construction crew get the updated site access time?

Coordinators spend enormous amounts of time trying to manage this chaos. Sending multiple versions. Chasing people to confirm they have the right version. Explaining over the phone what's changed since the last PDF was sent. It's not a failure of organisation - it's a structural problem with the format.

The version control problem

Version control - knowing which version is current and who has it - is genuinely hard when your tool is PDFs. You have to manage it manually. Email threads, shared drives, version numbering schemes that don't always get followed. It's easy to lose track. Someone downloads a schedule, saves it to their laptop, and now they're working from a version that may or may not be the current one.

If a department head or cast member is making decisions based on a schedule that's three days out of date, the knock-on effects are real. Car hire gets booked for the wrong date. Catering is planned for the wrong number of cast. A department brings the wrong equipment because they're prepping for a schedule that no longer exists.

The coordinator has to manage all of this by staying on top of who has what version, by sending updates proactively rather than waiting for people to ask, and by being immediately available to answer "has the schedule changed?" questions. Which coordinator hasn't received a dozen calls from the same person asking the same question because they're not sure if the version they have is current?

What good scheduling software looks like from a coordinator's perspective

From a coordinator's point of view, good scheduling software solves a specific problem: it allows the schedule to be current in a single location, and it allows people to access that current version without the coordinator having to send them anything.

That means:

• Live updates. When you make a change to the schedule, it's immediately visible to anyone with access. No re-exporting, no re-sending, no versions. You update it once and everyone sees the change.

• No version management burden. There's one schedule, not eight versions floating around. People access the current one because there's nowhere else to go. The question "do you have the latest version?" becomes unnecessary.

• View-only access that doesn't require a licence. Not everyone needs to edit the schedule. Directors, departments, cast - they need to read it. If every person who needs to see the schedule requires a paid user account or software installation, the coordinator ends up managing access instead of managing the schedule.

• Change visibility. When the schedule changes, people should be able to see what changed and when. Was that a timing update, a location change, or a complete rescheduling of this block? The history should be visible.

• Fast to update. Updating the schedule shouldn't be a 30-minute process. If a change takes longer to make in the software than it would take to explain on a phone call, the software is in the way. The coordinator needs to be able to make quick changes when problems arise on the day.

From a coordinator's perspective, the best scheduling software is invisible. It doesn't slow you down. It doesn't create work. It just makes sure the current information is available to the people who need it, without requiring you to manage distribution.

What coordinators say they don't need

Production coordinators don't need software that's designed for 1st ADs. They don't need complex breakdown tools. They don't need stripboard functionality or page-rate calculations or the ability to model different scheduling scenarios. Those are 1st AD tasks. They need the macro timeline that results from the 1st AD's work - they need to understand the shape of the production, the shooting blocks, the location moves, the dependencies - but they don't need the tool that builds it.

They don't need call sheets or script breakdown tools. Those live further downstream in the production process. The coordinator's job is keeping the team informed about the production schedule, not generating the detailed information that the 1st AD or production team will use to build the day's work.

What coordinators need is simpler than what those tools offer. They need a production timeline that's easy to read, easy to update, and easy to share. Everything else is feature creep.

How Planner fits into the coordinator's workflow

Planner is built around the macro production timeline - the shape of prep, photography, and post. The timeline is the document the line producer builds. But the shooting blocks, location moves, and production milestones that sit inside photography are things the production coordinator needs to communicate to the unit.

From the coordinator's perspective, Planner works like this: the 1st AD and line producer build the schedule. Once it's locked, the coordinator adds the macro timeline to Planner - the shooting blocks, the location moves, the key production dates. Then they share the link with the unit.

Everyone on the production - cast, departments, locations, anyone who needs to understand the schedule - gets a link to a current, live version of the timeline. They can see what's shooting when, where the unit is, what the location moves are. No PDFs. No versions. No "do you have the latest schedule?" calls. When something changes, the coordinator updates it in Planner and it's immediately visible to everyone with the link.

The coordinator doesn't have to manage distribution. They don't have to track who has which version. They don't have to re-export and re-send every time something shifts. They just maintain the current version. That's a fundamentally different relationship with the tool.

What Planner doesn't do

It's important to be direct about what Planner doesn't cover, because if these are your coordinator's primary responsibilities, you need a different tool.

Planner is not a scene-level scheduling tool. It doesn't break down the shooting day into individual scenes and their timings. That's the 1st AD's stripboard.

Planner doesn't generate call sheets. Call sheets come from the scene-level schedule - they're the daily breakdown of scenes, cast, equipment, and crew calls. They're produced by the 1st AD or an assistant director, not from the macro timeline.

Planner doesn't do script breakdown. Script breakdown - identifying what each scene requires in terms of cast, location, special requirements - feeds into both the scene-level schedule and the production timeline, but Planner doesn't handle that process.

If your coordinator's main responsibilities are managing the macro production timeline and keeping the unit informed about when and where the production is shooting, Planner covers that. If they're primarily working with scene-level scheduling, call sheets, and script breakdowns, they need a different tool. Most significant productions use different tools for those different jobs - it's not a limitation, it's a practical reality of how productions are structured.

The key insight: what coordinators actually do

Understanding what the coordinator's job actually is - version control, distribution, communication - changes what you look for in a tool. You're not looking for scheduling software. You're looking for communication software that makes the current schedule accessible to everyone who needs it, without requiring the coordinator to send it to them manually.

That's a simpler problem to solve than trying to build a tool that does everything a 1st AD needs. It's also a more solvable problem from a coordinator's perspective - because it focuses on their actual job rather than trying to make them into schedulers.

Getting started with a production timeline

Most coordinators work with whatever the line producer gives them. If that's Movie Magic or a spreadsheet, that's what they work with. What's changed in the last few years is that more productions are recognising that the coordinator needs a separate tool from the 1st AD's scheduler - one that's focused on keeping the team informed rather than building the schedule.

If you're setting up a new production and you want to try a different approach to schedule distribution, the workflow is straightforward. The 1st AD builds the scene-level schedule in whatever tool they use. The line producer or coordinator extracts the key production timeline - the shooting blocks, the location moves, the important dates - and adds it to a tool that can be shared live with the unit. When the scene-level schedule changes, the coordinator updates the macro timeline to reflect those changes. The unit always sees the current version.

It's a cleaner separation of concerns. The 1st AD focuses on the detailed schedule. The coordinator focuses on keeping the team informed. The tools support both jobs without trying to do everything.