The short answer: verifying a January 2026 release is mostly a matching exercise. You take the release name and the reference period, then check that both appear together in the schedule before you treat any figure as published. The schedule lists titles and periods; it does not give values, so your check has to stop at what was scheduled.
This checklist is built only from the release titles and periods in the source list. Where a step needs a number, it is labeled as a hypothetical example.
Step 1: Match name and period separately
Most errors come from fixing only half the pair. A title can repeat across months while the period moves forward, and a period can repeat across titles. Record both fields as text before comparing anything.
Example of the pattern: Job Openings and Labor Turnover Survey appears twice in the list, once for November 2025 (c01) and once for December 2025 (c12). The same survey, two different periods. If you only searched the survey name, you could attach the wrong period to a figure.
State Employment and Unemployment (Monthly) shows the same repetition: November 2025 (c02) and December 2025 (c08). Import and Export Price Indexes likewise: November 2025 (c03) and December 2025 (c14).
Step 2: Build a two-column ledger
Write the release name in one column and the period exactly as stated in the other. Do not paraphrase periods such as "Annual 2024" into a date range. The source uses several period formats, and normalizing them too early hides differences.
| Release (as stated) | Period (as stated) |
|---|---|
| Job Openings and Labor Turnover Survey | November 2025 (c01) |
| Job Openings and Labor Turnover Survey | December 2025 (c12) |
| State Employment and Unemployment (Monthly) | November 2025 (c02) |
| State Employment and Unemployment (Monthly) | December 2025 (c08) |
| Import and Export Price Indexes | November 2025 (c03) |
| Import and Export Price Indexes | December 2025 (c14) |
| Employer Costs for Employee Compensation | September 2025 (c17) |
| Quarterly Data Series on Business Employment Dynamics | Second Quarter 2025 (c18) |
The table is a selection, not the full list. What matters is the method: one row per release-period pair, no merging.
Step 3: Separate monthly, quarterly and annual periods
The list mixes three period types. Monthly items include State Job Openings and Labor Turnover for November 2025 (c09) and for December 2025 (c16). Quarterly items include Business Employment Dynamics for Second Quarter 2025 (c18). Annual items include Occupational Requirements in the United States for Annual 2025 (c05), Usual Weekly Earnings of Wage and Salary Workers for Annual 2025 (c10), and Employer-Reported Workplace Injuries and Illnesses (Annual) for Annual 2024 (c06).
Work Experience of the Population (Annual) is listed for Annual 2024 (c07), and Census of Fatal Occupational Injuries for Annual 2024 (c15). Notice that not every annual release refers to the same year. That is exactly the kind of mismatch a ledger catches.
Step 4: Check the schedule's own metadata
The page carries a last-modified line reading "Last Modified Date: January 20, 2026" and a navigation note for February 2026 Month View | List View (c11). Treat that as page metadata, not as the publication date of any individual release. A schedule page can be edited after a release without changing any release's period.
Hypothetical example of why this matters: if you assumed every item on a page last modified January 20, 2026 was published that day, you would assign the same date to annual 2024 releases and to December 2025 monthly releases. The source does not support that inference.
Step 5: Keep a status column
Because the schedule shows what was planned, not what was published, add a status field with fixed values: scheduled, confirmed, revised. The source list supports only scheduled. Anything beyond that needs a separate record you can point to.
- Scheduled: title and period appear in the list.
- Confirmed: you have separately matched the release to its own page.
- Revised: the period or value changed in a later record.
Calculation note: if you are tracking ten release-period pairs and only the scheduled field is populated, your completion rate is zero confirmed, not ten. Count only rows where the status is confirmed.
What the source does not say
The list gives no release dates, no times, no values, no units, no revisions, and no confirmation that any item was published. It also does not state which items are headline versus secondary. The order of items in the source is not a priority or importance ranking, and nothing in it establishes market impact.
Two items are worth flagging as open questions rather than answers: the State Job Openings and Labor Turnover entries (c09, c16) sit alongside the national survey but are separate releases, and the annual 2024 and annual 2025 items cover different years, so they cannot be compared as if they were the same cohort.
A compact checklist
- Copy the release name and period as written; do not merge fields.
- Check for duplicate titles with different periods.
- Classify the period as monthly, quarterly or annual.
- Verify the annual year, not just the word "Annual".
- Treat the last-modified line as page metadata only.
- Add a status column and count only confirmed rows.
- Log any claim that needs a value as missing until you have a source for it.
That last point is the discipline the schedule rewards. It tells you exactly which release-period pairs to look for, and it tells you nothing about their contents. Verifying means closing that gap with a separate record, one row at a time.