DATA GOVERNANCE · 2026-09-10
Data sources, freshness and corrections
This page explains where each Contract Atlas fact comes from, when it was reviewed, and which dates are confirmed schedules versus rule-based estimates.
- Contracts
- 75
- Date events
- 358
- Confirmed
- 160
- Official domains
- 13
01 · SCOPE
One search intent per page family
Live market state
The home timeline owns open/closed state, next transition and regular sessions.
Open the live clock →Contract specifications
Each contract page is the canonical owner of size, tick, tick value, expiry rule and upcoming dates.
Browse contracts →Expiry overview
The expiry view is an on-site finder only; it does not offer calendar downloads, subscriptions or duplicate month pages.
Browse expiry dates →02 · PROVENANCE
Source and review records
Every record must have a reachable official-exchange source, review date, review state and public-reference rights state. The exact source is exposed on the contract page and each expiry event.
A source-compliance self-review (publisher terms and citation practice checked source by source) was completed and archived on 2026-08-20.
| Field | Evidence | Publish rule |
|---|---|---|
| Size, tick and tick value | Official contract-specification page | Source and rights state accepted |
| Expiry rule | Official rulebook or contract guide | Traceable rule text and review date |
| Front-contract dates | Current schedule, or an accepted rule calculation | Must say confirmed or rule-based estimate |
Current review state: Accepted· Rights state: Approved for public reference· Latest review: 2026-08-10
03 · DATE STATUS
Confirmed and rule-based are different states
- Confirmed schedule
- A date explicitly present in the current contract schedule; shown without an asterisk.
- Rule-based estimate
- Calculated from an accepted expiry rule and marked *; holidays, notices or exchange adjustments can move the final date.
A rule-derived value must never be presented silently as confirmed. Re-open the linked official source before trading.
04 · FRESHNESS
Automated gates and review targets
- 120 daysMinimum future coverage; current coverage ends .
- 30 daysNear-term dates must carry an explicit review state.
- 80%Maintenance target for confirmed dates in the next 90 days; shortfalls remain visibly estimated.
- 90 daysMaximum record review age before the build gate alerts.
05 · CORRECTIONS
How corrections are handled
Send the page URL, field to correct, official notice URL and notice date. The accepted value stays in place until the evidence is reviewed through a traceable change; external feedback never silently overwrites it.
Report a data correction06 · OPEN DATA
Open data downloads (JSON and CSV)
Contract specifications, expiry events and regular trading sessions are published as machine-readable JSON and CSV — no key required and CORS enabled. The data hub lists versions, fields, licensing and every download:
| Field | Meaning |
|---|---|
| source · license · dataReviewed | Origin, citation terms and the date the schedule data was last reviewed |
| weekdayConvention | ISO 8601 weekday numbering: Monday = 1 … Sunday = 7 |
| products[].slug · code · exchange · name · chineseName | Product identifiers, exchange short code and bilingual names; slug matches the contract page path on this site |
| products[].timeZone | IANA time zone; every time in the record is local to it |
| products[].scheduleValidFrom · scheduleValidTo | Validity window of the session template (null when open-ended) |
| products[].calendarCoverageStart · calendarCoverageEnd | Date range covered by the reviewed holiday calendar |
| products[].sessions[] | Each session: label, tradingDays, open/close, day offsets and closeAnchor; seasonal variants (for example European summer time) are split with validFrom/validTo |
| products[].page | The contract page carrying sources, holidays and expiry dates |
Datasets update with reviewed releases and carry no prices or quotes. The license covers only our compilation, schema and documentation—not exchange facts or source materials. Verify official notices before trading.
07 · EMBED & CITE
Embedding, reuse and citation
Our original compilation, schema and documentation may be quoted, embedded and reposted with attribution to futuresclock.com; links may use rel="nofollow". Attribution records provenance and is not a ranking condition. Exchange facts and source materials remain with their publishers; this site carries no quotes.
Live status card (iframe)
Open/closed status and next open/close for 14 exchanges, refreshed every 30 seconds in the visitor’s time zone; preview: futuresclock.com/en/embed/status/
<iframe src="https://futuresclock.com/en/embed/status/" title="Global futures market status · Futures Clock" width="100%" height="320" loading="lazy" style="border:0;max-width:720px" referrerpolicy="strict-origin-when-cross-origin"></iframe>
<p><a href="https://futuresclock.com/">Futures hours by Futures Clock</a></p>2026 closures in one image
Direct image URL (SVG; keep the attribution printed on the image):futuresclock.com/en/holidays/2026/futures-holidays-2026.svg
<img src="https://futuresclock.com/en/holidays/2026/futures-holidays-2026.svg" alt="Global futures exchange closures 2026 · source futuresclock.com" width="1600" height="1060">Citation format
Every page ends with a “Cite this page” block you can copy in one click: Futures Clock. “Page title.” URL (accessed date). For research use, also note the review date printed on the page.