To set up crew scheduling software for schedule recovery and legality checks during severe disruption events, you want to configure it around two goals:

1. Recover the operation fast
2. Never assign illegal crew pairings

Here’s a practical setup approach.

---

1) Define the disruption recovery use case

First, make sure the software has a dedicated irregular operations / disruption mode. This mode should support:

• Flight cancellations, delays, diversions, aircraft swaps
• Crew no-shows, sick calls, deadheads, positioning
• Airport closures, weather events, ATC restrictions
• Time-based recovery planning over the next 4–72 hours

Set the system to prioritize:

• Critical flights
• Hub bank preservation
• Connection protection
• Crew legality and rest compliance
• Minimize cancellations and hotel/transport costs

---

2) Load all legality rules into the system

Crew legality checking only works if the rule engine is configured with your actual contract and regulatory rules.

Include these rule types:

• Duty time limits
• Flight time limits
• Leg count limits
• Minimum rest periods
• Time zone / circadian protections
• Consecutive duty day limits
• Overnight / augmented crew rules
• Standby / reserve limits
• Accumulated monthly/weekly limits
• Positioning/deadhead credit rules
• Fatigue or special safety rules, if supported

Best practice:

Use rule layers:

• Regulatory rules
• Company policy rules
• Union/CBA rules
• Exception rules for emergency operations

The software should evaluate legality in real time whenever a schedule is changed.

---

3) Configure crew data correctly

The system needs current crew information to validate recovery plans.

Required data:

• Crew base/station
• Qualification and fleet type
• Role qualification: captain, first officer, purser, cabin, etc.
• Current assignment state
• Time worked in current day/week/month
• Rest completion status
• Reserve availability
• Vacation, training, leave, sick status
• Deadhead/positioning location and timing
• Visa/passport or airport access restrictions, if applicable

If this data is stale, legality checks will be unreliable.

---

4) Set up recovery constraints and priorities

During severe disruption, the scheduler should optimize under constraints.

Typical constraints:

• Maintain legality
• Preserve required crew composition
• Keep aircraft and crew co-located where possible
• Avoid excessive repositioning
• Respect base rules and language/qualification requirements
• Protect flights with passengers/connectivity priority
• Minimize crew changes near departure
• Maintain minimum reserve coverage

Priority ranking example:

1. Safety and legality
2. Aircraft/flight coverage
3. Passenger-facing critical flights
4. Crew cost and operational efficiency

---

5) Enable scenario planning and what-if simulations

A good recovery system should let planners create multiple scenarios, such as:

• “Cancel low-priority flights and reassign crews”
• “Use reserves first, then deadhead crews”
• “Extend some crew duty if legally allowed”
• “Swap aircraft and re-pair crews”
• “Split pairings or rebuild pairings from scratch”

Make sure the software can:

• Run batch optimization
• Show legality impact instantly
• Compare recovery options by KPI

Useful KPIs:

• Number of flights recovered
• Number of canceled flights
• Crew legality violations
• Reserve utilization
• Recovery time
• Cost impact

---

6) Turn on real-time legality validation

This is critical.

The software should flag, at the moment of assignment:

• Illegal duty accumulation
• Insufficient rest
• Overrun of FDP/duty limits
• Qualification mismatches
• Base or station violations
• Sequence problems caused by delays or time changes

Recommended setup:

• Hard stop for impossible/legal violations
• Soft warning for near-violations or policy concerns
• Auto-recalculate on every change to a pairing or crew assignment

---

7) Build recovery workflows for planners

Create standard operating workflows so recovery is consistent.

Example workflow:

1. Import disruption event
2. Freeze current schedule snapshot
3. Identify impacted flights and crew pairings
4. Run legality filter to remove infeasible pairings
5. Generate recovery options
6. Assign reserves / reposition crews
7. Recheck legality after every change
8. Publish updated schedules
9. Send notifications to crew and operations teams

---

8) Add reserve management rules

Reserves are often the key to recovery.

Configure:

• Reserve call-out windows
• Home reserve vs airport reserve
• Priority order for assignment
• Maximum reserve utilization
• Escalation rules when reserves are exhausted

The system should choose reserve crews only if they remain legal after assignment and positioning.

---

9) Integrate with other operational systems

To make recovery effective, connect the scheduler to:

• Flight operations system
• Crew tracking / attendance system
• Flight delay and cancellation feeds
• Aircraft routing / tail assignment system
• Airport gate/ATC disruption feeds
• HR/leave/training system
• Crew notification tools

This ensures legality checks reflect actual operations in near real time.

---

10) Test disruption scenarios before going live

You should stress-test the configuration with simulated events like:

• Winter storm at a hub
• Multiple crew sick calls
• Aircraft grounding
• Long ATC delay chain
• International arrival delay causing rest violation

Verify that the system:

• Detects illegal schedules correctly
• Suggests workable recovery options
• Doesn’t over-assign reserves
• Handles cascading delays without producing false legality passes

---

11) Define approval and override rules

During emergencies, people may need to override recommendations. Set this up carefully.

Recommended:

• Only authorized schedulers can override
• Require reason codes for manual edits
• Log every override
• Require a second review for high-risk changes
• Keep audit trails for compliance

If your environment allows exceptions, the system should clearly label them and separate them from fully legal schedules.

---

12) Monitor post-recovery performance

After the event, review:

• Number of illegal attempts prevented
• Manual overrides used
• Recovery speed
• Crew fatigue indicators
• Cost of disruption
• Missed connections or additional cancellations

Use this data to refine optimization rules and reserve planning.

---

Simple implementation checklist

If you want the shortest practical setup path, do this:

• Load all legal, contractual, and fatigue rules
• Import accurate live crew status data
• Enable real-time legality validation
• Set disruption recovery priorities
• Connect flight, crew, and delay feeds
• Configure reserve and deadhead rules
• Test with disruption simulations
• Lock down approvals and audit logging

---

If you’re choosing software

Look for features like:

• Rule engine for legality
• Optimization / recovery solver
• Real-time crew tracking
• Scenario planning
• Audit trails
• API integration
• Reserve management
• Alerting and notification

---

If you want, I can also give you:

1. a vendor-neutral setup template,
2. a sample legality rule checklist, or
3. a disruption recovery workflow diagram.