5.06.26 – Contract Implementation Update #60: Rescheduling in ECS Now in Effect

Wednesday, May 6, 2026

Contract Implementation Update #60:
Rescheduling in ECS Now in Effect

Rescheduling notifications are now live in ECS for:

• Disrupted after report but prior to origination (10.J.3.d)
  • When a Flight Attendant experiences a disruption after report but prior to origination (CBA 10.J.3.d), Crew Scheduling has either four (4) hours after report time or three (3) hours after the disruption, whichever is later, to notify the Flight Attendant of their sequence repair. During this timeframe, a Flight Attendant must remain contactable. The notification of repair will now come via ECS instead of a phone call.
• Disrupted after origination (10.J.4.c)
  • When a Flight Attendant experiences a disruption after origination of their sequence (CBA 10.J.4.c), Crew Tracking has three (3) hours after the disruption is known to notify the Flight Attendant of the sequence repair. During this timeframe, a Flight Attendant must remain contactable. The notification of repair will now come via ECS instead of a phone call.

You can read more about these notifications here, as well as how to set up optional methods of communication and an FAQ here.

Click the image below to watch a video explaining these rescheduling changes.

If you encounter any issues in ECS, you can submit feedback under ECS > Profile > Send ECS Feedback.

In Unity,

Ashleigh Harbison
LAX

Hunter Meredith
PHL

Mike Sosa
DFW

Contact the CIC