Gold During Economic Releases: Calendar, Revisions and Risk

Trading gold around an economic release starts with identifying the exact announcement, the account rules and what information the market expected. A higher headline number does not automatically tell you whether to buy or sell XAUUSD. This guide provides a preparation sheet and conditional reaction plan, including the valid decision to take no trade.

Build the event sheet from the original publisher

Use the BLS employment calendar, BLS CPI calendar, Federal Reserve meeting calendar and BEA release schedule. Check the actual date rather than assuming that NFP is always the first Friday or CPI always falls on the same day. Official schedules identify releases; they do not supply a trading signal or every vendor’s consensus forecast.

• Record the reference month, publication date, original time zone and the converted platform time for that specific date. Do not hard-code EST or a European clock time throughout the year.
• Save your forecast provider and the time when its consensus was recorded. Keep the previous published value and later revision in different fields.
• For a Fed event, list the decision, statement, projections when scheduled, and press conference separately. A later communication can change the initial interpretation; minutes are a separate release.
• Record the exact symbol, account programme and stage, permission window, existing exposure and the conditions that invalidate any proposed entry.

Read the whole release, not just its largest number

The BLS methods guide distinguishes payroll jobs from the household survey of people. Read payroll growth together with revisions, unemployment and earnings; they need not point in one direction. For inflation, distinguish headline from core excluding food and energy, and monthly from twelve-month changes using the BLS CPI definitions. Compare the same series and adjustment basis.

Fictional worksheet, not a historical release: payroll consensus is + 180,000 and the new reading + 250,000, a + 70,000 difference. Two earlier readings are revised from + 220,000 to + 160,000 and from + 180,000 to + 130,000: combined revisions of − 110,000. Preserve all three observations; do not turn their arithmetic into a universal buy/sell score. A monthly CPI reading of 0.3% against a 0.2% forecast differs by 0.1 percentage point. That is not a forecast of gold’s percentage move.

Use scenarios that can be rejected

Dollar and interest-rate expectations can be useful context, but no fixed inverse relationship or “strong data means gold falls” rule identifies the next price. Define the relevant price level, invalidation and maximum affordable execution cost before testing a continuation or retracement idea. Neither waiting 90 seconds nor waiting 30 minutes guarantees normal spreads, permission or direction. There is no universal best stop distance, event count per week or 2R target that makes a strategy profitable.

Check permission before placing or leaving orders

Checked 16 October 2026: FTMO’s CFD news policy restricts executions on affected instruments for two minutes before and after selected releases; its table includes XAUUSD for selected USD events. This includes pending orders, stop-loss and take-profit executions. Swing accounts and Challenge/Verification stages are exceptions, subject to forbidden-practice rules. Check the current event and your exact account; this is not a blanket permission for every firm or product.

Placing two stop orders earlier does not exempt their later execution. Manual cancellation or EA-based OCO logic need not cancel the other order before a reversal fills it. Do not solve an uncertain rule by assuming that only market orders count. Retain the relevant written rules and resolve ambiguity before the event.

Size the proposed trade in the contract’s actual units

Hypothetical USD-account calculation: assume one XAUUSD lot represents 100 troy ounces, the planned executable entry-to-stop distance is $9 per ounce, round-trip commission is $10 per lot and the volume step is 0.01 lot. With a chosen $600 budget, one lot’s planned loss is 9 × 100 + 10 = $910. Round 600/910 down to 0.65 lot: planned loss $591.50. This budget is an illustration, not a recommended percentage or provider limit.

An extra $3 per ounce of adverse execution makes that loss 0.65 × (12 × 100 + 10) = $786.50. A stop is not a guaranteed fill. Include spread once through your executable-price assumptions, then other relevant fees and currency conversion. Recalculate if the stop changes. Check both daily and total equity headroom and all other positions; a nominal $100,000 label does not mean $5,000 remains available today. Do not mix mini lots, USD and an undefined gold “pip”.

Review execution and automation separately from the idea

Save the original release, forecast snapshot, revisions, bid/ask quotes, requested and filled prices, cancellations, fees and the reason for trading or skipping. Test continuation and fade ideas separately, with delayed or rejected fills and worse costs. A handful of events or an attractive chart cannot establish a reliable edge. Moving a stop to the entry price does not remove commission, spread or gap risk.

The EA Hub supplies customer-operated MetaTrader-compatible files; only the separate JPTC Algo service is hosted by JPTC. Verify the exact file’s documented features and programme permission. Do not assume that every file has a news module, automatic blackout, perfect copying or guaranteed drawdown protection. The company-published broker-statement figures describe the reported Algo period; they are not an independent audit or evidence that a news setup will pass an evaluation.

Pre-event decision checklist

1. Verify source date, time zone, platform conversion and each component of the event.
2. Freeze comparable forecasts and prior readings before publication; record revisions afterwards.
3. Confirm symbol-specific permission for every possible execution, including existing protective orders.
4. Calculate cash exposure from the actual contract, executable distance, costs and remaining account headroom.
5. Require the tested setup and cost conditions to remain valid. Skip the event when any required condition fails.