1 00:00:00,080 --> 00:00:03,841 Imagine a fictional handoff on Thursday, January twenty first, twenty 2 00:00:03,841 --> 00:00:07,601 twenty seven, at eleven in the morning in New York. 3 00:00:07,601 --> 00:00:11,738 That same half hour is eight in the morning in Los 4 00:00:11,738 --> 00:00:13,618 Angeles and sixteen hundred UTC. 5 00:00:13,618 --> 00:00:17,755 Our goal is to create one correctly timed practice event and 6 00:00:17,755 --> 00:00:20,763 verify the instant before anyone receives an invitation. 7 00:00:21,363 --> 00:00:25,251 January twenty first is in standard time for these two United 8 00:00:25,251 --> 00:00:29,139 States cities: New York is UTC minus five and Los Angeles 9 00:00:29,139 --> 00:00:30,552 is UTC minus eight. 10 00:00:30,552 --> 00:00:33,733 The difference is three hours for this particular date. 11 00:00:33,733 --> 00:00:37,621 Do not memorize the letters E S T or P S 12 00:00:37,621 --> 00:00:42,569 T as a year-round rule; daylight saving changes the offset in other months. 13 00:00:43,169 --> 00:00:47,674 In Google Calendar on a desktop browser, choose Create, Event, then More options. 14 00:00:47,674 --> 00:00:51,833 Beside the event time, select Time zone and search for New York. 15 00:00:51,833 --> 00:00:55,646 Our saved private event editor shows eleven in the morning in 16 00:00:55,646 --> 00:00:57,379 New York, with no guests. 17 00:00:57,379 --> 00:01:01,538 The generic offset label may reflect today's offset rather than the 18 00:01:01,538 --> 00:01:05,697 event date, so verify the saved clock time against the meeting date. 19 00:01:06,297 --> 00:01:09,428 Name the practice event Workshop handoff, fictional practice. 20 00:01:09,428 --> 00:01:13,733 Set Thursday, January twenty first, twenty twenty seven, from eleven to 21 00:01:13,733 --> 00:01:16,864 eleven thirty in the New York time zone. 22 00:01:16,864 --> 00:01:22,343 Leave the guest field empty and save it only to your own disposable calendar. 23 00:01:22,343 --> 00:01:27,822 This makes the test reversible and avoids emailing anyone while we verify the time. 24 00:01:28,422 --> 00:01:32,642 Open the saved event and confirm its date, time, and selected zone. 25 00:01:32,642 --> 00:01:36,511 In our private test, the editor retained eleven in the morning 26 00:01:36,511 --> 00:01:40,731 in New York, while our Prague calendar displayed five in the afternoon. 27 00:01:40,731 --> 00:01:43,545 Both represent sixteen hundred UTC on this date. 28 00:01:43,545 --> 00:01:47,765 Google's Calendar settings can show Los Angeles as an additional zone; 29 00:01:47,765 --> 00:01:50,579 its expected start is eight in the morning. 30 00:01:50,579 --> 00:01:53,041 We did not inspect a recipient account. 31 00:01:53,641 --> 00:01:57,329 If your primary calendar happens to show Los Angeles time and 32 00:01:57,329 --> 00:02:01,017 you enter eleven without selecting New York for the event, you 33 00:02:01,017 --> 00:02:03,364 may schedule three hours later than intended. 34 00:02:03,364 --> 00:02:07,722 A display change is not the same as changing the event's instant. 35 00:02:07,722 --> 00:02:13,087 Check the event editor's time-zone setting, not just the clock on the calendar grid. 36 00:02:13,687 --> 00:02:17,842 The companion dot I C S file encodes the expected start 37 00:02:17,842 --> 00:02:21,620 at sixteen hundred UTC and end at sixteen thirty UTC. 38 00:02:21,620 --> 00:02:26,531 It is an answer fixture, not evidence of a live Google Calendar result. 39 00:02:26,531 --> 00:02:30,686 The brief has the same New York and Los Angeles times. 40 00:02:30,686 --> 00:02:34,842 You can compare the saved practice event with those values before 41 00:02:34,842 --> 00:02:36,353 inviting any real participant. 42 00:02:36,953 --> 00:02:41,579 For a real meeting, check the actual date because time-zone rules 43 00:02:41,579 --> 00:02:44,663 and daylight-saving transitions can change the offset. 44 00:02:44,663 --> 00:02:48,904 Confirm the intended city zone in the saved event and inspect 45 00:02:48,904 --> 00:02:51,988 the clock in another zone before adding guests. 46 00:02:51,988 --> 00:02:56,614 Our private no-guest Calendar test matched the expected UTC instant; no 47 00:02:56,614 --> 00:02:58,542 invited-recipient view was tested.