Platform Time vs Local Time: Build an Event Alert That Survives Clock Changes

Why does an event alert set in local time go wrong when clocks change, and how do you build one that does not?

Short answer: An alert tied to a fixed local time breaks when clocks change, because the event and your own clock do not always change on the same date. Economic releases are scheduled in the publisher's time zone, your phone follows your local zone, and the MetaTrader platform follows the broker's server time, which a trader cannot change. To build an alert that survives clock changes, record the event in its own time zone, convert it each time instead of copying a converted time forward, and review every alert in the week before a clock change.

What are the three clocks you have to manage?

A trader working around scheduled events is dealing with three clocks at once, and they do not always move together.

Local time is the clock on your phone, computer and wall. It follows your country's rules, including daylight saving time (DST) where it applies. Platform time, also called server time, is the time shown on MT4 and MT5 charts and quotes. It is set by the broker's trading server, and the trader cannot change it. Event time is when a data release, central bank decision or market opening is scheduled, normally stated in the time zone of the organisation publishing it, such as New York or London.

Event time stays fixed in its own zone but drifts against the other two whenever regions change their clocks on different dates. The guide to commodity market hours already shows how exchange schedules published in Eastern, Central or London time move against UTC. This article applies the same principle to the alerts you set for yourself.

Why do clock changes break event alerts?

An alert fails when it is anchored to the wrong clock. Suppose you set a repeating reminder for 15:30 local time because that is when a US data release appeared on your calendar during the summer. The release itself is scheduled for 8:30 a.m. in New York. While New York and your city change their clocks on the same date, 15:30 keeps working. When they do not, the alert is an hour out and the release still arrives on time.

This is not a rare edge case. In 2026, Europe returns to standard time on Sunday 25 October, while the United States does so on Sunday 1 November. For that week, the gap between New York and European time is one hour shorter than usual. The same one-hour difference appears again in spring 2027, when the United States moves its clocks forward on Sunday 14 March and Europe follows on Sunday 28 March. Regions that do not use DST at all follow their own calendars.

Scheduled releases matter because gold and currency pairs can react sharply to them, as explained in How Does XAUUSD Behave Around Macro Events? Missing the right minute by an hour can mean preparing for the wrong moment.

What does the mismatch look like in numbers?

The table uses a US data release scheduled for 8:30 a.m. New York time and a trader in a zone that follows European DST, such as Athens (UTC+3 in summer, UTC+2 in winter). The NordFX server runs on GMT+2 in winter and GMT+3 in summer, moving on the European change dates, so the platform column is calculated on that basis. Release times are illustrative, so confirm the real time in your calendar.

For a trader in Athens, local and platform time move together, so the release appears at 14:30 for one week and returns to 15:30 on 1 November. A fixed 15:30 alert, whether set on the phone or read off the platform, is an hour late in the mismatch week. A trader in a zone without daylight saving sees something different: the platform moves by an hour against local time on the European change dates, while the release moves on the US ones. The reliable habit is to know which clock every number belongs to.

Which clock should an alert be anchored to?

Anchor the alert to the clock that defines the event, not the clock you happen to be looking at, and convert to the others at the moment the alert is created or fires.

Use the zone name, not a fixed offset. A name such as America/New_York carries the daylight-saving rules and knows when they start and end. An offset such as UTC−4 is correct only until the next change.

How do you build an alert that survives clock changes?

1. Record the event time. Write it as published: 8:30 a.m. New York, not only your converted time.
2. Store the original time zone. Calendar apps, spreadsheets and scripts use named zones that carry the rules, so let them do the arithmetic.
3. Convert for each clock change. Let the tool calculate the exact moment for each date instead of copying one converted time forward week after week.
4. Set a lead time. An alert 15 minutes before the release is tied to the instant, so it follows the event wherever the clocks move.
5. Check three times (event, local, platform). Put all three in the alert text, so a mismatch is visible at a glance.
6. Confirm in a reliable calendar. On the day, check the release time in a reliable economic calendar. Publishers can reschedule, and holiday weeks can change timetables.
7. Review before every clock change. Do it one week ahead. For 2026–2027 the dates to check are 25 October 2026 (Europe), 1 November 2026 (US), 14 March 2027 (US) and 28 March 2027 (Europe).

What does a clock-proof alert look like in practice?

In a calendar app, create the event with its own time zone set to New York, add a reminder 15 minutes before, and let the app display it in your local time. In a spreadsheet, keep one column for the published time, one for the zone name, and formula columns that convert to your local time and to platform time using the offset you measured. When a clock change moves the offset, you update a single cell instead of every row. Either way, the published time stays the source of truth, and every other time is calculated from it.

How do you check platform time in MT4 and MT5?

You cannot change platform time, so the practical task is to measure it and write the offset down.

1. Open Market Watch and note the time of the latest quote. Quote and chart time stamps show platform time.
2. At the same moment, check UTC on a reliable time source.
3. Subtract: platform time minus UTC gives the offset, for example GMT+2 or GMT+3.
4. Record the offset and the date, and repeat the check after each clock change.

Changing your computer's clock does not change chart time, because the platform follows the server. On NordFX the server time is GMT+2 in winter and GMT+3 in summer, and clients can use MetaTrader 5 and MetaTrader 4. Check the time stamps on your own account after each change rather than relying on another broker's convention. The platform's built-in Alerts tab also offers a time condition that works from platform time; test it in your terminal and re-test it after clock changes.

What about the hour that is skipped or repeated?

On the night clocks change, a local time can disappear in spring or happen twice in autumn. An alert for 02:30 local may never fire in spring because that time does not exist on that date, and in autumn it may fire once or twice depending on the tool. Clock changes usually happen in the early hours of a Sunday, when forex is closed but crypto CFDs, your personal reminders and any scheduled routine are not. Test alerts that fall between roughly 01:00 and 03:00 local time on change dates, or set them in UTC, which has no gaps.

What mistakes should you avoid?

1. Copying a converted time forward instead of recalculating it.
2. Using a fixed offset instead of a named time zone.
3. Assuming every country changes its clocks on the same date.
4. Assuming platform time matches your broker's website or another broker's server.
5. Forgetting that your phone, calendar and trading platform each keep their own time zone setting.
6. Trusting a recurring alert without checking it after a clock change.
7. Treating the alert as a trading signal. It tells you when something happens, not what to do about it.

Frequently asked questions

Can I change the time shown in MT4 or MT5?

No. Chart and quote time follow the broker's server. You can add your own reminders or indicators in local time, but the platform clock itself stays on server time.

Does platform time change with daylight saving?

Yes, on NordFX. The server runs on GMT+2 in winter and GMT+3 in summer. Other brokers use different rules, so measure the offset of the platform you actually trade on.

Which time zone is best for economic event alerts?

The event's own time zone, or UTC. Both stay correct when your local clock changes. Convert to local time for display only.

Do crypto alerts need clock-change checks?

Yes, if they are set in local time. The market trades continuously, but your alert still depends on the clock it was written against.

What is the safest way to store an event time?

Store the time as published together with its named zone, or store it as a UTC instant. Avoid storing only a converted local time.

How can you plan around scheduled events at NordFX?

Check your platform offset in MT4 or MT5, then build alerts from the event's own time zone. The Market Analysis section helps you follow the themes of the day, while the exact release time should always be confirmed in the calendar or source you trust.

What should you remember?

Know which clock every time belongs to. Anchor event alerts to the event's own zone, show local and platform time beside it, and review alerts the week before each clock change.

Risk warning: CFDs are complex instruments and come with a high risk of losing money rapidly due to leverage. Times and dates in this article are illustrative, and broker server conventions differ. This article is educational and does not constitute financial advice.