On this page
The days of Tashreeq are the hardest communications environment in any operating year. Networks saturate, staff are exhausted, family pressure converges from every direction, and the timeline for any individual decision is short. The plan below has held under load across multiple operator cohorts. It is procedural, not technological, because the technology is unreliable in exactly the moment the plan is needed.
One officer, one register
A single communications officer holds the message register for the duration of the season. The register is a written log of every external message sent, the recipient category, the time stamp, and the approving signature. Field staff route external comms through the officer rather than drafting their own. The discipline is the only thing that prevents contradictory messages reaching the same audience.
The family line
A family inbound line is a separate workflow with a separate phone tree. The line is staffed continuously through the days of Tashreeq and uses pre-drafted scripts that the officer has signed off. The script covers what the operator can confirm, what the operator cannot confirm, and the next time the family will hear from the operator. A regular cadence of updates, even when there is nothing new to share, is the single biggest determinant of family trust during an incident.
Pre-drafted templates that survive a crisis
The templates that hold under load are the ones written months in advance and approved by counsel: a missing-pilgrim notification, a hospitalisation notification, a hotel-relocation notification, a flight-disruption notification, and a confirmed-fatality announcement. Field staff in the days of Tashreeq cannot draft new messages. They can only adapt approved templates. The library is small but mandatory.
The fatality protocol
A confirmed pilgrim fatality is the hardest communication an operator will ever issue. The protocol is fixed before the season starts. The officer confirms the death through the documented Saudi channels, briefs the operations lead, calls the family in private with the line's senior staff, follows the call with a written confirmation, and only then issues any internal communication beyond the war room. No social media post precedes the family call. No staff member outside the war room knows before the call is made.
Network saturation and the satellite fallback
Mobile networks in Mina and Arafat saturate during peak periods. Operators that rely on WhatsApp for crisis communication discover the limit at the worst possible moment. A satellite phone in the war room and a written escalation path that does not depend on commercial mobile coverage are the only reliable fallback.
What survives the season
After the days of Tashreeq close, the message register is the artefact that survives the post-season review. Regulators, families, and journalists all ask for the same thing: a complete record of what the operator said and when. Operators that maintained the register from day one produce it in five minutes. Operators that did not spend three weeks reconstructing it from screenshots.
Field note
Families rarely need a perfect answer in the first ten minutes. They need proof that the operator knows about the incident, is looking at the right list, and will return at a named time.
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.