Summary

  • ITU released the first update since 1997 of its handbook on precise frequency and time systems, adding a chapter on “Time as a Service”.
  • The guide says an operator should be able to document a signal’s origin, its route to the user and the uncertainty added at each conversion.

Analysis

The phrase “traceable to UTC” fits neatly on a service page. The chain it describes can run from an international time reference or national metrology institute through clocks, conversion equipment and routed networks to the signal a customer actually receives. ITU’s new handbook asks operators to account for that trip.

On 30 October, the International Telecommunication Union released the 2026 edition of its Handbook on Selection and Use of Precise Frequency and Time Systems—the first update since 1997. The new Chapter 8, “Time as a Service”, addresses systems that distribute their embedded time information to third parties, sometimes beyond the operator’s own network.

The chapter’s test is concrete: the operator must assure the origin of the time information and its unaltered transport. Ideally, each step from UTC, or a national metrology institute’s realization of it, to the end-user signal should be transparent, including the uncertainty introduced by every conversion and routing step. A clock’s accuracy at the source cannot describe the entire route on its own.

That distinction matters because “traceability” has become a convenient word in documents where it does not always carry the strict metrological meaning. In that meaning, a result is connected to a reference through a documented, unbroken chain of comparisons or calibrations, with uncertainty stated at each link. The handbook says a GNSS input alone does not establish the required metrological traceability to UTC. A satellite receiver may be one part of the path; it is not the path’s complete record.

The same chapter treats the logs and hardware around the clock as part of the service. It recommends current documentation of signal routing and measurement software, monitoring and recording internal parameters, keeping parallel data off-site, identifying a dataset’s capture time, quantity and unit, and logging transfers to third parties. Its reliability section asks users to define their accuracy, availability and tolerable-deviation needs, then consider redundancy, power and holdover against those needs.

The handbook is technical guidance. It says some sectors already have legal or regulatory duties to demonstrate traceability, while local statutes and regulations set the legal details. Legal validation generally needs a log system and may require monitoring by an external regulator. ITU supplies the engineering questions; sector rules decide the legal test.

The release arrives as the international time scale is also changing. Resolution 5 of the 28th General Conference on Weights and Measures sets continuous UTC to take effect on 20 May 2027. A continuous reference settles one part of the system. A time service still has to show how that reference reached the receiving device.

That is the governance question hidden inside a technical label: who holds the records for each handoff, and can the buyer inspect them when an audit or dispute arrives? A procurement team can ask for the upstream source, calibration records, route, uncertainty budget, outage behavior and export logs before buying a “traceable” service. The best proof is not the word on the contract. It is a chain another party can follow.

Sources