Adriatic command centre
The launch board for a
charter fleet.
One Friday at one base: every departure in the window, what is holding each vessel back, who owns the next check, and which launches are still waiting on a decision.
Demo data only — nine fictional vessels, fictional guests and browser-local changes. No login, nothing real leaves this browser, and demo readiness is never permission to operate a vessel.
What the board shows
- Readiness per vessel, from the checks that are actually open
- The Friday launch window, with each departure's blocker
- Incidents mid-triage, and what has to clear before launch
- A season of charters, turnarounds and berth allocation behind it
Who works from it
- Base coordinator — runs the window, records the launch decision
- Crew — works assigned checks on a phone
- Fleet manager — incidents, handoffs and capacity across the season
What you do on it
- Attach evidence and complete a required check
- Report and resolve an incident, then close the linked task
- Record a launch decision, or waive a requirement with a reason
- Create the next turnaround from a returning booking
Three seeded situations, each with a different job to do.
Every screen reads the same fixture, so a change made in one is visible in the others.
- 01 / AURORA · START HERE
From missing evidence to review.
Record the fuel check and see readiness change everywhere.
At risk · 11 of 12 checks · one blocked fuel task
Open the Aurora turnaround - 02 / VELA
A safety issue stays visible.
Resolve the incident, complete the linked inspection, then review.
Blocked · 12 of 13 checks · open high-severity incident
Open the Vela incident chain - 03 / MISTRAL
One booking. One turnaround.
Repeat a handoff without creating duplicate work.
Not assessed · returning booking · no open turnaround
Open the Mistral handoff