On this page
Tasreeh rejections are predictable. Eight reasons account for the vast majority of refusals issued to tour operators every season, and seven of those eight are caught by a workflow that runs before submission rather than after. Operators that codify the checks see their rejection rate drop into the low single digits inside one season.
The pattern is simple: the Saudi side does not return verbose error messages, so operators who rely on the response alone never learn what to fix. Operators who build their own pre-submission validator catch the issues before the application is filed at all.
What the rejection codes do not tell you
The Tasreeh response carries a short rejection reason that maps to a category but not to the specific record. An entire batch can fail because one record is bad. The pre-submission workflow below catches the individual records before the batch ever leaves your platform.
The pre-submission workflow
The numbered steps below are the workflow we have seen drop one operator cohort from a 17% rejection rate to a 2.4% rejection rate inside a single season. The order matters: name reconciliation first, document expiry second, then the photo and entitlement checks before the health and assignment checks.
What to do when a record still rejects
A small number of rejections will always be inherent to the Saudi side and not to the operator. When that happens, the playbook is to isolate the record, refile it as a single submission, and capture the response for the audit log. Refiling the entire batch is the most common mistake operators make after the first rejection.
Field note
Permit teams often know the rejection reasons by heart. The improvement comes when those reasons stop living in one experienced officer and become a checklist every desk can run the same way.
What to do next
- Pull the policy owner, operations lead, and data owner into one review and agree which register is authoritative.
- Write down the evidence that proves each control was followed, then attach it to the pilgrim or operator record.
- Run a dry audit before the season opens so exceptions are visible while there is still time to fix them.
Step-by-step
-
Run a name reconciliation across passport, visa, and Nusuk record
Tasreeh rejects any record where the romanised name does not exactly match across the three source documents. Build a script that compares character-by-character. Single-name pilgrims and pilgrims with grandfather names appended cause most of the mismatches.
-
Verify the passport expiry buffer is at least eight months on the day of submission
Saudi authorities reject Tasreeh applications where the passport expires inside the eight-month buffer from the date of submission. This is not the visa rule, which is six months. Apply the longer buffer to be safe.
-
Confirm the issuing photo meets the strict portrait specification
Photos must be on a plain white background, with both ears visible, neutral expression, and a face area between sixty and seventy per cent of the frame. Most rejections in this category come from older photos taken for a different document.
-
Match the package category to the operator entitlement tier
Each operator carries a tier on the Saudi side. Filing under a higher tier than the entitlement allows causes a silent rejection that the operator only discovers when none of the permits issue. Verify the tier the day before submission, not the week before.
-
Verify hotel and transport allocations exist on the Saudi side before filing the permit
A Tasreeh application requires a Mecca hotel, a Madinah hotel where applicable, a Mina tent block, and a transport allocation. If any of these is not yet posted on the Saudi side, the application rejects without telling you which one is missing.
-
Confirm the meningitis vaccination is recorded and in date
The meningitis vaccination certificate is the most commonly missing health record. The vaccination must have been administered at least ten days before submission and no more than three years prior. Build a calculator into your pre-submission script.
-
Check that group leader assignments exist for every pilgrim
Every pilgrim in a Tasreeh submission must reference a registered group leader. Solo pilgrims, late-added pilgrims, and pilgrims swapped from one group to another are the records most likely to be orphaned.
-
Submit during the documented daily window
Tasreeh applications submitted outside the Saudi-side processing window queue without warning and frequently expire before they reach the assessor. Submit during the documented morning window in Saudi local time, not in your operator local time.