UTC stands for Coordinated Universal Time, the international time reference determined from atomic clocks. Local times are related to it by a specified offset. UTC does not change for daylight saving time. In military time notation, the letter Z, spoken as Zulu, identifies this reference. For isolated personnel, UTC connects agreed contact windows, timed intentions in an Evasion Plan of Action and the time attached to a position report: everyone can identify the same instant even when their local clocks show different hours.
A shared reference for contact and movement
A contact window specifies the period during which the person is to attempt an agreed connection or be ready for contact. Its start, end and date must use the same time reference. If a ten-minute window is agreed in UTC but read as local time on a clock two hours ahead, the person attempts contact two hours early. The intended recipient may become available only later. Repeated attempts at the wrong time consume limited power and can create unnecessary transmissions.
An EPA records personal intentions, such as planned movement times, intended duration at a hiding location, and primary or alternative contact times. The time reference therefore belongs in these arrangements before possible isolation. When actual contact occurs, new times are recorded and read back with their complete date and reference. A shared understanding of “23:00” is insufficient when one party means Zulu and the other means local time. An alternative contact window likewise comes from the existing arrangement; it is not established by the person choosing a new time after an unsuccessful contact attempt.
Reading military time notation
A four-digit time uses two digits for the hour and two for the minute on a 24-hour clock. 0935Z means 09:35 UTC. 2135Z means 21:35 UTC. Omitting the colon does not by itself specify a time zone; the Z or UTC reference makes the time unambiguous. A clock displaying 2135 may still be set to local time.
A date-time group, or DTG, combines the day of the month, hour, minute, time-zone character, month and year. In the US Army format for the corresponding map-symbol field, the order is DDHHMMZMONYYYY: DD is the day, HH the hour, MM the minute, MON a three-letter month such as OCT, and YYYY the year. Automated systems may additionally include seconds before the time-zone character. The actual reporting template determines the required year component and inclusion of seconds. A UTC group uses Z as its time-zone character.
The shortened group 092220Z identifies the 9th day at 22:20 UTC; its full date is known only when its month and year are already unambiguous. During isolation spanning a month boundary or when a report is assessed later, those details must accompany it. The meaning of the timestamp must also be clear: an observation, an intended action or the dispatch of a message.
Conversion and date changes
To convert local time to UTC, subtract its known offset. With an explicitly established UTC+2 reference, 00:20 local time on the 10th day corresponds to 22:20 UTC on the 9th day. Changing only the hour while retaining the local calendar day would move the timestamp by a whole day. The offset must match the setting in force at the location and date; a daylight saving change affects local time while UTC remains unchanged.
A UTC contact window from 23:50 to 00:10 also crosses a date boundary. Its end falls on the following UTC day. The personal record therefore includes both dates and, when necessary, both months and years. This prevents a night-time window from being scheduled twice or on the wrong day. “In ten minutes” instead describes a duration from a particular starting instant; two separated people need to share that starting instant if they are to act on it together.
UTC display, GPS time and clock accuracy
GPS system time differs from UTC because the GPS time scale does not incorporate UTC leap-second adjustments. The GPS message contains the conversion data, which a receiver usually applies. A device may then display UTC or local time calculated from it. Before adopting the display, check its stated time reference and the setting actually in use. Adding or subtracting a remembered GPS offset from an already corrected UTC display creates a further error.
A personal clock counts oscillations in its mechanism. A small error in the oscillation frequency accumulates into a time error as the clock runs. Even a radio-controlled clock continues on its own quartz oscillator between successful synchronisations. A UTC label and matching displays on two clocks therefore do not establish accurate agreement with the time reference. For a short contact window, what matters is the error found during the last usable comparison and how long the clock has run without another comparison.
A comparison requires an actually available live display suitable as a time source, or a receivable time signal with a known reference. With a signal, the instant identified must be clear, such as the announced start of a minute. Telephone delivery and buffered audio playback may deliver it late. The receipt time of an old message or a saved screen image is not a current time source. Record the source, comparison time and measured offset.
Correcting errors and retaining the reference
When times conflict, first check the date, UTC or local-time reference, and device setting. Only then determine an actual clock error against a usable reference. If the personal clock is two minutes fast at the comparison, subtract two minutes from its displayed time. The agreed contact instant remains the same; the correction changes how the person relates their clock to it. When a clock or its settings are changed, retain a traceable record of the original note, correction amount and comparison time.
A position report includes the time when the position was determined or observed. If the person subsequently leaves that location, the timestamp identifies an earlier situation. A later dispatch time must not make it appear to be a new position. If a timing error is discovered after transmission and actual contact is possible, the correction identifies the earlier report concerned and its corrected or still uncertain observation time. A newly measured clock offset cannot be applied blindly to every older record if the clock was changed in between or its past rate is unknown.
When no new time source is available, retain the last checked reference and the still-running clock. Elapsed time since a recorded start may remain useful for the duration of a rest or movement; absolute UTC times remain marked according to their known uncertainty. Averaging two disagreeing clocks without an independent reference does not establish the correct UTC time. After a clock stops or resets, the loss of the time reference must remain visible in personal records. Further contact attempts follow the previously agreed alternative times and procedures. An unknown clock error may shift an attempt before or after the actual contact window. A missing reply may then result from the timing offset even when the intended recipient is reachable during the agreed window.