Skip to main content

Calendar · prior · complete package · execution veto

Trading 6N Economic Releases: A Before-During-After Plan

Seconds before a scheduled release, three unanswered questions are enough to cancel the trade: What exactly is the market expecting? Which components or revisions would change the macro interpretation? What spread, depth, gap, and loss conditions make execution unacceptable? If those fields are not frozen before publication, the first price move cannot repair the plan.

Before
Freeze branches
At release
Read whole package
During
Execution gates
After
Evidence review
Prior?Outcome expectation, components, revisions, and priced policy path.Transmission?New Zealand versus U.S. rates, growth, inflation, exports, or risk.Veto?Market quality, latency, gap, invalidation, and maximum planned loss.

Before any market opinion

Verify the Event With the Publishing Agency

Release dates and times can move. New Zealand, U.S., China, and exchange clocks also change relative to one another around daylight-saving transitions. Store the official timestamp, timezone, retrieval time, and a UTC conversion; then check for overlapping releases.

Event familyPrimary calendarPackage to expectClock risk
RBNZ decisionRBNZ decision-date page and event noticeOCR decision, statement or MPS, implementation timing, media materialNew Zealand local time and schedule changes
Stats NZStats NZ release calendarHeadline, components, seasonal treatment, revisions, methods, downloadsNew Zealand time and local holidays
Federal ReserveFOMC meeting calendarStatement, implementation note, vote, projections when scheduled, press conferenceU.S. Eastern time and DST
U.S. statisticsBLS and BEA calendarsCPI or labor details; GDP or PCE details and revisionsAgency time, embargo, and concurrent releases
China, only if predeclaredNBS annual release calendarOfficial headline, components, methods, and later revisionsChina Standard Time and translation lag
A third-party calendar is a convenience, not authority

Use the Stats NZ release calendar, the RBNZ's official decision dates current in 2026, and the relevant U.S. or China agency page. Reconfirm on the event day.

The surprise denominator

Freeze What Was Knowable Before the Release

The market response is to new information relative to a prior, not to whether a number is “high” or “low.” Preserve the expectation source and retrieval time. If the prior is missing or unverifiable, the surprise must remain unknown.

Pre-event record

Capture the release and reference period; headline and component expectations; revision risk; previous official vintage; relevant RBNZ and Fed paths; active 6N contract and roll state; aligned spot and cross-market observations; event branches; invalidation; order policy; expected costs; and maximum planned loss.

Consensus
Named source + time
Vintage
Previous official release
Branches
Before outcome
Risk
Dollar limit
RBNZ prior

Expected decision, expected path, known alternatives, previous MPS assumptions, and the comparable U.S. curve.

CPI prior

Headline, tradeable and non-tradeable detail, weights or method changes, revisions, and implications for the medium-term path.

Labor prior

Employment, unemployment, participation, hours, wages, sampling, and any benchmark or seasonal revisions.

GDP prior

Production and expenditure composition, real versus nominal measure, previous-quarter revisions, and release vintage.

Trade prior

Goods-only versus broader external accounts, price versus volume, categories, destinations, imports, and seasonal treatment.

U.S. prior

FOMC package or official statistics, matched horizon, simultaneous releases, and expected effect on the dollar and U.S. curve.

At publication

Read the Release Package Before Naming the Surprise

A headline can be offset by components or revisions. Record the package in a fixed order so the most dramatic number does not crowd out the most informative one.

1

Authenticate

Confirm the publishing agency, release title, reference period, version, timestamp, and whether the page or file is complete.

2

Compare

Calculate actual minus frozen expectation for each predeclared field. Do not add components after seeing which ones moved the market.

3

Reconcile

Read revisions, seasonal adjustments, methodological notes, and internal offsets. A revised prior period can change the apparent surprise.

4

Classify

Label the new evidence as policy-path, inflation, growth, labor, external-income, or risk information. More than one label can apply, but avoid double counting.

5

Preserve uncertainty

Record preliminary status, confidence intervals where supplied, response rates, and future revisions. “Mixed” is an acceptable package result.

Example boundary: an upside CPI surprise can raise the expected RBNZ path, reduce expected real income, or signal a temporary import-price shock. The sign of the headline does not choose among those mechanisms.

From surprise to bilateral price

Map Competing Branches Before Looking for 6N Confirmation

6N is quoted in U.S. dollars per New Zealand dollar. Higher 6N is consistent with stronger NZD versus USD, but a dated futures contract includes basis and lifecycle. Route mechanics to the canonical 6N guide.

BranchRequired evidencePossible 6N hypothesisReject when
NZ path firms relative to U.S.Package changes medium-term policy expectations; matched NZ curve rises versus U.S. without stress6N may receive support if FX and futures confirmReal-return or risk interpretation deteriorates, or price rejects
NZ growth weakensComponents and revisions reduce activity or external-income expectations6N may weaken if relative rates and peers confirmPolicy, broad-dollar, or offsetting export evidence dominates
U.S. surprise dominatesU.S. curve and broad dollar reprice more than New Zealand evidenceCommon-dollar pressure may outweigh the local packageNZD-specific crosses and TWI show independent strength
Package is mixedHeadline, components, revisions, and policy implications conflictNo immediate directional inferenceOnly later, independent evidence can resolve it
Data or timing failsSource, clock, expectation, contract, or market data cannot be verifiedNo trade conclusionA repaired, point-in-time record is required

The macro view cannot waive market quality

Execution Gates Must Include Mandatory No-Trade Outcomes

A correct interpretation can still produce a poor or unacceptable execution. Gap risk, temporary spread expansion, shallow depth, latency, and slippage can exceed the planned loss before a protective order can operate.

Pre-position permitted by plan

Required: explicit gap-risk budget, known release, acceptable liquidity, declared maximum loss, and no reliance on an exact stop fill.

Otherwise: no position through the release.

Post-release confirmation

Required: authenticated package, resolved branch, price acceptance beyond the declared level, and spread/depth within limits.

Otherwise: wait.

Reduce size

Required: valid evidence but volatility or slippage stress consumes part of the risk budget.

Otherwise: full planned size is not justified.

Cancel the setup

Required: package conflict, failed confirmation, stale feed, wrong contract, excessive spread, insufficient depth, or overlapping unscheduled news.

Action: remain flat.

Margin is not maximum loss

Exchange and broker margin determine required collateral, not the largest possible loss. Size from the invalidation distance, contract dollar sensitivity, slippage and gap stress, fees, and the account's fixed loss limit. Use the 6N market-quality protocol before any event order.

After the event

Review the Evidence, Not Just the P&L

A profitable trade can be poorly designed; a losing trade can follow a valid process. Preserve the official vintage and replay what was knowable at each decision time.

Review fieldRecordFailure exposed
Calendar and sourceOfficial URL, scheduled and actual timestamp, files retrievedWrong event, late document, or clock error
PriorArchived expectations and market stateHindsight or unverifiable consensus
PackageHeadline, components, revisions, methods, uncertaintyHeadline-only reading
TransmissionBranch selected, rival branches, cross-market confirmationMechanism chosen after price moved
ExecutionOrders, fills, spread, depth, slippage, latency, gapPaper assumptions inconsistent with live conditions
OutcomeGross and net P&L, maximum adverse excursion, rule complianceCosts omitted or outcome substituted for process quality

Research boundary: this article reports no original event-study result or profitable setup. Testing requires point-in-time expectations, official vintages, synchronized market data, rolls, realistic fills and costs, and untouched validation events.

One-page operating checklist

Before, During, and After the Release

Before

Prepare or cancel

  • Verify the official calendar and UTC conversion.
  • Archive the prior, previous vintage, and full branches.
  • Identify active 6N contract and roll state.
  • Set spread, depth, slippage, gap, and dollar-risk vetoes.
  • List overlapping New Zealand, U.S., and global events.

During

Authenticate and gate

  • Use the primary release, not a headline relay.
  • Read components and revisions before classifying.
  • Observe matched curves and independent FX evidence.
  • Require price and market-quality confirmation.
  • Stand aside whenever a mandatory field fails.

After

Reconcile and learn

  • Save the official vintage and timestamps.
  • Record every fill and full cost.
  • Compare realized evidence with each branch.
  • Separate process quality from P&L.
  • Change rules only through a declared research process.
Sources, methods and editorial disclosure — reviewed August 20, 2026

This is a planning and evidence-classification framework. It does not report an original event study, fill study, predictive model, or profitability result.