Read an animal-program audit without losing the response

Where should you start reading an audit report?

To read an audit without losing the agency’s side, keep four layers apart: the findings, the recommendations, the agency’s written response, and the review team’s rebuttal, each tied to its date. Read the document itself first, before any summary of it. The City Comptroller’s review of the city’s animal population control efforts lays out a review period of July 1, 2022 through June 30, 2025, a set of numbered recommendations, and a formal agency response from the Department of Health and Mental Hygiene (DOHMH).

Reading it in that order matters. The report follows a set sequence: findings, then recommendations, then the agency’s reply, then a review team comment answering that reply.

Skipping to a headline finding and treating it as the final word misses the back-and-forth built into the document. DOHMH generally agreed with recommendations 6 and 8, partially agreed with 7, and either disagreed with or called unnecessary the remaining six: 1, 2, 3, 4, 5 and 9. That mix of responses is itself part of the record, not a footnote to it.

The report states that DOHMH does not publicly report core program data, including the number of spay and neuter surgeries performed, broken down by species and sex.

Before drawing conclusions from any single page, check where it sits: is it a finding, a recommendation, or DOHMH’s reply to a recommendation? Each carries different weight as evidence, and the report keeps them separate for a reason.

Separate the layers

A public-records audit like this one has three separate layers, and mixing them together is the fastest way to misread it. The first layer is the review team’s factual findings, drawn from records and interviews. The second layer is the review team’s recommendations, meant to close gaps the findings turned up.

The third layer is DOHMH’s response, written comments submitted after the review team shared a Draft Report.

The city review lays out this timeline: A summary of preliminary findings went to DOHMH on December 29, 2025. Agency officials raised concerns and asked for a meeting on January 7, 2026. That meeting happened January 22, 2026, and DOHMH supplied more information on January 29, 2026. A Draft Report followed on March 11, 2026, and DOHMH’s written response arrived March 31, 2026.

Each date marks a different layer’s contribution. The findings layer doesn’t change after the fact. The response layer is where the agency pushes back, agrees, or reframes.

The review team then adds its own comment on top of DOHMH’s response in several places. That forms a fourth, thinner layer: rebuttal.

Treating a recommendation as an admitted fact, or treating DOHMH’s disagreement as proof a finding was wrong, wipes out the distinctions the report itself keeps in place. Read each layer against the one before it, and note when the review team says outright that it stands by its original conclusion.

Track the disputed point

The clearest disputed point in the record involves recommendation seven, on monitoring the ASPCA contract. DOHMH’s written response calls the recommendation “not needed.” The same response then says the agency will “formalize a monitoring plan that is consistent with the contract scope of services and can consider making spay neuter numbers public.”

That’s a response that disagrees with the label while conceding the substance. The review’s own account of this recommendation points out exactly that gap between what DOHMH says and what DOHMH commits to do.

A related dispute involves fee structure. DOHMH’s response argues that New York City’s dog license fees are low compared to other municipalities, and that this gap explains why the Program’s fee structure falls short of what it needs to raise.

The review team countered that DOHMH does not identify the sources for the data used in its comparative analysis. It offers no opinion on the accuracy of that claim. Still, the team added that DOHMH’s argument reinforces the review’s own finding that the program needs additional funding streams.

Both points stay unsettled. One is a recommendation disputed on its label but partly accepted in substance. The other is a factual claim offered without sourcing, one the review team declined to validate.

Reading the audit for disputes means finding where the agency’s words and its promised actions pull apart, and where a claim shows up without the data behind it.

Keep the time boundary

The review’s findings apply to a fixed window: July 1, 2022 through June 30, 2025. Anything DOHMH did, changed, or committed to after that period sits outside the reviewed record, even when it shows up inside the same document.

That distinction matters because the response process itself ran past the review period. The preliminary findings went to DOHMH in December 2025. The meeting between agency officials and the Deputy Comptroller happened in January 2026. DOHMH’s written response landed March 31, 2026, roughly nine months after the review period closed.

Commitments made in that response, such as DOHMH’s stated willingness to formalize a monitoring plan, describe intended future action. They are not findings about what happened during the audited period, and the report treats them as such by keeping the response in its own labeled section rather than folding it into the findings.

The review also notes that DOHMH’s response included information the review team never received, at any point before or after the December 2025 findings summary, including after a meeting at which DOHMH indicated it would be provided. The consequence is stated plainly: the team was unable to examine the validity of that information, and offers no opinion on its validity or its potential impact on the review’s findings.

That timing detail is worth holding onto on its own. Information supplied late in the process, after the window the findings actually cover, counts differently than information available while the review was underway.

Reading the document with that boundary in mind keeps a promised future change from being mistaken for a verified past outcome.

Read for the unanswered question

The report leaves a specific gap open: what the city’s animal population control program actually produces, in numbers the public can check. The review states that DOHMH does not publicly report the total number of spay and neuter surgeries performed under the Program, broken down by species and sex, nor the zip codes of eligible owners who received sterilization services, nor a breakdown of recipients by eligibility category.

It also doesn’t report how many requested sterilizations went undone because of funding or capacity limits.

That absence extends to a wider population metric. The review points to the Shelter Animals Count’s Altered Status Data Report, which put sterilized dog and cat intakes at shelters at 22.3% and 22.0% in 2023, both down from 2019. The city does not publicly report this figure for its own shelter population, and the review calls that omission a gap in measuring whether population control efforts are working.

None of that is a claim that the program succeeds or fails. It’s a documented absence of the data that would let anyone outside DOHMH check either outcome.

The review records a target of 12,000 surgeries set in the ASPCA contract, and puts the number of surgeries the collected surcharge revenue would fund at 7,607 over the three-year period, far short of the target. Read the table carefully before quoting that number: the review derives 7,607 from the dog licensing surcharge revenue collected, at $125 a surgery. It’s a funding calculation, kept separate in the table from an actual count of completed operations. DOHMH’s own response “acknowledges that the number of sterilization surgeries has been lower than budget.” The document doesn’t say what that shortfall means for animals in the city; the record stops at the acknowledgment.

That’s the open question worth carrying forward: whether future reporting closes the data gap the review identifies, or whether the same categories stay unreported next cycle.