One FOMC meeting, three evidence records: statement, press conference and minutes

A meeting is the parent record, not a single publication

A research folder labelled Fed meeting can contain a policy statement, a press-conference page and minutes released later. If the folder date becomes the timestamp of every item, the notebook loses the order in which information became available. Start with the meeting interval, then give each source document its own type, publication evidence and checked-at observation.

This resource helps inspect those links. It does not plan a trading session or interpret the decision. Its result is a small evidence report: which source paths match the chosen meeting, which dates are supported by the supplied record, and which publication details remain unknown. The report is useful before any optional visit to this publisher’s separate Telegram offer.

Use the calendar as an index to the documents

The Federal Reserve calendar separates statement, press-conference and minutes links within a meeting entry. It explains that regularly scheduled meeting minutes are released three weeks after the policy decision. That general description is useful context, but it is not a substitute for inspecting the particular release entry.

For the September 15–16, 2026 meeting, the calendar lists a September statement and identifies October 7 as the minutes release date. These are different dates attached to the same meeting. We use the completed historical example rather than automatically turning an upcoming calendar appointment into a published document.

Sources: Federal Reserve — Meeting calendars and information.

The statement has its own source record

The September statement page is dated September 16 and carries a 2:00 p.m. EDT release label. That is a source-stated time, not a measurement of when your computer received the page. Keep the distinction if a project later needs dissemination or market-data latency evidence. This worksheet does not measure either.

In the worked form the statement uses the established date and deliberately leaves the optional publication timestamp blank. The original page remains linked for a reader who needs to inspect its time label. No exchange tick, headline arrival or account action is inferred from that date. A date-only record is still usable for checking which meeting the document belongs to.

Sources: Federal Reserve — September 16, 2026 statement.

A materials page and a recording timestamp differ

The Federal Reserve has a separate page labelled for the September 15–16 meeting under its press-conference route. The inspected page links related statement, implementation and projection materials, as well as the later minutes. It is a useful document hub, but a page label or last-update date alone does not establish the exact publication time of every video or transcript associated with it.

That is why the worked press_conference row remains unknown for publication. Its URL and checked-at note are retained, while event_date and publication_at stay blank. The report can therefore show all three document categories present without claiming three completed releases. This is an intentional evidence boundary, not a claim that the press conference did not happen.

Sources: Federal Reserve — September 15–16, 2026 meeting materials.

The minutes URL carries the meeting date

The inspected minutes page is titled for September 15–16, 2026. Its path contains 20260916 even though the calendar identifies its release as October 7. A script or notebook that reads the eight digits as a publication date would put that document three weeks too early in this example.

The local check extracts that path date only as a meeting identifier. The separately entered event_date carries the publication date. With the worked inputs, the gap between September 16 and October 7 is 21 calendar days. That result is date arithmetic, not an exact 504-hour dissemination interval: the form has not supplied two precise publication instants.

Sources: Federal Reserve — Minutes for September 15–16, 2026, Federal Reserve — Meeting calendars and information.

Check document type as well as hostname

A Federal Reserve URL copied into the wrong row is still the wrong evidence for that row. The checker recognizes one narrow HTML naming pattern for each of the three types, including the meeting date in the path. It compares that date with the selected meeting end and the row’s own meeting-end field. A July document will not complete a September record.

The hostname must be exactly www.federalreserve.gov, with HTTPS and no credentials, custom port, query or fragment. This prevents a lookalike hostname from passing the local pattern check. It is not a security certificate or source-authentication service. A legitimate PDF or a future changed path may fall outside the supported pattern and remain unverified; the tool never declares it false merely for that reason.

Keep New York dates and timestamp precision explicit

If you have a precise publication timestamp, enter its known Z or numeric offset, including seconds. The checker converts that instant to an America/New_York calendar date and compares it with event_date. A contradictory date is rejected. An unknown offset such as -00:00 is also rejected because it cannot support that conversion.

A missing timestamp stays missing. The tool does not create midnight, assume a standard 2 p.m. release, or borrow the time from another document. The checked-at time records your notebook observation and must not precede an entered publication instant. It also cannot be later than the report’s as-of time. These constraints describe the evidence you supplied, not an automated visit to the website.

Scheduled remains scheduled after the clock passes

Choose scheduled for an appointment supported only by a schedule. Even when its date is in the past relative to the report, the worksheet keeps the status scheduled_not_publication. Publication needs its own source evidence. A missing or unavailable source should stay unresolved rather than being filled by elapsed time or by a typical release pattern.

For a revised document, keep a separate report or version record. This form rejects duplicate document kinds within one report so that two statement versions cannot silently overwrite each other. Preserve the old URL, source excerpt or file reference in your own archive and explain what changed. The tool does not decide that a newer-looking page supersedes every earlier account.

A reproducible notebook without a market prediction

The CSV preserves the meeting interval, source URL, stated event date, optional original and UTC timestamps, checked-at time, saved reference and the path-matching result. Missing document types are listed separately from unknown publication fields. Cells that resemble spreadsheet formulas are treated as text; edits remove the old export until the report is generated again.

Use the completed report to locate evidence, not to predict a price move. No policy surprise, sentiment score, expected return or trading instruction is calculated. The source dates were checked on 20 October 2026 UTC and should be reviewed again if the page changes. The optional link below leads to the existing English-language crypto signals and updates offer; using it is not required to read or export this research.

Worked examples

{
  "meeting_start": "2026-09-15",
  "meeting_end": "2026-09-16",
  "as_of": "2026-10-20T21:00:00Z",
  "rows": "kind|meeting_end|state|event_date|publication_at|source_url|checked_at|evidence_ref\nstatement|2026-09-16|published|2026-09-16||https://www.federalreserve.gov/newsevents/pressreleases/monetary20260916a.htm|2026-10-20T21:00:00Z|Worked source record: statement date\npress_conference|2026-09-16|unknown|||https://www.federalreserve.gov/monetarypolicy/fomcpresconf20260916.htm|2026-10-20T21:00:00Z|Materials page seen; recording publication time not established\nminutes|2026-09-16|published|2026-10-07||https://www.federalreserve.gov/monetarypolicy/fomcminutes20260916.htm|2026-10-20T21:00:00Z|Worked source record: calendar release date"
}

{
  "matched_published_count": 2,
  "all_three_document_records_present": true,
  "statement_calendar_days": 0,
  "minutes_calendar_days": 21,
  "press_conference_status": "unknown",
  "market_effect": null
}

Questions about the method

Primary sources and scope

1. Federal Reserve — Meeting calendars and informationChecked 2026-10-20. Separate document links, regular-minutes three-week description, September 15–16 meeting and October 7, 2026 minutes release.
2. Federal Reserve — September 16, 2026 statementChecked 2026-10-20. Statement date and source-stated 2 p.m. EDT release label. No measured dissemination timestamp or policy prediction used.
3. Federal Reserve — September 15–16, 2026 meeting materialsChecked 2026-10-20. Separate press-conference route and related document links. Recording/transcript publication timestamp remains unverified.
4. Federal Reserve — Minutes for September 15–16, 2026Checked 2026-10-20. Meeting title and path identifier; October 7 last-update date corroborates, but does not alone establish, the calendar release record.

Examples explain a method. They do not predict prices or establish where a trading service is available. Check the named source before relying on future schedules.