Meeting time zone check: resolve a repeated local hour

When is a meeting time still unresolved?

A meeting time zone check is useful when two people agree on a clock reading but have not established a single instant. A remote support handover, supplier call or overnight coaching session can expose the problem. Your deliverable is a short decision record: the original request, any ambiguity, the question that resolves it and the invitation evidence.

A time zone is a location's date-dependent clock rule. UTC is a shared reference clock. An offset states how far the displayed local clock is ahead of or behind UTC at that moment. A city name helps identify the regional rule; a numeric offset helps identify the intended occurrence. Neither should disappear when you rewrite an ambiguous request.

This is not a booking-page setup guide or an instruction to alter a customer's calendar. Use a practice note first. If you need the wider booking workflow, start with the online appointment booking guide. Here the narrower question is whether one proposed appointment identifies one instant.

Consider an explicitly fictional business: a remote agency and its London contractor need an overnight handover. The contractor writes “25 October 2026, 01:30 London.” The date and city look precise. Around a clock change, however, that local reading needs another decision before anyone can safely treat it as a confirmed appointment.

Preserve the request before converting it

Open a blank document. Give the appointment an internal reference such as H-01 and copy the original wording exactly. Keep a separate field for your interpretation. This small separation lets a colleague see whether the customer supplied the information or you added it later.

The duration here is deliberately supplied by the exercise, not inferred from the handover's title. In your own record, leave missing duration blank. Also record whether the appointment is online or in person. A known time does not tell someone where to join.

Use a written month name in the clarification message. Do not add an assumed location from a telephone number, and do not turn an unqualified clock reading into UTC by adding a label. The expected outcome of this step is a faithful source record with an honest list of missing information.

If a colleague can inspect the note and distinguish supplied facts from assumptions without asking you, the capture step is complete. You do not need an AI account, a calendar integration or a new subscription to reach this point.

Separate the two London occurrences

The UK government's clock-change page lists 25 October as the 2026 autumn change. Under the stated rule, clocks move back from 02:00 to 01:00. London therefore experiences the local reading 01:30 twice that morning: once before the change and once after it. Those readings are separated by an hour of elapsed time.

Subtract one hour from the UTC+01:00 reading to obtain its UTC start. Subtract zero from the UTC+00:00 reading. This produces two candidate instants, not two appointments that should both be booked. Arithmetic cannot tell you which one the contractor intended.

The earlier candidate crosses the clock-change boundary during its fictional 45-minute duration. Its local end reading can therefore look earlier than its local start reading. Calculate elapsed duration on the UTC timeline instead of subtracting the two bare local clock numbers. Do not assume the starting offset must remain the ending offset.

This distinction matters operationally: a neat-looking local range can conceal the wrong duration, while a strange-looking range can describe the right one. Keep the source clock, chosen occurrence and elapsed duration together.

The report-day UTC audit answers a different question: which event IDs belong to a reporting day. This check resolves an appointment occurrence. It does not count records within a date boundary.

Ask a question that selects an instant

Write a clarification that exposes both candidates without asking the recipient to learn a technical standard. The message below is a draft for a responsible person to review and send. It is not an automation and it has not been sent to any real contractor.

Please confirm the handover on 25 October 2026. By 01:30 London, do you mean the earlier occurrence at UTC+01:00, which is 00:30 UTC, or the later occurrence at UTC+00:00, which is 01:30 UTC? Please also confirm the 45-minute duration. We will prepare one calendar invitation after your choice.

A reply saying only “yes” does not choose between the alternatives. Ask again if the selection is unclear. A reply naming the earlier occurrence, later occurrence or full UTC start can establish the intended choice. Record who replied and retain the wording rather than summarising it as “sorted.”

If the recipient changes the date instead, start a new candidate check for that date. Do not carry the old offset forward automatically. An alternative away from the clock-change window may be simpler, but still write its full date and location.

Until the answer arrives, the correct status is “awaiting clarification.” Preparing that question is useful progress even if the customer takes a day to respond. The note must not claim that confirmation happened merely because you completed your side of the task.

For later message delivery, the appointment reminder guide covers sending and cancellation checks. A reminder cannot resolve an appointment whose intended instant remains unknown.

Check the saved invitation against the decision

For this English exercise, suppose the contractor selects the earlier occurrence. Write the accepted start as “25 October 2026, 01:30 London, UTC+01:00; 00:30 UTC.” Write the accepted end as 01:15 UTC and the duration as 45 minutes. This answer is fictional.

This additional calendar check is separate from the first fifteen-minute text-file result. With an existing authorized Google account, open calendar.google.com. On a computer, use Create → Create event → More options → Time zone to select the practice event’s regional zone. For a UTC comparison, open Settings → General → Time zone → Show additional time zones and display UTC as an additional zone. This checks the saved instant; it does not promise a separate button selecting a repeated-hour occurrence. Without a reply, working account or clear display, retain “not checked”. Creating an account and obtaining another person’s reply are not promised within fifteen minutes.

Google documents that invitees see events in their own local zones. Outlook also provides settings for displaying additional time zones. Treat the recipient-facing display as something to inspect, not as something your written explanation has already verified. Account versions and interface labels may differ.

1. Save a practice event. Expected result: the requested date and regional zone appear.
2. Inspect its UTC start. Expected result: 00:30 UTC for the selected exercise branch.
3. Inspect the end and duration. Expected result: 01:15 UTC and 45 elapsed minutes.
4. Ask the recipient to read back their displayed date and time. Expected result: both displays refer to the same agreed instant.

If your interface makes the repeated occurrence unclear, leave the check unresolved and obtain help for that application. Do not silently choose whichever result appears first. Do not invite a real customer merely to experiment with an ambiguous setting.

The Calendly scheduling guide is the related setup path for availability and connected calendars. Neither availability nor a successful connection proves this particular invitation selected the right occurrence.

Finish one reusable confirmation record

Copy the following headings into your document. A plain text file is enough. The objective is to make one decision reviewable, not to redesign your entire scheduling system. Keep the unresolved fields visible when the answer or invitation evidence is unavailable.

Meeting reference:
Original date, local time and location:
Missing information:
Candidate UTC starts:
Clarification question:
Reply and respondent:
Accepted start, end and duration:
Saved invitation display checked:
Recipient display checked:
Status: awaiting / mismatch / confirmed

On Windows, search Start for Notepad, open it and create a new blank document. Paste the original request, both candidate UTC starts, clarification question and current reply status. Press Ctrl+S, select Documents, name the file meeting-time-check-V1.txt and choose Save. Close the editor; open Documents in File Explorer and double-click that named file. Verify that the selected earlier occurrence remains 00:30 UTC and the duration remains 45 minutes. If you have not inspected an invitation, retain “not checked”.

A 15-minute work session can finish the source capture, two-candidate table and clarification draft. It cannot guarantee another person's reply within that period. Your useful result is the saved record and the exact question required to continue. Later, add the answer and invitation evidence without rewriting the original request.

In his earlier Perfect versus Effect essay, Anar describes from personal experience how pursuing perfection delayed projects. The limited lesson used here is to complete one inspectable decision record before expanding the system. This is not evidence that Anar tested a time-zone product or achieved a customer scheduling result.

If reminders or integrations eventually become necessary, define the job before adding tools. The Google Sheets workflow guide can help organise a wider process. One unresolved appointment does not itself establish a need for a new platform. A finished note should tell the next person what was requested, what was chosen and what still requires verification.