How the Time Zone Bedtime Adjuster works
This tool builds a day-by-day pre-trip bedtime shift schedule to reduce jet lag on arrival. The core insight is that kid sleep cycles can only shift by a limited amount per day without breaking โ toddlers can handle 15 minutes, preschoolers 20, school-age 30, teens 45. The tool computes how much total shift you need for your destination's time zone difference and direction, then splits it into daily increments that fit within your kid's tolerance, over the days you have before departure.
If you have enough runway (usually 5+ days for a 3-hour shift with a preschooler), the schedule can fully close the gap before you leave. If not, the tool shows a partial shift and warns that arrival days will be harder. Either way, the specific schedule is more useful than a generic "start prepping a week early" โ it tells you exactly what target bedtime each night from today through departure.
Use it alongside light exposure. The schedule handles bedtime; you separately need morning light exposure at the destination time zone once you arrive to reinforce the shift. The FAQ covers the light + naps + melatonin combination.
What each input and output means
How the direction input (east or west) affects the shift
East means the destination is ahead of you โ you need to move bedtime EARLIER each night to sync with the future time zone. West means the destination is behind โ bedtime moves LATER. East shifts are harder biologically than west shifts (moving bedtime earlier fights the circadian rhythm). The tool applies a slight speed penalty for east shifts, meaning east trips often need more days of prep for the same hours of shift.
How the time-zone hours input drives the total shift needed
The absolute time-zone difference in hours. East coast to Hawaii is 5 hours west. East coast to London is 5 hours east. Denver to Tokyo is 15 hours (but the tool wraps to the shortest direction โ 9 hours west is faster than 15 hours east). Range: 1-12 hours. Under 2 hours barely needs a schedule; over 8 hours is essentially impossible to fully close in a pre-trip window and the tool will show a partial shift.
How the days-until-trip input calibrates the schedule
Number of days from today until you fly. This is your runway. More days = smaller daily shifts, easier on kids. Fewer days = larger daily shifts capped at the age-appropriate maximum. If runway * age-max < total shift needed, the schedule shows a partial shift and warns that arrival days will be rough. Range: 1-30 days. Anything more than 14 days is diminishing returns โ kids' internal clocks don't 'bank' progress that early.
How the age band input caps the daily shift
Toddlers: 15 minutes per day max. Preschoolers: 20 minutes. School-age: 30 minutes. Teens: 45 minutes. Push harder than these and the kid stays overtired, resists bedtime, and undoes the shift. The tool respects these caps and won't schedule aggressive shifts that would backfire.
How the current bedtime input anchors the schedule
Your kid's normal home bedtime in 24-hour format (e.g. '19:30' for 7:30 PM). The schedule starts from this bedtime and shifts by the daily increment toward the destination-adjusted bedtime. If your kid doesn't have a consistent bedtime, set one for the two weeks leading up to the trip โ the schedule needs a baseline.
How the destination input customizes hotel recommendations
Optional. Lets the tool show family hotels at your destination on the result page, along with the schedule. Purely for convenience โ doesn't affect the sleep math. Leave blank if you don't want the hotel recommendations.
What the day-by-day schedule output means
One row per day from today through departure, showing target bedtime, cumulative shift so far, and any notes (like 'schedule fully closed the gap' or 'this is the max you'll close before travel'). Use it as a daily reference โ set an alarm at target bedtime each night. The final row shows the last bedtime before you fly.
What the achieved-vs-needed output tells you
Total shift needed (based on time zones), total shift achieved (based on runway and age cap), and shortfall (if any). Zero shortfall means the schedule fully closes the gap โ you should arrive largely adjusted. A shortfall means you'll have some jet lag on arrival; the tool suggests low-key first 2-3 days at destination to let the remaining adjustment happen naturally.
Honest limitations of this adjuster
This tool assumes typical kid sleep patterns and can't account for kids with atypical sleep needs (twice-a-day nappers past 18 months, kids on ADHD medication with known sleep effects, kids with sleep disorders). If your kid's sleep is nonstandard, talk to your pediatrician before running any structured shift.
It doesn't factor in daylight saving time transitions. If your trip crosses a DST change (either at home or at destination), the actual time-zone math shifts. The tool computes based on the current offset; you may need to adjust manually if DST happens between planning and departure.
The tool assumes you can control bedtime environmental factors: quiet room, darkness, no screens. Kids in shared rooms with older siblings, kids on medications that affect sleep, or families in noisy summer environments will have a harder time hitting the target bedtimes even with the schedule.
Finally: the tool can't handle shifts larger than about 8 hours in any reasonable pre-trip window. For truly global trips (US to Asia, US to Africa) with young kids, plan on the first 3-4 days at destination being a wash regardless of pre-trip prep. Book relaxed activities for those days, not big theme-park visits.