Treat the invitation picture and the calendar event as two separate deliverables. The picture communicates the occasion; an ICS file carries event data that calendar software can import. Both must agree on the actual start time, end time, location and revision. An attractive date rendered inside an image does not create a usable calendar event.
Establish the event's time zone first
Ask the organizer which location or timezone defines the event. For an online occasion, choose a clear reference timezone and show it in the invitation text. Do not let the designer's computer timezone silently become the event timezone.
The iCalendar specification distinguishes UTC times, timezone-referenced times and floating local times. A floating time can be appropriate for some purposes, but it is a poor accidental choice for a simultaneous event attended from several regions. Use an external calendar tool that represents the intended timezone correctly instead of guessing at an offset.
Export the event, not an unrelated private calendar
Create and review the specific event in an external calendar application. Export or download the intended event where that application's workflow allows it. Check the contents before distributing the file; an export of an entire personal calendar can contain unrelated entries.
Keep the title concise and put essential joining instructions in a readable description. If the event requires a separate access link, confirm that the link works for the intended audience. Do not assume that importing an event automatically grants access to a private meeting.
Worked example: an invented online screening
This fictional screening begins at 18:00 in Asia/Shanghai and lasts one hour. The organizer confirms the corresponding 10:00 UTC start as a reference. The invitation says the reference timezone explicitly, and the event file is created with a coherent timezone representation.
Two reviewers import the file into test calendars set to different timezones. They check that each calendar displays the correct local equivalent and the same one-hour duration. If both see 18:00 regardless of timezone, they investigate whether the file used a floating time. The example illustrates a diagnostic; it is not a report of an actual generated event.
Do not promise synchronization or RSVP from an import
Google Calendar's import guidance supports ICS import on a computer and states that imported events do not stay synchronized. It also notes that guest and conference data are not imported. A static calendar file therefore should not be advertised as a complete live invitation system.
If the event changes, revise the visible invitation and the event data together. Explain the revision to recipients and test the target application's behavior; do not assume reimporting a replacement will update every existing copy rather than create a duplicate.
Check the final download path
Open the public or recipient-specific calendar link in the same way a guest will. Confirm that it downloads an ICS file rather than an HTML login page, then import that downloaded file into the intended calendar environment. Verify title, local start, duration, location and joining instructions.
Create the invitation art through Image Prompt, and add accurate event text externally. Deliver the image and tested event file with a timezone note. The finished invitation should support both visual reading and a verified calendar action without pretending those are the same feature.