A mayor announces a major housing initiative. A press release says it will create 100,000 homes. A headline repeats the figure. The public question is not whether the announcement sounds consequential. It is: what document makes the commitment real?
That is where a guide to government source documents becomes useful. Government produces a constant stream of statements, plans, data releases, directives, and reports. They do not carry the same weight. A press conference can signal intent; an adopted budget can allocate money; a contract can identify a vendor; an implementation report can show whether the work actually happened.
For residents, journalists, advocates, and public officials, source discipline is the difference between following politics and verifying government.
Start With the Claim, Not the Document
Do not begin by searching broadly for “city housing plan” or “mayor budget.” Begin with a claim that can be tested.
For example: “The administration funded 500 new sanitation positions.” That claim has several components: the number of positions, the agency, the funding source, the fiscal year, and whether the positions were authorized, hired, or merely proposed. Each component may point to a different record.
This framing prevents a common error: treating an official statement as proof of implementation. Government language often blends proposed action, authorized action, and completed action. Those are separate statuses.
A useful first question is: What would count as evidence that this claim is true? If the claim concerns money, look for budget documents and financial plans. If it concerns a rule, find the executive order, agency rule, or legislation. If it concerns results, look for agency performance data, audits, procurement records, or implementation reports.
The Government Document Hierarchy
Official does not automatically mean conclusive. A mayoral press release is an official document, but it is generally not the strongest record for proving that policy has been funded or carried out.
Think of sources in terms of what they establish.
- Legal and binding records include laws, enacted budgets, executive orders, contracts, regulations, meeting minutes, and formal agency determinations. These documents establish authority, requirements, or obligations.
- Planning records include preliminary budgets, strategic plans, capital plans, environmental reviews, and agency proposals. They show what government intends to do, not necessarily what it will do.
- Operational records include staffing reports, expenditure data, procurement notices, performance dashboards, inspection records, and project updates. These are often the best evidence of execution.
- Interpretive or promotional records include press releases, speeches, newsletters, social posts, and talking points. They can identify a claim or announce a decision, but they require corroboration.
The hierarchy depends on the question. An executive order is the primary source for what a mayor directed. It is not necessarily proof that agencies complied. For compliance, the stronger evidence may be an agency report, budget allocation, contract award, or measurable outcome.
A Guide to Government Source Documents in New York City
New York City government is especially document-heavy because authority is distributed. City Hall, agencies, the City Council, the Office of Management and Budget, the Comptroller, the Public Advocate, borough presidents, and independent oversight bodies each publish records that answer different questions.
If you are tracking a mayoral promise, start by identifying the institution that controls the next step. A mayor may propose a program, but the Council may need to authorize legislation. The Office of Management and Budget may need to include funding in a financial plan. An agency may need to issue rules, hire staff, or procure a provider. The Comptroller may later review spending or register a contract.
This chain matters because a single announcement can create an inflated impression of completion. A program is not “kept” merely because it appeared in a speech. It may be proposed, funded, launched, partially implemented, stalled, modified, or abandoned. The documents should show which status applies.
For budget questions, distinguish carefully between the preliminary budget, executive budget, adopted budget, and later financial plan modifications. An item can be announced in January, reduced in April, adopted in June, and then altered again during the fiscal year. The latest document may be the most current, but the prior versions explain what changed and who made the decision.
Read the Date, Version, and Scope
Most document errors are not dramatic. They are errors of timing and scope.
Before relying on a record, check its publication date, effective date, reporting period, and version. A fiscal year report may describe spending through March, not through June. A dashboard may update monthly. A budget table may list planned headcount rather than filled positions. A contract notice may show an intended award before registration or performance begins.
Then identify the document’s scope. Does it cover the full city, one agency, one program, or a pilot? Is the number annual, cumulative, or projected over several years? Does “affordable housing units” mean units financed, started, preserved, completed, or occupied? Those terms are not interchangeable.
When a number looks unusually clean or unusually large, read the footnotes. The footnote may reveal that a total includes prior-year activity, a separate funding stream, or an estimate rather than an audited count. Footnotes are not decoration. They are often where the definition lives.
Build a Verification Chain
The strongest accountability work does not rest on one document. It builds a chain of evidence.
Suppose the administration claims it expanded a mental health program. A disciplined verification chain might begin with the announcement, then move to the adopted budget for funding, a procurement record or staffing plan for operational capacity, and an agency performance report for service delivery. If the program’s stated goal involves outcomes, such as reduced emergency-room use, examine whether the available data measures that result or merely counts enrollments.
This method produces fairer conclusions. It avoids dismissing a real policy change because final outcomes are not yet available. It also avoids awarding full credit for a promise that exists only in a press release.
Use precise labels. “Announced” means an official commitment was made. “Funded” means money was formally allocated. “Launched” means operations began. “Implemented” means the responsible entity put the policy into practice. “Kept” should be reserved for cases where the relevant commitment was substantially delivered, with evidence that matches the original promise.
Know When the Record Is Incomplete
Government records have gaps. Data may lag by months. An agency may publish totals without methodology. A contract may be registered while its deliverables remain unclear. Some documents are scanned PDFs, difficult to search, or posted without prior versions.
Do not fill those gaps with certainty. State what the record establishes and what it does not establish. “The budget includes $10 million for the program” is a stronger and more accurate finding than “The program is fully funded and operating” when no operational evidence is available.
When a needed record is not public, a formal records request may be appropriate. But a missing document is not automatic evidence of wrongdoing. It is an accountability item: a gap worth identifying, tracking, and revisiting.
There is also a trade-off between speed and certainty. A same-day briefing may rely on an executive order and an agency statement. A deeper assessment should wait for budget details, implementation guidance, and reporting data. Good civic reporting makes that distinction visible rather than pretending every conclusion has the same level of proof.
Create a Record That Others Can Check
A source-based finding should be reproducible. Record the exact document title, issuing body, date, relevant page or section, and the claim it supports. Preserve the document version when possible. Government pages can be updated, files can be replaced, and dashboards can revise historical figures without fanfare.
For each major claim, keep a short evidence note: what the document says, what it proves, and what remains unresolved. This is the basic discipline behind useful public scorecards. It lets readers challenge a conclusion on the evidence rather than on partisan assumptions.
At ReviewMamdani.com, that distinction is central to tracking public commitments: the question is not whether a policy sounds good or bad, but whether the record supports a measurable status.
Government is easier to follow when every claim has a paper trail. Start with the promise, find the authority, trace the money, check the implementation, and leave room for what the evidence cannot yet prove.