Set Cabin Crew Roster Reminders Without Notification Overload
Report-time reminders, airport collection prompts and landing notifications do different jobs. Set them in order, then check quiet hours and iPhone permissions.
For the same flight, one person needs a prompt to report for duty tomorrow; another needs to know when to leave home for an airport collection. Turning on every notification can create noise. Turning everything off can hide the one moment that calls for action. Start by choosing the purpose of each reminder.
Local roster reminders help you prepare; they are not flight status
Feiban can schedule roster reminders for the day before a duty, or before a confirmed report or departure time. If a time came from screenshot recognition but has not yet been checked, compare it with the original roster first. A flight sector with no confirmed time is not a sound basis for a minute-by-minute reminder.
- In Me, open the notification and time settings, then check that this iPhone allows notifications.
- Choose the one reminder you need most: perhaps a document check the day before, or enough travel time before reporting.
- Check the flight sector’s report and departure times. If they are uncertain, correct the roster before saving the reminder.
Airport collection: allow for travel, then check the flight
An airport collection reminder works backwards from an expected arrival, allowing for the journey from home to the airport and any extra buffer. If arrival is marked TBC, do not turn that number into a firm departure time. Even after a reminder arrives, check the airline’s published information before leaving. Roster times are scheduled or confirmed times, not a substitute for actual flight updates.
There are two kinds of quiet hours
- The crew member’s general local reminders: quiet hours can follow base time. Previous-evening, day-off and monthly reminders may move until the quiet period ends, while time-sensitive report, departure and collection reminders keep their original times.
- Each device’s push preferences: crew and family set these on their own iPhones. General push messages may wait until quiet hours end; the handling depends on the notification type.
If family lives in another time zone, they should set quiet hours around their own routine, rather than copying the crew member’s base-time sleeping hours. Each person can avoid unnecessary messages in the middle of the night.
A landing notification is not a scheduled-arrival reminder
An expected-arrival reminder follows a time on the roster. A landing notification needs available flight data and the required permissions. Turning on a notification switch does not mean actual landing information is available for every flight. If a sector has no data, check the airline’s announcement or ask the crew member directly.
A useful check today: keep only the reminders you will act on, verify one flight sector’s times, then look once more at iPhone notification permission and quiet hours. Those three steps matter more than adding another alert.
Agree on sharing before family follows a rosterReminders can help, but the crew member controls what family can see.Explore Feiban’s roster featuresSee how roster days, flight sectors and family sharing work together.