Phoenix, Lisbon, Ho Chi Minh City and Auckland never share a working hour, so the MT262 Unit 4 plan meets in pairs weekly and rotates one night call among four sites. Searches like "mt 262 unit 4 assignment example", "mt262 unit 4 sample" and "mt262 unit 4 example" land here.
What a finished MT262 Unit 4 time zone working plan looks like
About five pages with three exhibits built from computed times. The first is an overlap grid: Phoenix and Auckland share five or six working hours, but only Monday to Thursday in Phoenix, because Phoenix's Friday afternoon is Saturday in New Zealand; Ho Chi Minh City and Auckland share four or five; Lisbon and Ho Chi Minh City three or four; Phoenix and Lisbon two or three; Lisbon with Auckland and Phoenix with Ho Chi Minh City, none. The second is a change calendar: Arizona and Vietnam keep one offset all year, while Portugal and New Zealand change clocks on four separate 2026 dates, moving the Lisbon to Auckland gap between eleven and thirteen hours. The third is a rotation table for the monthly all-hands.
How a MT262 Unit 4 example is structured
The plan works from arithmetic to fairness. Times come first, calculated from each site's clock rules rather than estimated, since the plan is useless if a grader can find a wrong hour. The overlap grid then drives the design: work that needs conversation is assigned to pairs that share hours, and the two pairs sharing none, Lisbon with Auckland and Phoenix with Ho Chi Minh City, are handled entirely in writing. Only the monthly all-hands needs everyone. Four candidate slots exist, each putting exactly one office in the middle of its night, so the plan rotates them and every office carries the cost three times a year. A cap follows: nobody attends more than one call between 22:00 and 07:00 local time in a month. The four clock-change dates close the plan.
Arithmetic before preference
Offsets for every site across 2026, with Arizona's absence of daylight saving and New Zealand's reversed seasons stated explicitly, because both are where hand calculations usually go wrong.
Overlaps by pair
The grid of shared working hours between 08:00 and 18:00 local. Two pairs share nothing, and the plan designs around that fact instead of meeting at a compromise hour.
A Friday that is already Saturday
Phoenix's Friday afternoon falls on the New Zealand weekend, so the Phoenix and Auckland meeting runs Monday to Thursday in Phoenix and never on Friday.
Four slots, four nights
At 19:00 UTC Ho Chi Minh City sits at 02:00; at 01:00 UTC Lisbon does; at 14:00 UTC Auckland; at 08:00 UTC Phoenix. The all-hands moves monthly through all four.
Dates when the gaps move
March 29, April 5, September 27 and October 25, when Portugal or New Zealand changes clocks. The plan republishes local times a week before each change.
Where marks go in MT262 Unit 4
Wrong times are the fastest way to lose credibility in this unit, and graders in MT262 frequently check a plan by converting its slots themselves. Plans that forget Arizona keeps standard time all year, or that New Zealand's daylight saving runs opposite to the northern hemisphere, carry errors a careful reader finds in minutes. A second weakness is defaulting the inconvenient hour to whichever office is furthest from headquarters, usually without saying so. Plans that meet distance by adding live calls lose ground when they never count who attends at night. Missing the date line, scheduling on a day that is already the weekend somewhere, is a subtler error. Plans that state who carries the cost, how often, and why tend to score highest on analysis.
Get a MT262 Unit 4 example written to your instructions
List every site in your Unit 4 scenario with its city, not just its time zone, since daylight saving rules differ within zones. Include team size, any fixed meetings and the rubric. The custom plan computes each hour, states who carries the night calls and how often, and arrives in 24-48h, free the first time.
MT262 Unit 4 questions, answered
How do I get the times right across daylight saving changes?
Work from each city's actual rules rather than a time zone label, and list the dates clocks change in the year your plan covers. Remember that some places never change, such as Arizona and most of Asia, and that southern hemisphere changes run in the opposite season. A small table of offsets by date prevents most errors graders find.
Should the plan cover public holidays?
Ideally, yes. Holidays rarely coincide across countries, and a day off in one office can stall work passing through it. A list of each site's public holidays for the plan period, with the longest marked, such as the Lunar New Year break in Vietnam, lets the plan move deadlines in advance instead of discovering the gap when a handoff goes unanswered.
What if no hour works for everyone?
That is common on teams spanning more than about twelve hours, and it is a finding rather than a failure. Reduce what requires everyone at once, use pairs or subgroups that share hours, and move the rest to written channels. Where a full meeting remains necessary, say who carries the night hour, how often, and how that is tracked.