Summary

  • ARIN’s 4 August announcement puts its Jacksonville workshop at 9:30 AM–3:00 PM ET; the current outreach page puts the same event at 10:00 AM–3:00 PM ET.
  • Both times may have a sensible role, but neither page labels a 9:30 arrival interval and a 10:00 programme start. A short operative schedule would settle the matter before 17 September.

There are two official clocks for one ARIN workshop in Jacksonville this Thursday. The dated announcement says 9:30 AM–3:00 PM Eastern Time. ARIN’s current outreach page says 10:00 AM–3:00 PM ET. The city and date match. So does the finish. The published start does not.

Thirty minutes is a modest discrepancy. That is precisely why it is useful. It can be corrected without reopening a policy, changing a service or diagnosing an incident. Before people travel to the Marriott Jacksonville Downtown, ARIN need only say what happens at 9:30 and what begins at 10.

The evidence does not establish that either time is wrong. A perfectly ordinary explanation is available: 9:30 may be for arrival, check-in or food, while the programme may begin at 10. The announcement says registration is free and lunch is provided. The live page asks attendees to state their main reason for coming at check-in. Neither source, however, assigns the extra half-hour to an activity. An attendee is left to supply the explanation.

That distinction matters because the two possible errors impose opposite costs. Someone who treats 9:30 as the programme start may arrive half an hour earlier than necessary. Someone who treats 10 as the only relevant start may miss a useful reception or briefing if one was intended at 9:30. There is no evidence that either has happened. The point is to close the choice before it can.

One event, three publication surfaces

ARIN’s meetings index confirms “ARIN on the Road: Jacksonville” on 17 September but lists no hour in its event table. That leaves the dated announcement and the live programme page as the two practical time sources. They are both ARIN publications, not an official page on one side and an unofficial calendar on the other.

The event content is not obscure. The live page lists ARIN’s mission and core function, governance and policy, resource requests, services, routing security, RPKI, IRR and community participation. The announcement promises access to ARIN decision-makers and time for questions. For a workshop about how to use registry systems and participate in their governance, the first operational instruction should not require interpretation.

There is also a pattern worth separating from proof. ARIN’s January notice for its Nashville workshop used the same 9:30 AM–3:00 PM format. That may show a standard event-day envelope. It does not prove how Jacksonville’s thirty minutes are allocated. Historical consistency is context; it is not a substitute for the current schedule.

The smallest adequate record

ARIN does not need a detailed conference platform for a five-hour workshop. A seven-line record would be enough:

Schedule field What the operative page should state
Doors or check-in Exact opening time
Food service Whether breakfast or refreshments begin before the programme
Programme Exact first-session time
Finish 3:00 PM ET, if unchanged
Time zone Eastern Time, stated once and consistently
Venue Marriott Jacksonville Downtown, with any room detail sent to registrants
Version Last updated time and a link used by every older notice

This is not bureaucracy for its own sake. It is a compact join between two public records. The dated announcement can remain as an accurate historical notice while pointing readers to a clearly labelled live schedule. The live page can become the controlling operational surface without erasing the earlier publication.

The same design also preserves uncertainty honestly. If 9:30 is check-in and 10 is the first session, the record should say so. If the start moved, the page should name the new operative time and when it changed. If no activity occurs before 10, the old notice should direct readers to the update. Each answer is acceptable. The unlabeled gap is the only problem demonstrated here.

A pre-event correction window

As of 14 September in Shanghai, the workshop is still ahead. This article is therefore not an after-action account and not evidence of an attendee failure. It is a time-limited opportunity to make the day easier to plan.

ARIN asks people at check-in what they hope to get from the event. That is a useful demand signal for a flexible workshop. It should sit beside an equally clear supply signal: when check-in opens and when teaching begins. One line can do the work.

The broader lesson is deliberately narrow. Durable announcements are good records of what an institution said at a moment in time. Live event pages are good places to publish the current operating instruction. When both remain public, a visible version link and labelled phases prevent history from competing with logistics.