Paris

How to publish an event time for an international audience

Make the date, location and intended instant clear wherever your invitation is read.

WhatTimeIsIt Published Updated
Photo

Write the complete primary time

Begin with the event’s date, local start time and named location. “15:00, 11 October 2026, Paris” carries much more information than “3 p.m. European time.” State the end time or duration as well, so attendees can assess the full commitment. A time-zone abbreviation may be added for convenience, but should not be the only geographic information in an announcement.

Show useful conversions without overwhelming readers

Use the converter for the exact event date and include a small number of local equivalents for your audience. If an equivalent lands on another day, display that date beside the hour. Keep the primary time prominent so readers know which schedule defines the event. A long list copied manually is harder to maintain and more likely to contain a stale conversion when details change.

Make every channel agree

Your registration page, confirmation email, calendar invitation and reminder should describe the same instant. Check them together after an edit. A correct website cannot compensate for an outdated invitation attached to an email. If the event is rescheduled, update the shared calendar record and clearly state the changed date or hour. Preserve enough context for attendees to distinguish an actual reschedule from their device merely showing a different local time zone.

Check edge cases before publishing

Review whether the event falls near a seasonal transition or inside a repeated local hour. If it does, clarify the intended UTC offset. Preview the invitation from a region ahead of the organizer and another behind it, particularly for events near midnight. For a series, choose the anchor time zone deliberately. Our recurring-meeting guide explains the consequences, while the clock-change guide covers ambiguous overnight times.

Sources

  1. IETF: RFC 5545 iCalendar
  2. IETF: RFC 3339 timestamps
Back to section · Guides