EST. NEW YORK · COMMUNITY · STORIES

Articles on community programs, technology, and travel — gathered under one roof.

Warm sandy-brown textured background with subtle highlights and shadows, conveying an earthy, archival mood.
Home » Welcome

Welcome to Cordnewyork

Cordnewyork is the home page of CORD New York, a community organization based in New York. The site also collects short articles and updates spanning technology, lifestyle, and travel. Use the menu on the left to jump to specific sections, or scroll down for the latest posts.

Within these pages you will find notes on CORD NYC's past events, profiles of the Leadership Advisory Board, and a growing archive of newsroom-style features published under the Cordnewyork byline.


Five Things You'll Find Here

  1. WordPress-powered news and notes from the CORD NYC desk.
  2. An events archive covering community activities in and around New York.
  3. Profiles of the Leadership Advisory Board members who guide the organization.
  4. Reports on the impact of community projects, including food drives and walkathons.
  5. Reader-friendly technology and travel write-ups, refreshed on a rolling basis.

Why Siri Struggles With Recurring Events and Custom Time Zones

Siri can add a single appointment to Apple Calendar with impressive speed, yet recurring events involving a specific time zone expose several weaknesses. A request such as “schedule a fortnightly meeting at 9 am Sydney time in New York time” combines repetition, location, conversion and calendar rules that Siri may not resolve reliably.

The difficulty is rarely one simple bug. Siri must interpret natural language, identify the intended calendar, convert the time correctly, contact Apple’s servers when necessary and translate the result into Calendar’s event fields. If any part of that chain is uncertain, it may create an event in the device’s current zone, omit the recurrence, or ask the user to finish the task manually.

This matters in Australia, where time zones vary across states and daylight saving does not apply uniformly. A person in Melbourne may be using AEDT while a colleague in Brisbane remains on AEST, and a recurring event with overseas participants can shift again when another region changes its clocks.

Recurring Events Are Harder Than One-Off Appointments

A one-time command has a relatively small set of variables: title, date, start time and duration. A recurring event adds frequency, end conditions, exceptions and sometimes a preferred time zone. Siri has to map everyday phrases such as “every second Tuesday” or “the first business day of each month” into Calendar’s structured recurrence settings.

Custom time zones add another layer. Calendar can store events with a zone identifier, but Siri may treat “Tokyo time” or “London time” as conversational context rather than a firm property of the event. The assistant can therefore understand the words while failing to place the correct zone in the saved record.

The problem resembles other Siri parsing limitations, including commands with extra grammatical qualifiers. An analysis of the playlist command issue shows how a short prepositional phrase can alter the intended meaning. Time-zone phrases create a similar risk because their position in a sentence can determine whether they apply to the event, the location or the speaker.

Device Settings Influence The Result

Siri usually relies on the iPhone’s language, region, calendar and time-zone settings. If the phone is set to Australia but the user is travelling in Singapore, the assistant may favour the current device zone, the selected region or the location inferred from the request. These signals do not always agree.

The Calendar app also has its own “time zone override” behaviour, while iCloud calendars can synchronise events across Macs, iPads and iPhones. An event created by voice on an iPhone in Sydney may display differently on a Mac configured for Perth if the event was not saved with a fixed zone. The result can look like a scheduling error even when each device is showing its local interpretation.

Australian daylight saving makes this particularly visible. New South Wales, Victoria, Tasmania and South Australia change clocks seasonally, while Queensland, Western Australia and the Northern Territory generally do not. A weekly event spanning Melbourne and Brisbane can appear to move by an hour unless its intended time zone is clearly stored.

Network Processing Can Change Siri’s Interpretation

Siri performs some basic tasks on the device, but complex language processing and account-based actions may depend on Apple’s servers. Network delay, an unavailable service or a failed connection can interrupt the hand-off between speech recognition and Calendar. In that situation, Siri may respond with a generic confirmation without completing every requested detail.

Server-side processing also helps explain why uncommon names, place names and time-zone labels can be misheard. Research into server-side name handling illustrates how less familiar language can receive weaker recognition scores. A zone such as “Lord Howe Island Time” or a meeting location in regional Australia may be less dependable than a familiar phrase like “Sydney time”.

Request type Likely Siri behaviour Main risk
Single event in the current zone Usually creates the event quickly Minor ambiguity over duration
Weekly event without a named zone Uses device or calendar settings Event shifts when travelling
Recurring event with an overseas zone May ask for clarification or simplify the request Zone may not be saved correctly
Recurring event with exceptions Often requires manual editing Exceptions or end dates can be lost
Event across daylight-saving regions May display different local times One-hour seasonal changes

Clearer Commands Reduce Ambiguity

Users can improve the odds by separating the request into smaller actions. First create the event with its title, date and recurrence. Then open it in Calendar and set the time zone explicitly. This is slower than a single voice command, but it gives the user a visible check before invitations or reminders are sent.

A structured sentence can also help: “Create a recurring event called team briefing, every Monday, at 9 am, in Melbourne time, starting 6 May, ending 30 September.” It is wise to avoid combining travel details, participants, location and multiple reminders in the same request. Siri may prioritise the first recognisable time expression and discard later qualifiers.

For Australians coordinating with the United States or Europe, stating both zones can expose a mismatch early. “Book it for 10 am AEST, which is 8 pm New York time the previous day” gives a clearer reference than “10 am New York time” when the speaker is physically in Canberra. The final event should still be checked in Calendar, especially around March and October when international daylight-saving schedules differ.

Better Integration Could Make Siri More Reliable

A stronger system would show a confirmation card containing the recurrence rule, saved time zone, first three projected occurrences and any daylight-saving changes. Users could then correct one field without repeating the entire command. The same preview would help identify whether “every fortnight” was interpreted as weekly, biweekly or a fixed number of days.

Apple could also expose more Calendar controls to Siri, including explicit IANA-style zones, recurrence end dates and exceptions. Better integration with iCloud would allow the assistant to report whether the event was saved locally, synchronised successfully or left incomplete because of a network problem.

The broader technology market is moving towards assistants that combine on-device recognition with cloud reasoning. Coverage of Android tech developments offers useful context for comparing how competing platforms handle voice commands, device settings and app actions. For Apple users, the goal is not simply a more conversational assistant; it is dependable control over the structured data that Calendar stores.

Checking the finished event remains the safest habit for now. Open the appointment, confirm its recurrence, inspect the displayed time zone and verify the next occurrence after a daylight-saving transition. Australian users should pay particular attention when a calendar includes Sydney, Melbourne, Brisbane, Perth or overseas offices.

For broader coverage of assistant behaviour and technology reliability, explore Cordnewyork’s technology coverage. When a recurring meeting matters, use Siri for the first draft, then make the final time-zone and repetition check directly in Calendar before relying on the notification.


Need a Hand Navigating?

If you are looking for something specific, the left-hand menu leads you to the main sections: About Us, Join Us, Past Events in New York, Impact of CORD, and the CORD NY Leadership page. The Donate page is the place to support the organization financially.


Ask a Question

Use the form below to send a note to the editorial team. We read every message.


What Readers Say

★ ★ ★ ★ ★

The events archive is the easiest way to follow what CORD NYC has been doing over the years. Clean and to the point.

— Recent visitor
★ ★ ★ ★ ☆

I appreciate having the leadership profiles alongside the community news. It keeps the people behind the work visible.

— Site reader
★ ★ ★ ★ ★

The technology and travel write-ups are a nice surprise on a community-focused site.

— Subscriber