Production weeks now stay true through hiatuses and breaks

Production weeks now stay true through hiatuses and breaks

Production week labels are only useful if they reflect the actual production run.

If a schedule pauses for a planned break, a holiday shutdown, or a production hiatus, teams still need the week count to pick up where production really resumes. They should not have to mentally subtract blank weeks every time they read the plan.

This update fixes that.

What ships in this release

• Set a production week start for the schedule.
• Add production breaks by start date and week count.
• Skip those break weeks from the PW counter automatically.
• Resume numbering from the correct next production week when work starts again.
• Show break-week styling in the grid body so paused weeks read differently from active production.

Why this matters

Production teams talk in production weeks, not just calendar dates.

PW 11 needs to mean the eleventh actual week of production. If a show stops for two weeks, the schedule should not quietly drift into a new number that no longer matches the way the team is talking about the run.

Before this, breaks could force that manual translation step.

Now the schedule keeps the production count aligned to the real run, even when the calendar keeps moving.

Built for real schedules, not ideal ones

Most productions do not move in one clean uninterrupted block.

There are shutdowns, pauses, delayed starts, planned hiatuses, and handoff gaps between phases. That is normal. The production week system now accounts for that directly instead of expecting teams to work around it.

Less mental math. Better handoffs.

When production week labels stay accurate, callouts, reviews, notes, and exports stay clearer too.

The team can keep talking in PW numbers with more confidence because the schedule is doing the counting properly in the background.