On this page
A clean charter manifest is not produced the day before departure. It is produced by a seven-day countdown that runs every flight through the same checks at the same intervals. The countdown survives the Saudi-side curfew on changes and avoids the cluster of cancellations and rebookings that mark a less disciplined process.
D-7: Lock the passenger universe
Seven days before departure, the passenger universe should be final. Late additions after D-7 are permitted but treated as exceptions and routed through a single sign-off path. Every pilgrim on the manifest must have a valid passport, a valid visa, a valid Tasreeh, and a confirmed bus assignment to the airport.
D-6: Validate identity fields against three sources
Compare the manifest against the Saudi-side Nusuk record, the operator's internal pilgrim record, and the carrier's reservation system. Names, dates of birth, and passport numbers must match exactly across all three. Single-name pilgrims and pilgrims whose grandfather name was added or removed by the visa office are the most common mismatch sources.
D-5: Flag special assistance
Wheelchair requests, oxygen requirements, dietary restrictions, and unaccompanied minors all carry separate codes the carrier needs at least one hundred and twenty hours before departure. Late special-assistance flagging is the field that triggers the most last-minute rework. Run a query against the pilgrim records and the medical screening notes, not the verbal report from the group leader.
D-4: Bus and luggage manifest reconciliation
The flight manifest, the bus manifest, and the checked-luggage manifest should reconcile to the same pilgrim count, the same group leader assignments, and the same arrival sequence at the airport. A reconciliation difference at this stage is almost always due to a pilgrim swapped between groups in the previous week.
D-3: Submit final manifest to the Saudi side
Seventy-two hours before departure, the manifest goes in. The Saudi side stops accepting clean changes after this point. Changes inside D-3 are possible only as exception requests, and they generate a paper trail that auditors will review later.
D-2: Run the carrier-side compare
The carrier's reservation system carries a second source of truth. Pull the carrier report and reconcile it against your manifest. A typical carrier-side discrepancy is a passenger whose seat was reassigned during a system maintenance window. Catch them now, not at the gate.
D-1: Brief the operations team
The day before departure is a briefing day, not a data entry day. The group leader, the bus coordinator, the airport coordinator, and the field medical lead should all leave the briefing with the same passenger list, the same sequence of movements, and the same escalation contacts. Print the briefing pack. WhatsApp messages do not survive the airport.
Departure day
The departure day playbook is purely operational by this point. There are no manifest changes left to make. Every disruption is now an exception that goes through a documented path. Operators who arrive at the airport with a clean manifest run their flights on schedule. Operators who arrive with an open manifest spend the day on calls.
Field note
The hardest manifest conversation is not with the airline. It is with the internal team that wants one more late change after the cutoff. Write the cutoff down and defend it early.
What to do next
- Name one accountable owner for the workflow and give that person authority to close exceptions.
- Turn the article checklist into a dated runbook with daily cutoffs, backup owners, and escalation thresholds.
- Review the runbook after the first field incident and update it while the details are still fresh.