How should daylight saving time be handled in time-bound reporting?

How should daylight saving time be handled in time-bound reporting?

• A. Use local daylight time without annotation.
• B. Use a mix of time standards across records without annotation.
• C. Ignore DST and rely on operator notes.
• D. Use a single reference time (UTC/BES time) to avoid DST ambiguity, and clearly annotate the time zone.

Answer: (D)

Daylight saving time introduces shifts that can make the same moment appear at different clock times across systems. To keep time-bound reporting unambiguous and comparable, all timestamps should be anchored to a single reference time and clearly annotated with the time zone. Using a universal reference like UTC (or BES time) ensures every event has a unique, monotonic timestamp regardless of local DST changes, and the explicit time zone removes any confusion about what the timestamp represents. This approach supports accurate aggregation, cross-system analysis, and auditability. Other methods—recording in local daylight time without annotation, mixing time standards without annotation, or relying on operator notes while ignoring DST—risk misinterpretation, misalignment during DST transitions, and inconsistent records.

Daylight saving time introduces shifts that can make the same moment appear at different clock times across systems. To keep time-bound reporting unambiguous and comparable, all timestamps should be anchored to a single reference time and clearly annotated with the time zone. Using a universal reference like UTC (or BES time) ensures every event has a unique, monotonic timestamp regardless of local DST changes, and the explicit time zone removes any confusion about what the timestamp represents. This approach supports accurate aggregation, cross-system analysis, and auditability. Other methods—recording in local daylight time without annotation, mixing time standards without annotation, or relying on operator notes while ignoring DST—risk misinterpretation, misalignment during DST transitions, and inconsistent records.