IN
Faith & culture (planning support)
If faith, culture, or community tradition shapes the ceremony, start from the India Faith & Culture hub and follow your pathway.
Parsi (Zoroastrian) Funeral Planning (India)
Parsi/Zoroastrian funeral practice in India is often community- and tradition-led. The practical challenge is coordinating the mobed (priest), the relevant community trust/committee, family decisions, and guest flow—without letting logistics overwhelm the moment.
Practice sensitivity (important)
This page is a planning container, not a rulebook. Where there are community/trust protocols (including eligibility/access rules), confirm details privately with the family, mobed, and the relevant trust/committee. Avoid debating sensitive details in guest groups.
If timing is affected by official steps or documentation requirements, keep this page as your ceremony plan and use India What to do after a death, Legal, and Government services for the administrative layer (kept separate from ceremony planning).
Planning-only scope (no legal/admin overlap)
This page covers ceremony structure, guest experience, and practical planning. It does not include registration, certificates, police/medical formalities, permits, probate, inheritance, pensions/benefits, or any legal/administrative steps.
The rule that prevents chaos
Keep it to: one coordinator, one update thread, and one run-sheet. Don’t publish timing (or a second location) until the mobed + community trust/committee confirm what’s practical.
2-minute decision tree (choose your safest plan)
Back to topUse this to choose a plan that protects tradition, community rules, and timing realities.
Step 1: Which pathway applies in your city/community?
- A — Community-regulated pathway: trust/committee coordinates core logistics and the mobed leads prayers.
- B — Home + prayer hall focus: prayers at home and/or a community hall; guest flow is the main challenge.
- C — Alternative pathway: if the usual pathway is not used/available, plan with mobed + family + local rules for the respectful option.
Step 2: Is timing uncertain (hospital release/transfer)?
- Yes: keep the first viewing window flexible; publish updates in real time.
- No: still build buffers—traffic and queues can shift plans fast.
Step 3: Will the venue be low-resource (no seating/PA/AC)?
- Yes: set an elder station + water point; design a “no-tech” flow.
- No/unsure: still bring a no-tech backup plan (paper signage + ushers).
Step 4: Is there a second location?
- Yes: publish only after fully confirmed; use convoy-proof rules.
- No: keep it to one location + after-gathering (if any).
Links for the separate admin track (kept separate)
If documentation or official steps are affecting timing, keep that track separate and use What to do after a death, Legal, and Government services.
India realities (design around these first)
Back to top- Trust/committee rules may decide what’s possible: confirm early to avoid last-minute conflict.
- Timing can change suddenly: especially with hospital release/transport and city traffic.
- Gate/landmark beats addresses: share the correct entrance + meeting point, not just a map pin.
- Heat/monsoon: water on arrival, shade/umbrellas, and a step-out plan keep elders safe.
- Resource levels vary: some venues have no PA, minimal seating—plan a “no-tech” flow.
- Street-edge reality: crowd spillover, uneven pavements, and open drains can be hazards—assign one “safety watcher.”
Velanora planning principle
Separate the plan into two layers: core prayers (protected) and community support (condolences/hosting). If logistics are tight, keep core prayers simple and shift support to a calmer gathering later.
Links for the separate admin track (kept separate)
If documentation or official steps are affecting timing, keep that track separate and use What to do after a death, Legal, and Government services.
The first-hour plan (calm coordination, fewer mistakes)
Back to top- Nominate two roles: (1) mobed/trust liaison, (2) guest communications.
- Create one WhatsApp update thread: guests get updates there; close family aren’t fielding calls.
- Confirm the trust/committee contact: who approves timing/venue access/onsite flow.
- Confirm the mobed timing: what time windows are realistic and what prayers/format will be used.
- Elder station + water point: do this early (it prevents medical stress later).
- Ops discipline: post the next update at a promised time—even if the message is “No change.”
- Do not publish the second location: hold until fully confirmed; use convoy-proof rules.
Buffer math (India-realistic)
Reverse-plan arrivals. Example: if prayers start 10:00am, set guest arrival for 9:30am and helpers for 9:10am.
Update cadence (prevents constant calls)
Update cadence: we will post the next update at [Time]. If there is no change, we will still message “No change” so you are not left guessing.
Links for the separate admin track (kept separate)
If documentation or official steps are affecting timing, keep that track separate and use What to do after a death, Legal, and Government services.
Who to call first (planning layer — coordination, not paperwork)
Back to top- Mobed / priest contact: confirm prayers, timing, and any participation expectations.
- Community trust/committee (Punchayet/Anjuman/local trust): confirm rules, access, and logistics lead.
- Venue contact: home society security / hall manager / funeral grounds gate contact.
- Local fixer: someone who knows gates, parking, and pinch points.
- Travel coordinator: one person for arrivals/delays so family aren’t flooded with calls.
Links for the separate admin track (kept separate)
If documentation or official steps are affecting timing, keep that track separate and use What to do after a death, Legal, and Government services.
Roles matrix (roles + backups)
Back to topSuggested roles (fill names now)
Decision owner (today): [Name/Role]
Coordinator (primary): [Name] • Backup: [Name]
Guest communications: [Name] • Backup: [Name]
Mobed liaison: [Name] • Backup: [Name]
Trust/committee liaison: [Name] • Backup: [Name]
Venue/security liaison: [Name]
Flow keeper (movement): [Name]
Elder support (station + drop-off): [Name]
Quiet guide (non-Zoro guests): [Name]
Child support (calm helper): [Name]
Travel coordinator: [Name]
Cost handler (private only): [Name]
Safety watcher (drains/footing/crowd edges): [Name]
VIP boundary liaison (if needed): [Name]
Community trust rules (confirm early — prevents day-of conflict)
Back to topIn many Indian cities, key elements can be community/trust-regulated. Confirm early so you do not publish a plan that clashes with local rules.
- Confirm eligibility/requirements for the pathway being used (rules may apply).
- Confirm who the on-site logistics lead is (the person you coordinate with on the day).
- Confirm timing windows and how changes are communicated.
- Confirm guest rules (entry points, crowd limits, phone rules, etc. — varies).
- Confirm whether a second location is involved and what the approved routing is (publish only once confirmed).
One-line alignment script (copy/paste)
“We want to follow the community rules and keep things calm. Can you confirm what is essential, what time windows are practical, and who is the on-site logistics lead?”
Links for the separate admin track (kept separate)
If documentation or official steps are affecting timing, keep that track separate and use What to do after a death, Legal, and Government services.
Eligibility & mixed-family realities (handle privately — protect mourners)
Back to topSome decisions can be sensitive (eligibility, access, family tradition, mixed-faith families). The best practice is to handle it privately and keep guest communications simple and respectful.
- Do not workshop sensitive issues in guest groups: route questions to the private liaison.
- Publish the minimum public plan: one clear main location + time + gate/landmark + meeting point.
- Use a guest-safe line: “Details are being handled privately. Please follow the family’s plan and ushers.”
- Name one liaison: only one person speaks with the trust/committee/mobed about sensitive questions.
Copy/paste guest-safe line (for ushers)
Guest-safe line (use if asked sensitive questions): “Details are being handled privately. Please follow the family’s plan and ushers.”
Mobed coordination (what to confirm before you publish time)
Back to top- Prayer format + timing: what will happen, where, and for how long (local practice varies).
- Participation: any expectations about who stands where, who responds, and any family roles.
- Women’s participation norms: confirm seating/roles expectations (varies by setting).
- Language plan: if guests are mixed-language, keep announcements bilingual and minimal.
- Second location: if any movement is involved, confirm the exact sequence and what guests should do.
Comfort + dignity rule
Keep announcements short, keep movement gentle, and protect elders with seating + water + a step-out plan.
Prayer flow options (choose what fits your time window)
Back to topZoroastrian ceremonies are tradition-led. Use these as planning containers, then align with the mobed + trust/committee.
Tight window (focused, dignified)
- Helpers arrive early; elder station + water point set
- Mobed-led core prayers
- Controlled entry/exit flow
- Clear instructions for next location (ONLY if confirmed)
Balanced flow (typical planning container)
- Arrival + settling + quiet greetings
- Prayers
- Condolences after prayers (in waves)
- Movement to next location if applicable (one meeting point + convoy-proof rule)
Crowded/heat/monsoon reality (low-resource friendly)
- Seating/water/step-out points are core logistics
- No-PA plan: ushers guide quietly; keep movement minimal
- Keep the near-circle quiet; overflow stays included
- Move support/hosting to a calmer venue later
Ritual items & sensory plan (practical, non-legal)
Back to topSmall practical gaps cause the most day-of stress. Confirm what the venue/trust provides and bring a minimal “calm kit” so the ceremony stays dignified even in low-resource conditions.
- Confirm what is provided onsite: lighting/candles, basic seating, water availability, and any locally used ritual/sensory elements (varies).
- Bring a minimal calm kit: water/ORS, tissues, 2 spare shawls/scarves, safety pins, umbrella, paper + marker for a gate sign, and a lighter/matches.
- Step-out point: define one place people can step out for air without feeling awkward.
- Seating placement: elders + respiratory-sensitive guests near airflow/exit route.
Why this matters
If you remove the small frictions (water, seating, signage, step-out), you prevent panic—and the prayers stay protected.
Bells & incense heads-up (for unfamiliar guests — reduces anxiety)
Back to topSome guests will be unfamiliar with sensory elements (bells, incense, ritual cues). A simple heads-up prevents worry and helps people follow respectfully.
- If bells are used locally, tell guests: “Bells may ring at specific moments—this is normal.”
- If incense/smoke is present (varies), set a step-out plan: “If you need air, step out to [Spot]—a helper will guide you back.”
- For elders/respiratory sensitivity, seat them near a calm exit route.
Non-Zoro guest comfort line (optional)
“We’ll follow the mobed’s cues. If something is unfamiliar (bells/incense), it’s part of the tradition—please feel free to step out quietly if needed.”
Hospital → home (timing uncertainty — plan for flexible first viewing)
Back to topIn some cities, release/transfer can happen with minimal notice. If timing is uncertain, plan for flexibility so the family isn’t forced to “re-invite” people repeatedly.
- Keep the first viewing window approximate (e.g., “from ~[time]”).
- Use a single update thread and pin the latest “go-time” message.
- If there’s a delay, shift guests into a calm holding pattern (water available, quiet seating, start after arrival).
Copy/paste timing uncertainty note (optional)
Timing note: if hospital release/transfer timing is uncertain, we will post updates in real time in this thread. Please rely only on the latest pinned update from [Name]. We will confirm start time once [mobed/trust guidance + arrival timing] are confirmed.
Copy/paste status cadence (optional)
Update cadence: we will post the next update at [Time]. If there is no change, we will still message “No change” so you are not left guessing.
Links for the separate admin track (kept separate)
If documentation or official steps are affecting timing, keep that track separate and use What to do after a death, Legal, and Government services.
Venue patterns (home / hall / funeral grounds — pick what reduces strain)
Back to topPattern A: Home prayers → calm gathering later
- Best for: elders, limited movement, short notice.
- Watch for: apartment/society gate logistics, lift access, crowd spillover.
- No-PA reality: ushers guide quietly; avoid long announcements.
Pattern B: Prayer hall/community venue
- Best for: structured entry/exit and better crowd control.
- Watch for: parking, correct gate, and overflow plans.
- Low-resource possibility: limited seating/AC/PA—plan for standing + water point.
Pattern C: Trust-managed pathway (where applicable)
- Best for: aligned tradition + established procedures.
- Watch for: strict rules and timing windows—confirm early.
- Publish only what the trust/committee confirms is practical.
Links for the separate admin track (kept separate)
If documentation or official steps are affecting timing, keep that track separate and use What to do after a death, Legal, and Government services.
Society security, lifts, and gate friction (India-specific)
Back to topApartment societies and gated communities can accidentally create the most stress (access control, lifts, parking). Solve it with a simple “gate plan” and one liaison.
- Gate liaison: one person coordinates with security so mourners aren’t disturbed.
- Name list / pass plan: if needed, share a short list of key family names with security.
- Lift reality: plan for slow lift cycles; reserve priority for elders; keep stair fallback calm.
- Noise sensitivity: keep announcements minimal; use ushers rather than loud instructions.
- Parking triage: elder drop-off first; park away from the gate; keep a clear path.
Second location & convoy-proof transport rule (prevents ‘lost convoy’ chaos)
Back to topIf the ceremony involves multiple locations (for example: home → prayer hall → grounds), the fastest way to create chaos is publishing partial details. The fix is a strict “publish only when confirmed” rule + convoy-proof routing.
- Hold publication: do not share the second location until mobed/trust/venue confirm it is approved and practical.
- One meeting point at each location: “Go here and wait,” not “follow the car in front.”
- Repeat Gate + Landmark: every update includes the correct entrance and a landmark.
- Keep family out of traffic calls: direct lost guests to the meeting point, not to mourners.
Copy/paste: hold second location
Second-location note: we will NOT publish the second location until it is fully confirmed by mobed/trust/venue. If you hear a different second-location plan elsewhere, ignore it and check this thread.
Copy/paste: convoy-proof rule
Convoy-proof transport rule: • Do NOT follow another car based on assumption. • Every guest uses the same Gate + Landmark + Live location + Meeting point. • If you get separated, go directly to the meeting point (do not call the family).
Tower/dakhma pathway (where applicable — plan with trust rules)
Back to topIn some communities and locations, the pathway may involve trust-managed funeral grounds and strict protocols. Planning success comes from confirming rules early and designing guest flow to minimize confusion.
- Confirm whether attendance/access rules apply (confirm privately with the trust/committee).
- Confirm arrival gate + meeting point and the “where to stand” instruction.
- Keep guests on a one-direction flow (arrive → prayers → exit) with ushers.
- Plan an elder station (shade + water + seating) and a step-out spot.
Respect + clarity rule
Don’t improvise around trust rules on the day. Confirm, then communicate one clear guest plan.
Alternatives (where tower not used/available — keep planning respectful)
Back to topIf the usual pathway is not being used/available, decisions can be sensitive and highly local. The planning goal is to align family wishes with what is permitted and dignified in your area.
- Confirm the approach with mobed + family + local community guidance.
- Keep the guest plan simple: one main prayer location + one after-gathering (if needed).
- If there is a second location, publish only after it is confirmed and practical—use the convoy-proof rule.
Mixed-family reality (handle gently)
If the family is mixed-faith or unsure about local expectations, appoint a quiet liaison to coordinate privately with the mobed/trust so the grieving family aren’t pulled into difficult conversations on the day.
Links for the separate admin track (kept separate)
If documentation or official steps are affecting timing, keep that track separate and use What to do after a death, Legal, and Government services.
Sensitive social dynamics (handle privately — protect the family)
Back to topSome issues (eligibility, access, family dynamics, community status, personal history) can become emotionally charged. The planning rule is simple: handle sensitive matters privately so mourners are not exposed to conflict.
- No debate in guest groups: if someone disputes access/eligibility/rules, route to the private liaison.
- One private liaison: [Name] speaks to the trust/committee/mobed; others do not engage.
- Guest-safe line: “Details are being handled privately. Please follow the family’s plan and ushers.”
- Women in the family: confirm expectations early so they aren’t surprised or pressured on the day.
Why this matters
The day-of goal is dignity and calm. Private handling protects the family from “public negotiation” while grieving.
Low-resource venue realities (no seating/PA/AC, street overflow, drainage hazards)
Back to topNot all community halls or prayer spaces have strong infrastructure. Plan for a dignified ceremony even if there is no PA, limited seating, heat, or crowd spillover.
- No-PA plan: keep instructions “whisper-level” via ushers; avoid long spoken announcements.
- Seating triage: reserve chairs for elders and those who need them; everyone else stands quietly.
- Heat plan: water point at arrival + ORS packets + shade/umbrella; assign 1 helper to watch for faintness.
- Street overflow: keep one clear central path; place 1–2 ushers outside to reduce crowding at the entrance.
- Safety watcher: if there are open drains/uneven footing, assign one person to guide elders and children.
- No-tech signage: a paper sign at the gate: “Prayers inside → Please keep phones silent → Follow ushers”.
Copy/paste low-resource note (optional)
Low-resource venue note: seating/PA/AC may be limited. Please be prepared to stand quietly, keep pathways clear, and follow ushers. Water will be available at [Spot].
Parking & elder drop-off (India pain point — plan it once)
Back to topParking and drop-off are where crowds and tempers spike. A simple micro-plan prevents gate blocking and keeps elders safe.
- Choose one elder drop-off point: [Spot] with one helper guiding arrivals.
- Parking lead: one person points cars away from the gate and keeps a corridor clear.
- No-block rule: keep the gate/entrance clear (ambulance logic).
- Overflow: if the street is tight, direct cars to park 3–5 minutes away and walk in.
Copy/paste parking note (optional)
Parking note: please avoid blocking the gate. If possible, do a quick drop-off for elders at [Drop-off spot], then park at [Area]. If you’re unsure, go to the meeting point and ask the usher.
Guest flow (arrivals, queues, exits — the ‘calm engineering’ layer)
Back to top- Publish Gate/Entrance + Landmark + Meeting point (repeat it in every update).
- Create two waves: helpers early, guests 15–20 minutes before.
- Use ushers to keep a clear central path for elders and ceremony movement.
- Do condolences in small waves after prayers, not as a crushing line.
- If there is movement to a second location, use the convoy-proof transport rule (no following cars).
- Safety reality: watch for open drains/uneven footing near entrances, especially in monsoon.
India navigation reality
Don’t rely on “nearby” or map pin names. Gate + landmark + meeting point prevents dozens of calls to the family.
Links for the separate admin track (kept separate)
If documentation or official steps are affecting timing, keep that track separate and use What to do after a death, Legal, and Government services.
Arriving mid-prayer (guest guidance — reduces anxiety)
Back to topGuests often worry about disrupting the prayers. A simple instruction helps everyone move respectfully.
- If you arrive mid-prayer, join quietly at the back/side and wait for a natural pause before moving.
- Keep phones silent and avoid walking across the prayer space.
- If you’re unsure, follow ushers’ cues or ask the quiet guide after the prayer moment.
Copy/paste arrive-mid-prayer note (optional)
If you arrive during prayers, please join quietly at the back/side and wait for a natural pause before moving closer. Thank you for helping keep the moment peaceful.
Women’s roles & children present (plan ahead, reduce stress)
Back to top- Women’s participation varies: some settings may have informal expectations about seating, speaking, or where family members stand. Confirm privately with the mobed/committee so women in the family aren’t surprised.
- If women in the family want to participate actively, appoint a liaison to confirm what’s appropriate in your setting.
- Designate a quiet space for children/overwhelmed guests and assign a calm helper.
- Keep a small kit: water, tissues, and 2 chairs for elders/anyone feeling faint.
Copy/paste kids note (optional)
Children are welcome. If a child becomes distressed, please step with them to the quiet space at [Spot]. [Name] will help.
Quiet confirmation line (protects women from last-minute surprises)
“We want to confirm women’s seating/participation expectations for this venue so we can plan calmly—what should we expect today?”
Non-Zoroastrian guests (quiet guide script — mixed-faith friendly)
Back to topMany non-Parsi colleagues and friends attend. The best guest experience is a quiet guide who can explain in one or two sentences, without turning the moment into a lesson.
- Assign one quiet guide (not the closest mourners) to answer quick questions.
- Use simple cues: follow the mobed, keep phones silent, avoid walking around during prayers.
- Normalize observation: people do not need to “perform” participation to be respectful.
Copy/paste quiet guide script
Quiet guide (1–2 sentences): “We’ll follow the mobed’s cues. We may stand for parts of the prayers and sit for parts—just follow the people around you. It’s perfectly fine to observe quietly.” If you want a quick explanation, ask [Name] (quiet guide).
Copy/paste quick help line
If you’re unsure what’s happening at any point, please observe quietly and follow ushers’ cues. If you’d like a quick explanation, ask [Name] (quiet guide) and they’ll explain in 1–2 sentences.
VIP/political arrivals (keep dignity, no disruption)
Back to topSometimes public figures, employers, or community leaders arrive. The goal is dignity: no disruption, no crowding, and no additional stress on the family.
- Assign a VIP boundary liaison to greet/seat them quietly (not the closest mourners).
- Keep VIP greetings outside the prayer space where possible; no handshake lines during prayers.
- No photos/selfies/requests during prayers. If photos are allowed at all, do them after in a designated spot.
- If media presence is possible, use the media boundary rule and keep cameras away from mourners.
Copy/paste VIP boundary note (optional)
VIP arrivals note: if any VIP/public figure arrives, ushers will guide them quietly. No interruptions, no crowding, and no photo requests during prayers. Please keep focus on the family.
Guest etiquette (mixed-faith friendly, tradition-safe)
Back to top- Dress: simple, respectful; many wear white (local custom varies).
- Phones silent; avoid walking around during prayers.
- Follow ushers/committee guidance for where to stand/sit.
- If you’re unfamiliar: observe quietly—no need to “perform” participation.
- If you arrive during prayers, join quietly at the back/side and wait for a natural pause before moving closer.
- Condolences: keep it gentle; avoid crowding immediate family.
- If the venue is low-resource, be prepared to stand quietly and keep pathways clear for elders and movement.
Photos/video boundaries (set it once, clearly)
Back to top- Choose one rule: no photos, outside-only, or one designated operator.
- If relatives abroad need footage, keep it to one designated person.
- If the venue is crowded, “no filming” protects dignity and reduces conflict.
- If VIPs/media are possible, enforce the boundary early (before prayers begin).
No-photos message (copy/paste)
We kindly ask guests not to take photos or record during prayers/ceremony. Thank you for keeping the moment peaceful.
Designated recording message (copy/paste)
One designated person will record briefly for relatives who cannot attend. We kindly ask guests not to record or share footage.
Gentle enforcement line (for the flow keeper)
Kindly please keep phones away—this is the family’s request. Thank you.
Accessibility & comfort planning (quietly essential)
Back to top- Create an “elder station”: two chairs, water, shade/umbrella, and one helper.
- Water available immediately on arrival (not “later”).
- Choose a step-out point near an exit: “If you need air, meet at [point].”
- Monsoon footing: surfaces can be slippery; keep elders supported.
- If the venue is low-resource, keep a no-tech plan: ushers + paper signage + minimal spoken instructions.
Links for the separate admin track (kept separate)
If documentation or official steps are affecting timing, keep that track separate and use What to do after a death, Legal, and Government services.
Intercity & NRI travel reality (reduce stress, protect the family)
Back to top- Add a supportive option: “If you can’t make the main prayers, please join us at the after-gathering.”
- Keep updates in one thread; ask guests not to call close family for checks.
- Name a travel coordinator for arrivals, delays, and basic guidance.
- Normalize constraints: travel/work/visas are difficult—support in any form is appreciated.
- If there is a second location, remind travellers: do not follow the convoy—use the meeting point.
Copy/paste add-on for travellers
If you’re travelling and may arrive late, please message [Name] (travel coordination). If you can’t make the main prayers, you are welcome to join us at [After-gathering location/time]. Please don’t feel pressure—travel is difficult and your support is appreciated.
If timings change (WhatsApp ops that keep everyone calm)
Back to top- Pin one message: latest confirmed timing + gate/landmark + live location + meeting point.
- One person posts logistics: everyone else avoids “helpful” updates.
- Forward-control rule: “Ignore forwarded messages—check this thread.”
- Two-thread discipline: logistics only in the official thread; family-only coordination elsewhere.
- Second location hold: do not publish until fully confirmed; use convoy-proof rule.
Copy/paste pinned summary (recommended)
📌 PINNED (Official plan) Today’s plan (confirmed): • Main prayers: [Time] at [Place] • Gate + Landmark: [Gate / Near ___] • Meeting point: [Where to stand] 📍Live location: [Link] Second location (ONLY if confirmed): • [Place] at ~[Time] • Gate + Landmark: [Gate / Near ___] 📍Live location: [Link] Next update: [Time] (even if no change).
Copy/paste ops discipline (recommended)
Ops discipline (please read): • This is the ONLY official logistics thread. • Please ignore forwarded messages with different timing/location details. • Use Gate + Landmark + Meeting point (not map pin names). • Family-only coordination stays in a separate family thread. If you’re unsure, check the latest pinned update from [Name].
Copy/paste timing-change update
Update: timings have changed due to venue/traffic/queue conditions. Please follow only the latest message from [Name]. New timing: [Time] Gate/Landmark: [Gate + Landmark] 📍Live location: [Link] Meeting point: [Where to stand] Thank you for your patience.
Copy/paste forward-control rule
Please rely only on updates posted by [Name] in this thread. If you receive a forwarded message with different timing/location details, please ignore it and check this thread. India navigation note: use Gate + Landmark + Meeting point (not map pin names).
Copy/paste two-thread rule
Operations rule: 1) This thread is the ONLY official logistics thread. 2) Family-only coordination stays in a separate family thread. Please don’t repost logistics in other groups—check here for the latest update.
Copy/paste second-location hold
Second-location note: we will NOT publish the second location until it is fully confirmed by mobed/trust/venue. If you hear a different second-location plan elsewhere, ignore it and check this thread.
Copy/paste convoy-proof rule
Convoy-proof transport rule: • Do NOT follow another car based on assumption. • Every guest uses the same Gate + Landmark + Live location + Meeting point. • If you get separated, go directly to the meeting point (do not call the family).
Links for the separate admin track (kept separate)
If documentation or official steps are affecting timing, keep that track separate and use What to do after a death, Legal, and Government services.
After the ceremony (hosting, support) — planning context
Back to topMany families host a simple gathering after the prayers. Keep it calm, protect the family’s space, and avoid money discussions in front of mourners.
- Choose a calm venue: home, community hall, or a simple restaurant/hall.
- Keep it simple: water/tea/light food + seating + quiet space.
- Guide condolences into small waves; avoid crushing lines.
- If multiple languages are present, assign a quiet guide for 1–2 sentence explanations.
- If the venue is low-resource, prioritize shade + water + seating for elders over décor.
Quiet money-handling boundary (prevents friction)
If any hosting/help costs come up on the day, please message [Name] privately. We’ll handle it quietly—no discussions in front of mourners.
Links for the separate admin track (kept separate)
If documentation or official steps are affecting timing, keep that track separate and use What to do after a death, Legal, and Government services.
Run-sheets (copy/paste, version-controlled)
Back to topPaste this into WhatsApp (or Notes) and update line-by-line.
Day-of run sheet (template)
Decision owner (today): [Name/Role]
Updates by: [Name]
Official logistics thread: [WhatsApp group name/link]
Family-only coordination thread: [WhatsApp group name]
Mobed: [Name + contact]
Trust/committee: [Name + contact]
Main location: [Home/hall] • Time: [Time]
Gate/entrance: [Gate + landmark]
📍Live location: [Link]
Meeting point: [Spot]
Second location (ONLY if confirmed): [Place + time + gate + landmark + link]
Convoy-proof rule: use meeting point; do not follow other cars
Elder station: [Who + where]
Water point: [Where]
Elder drop-off: [Spot] • Helper: [Name]
Parking lead: [Name]
Kids quiet space: [Spot] • Helper: [Name]
Quiet guide (non-Zoro guests): [Name]
Safety watcher (drains/footing/edges): [Name]
VIP boundary liaison (if needed): [Name]
Media boundary: [No photos / Designated]
After-gathering (if any): [Place + time]
Next update at: [Time] (even if no change)
Links for the separate admin track (kept separate)
If documentation or official steps are affecting timing, keep that track separate and use What to do after a death, Legal, and Government services.
Copy/paste WhatsApp templates (India-ready)
Back to topMain message (copy/paste)
We will be holding the Parsi (Zoroastrian) funeral prayers for [Name] on [Date]. Main location: • Place: [Home / Prayer hall / Community venue] • Time: [Time] • Gate/Entrance: [Gate] • Landmark: [Near ___] 📍Live location: [Link] Meeting point: [Where to stand] If there is a second location afterward (ONLY if confirmed by mobed/trust): • Place: [Location] • Approx time: [Time] • Gate/Entrance: [Gate] • Landmark: [Near ___] 📍Live location: [Link] Meeting point: [Where to stand] Please arrive 15–20 minutes early due to traffic/queues. Updates will be posted in this thread by [Name]. Kindly keep phones on silent and follow ushers/committee guidance.
Pinned summary (copy/paste)
📌 PINNED (Official plan) Today’s plan (confirmed): • Main prayers: [Time] at [Place] • Gate + Landmark: [Gate / Near ___] • Meeting point: [Where to stand] 📍Live location: [Link] Second location (ONLY if confirmed): • [Place] at ~[Time] • Gate + Landmark: [Gate / Near ___] 📍Live location: [Link] Next update: [Time] (even if no change).
Ops discipline (recommended — copy/paste)
Ops discipline (please read): • This is the ONLY official logistics thread. • Please ignore forwarded messages with different timing/location details. • Use Gate + Landmark + Meeting point (not map pin names). • Family-only coordination stays in a separate family thread. If you’re unsure, check the latest pinned update from [Name].
Forward-control rule (copy/paste)
Please rely only on updates posted by [Name] in this thread. If you receive a forwarded message with different timing/location details, please ignore it and check this thread. India navigation note: use Gate + Landmark + Meeting point (not map pin names).
Timing uncertainty note (copy/paste)
Timing note: if hospital release/transfer timing is uncertain, we will post updates in real time in this thread. Please rely only on the latest pinned update from [Name]. We will confirm start time once [mobed/trust guidance + arrival timing] are confirmed.
Status cadence (copy/paste)
Update cadence: we will post the next update at [Time]. If there is no change, we will still message “No change” so you are not left guessing.
Second-location hold (copy/paste)
Second-location note: we will NOT publish the second location until it is fully confirmed by mobed/trust/venue. If you hear a different second-location plan elsewhere, ignore it and check this thread.
Convoy-proof transport rule (copy/paste)
Convoy-proof transport rule: • Do NOT follow another car based on assumption. • Every guest uses the same Gate + Landmark + Live location + Meeting point. • If you get separated, go directly to the meeting point (do not call the family).
Two-thread rule (copy/paste)
Operations rule: 1) This thread is the ONLY official logistics thread. 2) Family-only coordination stays in a separate family thread. Please don’t repost logistics in other groups—check here for the latest update.
For travellers / late arrivals (copy/paste)
If you’re travelling and may arrive late, please message [Name] (travel coordination). If you can’t make the main prayers, you are welcome to join us at [After-gathering location/time]. Please don’t feel pressure—travel is difficult and your support is appreciated.
Non-Zoro guest ‘quiet guide’ script (copy/paste)
Quiet guide (1–2 sentences): “We’ll follow the mobed’s cues. We may stand for parts of the prayers and sit for parts—just follow the people around you. It’s perfectly fine to observe quietly.” If you want a quick explanation, ask [Name] (quiet guide).
Mixed-faith quick help note (copy/paste)
If you’re unsure what’s happening at any point, please observe quietly and follow ushers’ cues. If you’d like a quick explanation, ask [Name] (quiet guide) and they’ll explain in 1–2 sentences.
Arrive mid-prayer note (copy/paste)
If you arrive during prayers, please join quietly at the back/side and wait for a natural pause before moving closer. Thank you for helping keep the moment peaceful.
Parking note (copy/paste)
Parking note: please avoid blocking the gate. If possible, do a quick drop-off for elders at [Drop-off spot], then park at [Area]. If you’re unsure, go to the meeting point and ask the usher.
Kids note (copy/paste)
Children are welcome. If a child becomes distressed, please step with them to the quiet space at [Spot]. [Name] will help.
Low-resource venue note (copy/paste)
Low-resource venue note: seating/PA/AC may be limited. Please be prepared to stand quietly, keep pathways clear, and follow ushers. Water will be available at [Spot].
VIP boundary note (copy/paste)
VIP arrivals note: if any VIP/public figure arrives, ushers will guide them quietly. No interruptions, no crowding, and no photo requests during prayers. Please keep focus on the family.
Costs boundary (copy/paste)
If any hosting/help costs come up on the day, please message [Name] privately. We’ll handle it quietly—no discussions in front of mourners.
Media boundary — no photos (copy/paste)
We kindly ask guests not to take photos or record during prayers/ceremony. Thank you for keeping the moment peaceful.
Media boundary — designated recording (copy/paste)
One designated person will record briefly for relatives who cannot attend. We kindly ask guests not to record or share footage.
Media enforcement line (copy/paste)
Kindly please keep phones away—this is the family’s request. Thank you.
Timing change update (copy/paste)
Update: timings have changed due to venue/traffic/queue conditions. Please follow only the latest message from [Name]. New timing: [Time] Gate/Landmark: [Gate + Landmark] 📍Live location: [Link] Meeting point: [Where to stand] Thank you for your patience.
Links for the separate admin track (kept separate)
If documentation or official steps are affecting timing, keep that track separate and use What to do after a death, Legal, and Government services.
What this page does not cover
Back to top- Registration, certificates, permits, or paperwork
- Police/medical formalities or administrative processes
- Probate, inheritance, benefits, or legal rights
- Government services