By Eric Stracke, Co-Founder of Dayframe | Co-Founder & Creative Director at Gorilla Creative
If you've ever called your shooting schedule a "project timeline" in an email to a client, you're not alone. In branded content and commercial video production, these two terms get confused all the time. But a shooting schedule and a project timeline are different documents with different purposes. Understanding the difference between a shooting schedule vs. project timeline will save you from sending the wrong level of detail to the wrong people.
Here's the short version: a project timeline is the big-picture plan for your entire project. A shooting schedule is the detailed, minute-by-minute plan for what happens on set each shoot day. One zooms out. The other zooms in. Every project needs both, but they serve different audiences and answer different questions.
Let's break each one down.
A shooting schedule is the operational document that drives your shoot day. It breaks the day into time blocks, assigns scenes or setups to specific windows, and accounts for crew calls, meal breaks, company moves, and wrap time.
If you've ever built a video production shooting schedule, you know the level of detail involved. A typical shooting schedule includes:
The shooting schedule answers one question: what is everyone doing, and when, on this specific shoot day?
On larger productions, the 1st AD builds the shooting schedule in collaboration with the director and producer. On a branded content or corporate video shoot, the producer often handles this directly. Either way, it's the document that gets referenced on set more than any other.
For multi-day video shoots, each day gets its own schedule. The scenes might be reordered based on location efficiency, talent availability, or lighting conditions rather than script order. That reordering is the whole point. You're optimizing for production efficiency, not narrative sequence.
A project timeline is the high-level plan that spans the entire lifecycle of your project. It covers pre-production, production, and post-production milestones from kickoff to final delivery.
Think of it as the project roadmap. A project timeline typically includes:
The project timeline answers a different question: where does this project stand in the overall plan, and what needs to happen by when?
Project timelines are usually managed by the executive producer or project manager. On smaller teams, the producer handles both. The format is typically a Gantt chart, a shared spreadsheet, or a project management tool like Asana, Monday, or Basecamp. It looks and functions more like a project plan than a shoot document.
Here's where the distinction gets concrete.
The simplest way to remember the difference: the project timeline tells you which days you're shooting. The shooting schedule tells you what happens on those days.
One reason these terms get confused is that producers don't always think about where each document sits in the hierarchy. Here's a framework we use at Gorilla Creative that makes it easier to keep things straight.
Picture a ladder with four rungs, from broadest scope at the top to most granular at the bottom:
Each rung feeds into the next. The project timeline determines your shoot dates. The shooting schedule breaks those dates into operational time blocks. The call sheet communicates the schedule to the crew. The shot list tells the DP and director what to capture within each block.
Here's how this plays out on a branded content or corporate video project. At Gorilla Creative, we use Asana's timeline view for the project timeline, with tasks assigned to different team members across pre-production, production, and post. We build our shooting schedules in Dayframe. Call sheets get built in Google Docs and shared as PDFs. Shot lists live in Google Sheets. Four documents, four tools, each doing what it's best at.
Narrative work (short films, episodic, features) may need additional tools that specifically handle script breakdowns and stripboards, like Movie Magic or StudioBinder. The document ladder is the same, but the tools at each rung change based on the complexity of your production.
When a producer says "send the client the schedule," the confusion usually starts because it's not clear which rung they mean. For most client communications, the project timeline is the right document. For crew communications, the shooting schedule (and the call sheet derived from it) is what matters.
Every video project, no matter how small, has at least three dates that matter: when the script locks, when you shoot, and when you deliver. That's a project timeline. The scale changes based on the project, but the need doesn't.
Your project timeline might be simple: script approval by Monday, shoot on Thursday, rough cut the following Tuesday, final delivery by end of month. You can track that in a few lines inside Asana or even a shared doc. It doesn't need to be elaborate, but you still need those milestones documented and visible to your client. The shooting schedule handles the shoot day itself.
The project timeline earns its keep here. Pre-production milestones stack up fast: creative brief approval, script rounds, casting, wardrobe pulls, location scouts, permits, equipment orders. Each shoot day appears as a block on the timeline while getting its own detailed shooting schedule. Post-production deadlines (rough cut, client review rounds, color, sound, final delivery) extend the timeline weeks or months past wrap.
The project timeline becomes your command center. When you're producing a rolling series of videos for a client, the timeline is what keeps everyone aligned on which videos are in pre-production, which are shooting, and which are in post. Each individual shoot still gets its own schedule, but the timeline is the only document that shows the full picture.
If you're knocking out ten short-form videos in a single shoot day, the shooting schedule is doing heavy lifting. But the project timeline still matters for tracking the broader campaign: when content needs to be delivered, which platforms have specific deadlines, and how the shoot day fits into the overall rollout.
The biggest source of confusion isn't the documents themselves. It's how producers talk about them in emails and Slack messages.
This happens constantly in branded content work. A producer sends a client the detailed shoot day breakdown and calls it "the project timeline." The client then asks why their post-production dates aren't on it. Two different expectations, same attachment.
Many producers maintain a single spreadsheet with a "Timeline" tab and a "Schedule" tab. The problem is that those tabs serve different stakeholders, update at different frequencies, and have completely different levels of detail. When changes happen, you're updating two things in one file, and it's easy for one to fall out of sync with the other.
Clients care about milestones and deadlines. Send them the project timeline. Crew members care about call times, locations, and the order of the day. Send them the shooting schedule (and the call sheet). Sharing the wrong document creates unnecessary questions and confusion.
Pro tip: Default to sharing the project timeline with clients and the shooting schedule with crew. If a client specifically wants the shoot day detail, share it as a supplement, not a replacement for the timeline.
The trickiest part of maintaining separate documents is keeping them aligned when things change. And things always change.
Here are a few practices that help.
Start with the project timeline to lock your shoot dates. Then build the shooting schedule for each date. This keeps the hierarchy intact and prevents the tail from wagging the dog.
When the shooting schedule changes during the day (you cut a scene, you run over, you wrap early), note anything that affects the broader project timeline. If you lost a setup today and need to pick it up tomorrow, that could shift your post-production deadlines. Update the timeline before the next morning.
Maintaining both documents in parallel Google Sheets tabs is doable, but it's slow and fragile. As we mentioned earlier, we use Asana for the project timeline and Dayframe for the shooting schedule. The timeline lives in a project management tool designed for milestones, dependencies, and task assignments. The shooting schedule lives in a tool designed for time-blocked scheduling with drag-and-drop rearranging and automatic time recalculation.
The goal is to avoid one bloated spreadsheet trying to do two jobs poorly. Let the timeline tool handle the timeline. Let the scheduling tool handle the schedule.
You can, but it usually creates more problems than it solves. The two documents serve different audiences and different levels of detail. A combined document either overwhelms your client with shoot-day minutiae or leaves your crew without enough operational detail. Keep them separate and cross-reference by date.
Start with the project timeline. Clients want to see milestones, shoot dates, review windows, and delivery dates. If a client is particularly hands-on and wants to know the shoot day plan, share the shooting schedule as a supplement. But the timeline is always your primary stakeholder communication tool.
Yes, but it doesn't need to be elaborate. Even a simple one-day shoot has milestones worth tracking: script lock, shoot date, rough cut delivery, final delivery. A few lines in a project management tool or a shared doc is enough. The point isn't the format. The point is that your client can see the timeline and knows what's coming.
"Production schedule" is a general term that can mean different things depending on context. Sometimes it refers to the project timeline (the full plan across all phases) and sometimes it refers to the shooting schedule (the shoot day plan). When someone says "production schedule," ask whether they mean the project timeline or the daily shoot plan. You'll avoid a lot of miscommunication.
The distinction between a shooting schedule and a project timeline is simple once you see it. The timeline is your project roadmap. The schedule is your on-set playbook. Knowing which one to build, when to build it, and who to send it to will make your productions run smoother from kickoff to wrap.
For the shooting schedule side of the equation, a purpose-built tool makes a real difference. Dayframe lets you build and rearrange shoot day schedules with drag-and-drop time blocks, automatic time recalculation, and one-click PDF export. It's what we use at Gorilla Creative, and it handles the on-set document better than any spreadsheet.