The flight manifest is the least forgiving document an Umrah agency produces. The rooming list has a human on the other end; the manifest is checked by systems, against machine-readable passports, with zero tolerance. One wrong character can mean a pilgrim argued over at a check-in desk while sixty people watch.
What a manifest is, and who demands it
A group passenger manifest is the structured list of everyone traveling on a flight — the file your airline or consolidator requires by their name-submission deadline. Depending on your setup, versions of the same data also go to your Saudi ground operator and into visa processing.
Each recipient wants specific columns in a specific order — and often their own template. Turkish Airlines' expected format is not Saudia's, which is not flynas's.
The fields that must be perfect
| Field | The trap |
|---|---|
| Full name | Must match the passport's machine-readable zone exactly — the airline doesn't care how the family actually spells it |
| Passport number | One transposed digit = a flagged passenger; O vs 0 from a re-typed photo is a classic |
| Date of birth & expiry | Format confusion (день/month order) and expiry below the ~6-month Saudi validity rule |
| Nationality | Must match the document, not the pilgrim's residence |
| Gender / title | Trivial — until it contradicts the passport |
Notice what these have in common: none of them are judgment calls. They're transcription. Which means every error in a manifest is a copying error — introduced somewhere between the passport and the spreadsheet.
Why manual manifests fail
The typical pipeline is: passport photo on WhatsApp → typed into Excel → copy-pasted into the airline's template → edited again after every change. Each arrow is an error source:
- Re-typing from photos produces the
O/0,I/1and transliteration mistakes. - Copy-pasting between templates shifts a row, silently misaligning every passenger below it.
- Late passenger swaps get patched into the template but not the master list — so the next export regenerates the old mistake.
- And the person doing all this is doing it at 11 p.m. before the deadline, which is when accuracy dies.
A manifest workflow that doesn't break
Three principles fix nearly everything:
- Single source of truth. Passport data lives in one place — the pilgrim's profile — entered once and verified against the scan. Ideally the pilgrim types it themselves at registration and you verify on approval.
- Generate, never edit. The manifest is an export of the profiles, produced in the airline's format. If something's wrong, fix the profile and regenerate — never hand-edit the output file.
- Gate on approval. Only verified ("approved") pilgrims appear on official exports, so a half-complete registration can't leak onto a manifest.
With this workflow, a late change is a one-record edit and a regenerated file — not an evening of cross-checking.
How Ziyara does it
In Ziyara, you create the flight (number, airline, route, dates), link it to the group, and download the passenger manifest as Excel or PDF. The format is matched automatically to major carriers — Turkish Airlines, Pegasus, Saudia, flynas, flydubai and Qatar Airways — so the file is ready to submit, and manifests can be generated in English, Bosnian, Turkish or Arabic.
Only approved pilgrims are included, and the data comes from the same encrypted profiles used for rooming and visa exports — entered once, verified once, never re-typed. When a passenger changes two days out, you update one profile and regenerate the manifest in seconds.
You can test it end-to-end on the free trial: add 20 pilgrims, create the flight, and compare the export against what your airline last asked of you.