A departure starts in Prepare while you staff it and resolve its issues. When nothing blocks it, you mark it Ready. Those two stages are what this article covers. A departure can also show Sent, Done or Cancelled for later stages of its life. Sending the daily messages to your people is tracked separately, in the departure's Activity view, and does not change the badge.
Blockers, warnings and information
The departure's Overview lists its findings under Warnings and blockers, each with a severity:
- Blocking: must be resolved before the departure can be Ready. Incomplete staffing of a required requirement is the common case.
- Needs attention: worth reviewing, but does not stop Ready. "A confirmed Resource is not available at this time" is an example.
- For information: recorded for your awareness only.
Control Room's Priorities panel shows the same findings across all dates as To resolve, To review and For information.
Before you start
- The departure is open in its Overview view.
- Required requirements are staffed (see Assign resources and understand booking-group coverage).
Mark a departure Ready
- Step 1:
Read the readiness line at the top of Overview, for example "Ready — 0 blockers, 3 open warnings", or the reason it is not ready yet.
- Step 2:
Resolve each Blocking finding, usually in Resources & groups.
- Step 3:
Review each Needs attention finding. Once you have looked at it, you can mark it with Acknowledge in Control Room's Priorities, with an optional note. Undo reverses it.
- Step 4:
When no blocker remains and every required requirement is staffed, Mark Ready appears. Select it. The badge changes to Ready and Control Room's readiness count goes up.
- Step 5:
To reopen the departure for changes, select Return to Prepare.
Apply latest Product setup is a separate choice. A departure keeps the Product setup it was created with; select this only when you have changed the Product or its Operating Profile and want this departure to follow the newer setup.
What you should see
The departure shows Ready with 0 blockers. Warnings you chose to leave open stay visible; they are not hidden by marking Ready.
If something looks wrong
If Mark Ready is not offered, the line beneath it says why: readiness could not be read, a configured requirement still holds the departure back, or open blockers remain. Staff the requirement or resolve the blocker, and the button appears without any further step.