Serving families across borders with the same calculation

Keep the birth event intact

A natal chart starts with the original birth date, time and place. Moving to another country does not move that event. Store the name of the birth city with its region and country, and check the civil-time rule for the birth date. A time-zone database represents historical rules for local clocks. Today’s offset alone is a poor shortcut for an older record.

For a transit or a local timing question, ask which place is relevant now. The client’s current city may differ from the venue of a family event. If a tool uses a practice location as a fallback, say which place it used before showing the result.

Sources: IANA Time Zone Database

Send a note that can be read in either country

A timing message should identify the event, venue and time zone. For a call, add the converted time in the other location, including the date when it crosses midnight. For an observance, separate a shared participation time from a locally calculated window if both are needed.

Write the venue first on the message. “Toronto ceremony, venue local time” helps a reader decide which line to place on their calendar. A person forwarding the note can preserve the label even when the rest of the discussion is omitted.

Build for the family that asks twice

The planned Panditji desk is for practitioners serving families across borders as well as people in their own towns. A good follow-up question is “Which city does this line refer to?” If the client can answer that from the note, the work has travelled well.