Eighteen clickable screens

What changed since Friday, as worse and better. Today's flights live from the EFB. Then one queue of problems by when they bite, with the calls, offers and documents under the problem they belong to, and the week as a horizon.

Every round trip as a whole plan: outbound and return leg chips, lifecycle status, open items, pilots, documents, weather and next action. Filters and density work.

The status as you would say it on the phone. Open items first, by when they bite, with their actions. Legs as a timeline with the confirmed ones folded, what each pilot can see, and one timeline of messages, documents and plan versions.

Every mission leg scored against planning thresholds and the pilot's own minimums, with trends, factors, a forecast history and suggested fixes.

The phone call: reason, what it touches, recovery options with real likelihoods, and who hears what. Apply unlocks only after the client call is logged.

Miguel's phone-first page by magic link: is it still on, who the pilot is and what the plane is like, what we still have to sign, how to tell Maria we are late. The same page Tuesday morning with the plane in the air, and Thursday night with the thank-you and the next appointment. Spanish and large type.

What Tom Reyes sees: today's flight from departed to the one-minute post-flight report, tomorrow's with the fog decision and a text to the family, open missions matched to him with fit and minimums, the offer sheet, releasing a mission with a reason, and what he is matched on.

Where trips come from: hospital social work and nurse navigators through partner links, patient-support organizations, the ACA website, self-referrals. Source, people, eligibility, decision.

The other recovery: nobody called, the 06:00 run scored Wednesday's return Concern. No pilot to release, so the day changes shape: earlier return, overnight, or wait.

How an open mission finds its pilots: who may be offered it, who hears first, when it comes back to the coordinator. Edit a rule and watch a real mission re-rank; replay the last 90 days; publish with a reason.

The board as a funnel: six boxes count where every mission stands, from not postable to confirmed, with how many are past their countdown. Open one to see who was told in which wave, who offered and why; confirm, hold, call; ask a pilot directly, even around a soft rule; split a leg nobody can fly at the best handoff.

Not the roster: who to thank, who is drifting away, whose medical lapses next, who keeps saying no. Built on the same engine data as the matching rules. Every message shows its words before it goes.

The person over time, not the trip: history with who flew her, needs and language, the people around her, the pilots she knows, and the last trip closed out: pilot's report, handoffs, the thank-you, the report line.

A hospital social worker's dashboard: what needs her first, who is arriving at her hospital today and tomorrow, every referral as a row with its milestones, the quarter in one line, a three-minute referral form, and what she never sees and why.

Where a notification lands: one referral with its milestones and dates, what happens next, the one thing waiting on her, the dated history, documents, the thread with Maria, and the patient's earlier trips.

The page a social worker sends upward: referrals, patients flown, days to a pilot, donated flight value, road miles the families did not drive, by clinic, declined and why. Printable. Nothing names a pilot or a weather call.

Where every request went, including declined, cancelled and unmet need with reasons; lead times by stage and purpose; requests by region; pilots against demand; cost and donated value by segment type. Export the rows, or a donor summary with nothing identifiable.

Away from the desk: rose rows pushed as they turn rose, two taps each, and the day-of line ringing into the same call sheet with the caller matched to their trip before you answer.