Open shifts
Shifts available for pickup. Supervisors can post a new opening, move an existing shift here, or assign one to a dispatcher (or to the most junior available).
Dispatchers
Core tools for all dispatchers
Main Dispatch Links
Coverage Trend
How to read this
- What it shows
- Daily dispatcher staffing — how many dispatchers are scheduled vs. how many called out, sick, or on PTO — over the selected window. Centered on today: half before, today, half after. Trainers and supervisors are NOT in the bar (they don't take flights); they appear in the tooltip's roster line for context.
- 1D / 7D / 1M tabs
- Window length. 1D is just today, 7D spans 3 days back through 3 days forward, 1M spans roughly 15 days each side.
- Bar colors
- Green — scheduled dispatchers meet or exceed that day's target. · Amber — scheduled below target (under-covered). · Red (stacked on top) — dispatchers out for the day (callout / sick / PTO).
- Target line (dynamic)
- Dashed blue step function — minimum dispatchers needed for each day's flight load. Computed independently for mainline and charter pools (per-desk and per-hour caps both honored, whichever is tighter binds), then summed. Days with zero flights drop to target 0. Hover any bar for the exact derivation. Falls back to the global desk count when no SSIM is loaded.
- Operational day
- Each bar covers a 24-hour duty cycle starting at 04:00 local Mountain Time — auto-shifts to 1000Z (MDT) and 1100Z (MST) on DST transitions. Consecutive bars don't share flights.
- Reading the X axis
- Date labels (M/D) below the bars. With a wide window, only every Nth label is drawn to keep things readable.
My Shifts
Your upcoming assigned shifts. Click a row to jump to that day on the Scheduler.
Desk Assignments
Today: —
Everyone on shift today, grouped by role. Dispatchers show their assigned desk + flight count from the auto- assigner; trainers, supervisors, and jump-seaters show their shift + desk with no flight count (they're not flight-assigned). Live mirror of the same widget on the Desk Assignments page — any callout, settings change, or roster update reflects on both copies.
| Desk | Dispatcher | Shift (L) | Shift (Z) | FA Time (Z) | Flights |
|---|
Time clock
Clock in when you start your shift, clock out at the end. Today's sessions are listed below; click View archive to filter and export the past 6 months of duty time.
Today
| In | Out | Duration |
|---|
Junior Assignment Log
Top of the list is next up for junior assignment. When someone is junior assigned or picks up a critical shift the system moves them to the bottom and logs the date, shift, supervisor, and timestamp.
| # | Dispatcher | Shift date | Shift | Reason | Sup. | Sup. acted |
|---|
EDCT/Route Requests
Submit an EDCT reduction or route change request to the supervisor on duty. Status updates show below as soon as they're decided.
My recent requests
No requests submitted yet.
Dispatch Suggested Passdown
When a desk's dispatcher clocks out, their still-airborne flights pass to the target desk shown. A target like 00/01 means either desk — or split the load if there's a lot to hand off. Edited on the Desk Assignments page.
| Sunday | Monday | Tuesday | Wednesday | Thursday | Friday | Saturday |
|---|
Adjusted for the schedule
rerouted desk out split to cover 2nd passdown supervisor decision
Supervisors
Tasking, pass-down notes, attendance points, roster, and user accounts
Morning Briefing
What needs your attention across coverage, open shifts, duty-time, assignments, and requests — refreshed automatically each morning.
Open requests
PTO, Sick, Swap, and Offer requests that need your approval. Swap and Offer requests appear here only after the other dispatcher has accepted them.
Daily Task Items
Supervisor Links
Pass Down Whiteboard / Running Log
Dispatcher Point System
| Name | Late | Call-Out | Total |
|---|
User settings
Supervisors and managers: manage the roster, roles, and user accounts.
Employees
| Name | Role | Username | Password |
|---|
Desks & time frames
Manage desks and their operating windows. Changes apply to desk assignment and the schedule.
| Desk | In rotation (per day) | Desk (L) | Desk (Z) | Flt (Z) | |||||||
|---|---|---|---|---|---|---|---|---|---|---|---|
| S | M | T | W | T | F | S | |||||
Desk assignment uses the first 0 active desk row(s); adjust in Desk Assignment or here.
Duty-time compliance (FAA 121.465)
Errors block save; warnings still need a supervisor to acknowledge before saving. This list is read-only — open the offending shift on the calendar to fix it.
| Severity | Dispatcher | Rule | Date | Shift | What's wrong | Recommendation |
|---|
Daily flight coverage check
Read-only forecast. Capacity per day is computed using the same per-desk and per-hour caps as the auto-assigner. Open the offending day on the scheduler to add a shift.
How to read this
- Date
- Mountain Time calendar day.
- Disp.
- Unique dispatchers scheduled that day (jumpseats and supervisors/trainers excluded — only people who can be assigned flights count).
- Mainline / Charter cell
-
OK
42/50
84%
— read as flights / capacity (utilization %).
- flights = SSIM legs operating that day in that pool (mainline or charter).
- capacity = total flights the working desks in that pool can absorb. Per desk:
min(max-per-desk, FA-window-hours × max-per-hour), summed across the pool. Hours = each desk's FA window length. - utilization % = flights ÷ capacity. Drives the pill color.
- Pill colors
- OK under 90% — comfortable. · Watch 90–99% — tight, should fit. · Action 100%+, a coverage hole (flights with no desk in window), or an hour over the per-hour cap.
- Mainline vs. Charter
- Tracked separately so a charter shortage doesn't get hidden by mainline surplus. Charter desks are the C-prefix desks (C5, C9, C13…); charter flights are SSIM type C plus the 6000-series numeric range. Mainline = everything else.
- Recommendation
- Specific actions to bring the day to OK. Each item is tagged Mainline or Charter so it's clear which pool needs the extra capacity. The Z time window points at the densest hour(s); pick a desk template whose FA window covers that range.
| Date | Disp. | Mainline | Charter | Recommendation |
|---|
Blackout dates
Days dispatchers can't request PTO or days off. Each window shows on the calendar with a striped red background and a BLACKOUT badge; PTO submissions that overlap are blocked automatically.
Reminders
Important recurring days — paydays, timesheet deadlines, and anything you add. They show as chips on the calendar and send bell reminders to everyone. Supervisors can add, edit, or remove them.
Supervisor Reminders
Supervisor-only reminders. Calendar chips and notifications are visible to supervisors only — either the whole supervisor group, or a single supervisor (private). Dispatchers never see these.
Shift colors
Set the calendar color for each shift category. The category picker on the shift edit dialog uses these colors to paint the left border of every scheduled shift pill. Add custom categories with the form below; Regular and Training are built-in and can't be removed.
Dispatcher time clock
Live status of every dispatcher. Click Edit on any row to adjust a missed clock-in or clock-out — all edits are written to the security log with the original timestamps preserved.
| Dispatcher | Status | Desk today | Clock in | Clock out | Duration | Note |
|---|
EDCT/Route Requests
Approve or reject EDCT reduction and route change requests submitted by dispatchers. Decisions are logged.
No requests yet.
Bid Seniority
Order dispatchers from most senior (rank 1) to least senior. Used by the Bid Cycles award engine. Lower number = picks first. Leave a row blank to exclude that dispatcher from bidding.
Super User
Restricted view. Audit and trace tools live here so they're separated from day-to-day supervisor work.
Notification system
OnMaster switch for the toast + bell notification system on this (main) site. The beta site always runs notifications for testing and is not affected. Changes apply to every user on main.
System stats
Snapshot counts. Updates every render so any mutation you observe in the inspector is reflected here too.
Role × Permission audit
Read-only view of every role and which permissions it grants. ★ marks an admin role (full access via the master switch). Edit roles in Manage Roles on the Supervisor Dashboard.
Auto sign-out
Per-user idle-timeout exemption. By default Supervisors and Managers are exempt; Dispatchers and Trainers sign out after 5 min of inactivity. Flip an individual user's toggle below to override the role default. Reset reverts to role default.
| User | Primary role | Role default | Override | Effective |
|---|
Data tools
Maintenance actions. Use carefully — Import and Factory reseed both replace the entire persisted snapshot.
Backups
Hourly cron checks the configured schedule below. Backups cover the entire site (state, credentials, per-user prefs). Restores auto-archive the current state first so the rollback is itself reversible. Full snapshots kept 14 days; time-clock entries kept 6 months.
| When | Slot | Type | Scope | Size | Label |
|---|
API tokens
Bearer tokens for programmatic access (mobile app, webhooks, scripts). Tokens inherit your full Super User permissions — treat them like passwords. The raw token is shown only at creation — save it before closing the dialog.
| Label | Created | Last used | Expires | Status |
|---|
Security log
Running audit trail of logins, role & permission changes, password resets, desk-assignment runs, and desk / roster mutations. Filter to find a specific event; export CSV to archive. Capped at 5,000 most recent entries.
| When | Actor | Action | Target | Details |
|---|
Daily OPs Brief
Live AWC weather + FAA NAS status, filtered to Breeze bases and the airports we fly to, synthesized into a regional operations brief. Edit any paragraph inline; regenerate to pull a fresh brief.
Generate this brief only ONCE per day.
Each run pulls fresh data and calls the AI engine — repeated
generations add API cost and overwrite your edits. Edit the
brief inline as needed; only use Pull a new brief
if you truly need to start over.
Sources
Not fetchedWeather (AWC) and FAA NAS status are pulled automatically for every airport in the roster below. Paste the current FAA OPs Plan so route/SWAP/VIP/rocket/flight-check notes get folded in.
A brief was already generated today. Re-running adds API cost and overwrites edits. Enter a reason to pull one more — this is logged and the Super User is notified.
Brief
—The full brief reads as one paragraph; the regional breakdown follows. Everything is editable — click in and type, changes save automatically. Use Pull a new brief to regenerate from scratch.
Full brief
Regional breakdown
Breeze roster
Airports the brief covers, grouped by region (IATA codes, comma- or space-separated). This is the source of truth — edit it to add/remove cities, then regenerate. Bases are listed separately.
Edit roster
Bid Cycles
Build the dispatcher schedule for the next 3 months. The computer makes the shifts, dispatchers pick the ones they want (most senior picks first), and everyone gets a schedule.
How this works, start to finish
1
Start
Open a new schedule for the next 3 months.
2
Build it
The computer makes shifts that cover all the flights.
3
Share it
Look it over, then send it to the dispatchers.
4
They pick
Dispatchers choose the shifts they want, best first.
5
Hand out
Most senior picks first, then the next, and so on.
6
Done
Everyone's new schedule is set for the quarter.
No bid cycles yet
Make your first schedule to get started. The app grabs your list of dispatchers and builds shifts that cover all the flights.
You're here: making a brand-new schedule.
Give it a name and dates, peek at the chart that shows your busy times, choose your shift "waves,"
tell it how many shifts you have, then press Generate.
The computer builds a schedule you can check and change in the next step.
Tip: rest your mouse on any word or chip and a little note pops up explaining it.
1 · Name it & pick the months
First, give this schedule a name and tell it which 3 months it's for. Pick a quarter (Q1, Q2, Q3, or Q4) and the start and end dates fill themselves in. The name is just what dispatchers see, like Q3 2026. You only need to touch the dates by hand if you want something unusual.
2 · See when it gets busy
This picture shows how many people you need working at each hour of the day. It looks at your busiest recent days and figures out the pattern, so it stays right even as the airline grows. The tall pink bars are your busiest times — that's where you want shifts to start. The little chips under the chart already do that thinking for you.
How to read the picture
-
Each bar is one hour of the day.
The top label is Zulu (the airline clock); the bottom label is our local time.
So
13Z / 07Ljust means 7:00 in the morning here. - Taller bar = busier hour. The number inside the bar is exactly how many people you need working that hour.
- Two bars side by side: tan is a normal weekday, blue is the weekend (weekends are usually a bit quieter).
- The glowing pink bars are your busiest hours. Those are the times you most need people, so that's where your shifts should land.
- It keeps itself up to date. The picture is made from your busiest recent days, so as the airline gets busier the picture grows with it. The little line right above the bars tells you which days it used.
3 · Set your shift "waves"
A block is just a start time for a group of shifts — a "wave" of dispatchers who all clock in at the same hour. Each shift is 10 hours long. The waves start about 3 hours before a busy time — not right at it — because flight releases are due 2 hours before a flight leaves, and dispatchers need about an hour before that to build the plan. Change a row's start time below, use + / − to add or remove a wave, or just click Apply suggested starts to use the times the picture in step 2 already picked for you.
| Block | Local start | Zulu start | End (local) |
|---|
4 · How many shifts you have
This is how many shifts you can hand out each week — basically your total people-power. The app works it out from your roster automatically (each dispatcher works 4 shifts a week), so when you add or remove people it updates on its own. You only need to change it by hand for a special case (someone on leave, new hires not bidding yet). If the work needs more shifts than you have, you'll see red "short" marks on the next screen — those gaps usually get filled by reserves or overtime.
Off: everyone works 4 days in a row, then gets 3 days off in a row (the normal way). On: the computer is allowed to give a few people a day off in the middle of the week — but only when it helps cover a busy spot. It still keeps days together whenever it can.
Weekends off (Saturday + Sunday)
In a 24/7 operation only some people can have the weekend off — somebody has to work Saturday and Sunday. These settings decide how the computer hands out the weekends that ARE free. The first two never hurt your coverage; the last one is the only one that can.
Most weekends off: piles the free time into whole Sat+Sun pairs — the most senior folks get them. Spread it around: tries to give more people at least ONE weekend day off instead of a few getting both. Both of those are free — they never drop coverage; if the weekend is too busy to help, the computer just keeps the best-coverage plan and tells you. Guarantee weekend-off lines is the only knob that can cost coverage: it FORCES the number you type, then shows you exactly how much coverage it gave up so you can decide.
5 · Build the schedule
Press the button and the computer builds the whole schedule for you — one shift for each dispatcher. It'll take you to the next screen where you can look it over, change anything you want, and then send it to the dispatchers once it looks good.
No cycle selected
Open a cycle from the Cycles tab, or create a new one.
You're here: . Change how many people you want if you need to, rebuild it, then send it out.
How many people on each shift, each day
Each box is how many people you want working that wave on that day. Type right in a box to change it. The total on the right is how many dispatchers end up on that wave.
Did we cover the day?
This compares what you need to what you've got, hour by hour. The tan bar is how many people the flights need. The green bar is how many your schedule actually puts on. If green is shorter, a red mark shows you're short that hour. Use it to make sure the schedule really covers the whole day.
Demand
Coverage
Shortfall
The shifts dispatchers will pick from
Each row is one dispatcher's schedule — the shift they'd choose. They're grouped by wave. A filled-in box is a work day; a dashed box is a day off. The Coverage row at the bottom of each wave shows how many people are working that shift each day.
No open bid right now
A cycle has to be in the Posted state before dispatchers can bid.
How to pick: tap + on a shift to add it to your list, then use the ↑ and ↓ arrows to put your favorite at the top. Whatever's on top is your #1 choice.
Your preferences for —
Available lines
Your ranked picks
No cycle to award
Open a cycle from the Cycles tab once dispatchers have submitted their bids.
What this does: hands out the shifts by seniority. The most senior dispatcher gets their top pick first, then the next person gets their best still-open pick, and so on down the line. Anyone who didn't pick gets whatever shifts are left over.
Status — —
Awarded assignments
| Seniority | Dispatcher | Line | Block | Picked rank |
|---|
Who picks first: this is the pecking order for choosing shifts. Rank 1 is the most senior person and picks first. To change the order, go to Supervisor Dashboard → Bid Seniority.
| Rank | Name | Role |
|---|
The whole thing, step by step
You build one schedule every 3 months. It goes through these steps in order:
- Start it: you make a new schedule and set the shift waves and how many shifts you have. The app figures out the busy times for you.
- Build it: the computer makes a shift for each dispatcher that covers the flights.
- Check it: you look it over, change how many people are on each shift if needed, rebuild it, and then send it out.
- They pick: dispatchers open their bid sheet, put the shifts in the order they like best, and hit submit.
- Hand it out: you press the award button. The most senior person gets their top pick, the next gets the best one left, and so on. Anyone who didn't pick gets whatever's left.
- It's live: the finished schedule is set for the 3 months. Time-off and swaps are handled on top of it in the Scheduler.
Words you'll see, in plain English
- Block (or "wave")
- A start time for a group of shifts. Everyone in the same wave clocks in at the same hour. Each shift lasts 10 hours.
- Cadence
- How far apart the waves start. The usual setup is 5 waves, one every 5 hours (00, 05, 10, 15, 20 our time).
- Bid line
- One dispatcher's schedule they can pick — a wave plus which 4 days they work and which 3 they're off.
- Demand
- How many people you NEED working each hour, based on the flights.
- Coverage
- How many people you actually HAVE working each hour, based on the schedule.
- Short / extra
- "Short" = you have fewer people than you need that hour. "Extra" = more than you need. The computer fixes short spots first.
- Shifts you have
- How many shifts you can hand out in a week. About 4 per dispatcher (so 29 dispatchers = ~116 shifts).
- Seniority
- Who picks first. Rank 1 is the most senior. Change it in Supervisor Dashboard → Bid Seniority.
- L / Z time
- L is our local clock. Z is the airline's worldwide clock (UTC). Our time + 6 hours = Z (in summer).
Desk Assignments
Assign dispatchers to desks using roster local (L), desk Zulu, and flight-assignment Zulu windows.
Flight schedule
Import an SSIM (Standard Schedules Information Manual) file to load the flight schedule. The desk assignment tool uses these flights to know what coverage is needed throughout the day.
No flight schedule loaded.
Flight schedule list
Import a flight schedule to browse flights here.
| Flight | Aircraft | From | Dep (L) | Dep (Z) | To | Arr (L) | Arr (Z) | Service |
|---|
Control Panel (Supervisor/Manager only)
Auto-assigner settings. The cycle runs from the day start (Zulu) on the operational date through the day end on the following Zulu day. Flights stop being assigned to a desk within the cutoff hours of the end of its FA window. Assignments auto-recompute on call-outs and no-shows.
Cycle covers one calendar Z day. Cross-midnight dispatchers from yesterday are pulled in to cover today's morning Z hours, and each desk row only contains flights operating on today's Z calendar — no duplicates across consecutive days' runs.
Cycle coverage check
Mainline + charter capacity check for the cycle dates above. Same caps as the auto-assigner — a row flagged Action here will produce force-placed flights when you run assignment.
How to read this
- Mainline / Charter cell
-
OK
42/50
84%
— flights / capacity (utilization). Capacity = sum across the pool's working desks of
min(max-per-desk, FA-hours × max-per-hour). - Pill colors
- OK <90% · Watch 90–99% · Action ≥100%, a coverage hole, or an hour over the per-hour cap.
- Recommendation
- Tagged Mainline / Charter. The Z window points at the densest hour(s); pick a desk template whose FA window covers it.
| Date | Disp. | Mainline | Charter | Recommendation |
|---|
Desk Assignments
Today: —
·
Running for: —
Desks currently working today, derived from the scheduler. FA Time (Z) is the desk's Flight Assignment window — the Zulu range the auto-assigner uses to match flights to that desk. Flights shows how many the auto-assigner placed on each desk for the current cycle, auto-recomputed when a desk calls out or settings change. Click Show assignments on the Control Panel for the full per-desk flight list.
| Desk | Dispatcher | Shift (L) | Shift (Z) | FA Time (Z) | Flights |
|---|
Dispatch Suggested Passdown
The passdown chain for each day of the week. Edit when the bid changes. A target like 00/01 means either desk (or split the load). The read-only copy on the Universal Dashboard updates automatically.
Suggested Passdown — Live
The passdown chain bent around actual staffing for the chosen date. Unstaffed desks drop out; their hand-offs reroute to an eligible desk (on shift, 5h+ in, ending later), spread evenly. Edit the baseline chain in the card above.
rerouted desk out split to cover 2nd passdown supervisor decision
STAR D0 Tracker
Daily on-time tracker for each station's first morning departure. Enter Block Out (Zulu) when the flight pushes and the Result column auto-computes against the scheduled ETD. Only late / delayed flights count against the day's STAR D0 percentage.
STAR D0 Flight Tracker
Times are Zulu, 4 digits, no colon (example: 1430). Minutes vs ETD = Block Out − ETD with ±720 min wrap. Result is empty if either time is blank, "Late" when minutes > 0, "D0" when ≥ −15, ">15 Early" otherwise. Crew Concurrence only applies to >15 Early flights.
D0 · 0–15 min early
>15 Early · w/ concurrence
>15 Early · NO concurrence
>15 Early · pending
Late
| # | Flight # | City Pair | ETD (Z) | Block Out (Z) | Min vs ETD | STAR D0 Result | Crew Concurrence | Remarks |
|---|
All edits autosave. 100 rows always available — type into any blank row.
Dispatch Scheduler
Day, week, and month views · shift edits are supervisor-only · shifts show local (L) and Zulu (+6h roster rule)
My Shifts
Your upcoming assigned shifts. Click a row to jump to that day in the calendar.
Schedule
Time clock
Clock in when you start your shift, clock out at the end. Today's sessions are listed below; click View archive for the past 6 months.
Today
| In | Out | Duration |
|---|
Open shifts
Shifts available for pickup. Supervisors can post a new opening, move an existing shift here, or assign one to a dispatcher (or to the most junior available).
Open shift availability
Dispatchers: mark days you can pick up extra shifts. Supervisors see these on the week schedule.
Requests pending your approval
0Swap and Offer requests another dispatcher sent to you. Accept routes the request on to a supervisor for final approval. Deny archives the request — the other dispatcher will see the decision in their notifications.
Dispatcher requests
Supervisor: call-outs & sick
Record official attendance in the Power Apps tracker after logging here.