The November clock change: a gold research plan for JOLTS and payrolls

First fix the clock

NIST's 2026 daylight-saving guidance states that US daylight saving ends on Sunday, 1 November at 02:00 local time. New York then returns to Eastern Standard Time, UTC−5. Dubai remains UTC+4, so the time difference for the coming week's US releases is nine hours. Copying the previous week's Dubai alert without checking the offset would make it one hour early.

This is a preparation edition published on Saturday, 31 October. The last completed New York trading session was Friday, 30 October. There is no Saturday gold session in this article and no preview price presented as an executable market quote. The purpose is to make next week's observations comparable before the headlines arrive.

Source notes: [1] National Institute of Standards and Technology — Daylight Saving Time Rules

Three scheduled releases, three separate questions

The BLS November calendar lists September JOLTS for Tuesday, 3 November at 10:00 Eastern: 15:00 UTC and 19:00 Dubai. Preliminary third-quarter Productivity and Costs is scheduled for Thursday, 5 November at 08:30 Eastern: 13:30 UTC and 17:30 Dubai. October's Employment Situation follows Friday, 6 November at the same 08:30 Eastern time.

These times are verified against the official calendar as checked on 31 October; a schedule is not a guarantee against later changes. I would confirm the agency page again before each release. The coming week's information is not available yet, and this article supplies no invented forecast, consensus estimate or result.

Source notes: [2] Bureau of Labor Statistics — November 2026 release calendar

Tuesday: read vacancies alongside movement

BLS distinguishes job openings, a stock measured on the month's last business day, from hires and separations, flows measured through the month. The distinction matters because a vacancy count describes positions waiting to be filled, while hires and departures describe activity that actually occurred. Revisions can also change the previous comparison.

My preparation sheet would place openings, hires and quits in separate rows. For each, I would save the previous published vintage and the new value when released. A lower opening count alongside stable hiring should not automatically receive the same interpretation as lower openings alongside contracting hiring. These are conditional questions, not predictions of Tuesday's report or assertions about a future gold response.

Source notes: [3] BLS — JOLTS Frequently Asked Questions

Thursday: keep the cost question distinct

The calendar's productivity release offers a separate opportunity to test a cost narrative. If commentary argues that compensation pressure must translate directly into higher prices, the researcher should ask what happened to output relative to labour input and which productivity measure is being discussed. Those questions belong beside, rather than inside, the vacancy story.

I would prepare a note with the exact series labels, units, observation quarter and revision status left blank for completion from the release. Annualised quarterly changes and year-over-year changes should occupy different fields. The discipline is useful even when the headline reaction is small: it prevents an attractive narrative from quietly changing the statistic it relies on.

Friday: do not make two surveys compete for one label

The Employment Situation draws on distinct household and establishment surveys. BLS's technical documentation explains their different coverage and concepts. A payroll employment change and an unemployment-rate movement are not two interchangeable estimates of the same quantity.

For the research note, I would capture payrolls, prior-month revisions, unemployment, participation, earnings and hours as separate observations, using the definitions in the new release. The first task is to describe agreement or disagreement across the measures. The second is to compare that information with a timestamped pre-release expectation. Calling an outcome strong or weak without stating the comparison can confuse growth with surprise.

Source notes: [4] BLS — Employment Situation Technical Note

Build the event record before building the explanation

For each release, I would record a clean pre-event gold observation, the source and instrument, and consistent post-event windows. The same windows would be used for a specified dollar pair or index and a specified yield series where reliable data are available. If a feed is delayed or an observation is missing, that field remains explicitly unavailable. It is not backfilled with a convenient screenshot from a different clock.

The written conclusion would have three parts: what the agency reported, what the measured market series did, and my interpretation of the connection. I would also list alternative catalysts that entered the window. If data are revised later, the original information set stays intact and the revision receives a separate note. This preserves the difference between what an analyst could know at release time and what became clear afterward.

What a useful Friday review should deliver

At the end of the week, the goal is not to force every release into a winning gold thesis. It is to compare the questions written beforehand with the evidence that arrived. Did the labour measures tell a coherent story? Did the currency and rates observations support the proposed transmission? Where did the interpretation fail or remain unresolved? A review that records those limits is more useful than a confident narrative assembled only after the chart is complete.