The batch has just been created and is queued to start. Brief — usually moves to Building entries within seconds.

Available actions: Cancel

The system is loading every client schedule entry that matches your filters and creating a draft booking for each one. The total count isn't known yet — it ticks up as drafts are built.

Available actions: Cancel

Each draft booking is being checked against current carer availability, service contracts, suspensions, and overlaps. The valid / invalid counts grow as chunks of work complete.

Available actions: Cancel

The batch is waiting for you to review the entries and click Confirm. You can edit allocations, fix invalid entries, remove entries, and select / deselect which entries you want to confirm.

Available actions: Confirm, Refresh entries, Revalidate stale entries, Cancel, Remove entries.

The system is re-checking entries that were flagged because something they depend on (client, schedule, carer) changed. The table stays visible while it works.

Available actions: Cancel.

A final validation pass runs against the entries you confirmed, in case anything changed between review and confirm. If everything still passes, the batch moves to Confirmed.

Available actions: Cancel (returns to Ready to review).

All confirmed entries passed re-validation and the batch is queued to start creating bookings. Brief — usually moves to Creating within seconds.

Available actions: Cancel (returns to Ready to review).

Bookings are being created in the database. The progress bar shows how many are done. You can navigate away — this continues in the background.

Available actions: Cancel (terminal — bookings already created are kept), Force complete (only appears if the batch has stalled).

Every confirmed entry was successfully turned into a booking.

Available actions: Done, Retry as new batch.

Some entries became bookings, others hit errors during creation. The entries table shows which are Created vs Failed.

Available actions: Done, Retry as new batch (the retry skips already-created bookings).

The batch failed to complete — usually because of an unexpected error during initialisation or validation. Open the timeline disclosure on the batch's detail page for the failure reason.

Available actions: Done, Retry as new batch.

Someone (or you) cancelled the batch. If it was cancelled mid-Creating, any bookings already in the database are kept and the remaining entries are marked Failed.

Available actions: Done, Retry as new batch.

Inside a batch, individual entries have their own status: