Nanny Agency JobsA travel calendar needs to preserve what each time means. Before entering an itinerary, identify the local date and time at each location. Then keep the journey, childcare coverage and handover as separate entries. A flight appearing on your calendar does not define your working hours.
The method below is an original NAJ workflow for translating an agreed itinerary into readable calendar entries. It assumes the family has already confirmed the travel plan and will resolve any changes to your responsibilities.
Start with the booking, including its dates
Work from the current booking confirmation, not a remembered departure time or a cropped message. Copy the departure airport, departure date, departure time, arrival airport, arrival date and arrival time. Preserve the local-time meaning of each endpoint.
Name the cities or time zones rather than writing only “home time” and “away time.” Those labels become confusing when people view the same calendar from different places. Include the year when preparing a trip far ahead, and retain any overnight arrival indicator from the booking.
If the itinerary has several legs, give each leg its own record. A connection has its own airport and date. Do not fill a missing arrival date by assuming the journey ends on the departure day.
Set the event's zones deliberately
Google Calendar's help documents separate start and end time zones for an event.
Use the linked product instructions to locate those controls. Then work through your own booking one endpoint at a time: departure place and date first, arrival place and date second. Check the saved event against the original before inviting anyone. Our suggested checking order is a practical way to catch transcription errors, not an additional feature of the app.
Other calendars have different controls. Use the instructions for the actual app and account. If you cannot tell whether a field expects local departure time or your current display time, resolve that before saving a guess.
Keep a plain-language itinerary beside the event
Put a short itinerary in the description: “Departure: date, local time, city. Arrival: date, local time, city. Booking checked: date.” This gives another reader something concrete to compare with the calendar display.
Keep booking references and identifying details in the family's agreed private location. A notification title usually needs only enough information to distinguish the journey. Avoid putting children's full names or document details into titles that may appear on a locked screen.
Create separate entries for meeting at the departure point and handing over after arrival. Use the place where each meeting happens to choose its zone. Ask who checks these entries when a booking changes.
Work through an overnight example
Fictional example: A practice itinerary shows departure from Los Angeles on November 10, 2026, at 7 p.m. local time and arrival in London on November 11 at 1 p.m. local time. These are invented booking details, not a real flight or a flight-duration estimate.
Nanny Mira creates one journey event using the Los Angeles zone for the start and London zone for the end. She enters November 10 at the start and November 11 at the end. In the description, she repeats both local endpoints.
The agreed arrival handover is a separate London event on November 11 at 3 p.m. Mira checks that it has not accidentally landed on November 10. A parent viewing from Los Angeles reads the description and confirms the London handover time. Mira records the separately agreed coverage; she does not use the journey's length as a substitute for it.
Check what the other person actually sees
Open the saved entry together before departure. Ask the other reader to say the event's local date, place and time aloud. Compare that answer with the booking and the written description, especially around midnight.
If your device changes its display while traveling, revisit the next handover rather than editing every event to make the numbers look familiar. First determine whether the event changed or only its display changed. Keep a readable copy of the confirmed itinerary available through the family's agreed method.
Recheck the whole chain after a change
When an airline or family changes a leg, check the departure, arrival, connection and handover entries individually. Mark superseded plans clearly. Tell affected people which local date and time changed and which decisions remain open.
Finish with four checks: the booking is current; each endpoint has a named zone and full date; handovers are separate; the people involved have confirmed the current plan. Use NAJ's shared schedule guide for recording approvals and version changes around this technical calendar task.
Sources
Google Calendar's help. Source checked October 27, 2026.