GatherKin reunion planning hub

Multilingual Family Reunion Communication Plan

Quick answer: Maintain one approved message, assign a reviewer for each needed language, and distribute equivalent practical details rather than assuming automatic translation is sufficient.

Start a reunion page free

Language access starts by asking families what they prefer. Do not infer a language from a surname, country of birth, or family branch. This is a manual communication workflow, not a claim that GatherKin automatically translates event pages or provides professional interpretation.

Ask about format as well as language

Some relatives may prefer a short call, a printed schedule, a translated message, or plain-language text in the main event language. Ask privately and allow more than one answer. Identify a willing reviewer who understands the event context. Do not assign a child responsibility for translating private payment matters or sensitive family discussions. Agree with adult helpers on the limits of their role.

Copy this translation control sheet

Example message version log
MessageVersionReviewerChecked details
Arrival instructionsNov 13, revision 2Language reviewerDate, entrance, time zone, link
Location changeRevision 3Second readerOld location replaced everywhere

Keep names and addresses in their agreed forms. Check that translated instructions still refer to the actual signs guests will see at the venue.

Write a master message that translates well

Use short sentences, full dates, explicit time zones, and one action per paragraph. Avoid idioms such as "swing by whenever" when there is a real arrival deadline. Write "Saturday, June 12, at 4:00 p.m. Central Time" rather than relying on an ambiguous numeric date. Ask the reviewer to explain the intended action back to the coordinator before sending. Use the welcome-packet checklist to include a non-digital alternative.

Update every version together

When the room changes, revise the master, notify reviewers, and mark previous copies superseded. Record who sent each version and when. Never send one language group an older deadline because its translation was completed first. GatherKin's email reminder workflow can support confirmed organizer communication on eligible plans, but translation quality and distribution to the right households remain the committee's responsibility. Keep sensitive needs out of broad recipient lists.

Frequently asked questions

Can we use machine translation?

It can help draft routine text, but a competent human should check names, dates, instructions, and culturally sensitive wording before distribution.

Must everyone receive the same language version?

No. Ask preferences and provide equivalent information through appropriate formats rather than forcing one language on every household.