Feedback on Jet Lag Advisor – Incorrect Guidance for Eastward Travel

Dear Garmin Support,

I have been trialling the Jet Lag Advisor feature in my Garmin device while preparing for a long-haul trip (Melbourne → Paris, via a brief transfer in Dubai).

The tool has been advising me to delay morning light exposure and push my schedule later in the days leading up to travel. However, this is contrary to established circadian science for eastward travel.

  • For an eastward trip crossing ~8–9 time zones (Melbourne → Paris), the evidence-based approach is to advance the body clock — that means encouraging earlier sleep, using evening melatonin at destination bedtime, and seeking morning light in the new time zone.
  • Delaying light exposure (as advised by Jet Lag Advisor) would push my clock later, which is appropriate for westward travel (e.g. Paris → Melbourne) but actually worsens misalignment for eastward travel.

I believe the Jet Lag Advisor may be misapplying the “delay” strategy regardless of direction, or is presenting generic advice not tuned to the actual time-zone shift.

Could you clarify whether the algorithm distinguishes between eastward vs westward travel, and whether updates are planned to align the advice with sleep medicine best practice (e.g. guidelines from the American Academy of Sleep Medicine)?

I enjoy using Garmin products and appreciate the inclusion of circadian coaching, but at present the advice given appears to be misleading and potentially counterproductive for travellers going east.

Kind regards,

AR

  • I’m writing to correct a concern I raised about the Jet Lag Advisor.

    For my trip from Melbourne to Paris (arriving 8:00 PM local time on 6 Sept), your Advisor recommended delaying morning light and shifting bedtime later. That guidance is correct for an eastbound evening arrival.

    The confusion came from advice I received through ChatGPT. It gave me a plan that shifts the body clock earlier — a method better suited to morning arrivals. I didn’t notice that it hadn’t mapped its plan to my specific circumstances, and I wrongly assumed Garmin was contradicting best practice.

    To be clear: the mistake was ChatGPT’s (and my acceptance of it), not Garmin’s. I apologise for misattributing the error and for any unnecessary support effort this caused.

    Thank you for your excellent tools and for helping travellers manage jet lag effectively.

    Kind regards,

    AR