Tokyo to London, One Business Trip: Three Jet Lag Protocols Compared
A 9-time-zone eastward crossing, one business week, and a test of three different approaches to jet lag management. What worked, what didn't, and what the protocols actually require you to commit to.
In this article8 sections
A 9-time-zone eastward crossing from Tokyo to London produces one of the more brutal jet lag patterns in routine business travel. The circadian clock must advance nearly half a day, and it must do so in the direction the human clock resists most. The flight itself is 12 hours. The productive business window at the destination opens roughly 18 hours after departure.
What follows is a documented test of three different approaches on one trip, with daily outcome tracking across a week in London. The protocols are real; the trip is composed from the pattern of a frequent traveler’s experience over multiple similar crossings. The methodology isn’t clinical. The patterns are consistent enough to be instructive.
The crossing and why it matters
Tokyo (GMT+9) to London (GMT+1) represents an 8-hour time zone difference — effectively 9 hours when accounting for daylight saving time in summer. For eastward travel, the circadian clock must advance its phase by approximately 8 hours. Given the clock’s natural tendency to run slightly longer than 24 hours (most people’s intrinsic period is 24.1–24.2 hours, per Till Roenneberg’s large-scale chronotype research at Ludwig Maximilian University in Munich), advancing phase is the harder direction.
The naive experience without intervention: arrival in London at 7 AM local time, body clock at 3 PM Tokyo time. First London night, the traveler cannot sleep before 2 or 3 AM local time. First London morning, waking is possible only after 10 or 11 AM. Business meetings at 8 or 9 AM are conducted in a state of physiological impairment that is functional enough to hide — but impaired enough to affect judgment.
Three protocols were tested across three comparable crossings:
Protocol A: No intervention (“power through”)
What it involves: Flying through, adjusting to local meal and social schedules immediately upon arrival, using caffeine to manage daytime fatigue, attempting to sleep at local bedtime, and relying on willpower and ambient light to reset.
What actually happened: Arrival day felt moderately manageable — sustained by flight-induced sleep debt and arrival adrenaline. Night one in London: sleep onset at approximately 1:45 AM local time. Wake time: 9:20 AM (alarm bypassed; first alarm dismissed). First meeting at 9 AM: not functional as intended. By day three, sleep was reaching local-adjacent timing. Full subjective normalization took six to seven days.
Assessment: Protocol A works in that it resolves, but it extracts a significant cognitive tax across the first three to four days — precisely the days that typically contain the highest-priority meetings. The subjective confidence that “I’m managing” significantly overestimated actual cognitive performance, based on error rates and recall quality when reviewed afterward.
Protocol B: Light therapy + melatonin (the standard evidence-based protocol)
What it involves: Beginning light exposure management 48 hours before departure (avoiding bright light in the evenings, seeking morning light) and continuing for the first five days at the destination; taking 0.5mg melatonin at the destination bedtime for five nights; using a light therapy lamp (10,000 lux) for 30 minutes between 7 and 9 AM London time from day one.
What actually happened: Arrival day was harder than Protocol A’s arrival day — the light avoidance in the Tokyo evenings meant less social light exposure and felt disorienting. Night one in London: sleep onset at approximately 12:30 AM. Wake time at the 7 AM alarm — with difficulty, but without the 90-minute snooze behavior of Protocol A. By day two, morning alertness was meaningfully better than the equivalent day under Protocol A. Full subjective normalization: day four to five.
Assessment: Protocol B produces roughly two days faster adaptation than Protocol A, with meaningfully better cognitive function in the critical first 48 hours. The cost is real: the protocol requires carrying a light lamp (or using a hotel lamp + app), maintaining discipline about evening light (no bright restaurants, no hotel lobby screens at 10 PM London time), and correctly timing the melatonin. The commitment overhead is higher than most business travelers are willing to sustain.
The melatonin timing detail turned out to be critical. On one day when melatonin was taken at 11 PM instead of 9:30 PM (the target bedtime), the morning grogginess extended significantly. The difference between “at target bedtime” and “two hours after target bedtime” was functionally significant.
Protocol C: Pre-trip phase shifting + light + melatonin
What it involves: Starting 5 days before departure, advancing bedtime by 30–60 minutes per night and wake time correspondingly — a total phase advance of 2.5–3 hours before even boarding the plane. Continuing the light and melatonin protocol from Protocol B during the trip. On arrival, the circadian clock has partially pre-adapted.
What actually happened: The preparation period was the hardest part — rearranging four consecutive evenings in Tokyo around an earlier bedtime (9:30–10 PM for someone accustomed to midnight) required declining social engagements and noticeably affected work patterns in the final pre-departure days. Night one in London: sleep onset at 11:15 PM. Wake at 7 AM without alarm. Functional cognitive performance from day two.
Assessment: Protocol C produced the best outcomes but required the most commitment. The preparation window is the realistic constraint: a business traveler with meetings through the evening of departure day cannot phase-shift. For planned trips with a 5-day preparation window and evening flexibility, Protocol C reduces the adaptation timeline to approximately two days.
What the comparison shows
| Protocol A | Protocol B | Protocol C | |
|---|---|---|---|
| Days to functional cognitive performance | 3–4 | 1–2 | Same day–1 |
| Sleep onset night one | 1:45 AM | 12:30 AM | 11:15 PM |
| Preparation overhead | None | Minimal | Significant |
| Equipment required | Nothing | Light lamp + melatonin | Light lamp + melatonin + schedule restructuring |
| Realistic for most business travelers | Yes | Usually | Rarely |
The pattern that emerges: each step up in protocol sophistication produces roughly a day faster adaptation. The question for any specific trip is whether the cost of the preparation work is worth the day gained. For a five-day conference where day one is orientation and day five is travel home, Protocol B’s gains matter. For a two-day trip where the calendar is dense from the moment of arrival, Protocol C’s preparation is the only thing that makes the trip fully functional.
The limitations the protocols share
All three protocols share one structural limitation that the research doesn’t adequately address: the social and professional environment at the destination doesn’t adapt with you.
Under Protocol B and C, avoiding bright light in London evenings means avoiding evening client dinners in brightly lit restaurants. Taking melatonin at 9:30 PM means leaving cocktail receptions at 9 PM. The circadian management interventions that work biologically are frequently incompatible with the professional social schedules that accompany business travel. The traveler who follows the protocol correctly is the one who goes to bed when colleagues are at the hotel bar.
This is not a reason to abandon the protocols. It is a reason to be realistic about what you can actually implement, and to prioritize the interventions that don’t require social disruption (primarily light management in the morning, rather than melatonin at a specific evening time) over those that do.
A word on destination social schedules as the missing zeitgeber
Till Roenneberg’s work on social jet lag — the circadian disruption from social schedules rather than time zones — is relevant here in an underappreciated way. The jet lag protocols described above all focus on biological adjustment. What accelerates adaptation equally, and is almost never prescribed, is immediate integration into the destination’s social schedule.
Eating at local meal times (not your departure city’s meal equivalents), having social contact at predictable destination hours, and establishing a consistent morning engagement — even a brief walk or coffee at the same local time each day — provides the social zeitgebers that are the second most powerful class of circadian cues after light. The jet lag research tends to focus on light and melatonin because they’re measurable and controllable. The social schedule effects are harder to measure and frequently ignored in formal protocols.
The social zeitgeber explainer covers why these social cues matter so much; the weekend social jet lag post examines what happens when you experience a similar circadian disruption without leaving your city.
On DontSnooze for jet lag
DontSnooze is a social accountability alarm app. Its core mechanism — video-proof wake time commitment to a social audience — has a specific limitation in international travel that’s worth naming directly: it works best when your accountability network is awake at the same time you’re waking up. A Tokyo network isn’t available at 7 AM London time. A London network isn’t yet active when you’re departing Tokyo.
For jet lag specifically, DontSnooze is most useful in the recovery phase — the third or fourth day onward, when the circadian clock is close enough to local time that the morning wake commitment is achievable and the social circuit functions again. As a tool for enforcing Protocol B’s 7 AM local wake time against the resistance of a clock that thinks it’s 3 AM, the social accountability mechanism is genuinely useful. In the first 48 hours of a major time zone crossing, when the biological pull is toward sleeping until noon, external accountability has real value. The limitation is the network timing mismatch; whether that’s prohibitive depends on whether you have connections in or near the destination time zone.
The genuine critique: DontSnooze doesn’t solve the jet lag problem any more than an alarm clock does. What it does is make the morning anchor commitment harder to quietly abandon when you’re sleep-deprived and the commitment cost is low. For that specific function — enforcing consistency when you don’t feel like it — it works for the same reasons it works at home.
For how the circadian clock resets after disruption and the interventions that accelerate that process, see the circadian reset guide. For the melatonin timing details that made the biggest difference between protocols, see melatonin: the three numbers that actually matter.