Ebola Screening and Duty of Care Travel Disruption Brief

On May 21-26, 2026, U.S. entry rules shifted fast for passengers with recent presence in the Democratic Republic of the Congo, Uganda, or South Sudan. Enhanced Ebola screening is now tied to specific U.S. airports, with cutover times by date. If your teams are moving across East Africa this week, this is not background noise. This is an immediate duty of care test.

The operational risk is straightforward. A traveler can be fit to fly, properly documented, and still miss a connection or face rebooking if routing does not match the new screening flow. The legal and governance risk is just as real. If your process did not detect this change and adapt itineraries in time, you own the delay and exposure.

What changed in U.S. screening requirements

According to the U.S. Department of State worldwide caution update and related CDC and DHS actions, U.S.-bound passengers who were present in DRC, Uganda, or South Sudan within 21 days must enter through designated airports for enhanced public health screening.

Current airport cutovers listed by U.S. authorities:

• Washington Dulles (IAD), after 11:59 PM on May 21, 2026
• Hartsfield-Jackson Atlanta (ATL), after 11:59 PM on May 22, 2026
• Houston George Bush Intercontinental (IAH), after 11:59 PM on May 26, 2026

For employers, this creates three immediate realities:

• Routing risk: previously acceptable return paths can become non-compliant.
• Time risk: screening and airline processing can add schedule friction.
• Communication risk: travelers can receive mixed guidance from local teams, TMCs, and airlines if your central instruction is late.

Why this is a duty of care issue, not just a travel admin issue

Duty of care means foreseeable risk, timely mitigation, and evidence that you acted. Public-health screening changes hit all three.

A risk manager can reasonably foresee disruption when:

• A government issues destination-linked entry restrictions.
• Airlines begin route adjustments around those restrictions.
• Travelers are transiting multiple regions with high schedule sensitivity.

What can go wrong if your controls are weak?

• Travelers are stranded in transit because the final U.S. entry point is not designated.
• Critical staff miss project milestones or regulatory meetings.
• Medical and welfare concerns escalate if a traveler is delayed with limited local support.

That is exactly why an ISO 31030-aligned program should treat advisory updates as operational triggers, not passive reading.

Immediate playbook for corporate travel risk teams

1) Re-check all affected itineraries inside a 21-day exposure window

Do not wait for travelers to self-report at departure. Pull manifests now for anyone who has been in DRC, Uganda, or South Sudan in the past 21 days and is heading to the U.S. Confirm entry airport alignment against current restrictions.

2) Create one source of truth for routing and traveler instructions

Send a single internal advisory that includes:

• Affected countries and the 21-day lookback rule
• Designated U.S. entry airports and cutover dates
• Airline confirmation requirement before departure
• Escalation contact for urgent re-ticketing

Mixed messages are a preventable failure mode.

3) Coordinate travel, security, HR, and medical support

This is cross-functional. Travel can rebook, security can assess route friction, HR can track welfare obligations, and medical partners can advise on health protocol questions. Keep one incident owner.

4) Pre-authorize cost exceptions

If your teams need last-minute re-routing, waiting for finance approval creates avoidable risk. Temporary policy flexibility this week is cheaper than disruption to critical operations.

5) Capture your decision trail

Log what changed, when you assessed it, who approved mitigations, and how travelers were informed. If a disruption happens, documentation matters for governance, insurer conversations, and internal audit.

Broader trend, more frequent rule shocks

This event is also a pattern signal. Entry requirements tied to health, security, and geopolitics are changing faster and with narrower notice windows. Corporate programs that rely on manual monitoring and ad hoc email chains will keep losing time.

High-performing teams are moving toward:

• Continuous advisory monitoring
• Automated traveler exposure matching
• Fast multi-channel traveler communication
• Real-time check-ins when itineraries deviate

That capability shift is exactly where modern duty of care programs gain resilience. If your current setup is mostly spreadsheet plus inbox, this week is a clear stress test.

What to do this week

If you run a travel risk program, prioritize these actions in the next 24 hours:

• Audit all U.S.-bound travelers with recent presence in DRC, Uganda, or South Sudan
• Validate entry airport compliance and contingency routes
• Issue one consolidated traveler advisory and manager briefing
• Stand up a temporary rapid-response desk for rebooking and welfare checks
• Record all interventions for post-incident review

A final point. This is not about creating alarm. It is about creating reliability when conditions move quickly. Your travelers do not need noise. They need clear direction, practical support, and confidence that someone is watching the risk picture in real time.

If you want to pressure-test your response model against events like this, HAAVYN’s /en/secure-mobility framework is a good place to benchmark your current gaps and response speed.