Re-seeding bookings

Update a booking's schedule from the live timeline or a snapshot, review the changes, and notify the person.

Re-seeding brings a booking up to date with your plan when you're ready. This page covers the mechanics: when to re-seed, the dialog, batching, and notifications.

The concept

A booking holds its own saved schedule — it only changes when you re-seed it. How scheduling works explains why.

When to re-seed

You'll know a booking has fallen behind because CrewGrid tells you:

On the Staffing page, a booking whose schedule no longer matches the plan is flagged as out of sync — a ● drift pill on the role — with a way to re-seed.
In the Budget, the same situation shows as drift on the affected line. See Allocated vs Actual.

Being out of sync is normal — it just means your plan moved on. Re-seed when the change is settled and you want the booking to reflect it.

Re-seeding one booking

Open the re-seed dialog from the booking. It walks you through:

Choose the source — the live timeline or a snapshot. If the booking was originally built from a snapshot, the dialog starts on that snapshot.

Review the changes — a table shows each day that would change, with its current value, what it would become, and the difference. Nothing is hidden.

Notice material changes — if the change is significant (a shift in working days, or a change of day type), CrewGrid highlights it, because that's the kind of change people usually need to hear about.

Decide whether to notify — a Notify checkbox controls whether the person is emailed. Its default comes from your project settings.

Confirm — only now does the booking's schedule actually change.

📷 Screenshot: /images/docs/staffing/reseed-dialog.png The re-seed dialog with the before-and-after day table and Notify checkbox. Alt: A re-seed dialog showing a source picker, a table of changing days, and a Notify option.

Re-seeding several at once

When more than one booking is out of sync, you don't have to do them one by one. On the Staffing page, select the out-of-sync bookings and Re-seed them together — you'll review and confirm as a batch. For pushing changes across bookings and call sheets at the same time, use Propagate from the timeline instead. See Propagating changes.

How notifications work

CrewGrid notifies people automatically when a re-seed makes a material change — unless the project is in Live mode, which holds all automatic notifications back. For non-material changes, you decide by ticking Notify. See Project settings for Live mode and the notify default.

Bookings you maintain by hand

Some bookings are set to be maintained manually rather than derived from the timeline — for those, you edit the days directly and re-seeding is skipped. If you re-seed a batch that includes one, it's simply reported as skipped.

Where to go next

Propagating changes — push to everything at once.
The booking lifecycle — re-confirmation after a change.
How scheduling works