Flights is the travel ledger. Every flight booked for the tour in one place.
WHAT YOU SEE:
A timeline of flight legs with: passenger, airline + flight number, origin → destination, departure + arrival, status (Scheduled / Boarding / In-Air / Landed / Cancelled / Delayed).
SCAN YOUR INBOX FOR FLIGHTS:
Day page flight card, Scan Inbox: ATOM reads your connected Gmail for flight emails; you tick what to import. Gmail only, no drop-a-PDF for flights yet (use + Flight).
FLIGHT EMAILS AND MONEY:
Only the purchase receipt (the booking email, sent the day the ticket was bought) logs its fare to Money, once, filed on the day it was bought (the receipt's issue date, else the day the email came in), never the travel day. Change, cancellation, credit, upgrade, check-in, reminder and boarding-pass emails never go to Money; they repeat the original fare. A real change fee or fare difference arrives as its own charge email and is logged like a booking. A cancellation goes to the flight-credit ledger instead.
A ticket with connecting flights is ONE fare: it is counted once per passenger, on their first flight, never once per flight. A booking for three people is three fares, one each. Miles and points are never read as money (an award ticket logs only its cash taxes and fees), and a price that looks like miles or is over $5,000 for one ticket is held on the row for you to check instead of being sent. When a ticket's per-flight prices don't add up to one clear fare, the row says Check fare and waits for you.
WHICH CARD PAID: a fare only goes to Money on its own when the airline email shows one of the tour's own cards (set in Money > Settings > Cards & team > Tour cards). If it was paid on anyone else's card, or the email doesn't show a card, or no tour cards are set up, nothing is written; the row asks you: Paid on a tour card, Reimburse them (logged as a pending reimbursement to whoever paid, not as tour spend), or Not ours (never asked again). ATOM never assumes a personal card is the tour's.
LIVE STATUS:
Flights matched to the airline feed update on their own: gate changes, delays, baggage carousel.
ADD A FLIGHT OR A GROUND RUN:
On the day you want, open Travel and tap + Flight or + Ground. Each opens its own full screen; the back arrow returns you to the day.
Flights: type the flight number and ATOM looks up the real airline, route and times; add connecting legs; pick who is flying from the roster; add seats and confirmation numbers; and if an unused airline credit matches that traveler, it is offered right there. Ground: bus, van, shuttle or black car with stops along the route, drive time and mileage, DOT driver-hours warnings, rest stops, and an optional link that books the cost straight into Money.
TIME ZONES ON A DRIVE:
A drive's arrival time is shown in the destination's local time, the same way Master Tour shows it. If you leave Nashville at 10:40 PM and drive eight hours east into the Eastern zone, ATOM says you arrive at 7:40 AM local, not 6:40.
ATOM works the zone out from the map pins on the start and end of the trip, so there is nothing to set. It uses the zone as it will be on the day you arrive, which means daylight saving is handled, including a drive that crosses the changeover overnight.
The one case it cannot do this: if you typed the miles and drive time by hand and never pinned a location, there are no coordinates to read a zone from, so the arrival is plain clock arithmetic. Pin the start and end and it corrects itself.
WHAT EACH DAY ON THE TRAVEL BOARD SAYS:
Every day on the board is headed by its date, city and day type (Show day, Festival, Travel day, Day off). On a show or festival day the venue is named right after the city, for example "Charlotte · The Amp Ballantyne", so you can see what the day is for next to the moves and the hotel. Travel days and days off show no venue. The show itself lives on the day page; tap the date to open it.
OVERNIGHT DRIVES ON THE TRAVEL BOARD:
A move that leaves after tonight's show and lands tomorrow morning is not shown inside either day. It sits between them, as a dashed connector marked Overnight, because that is when it actually happens. It reads by city ("Charlotte to Asheville"), with the venue, miles and drive time underneath, and the departure and arrival times including the fact that the arrival is the next morning.
This is one travel record, not two. The day you leave keeps the booking; nothing is duplicated onto the next day. Tap the connector to open the run.
OPEN A GROUND RUN (bus, van, sprinter, train, ferry):
Tap a ground card on the day and you land on that run's own screen, the same way a flight does. It shows the whole route with every stop and its address, depart and arrive times (an overnight arrival is marked +1), miles and drive time, who is driving with their DOT hours for the day and the week against the legal caps, flagged amber near the cap and red over it, who is riding, and any notes. Edit and Delete trip are in the top bar. Back returns you to the day.
OPEN A FLIGHT (one place, from anywhere):
Tap a flight anywhere in ATOM: the day page's Travel section, the Travel board's flight cube, either calendar, or the flight list inside the day's travel editor, and you land on that flight's own screen. It is a real page, not a pop-up: nothing covers what you were looking at, the back arrow (or your phone's back swipe) returns you exactly where you came from, and the address bar holds a link to that flight you can send to someone.
On that screen you can edit in place: departure and arrival times, aircraft, flight notes, and each traveler's seat and confirmation number. Nothing saves until you tap the checkmark, so a mis-tap never changes a booking. Confirmation numbers: in Who's flying, tap a person's + Conf chip, type it, tap the check. One number for the whole party? Tap + Conf for everyone. Prev / Next step through the tour's flights without leaving the screen.
DELETE A FLIGHT, OR TAKE ONE PERSON OFF IT:
Both live on the flight's own screen, and they mean different things.
Delete flight (top bar, red) removes the whole flight for everyone on it. It confirms first and tells you how many passengers it affects. Once you confirm, the calendar, day sheet, and Money manifest all drop it automatically. No separate cleanup. This is different from marking a flight cancelled-for-credit, which keeps the record and tracks the airline credit instead.
The X beside a traveler's name takes just that person off the flight and leaves the flight itself alone for everyone else. Use this when one person's plans changed, not the booking.
There is no second delete hiding anywhere else. The day's travel editor lists what's on the day and takes you to the flight; it does not delete.
If you can see a flight but can't change it, that's your role on this tour, not a broken screen. Travel editing is limited to tour managers and admins. Ask your TM to make the change.
MATCH TRAVELERS (Trips list):
When ATOM can't tell who a booked name is, it asks. Yes, that's [name] saves the booked name onto that contact so it links everywhere from then on. + New contact or Add as contact makes a new contact for them. Not them or Dismiss tells ATOM to stop asking about that traveler on this tour, and it remembers on every device you log in on.
MANIFEST EXPORT:
Every leg writes to the per-passenger manifest. Export PDF for visa applications, travel manager handoffs, or the per-diem accountant.
TIES INTO:
Leg passenger names pull from the Personnel roster. Departure/arrival cities are sourced from the IATA airports directory in ATOM Intel (6,858 airports as of S109).