September 11th Documents ToolkitIndependent project. Not an official City of New York website. Not legal advice.

Overview

New York City’s September 11th records

On September 8, 2026, the City of New York opened the September 11th Document Portal under a stipulation and order of settlement with 9/11 Health Watch, in two Article 78 proceedings before Justice James G. Clynes Stipulation and Order. The records are scanned PDFs, Bates-numbered on every page, with no titles and no dates. A Department of Investigation inquiry ordered by the City Council runs alongside the release and reports in July 2027.

24,441documents in the catalog capture of September 9, 2026 catalog summary
173,299pages, as the catalog counts them
36.6 GBof PDFs, by the catalog’s sizes
3collections: DEP’s 68 boxes, WTC 7, DORIS Giuliani
4,173distinct folder labels, many of them building addresses

Purpose

This toolkit was built so that New Yorkers, first responders, survivors and their families can read what the City’s records show about the air in Lower Manhattan after September 11, 2001. It also lets them check what the City has committed to in releasing those records. The official directory lists the records that prove presence for care and compensation, and who issues them.

The commitments, as stated

Quoted from the stipulation, the resolution, the September 8 transcript and release, and the Department of Investigation’s letters and page. Each quote opens its source.

The stipulation, so-ordered September 2026

Council Resolution 560-A, adopted July 14, 2025

The announcement of September 8, 2026

The Department of Investigation’s account

Announced commitments

The three commitments were announced separately and cover different fiscal periods. An announcement records a promise; the ledger follows each one through appropriation, contract, payment and delivery.

$34.2 millionRecords access · FY 2027 Mayor’s budget announcement
$4 millionDOI investigation · fiscal period unresolved Council announcement
$1 millionMemorial education · FY 2027 Council announcement

Obligations

What the settlement and Resolution 560-A require, and what was observed on a public surface on the date checked. Whether the City has complied is for the court to decide; it keeps jurisdiction until September 2027.

The obligations and what was observed
DateObligationSourceStatus (2026-09-09)
2026-09-08Portal launched with the records sought under FOIL plus other records of public intereststipulationobserved
2026-09-08Harding memo linked under "Documents of Interest"; FAQ explains how it was identifiedstipulationpartially observedTab previously observed; FAQ explanation read September 9; independent review pending.
Monthly, Sept 2026 – Aug 2027Law Department meets 9/11 Health Watch: documents and pages produced, sources, subjects; new search terms may be raisedstipulation ¶1upcoming
RollingAgreed search terms posted on the portaltranscriptnot observed on inspected surfaces
RollingPrivilege log of documents located but withheld, posted on the portalstipulation ¶7not observed on inspected surfaces
NowDCAS and Department of Education personnel designated to gather proof-of-presence records for City employees and former public-school studentspress releasepartially observedAnnounced; contact path not published.
2026-12-31DOI written status update to the SpeakerRes. 560-A §1upcoming
2027-06-30DOI written status updateRes. 560-A §1upcoming
2027-07-14DOI report: what administrations knew, a timeline of awareness, and the contrast with what was conveyed to the publicRes. 560-A §2upcoming
2027-09-08Twelve-month mark; proceedings dismissed with prejudice if the City has performed; the court keeps jurisdiction until thenstipulation ¶7–8upcoming

The rows are in scorecard.json, which the MCP serves as the doi_milestones tool.

The release watchdog

The portal’s Update History lists additions by agency portal, Update History. The watchdog records every document in the catalog. Each run makes one export, stores it unchanged and compares it only with an earlier accepted capture. A document present in one capture and absent from a later one is recorded as absent. The capture does not show whether it was removed, replaced or withheld.

Written by the watchdog script (scripts/watchdog.py). A capture that shrinks unexpectedly, arrives malformed, or repeats a document ID is held for review instead of published, and the pointer keeps the last good record.

The toolkit