But, I will also put the time zones in West -> East order of our trip block, AFTER our work time zone of course. Sometimes we go back and forth, so when needed, I will number the order we use them at the very top, as seen in the example chart at the top of the article. Now, I try to put the time zones in the order in which we will encounter them. In the end, it was hard to keep track of how our work time zone mapped to everything else (read: set our local work hours everywhere). Then, the rest are listed in the order we visited them, but it happens to line up West -> East from our US departure city.Įxperience Tip: When I first started tinkering with the chart, I used to put all the time zones in UTC offset order. I’m sure the order of the time zones makes no sense at all - allow me to explain! I’ve got Pacific and Eastern on the end because they are our work and base time zones. This is where comes in! I’ll break this out into steps since this is where it gets tricky. Columns 2+: All the time zones in your trip block However, most of them start with 12:00 am or 00:00, as in the immediate example above (and the one I will use going forward). To make it easier to read for the majority of the trip, I based all the conversions on PDT so 12:00 am could be at the top. The chart at the top of the article (Spain / Portugal trip block) starts with 11:00 PM because we began the trip block in Pacific Standard Time but very quickly switched to Pacific Daylight Time. The first cell will be 12:00 am and fill in every hour until 11:00 pm, probably. It is from our South Asia to South America trip block.Ĭolumn 1: Your home / default / most important timezone I used to only use am / pm but now I will use a little of both.įor this section, I’m going to walk through a new example. You can use am / pm or you can use 24-hr, whichever you prefer. This is where the magic happens!!! I make an hourly list in each time zone. For example in the above chart, for Central European Time (CET), I listed “Spain, Gibraltar.” But, since we were still in Gibraltar and went back to Spain after the time change, for Central European Summer Time (CEST) I listed “Spain, Gibraltar” again. I will also list ALL of them even if we leave the timezone and come back to it later in the trip. whatever makes the most sense for the trip. This could be by country, by city, by state, etc. In this row, I list the specific places we will be. If I do end up lumping everything into the same UTC offset, I will usually just put the time zone name we will be in the longest and indicate the rest by the location section (keep reading). For example: Pacific Standard Time (PST), Hong Kong Time (HKT), Central European Time (CET), Central European Summer Time (CEST). I like both the long, spelled out version and the three-letter abbreviation.
#Marvel 5 spreadsheet converter full
Depending on how many time zones we are passing in a trip block, if things get full and I can’t print it all on one page, I can merge things together pretty quick by the UTC offset. I prefer to list HKT and MYT in their own columns with UTC +8 at the top of both, letting me know quickly they are the same actual time. For example, Hong Kong Time (HKT) and Malaysian Time (MYT) are both UTC +8.
It is actually pretty common for countries to have their own names for the same UTC offset, especially when dealing with Daylight Savings Time. I also will include if we will encounter any Daylight Savings (in or out) both in the US and in other places (which obviously never match up with US time changes - that would be too easy!). I include every time zone we will visit in each trip block (what we call a US -> other places -> US loop). Since our work time zone (Pacific) is the most important, it always goes on the far left. The general format of the spreadsheet is the same every time.