Dashboard Overview

The dashboard is where everything comes together. It's designed to give you a complete picture of your team's work at a glance - no drilling into sub-menus, no navigating through five screens to find out what's in progress. One view, everything you need.

The Airport Board

The centrepiece of the dashboard is the airport board. If you've ever glanced at a departure and arrival board at an airport, you already understand how it works. Every flight your team is running is displayed in one place, organised by status.

The Takeoff Runway shows flights that are preparing to launch. These are flights with assigned crews and loaded crates that haven't started yet. Think of this section as the gate area - the flight is boarded and ready, just waiting for clearance to take off. This is where you review upcoming work and make sure everything is properly scoped before going active.

In Flight is where the action happens. These are your active flights - work that's currently underway. Each card shows the flight's name, captain, progress, and how many days remain until the landing date. This section should represent your team's current focus. If you have too many flights in the air simultaneously, it's a visual signal that the team is spread too thin.

Emergency Landing surfaces flights that have hit critical blockers. A flight in emergency status is a call for attention - something has gone wrong that the crew can't resolve on their own. This section is intentionally prominent. Emergencies shouldn't be hidden in a sub-tab or filtered out of the default view. If a flight is in trouble, everyone should know about it.

The Landing Runway shows recently completed flights. These are the wins - work that has been delivered and landed. Keeping landed flights visible for a period serves two purposes: it gives the team a sense of accomplishment, and it provides context for anyone who needs to reference recently completed work.

Flight Cards

Each flight on the board is represented by a card that packs a lot of information into a compact, scannable format. The card is designed so you can assess the state of a flight without clicking into it - the essential information is all right there on the surface.

The flight name and captain are displayed prominently at the top. Below that, you'll see the crew count - how many people are assigned to this flight. This gives you an immediate sense of the flight's scale. A flight with two crew members is a focused effort. A flight with eight is a major initiative.

Crate progress is shown as a visual indicator - how many crates are complete versus the total loaded. This is your at-a-glance measure of how the flight is tracking. A flight that's 70% through its timeline but only 30% through its crates might need attention. A flight that's completed all its crates ahead of the landing date is ready to land early.

The timeline is the card's most important visual element. It shows the takeoff date, the landing date, and where the flight currently sits in that window. Cards change colour as flights approach or pass their landing date. A flight running on schedule looks calm and controlled. A flight that's overdue turns visually urgent - a deliberate design choice that makes problems impossible to ignore without anyone needing to send a status-check message.

Clicking a flight card opens the full flight view where you can see all crates, detailed crew assignments, status history, and flight metadata. It also updates the URL to include the flight ID. But for day-to-day monitoring, the card itself tells you what you need to know.

Shareable Flight URLs

Each flight has its own direct URL. When you click a flight card, the address bar updates to /dashboard/flight/:id. Copy that URL to bookmark a specific flight or share it with a crew member. Navigating to a flight URL opens the detail pane automatically once you are signed in. Closing the pane or pressing back returns you to the main dashboard - no history clutter from opening and closing flights.

In-Flight Badge

Next to the New Flight button in the dashboard header, you'll see an "X/Y in flight" badge showing how many of your plan's active flight slots are currently in use. This gives you an at-a-glance sense of your team's capacity without needing to count cards on the board.

The badge changes colour as you approach your limit. It stays grey when you're well within your allocation, turns amber when you've used 80% or more of your slots, and turns red when you're at your limit. When the badge is red, the New Flight button is disabled - you'll need to land or archive an active flight before launching a new one, or upgrade your plan.

Plans with unlimited active flights (such as Enterprise) don't show the badge, since there's no limit to track against.

READY TO LAND Indicator

When all crates linked to a flight reach a done state (completed, merged, or closed in your integrated platform), a "READY TO LAND" badge appears in the flight detail pane, shown alongside a rotated plane icon. This is the system telling you that every linked work item has been resolved and the flight is clear to land.

The badge is a signal, not an automated action. It means the system has detected that all linked work items are complete, but the captain still needs to make the call. Landing is a deliberate act: the captain reviews the outcome, triages any loose ends, and manually sets the flight to landed status. The "READY TO LAND" indicator simply removes the guesswork about whether outstanding work remains.

If your team has enabled auto-landing through an integration, the flight may land on its own once all crates are done. In that case, "READY TO LAND" appears briefly before the automatic transition kicks in. If auto-landing is not enabled, the badge is your prompt to act: review the flight, confirm the objective is met, and land it. See the Integrations page for details on configuring auto-landing.

Don't ignore a "READY TO LAND" badge. A flight sitting in active status after all its crates are done distorts the board and delays the next flight's takeoff. When you see the badge, treat it as a nudge: the cargo has been delivered, the runway is clear, bring it in.

When your team has 8 or more flights in the air at the same time, the dashboard shows a yellow advisory banner above the flight board. This appears regardless of your plan tier - even if your plan allows 25 or unlimited flights, the banner reminds you that running too many concurrent flights can dilute team focus.

The banner is dismissable. Click the X to hide it for the rest of your browser session. It's a recommendation, not a restriction - some teams genuinely need 8 or more active flights, and that's fine. The banner just makes sure the decision is conscious rather than accidental.

Control Tower

The Control Tower gives you a live activity feed for your team without leaving the dashboard. Look for the floating button in the bottom-left corner of the screen - clicking it opens a compact panel that slides in alongside the board.

The feed is scoped to your team. You only see activity for teams you belong to. If you switch teams, the feed refreshes automatically to show the new team's activity. There is no manual reload needed.

Feed items are grouped by date. Today's activity appears at the top under a "Today" heading, yesterday's under "Yesterday", and older entries show the full date. Each item has a relative timestamp so you can tell at a glance how recent the activity is.

Each item shows what happened. An action badge marks the type of change: NEW for created records, UPD for updates, and DEL for deletions. A small emoji next to the badge indicates which table the activity came from, so you can tell whether you're looking at a flight update, a crate change, or something else.

Clicking a flight-related item opens the flight detail pane. On desktop, the feed stays open alongside the flight detail so you can review the activity and the flight at the same time. On mobile, selecting a flight entry closes the feed so the detail pane has room to display.

If there is more history to load, a "Show more" button appears at the bottom of the feed. Clicking it loads older entries without replacing what you have already seen.

Team Overview

The team overview gives you a bird's-eye view of your team's current state. It answers the questions that managers and team leads ask most often: How many flights are in the air? How many have landed recently? Is anyone unassigned? Are we running at capacity or do we have room for another flight?

You can see the total number of active flights, flights preparing for takeoff, and recently landed flights. These numbers give you a quick health check. A healthy team typically has one or two flights in the air, one or two preparing, and a steady stream of landings. If you see five active flights and zero recent landings, that's a sign the team is starting a lot of work but not finishing it.

The overview also shows who's on which flight and who's currently serving as ground mechanics. This allocation view is critical for capacity planning. Before launching a new flight, you can see at a glance whether you have crew available or whether everyone is already committed to existing flights.

For organisations with multiple teams, each team has its own overview. Team leads can see their team's state independently, while organisation admins can look across all teams to understand the broader picture. This layered visibility keeps local teams autonomous while giving leadership the context they need without micromanaging.

Crew Status

The crew status section shifts the view from flights to people. Instead of asking "how is this flight doing?" it answers "what is this person working on?" Both perspectives are important, and the dashboard provides both.

For each team member, you can see their current assignment: which flight they're on, what role they're playing (captain, crew, or ground mechanic), and their current workload. A crew member on one flight in a crew role is in a normal state. A person listed as captain on two flights simultaneously is a red flag - that's a bottleneck waiting to happen.

The crew status view is especially valuable for team leads managing capacity. When a new project comes in and you need to assemble a crew, this view tells you who's available. When someone finishes a flight and lands, you can see them transition from an active crew role to being available for the next assignment.

Ground mechanics are also visible in this view. You can see who's currently on maintenance duty, which helps with rotation planning. If the same person has been on ground mechanics for three consecutive rotations, the crew status makes that visible so you can rotate someone else in. Fair rotation keeps the team balanced and prevents resentment - nobody wants to be permanently stuck on maintenance while everyone else gets the exciting flight work.

Together, the airport board, flight cards, team overview, and crew status give you complete visibility into your team's work. No status meetings required. The dashboard is the status meeting.

Analytics (for Beta enabled accounts)

The dashboard has a dedicated Analytics tab that lives at /dashboard/analytics. You can switch between the Flights tab (the airport board) and the Analytics tab at the top of the dashboard. Switching tabs updates the URL, so if you reload the page or share the link, you land right back on the view you were looking at. No hunting through menus - your analytics are one click from the board and vice versa.

The Analytics tab gives you a bird's-eye view of how your team has been performing over time. Rather than scrolling through individual flight cards and piecing together a story, the charts do the work for you. Each chart answers a specific question about your team's delivery patterns, bottlenecks, and capacity.

Available Charts

Flight Velocity shows how many flights your team lands per period. This is your throughput metric - the number of flights that touched down in each time window. It also includes a period-over-period comparison so you can see whether your team is accelerating, holding steady, or slowing down. A consistent velocity means your team has found a sustainable pace. A sudden drop is worth investigating.

Cycle Time measures the average number of days between takeoff and landing. Shorter cycle times generally mean the team is scoping flights well and shipping without unnecessary delays. The chart includes an all-time comparison so you can benchmark against your own history, along with a distribution view that shows how flights spread across time buckets. If most flights land in one to two weeks but a few drag on for months, the distribution makes that visible immediately.

Status Distribution breaks down all flights by their current status. It gives you a snapshot of how work is distributed across takeoff, active, emergency, landed, and archived. A healthy distribution has most flights landed or archived, a small number active, and very few in emergency. If your emergency count is climbing, that is a signal to dig in.

Crew Utilisation ranks team members by the number of flights they have been on. This helps you spot imbalances - if one person has been on twelve flights and another has been on two, you may want to spread the load more evenly. It is also useful for recognising crew members who have been carrying a heavy share of the work.

Emergency Frequency groups emergency events by time period. If emergencies are clustered in a particular week or month, that pattern often points to an external cause - a dependency that keeps breaking, a team that was understaffed, or a spike in scope changes. Seeing the pattern is the first step toward fixing the root cause.

Avg Time Per Status shows the average number of days that landed flights spent in each status. This tells you where time actually goes. If flights spend two days in takeoff and ten days active, that is a healthy split. If flights sit in takeoff for a week before going active, your planning phase might need attention. This chart only counts flights that have landed, so in-progress flights do not skew the numbers.

Landed Flights by North Star groups your landed flights by the North Star they are linked to. This chart only appears when North Stars are enabled for your team. It answers a strategic question: where has the team's delivered work actually gone? If one North Star has ten landed flights and another has zero, the team's effort may not be aligned with the organisation's priorities.

Flight Type Performance is a horizontal bar chart that shows the average cycle time for each flight type, with bars colored to match each type's configured color. This chart only appears when flight types are enabled for your team. It helps you understand which kinds of work move quickly and which tend to take longer. If bug-fix flights average three days but feature flights average three weeks, that is useful context for planning.

North Star Progress shows a progress bar for each North Star, representing the percentage of linked flights that have landed. This chart only appears when North Stars are enabled. It gives you a quick read on how close each strategic goal is to completion. A North Star at 80% with two flights still in the air is nearly there. One at 20% with no active flights might need a new flight launched to keep it moving.