Key dates can now follow the episode or category they belong to
Planner key dates can now be scoped to the whole schedule, an episode, a category, or both, so important milestones show up where they actually matter.
Key dates can now follow the episode or category they belong to
Most production schedules have dates that everyone needs to know: bank holidays, shoot start, picture lock, final delivery.
But plenty of dates only matter to one episode, one department category, or one slice of the work.
Until now, key dates in Planner behaved more like show-wide markers. That was useful for big milestones, but too loud when a cut due date only applied to EP03 or a casting sign-off only sat in pre-production.
What changed
Key dates can now be scoped to:
- the entire schedule
- one or more episodes
- one or more categories
- an episode and category together
That means a key date can sit with EP04, with Production, or with EP04 inside Production.
Why this matters
A production schedule is not one audience.
The line producer may need the full schedule view. A post supervisor may only care about edit, review, and delivery milestones. An episodic team needs dates that do not make every episode look at risk.
Scoped key dates keep the signal where it belongs.
How it works in the grid
If you are looking at episodes, episode-specific key dates sit with the episode they belong to.
If you are looking at categories, category-specific key dates sit with the category lane.
If a key date has both an episode and a category, Planner keeps both pieces of context visible with a compact scope badge.
And if you switch to a layout where that scope is not currently visible, the key date still appears in the key-date lane instead of disappearing.
What to use it for
Use show-wide key dates for:
- shoot start
- bank holidays
- picture lock
- final delivery
Use episode or category key dates for:
- EP03 cut due
- EP04 casting sign-off
- production availability windows
- post review dates
- delivery checks that only apply to one workstream
The point
The schedule should stay quiet where it can and specific where it needs to.
Scoped key dates let production teams flag a real milestone without turning the whole grid into a warning sign.