Direct answer and scope
A higher row count does not prove that facilities opened. A lower row count does not prove that facilities closed, relocated, merged, split, or lost a licence. The arithmetic describes only a difference between two reported row totals. It does not supply the identity of the rows behind that difference or establish the reason for any change.
The relevant New York snapshot is the Department of State PDF revision dated December 11, 2024, reached through the official endpoint checked August 26, 2026. Its measured total is 48 physical-crematory listing rows in 30 counties. The revision date and verification date must remain separate: a reachable endpoint on the later date does not turn the older PDF into a current operating-status roster.
The source fields support a controlled row comparison using county, cemetery number, name, address, city, state, ZIP code, and telephone number. They do not, standing alone, establish current operation, capacity, services, ownership, direct-to-public access, or an arranger relationship.
How to use the supplied evidence
First preserve the identity of each source revision, including its revision date and the date on which the endpoint was checked. A later verification date is not a substitute for a later source revision. The earlier and later snapshots must therefore be recorded as distinct evidence states rather than blended into one date.
Next preserve the raw row count for each exact snapshot. A count can be compared as an aggregate measurement, but it cannot be used to publish a changed-row list unless the underlying rows have been matched deterministically. A difference in totals may coexist with duplicate, renamed, reformatted, added, removed, incomplete, or unresolved rows.
For row-level comparison, use the published fields and the cemetery number as the administrative row identifier supplied by the PDF. Do not enrich or resolve a row from a shared name, address, telephone number, marketing statement, map, or third-party source. If identity is not deterministically established, retain the match as unresolved.
Lifecycle evidence is a separate state. Even a resolved row identity would not, by itself, establish current operation, a closure, a relocation, a merger, a split, a licence change, services, capacity, or availability. Those conclusions require the appropriate current primary evidence; absent that evidence, the relevant point remains unknown.
Decision framework
A count comparison can be treated as resolved only when both exact complete source revisions are available and their identities are preserved. The raw totals should then be reported separately from any row-level result. The totals answer how many rows were measured in each snapshot; deterministic matching answers whether particular published rows correspond.
The row-level state should remain unknown when a row is missing, inaccessible, conflicting, incomplete, stale, or unmatched. It should not be converted into zero, false, added, or removed merely because the aggregate count changed. A changed field should likewise remain a field-level difference until the evidence supports a narrower interpretation.
A lifecycle state should be assessed independently from the row state. A matched row is not the same thing as a currently operating facility, and an unmatched row is not the same thing as a closure. The dated Department of State snapshot does not supply a live operating-status conclusion, so the current lifecycle state cannot be taken from that count alone.
Any documented arranger-to-crematory chain also requires separate arranger identity evidence, separate physical-facility evidence, and case-specific authorization evidence. Each link can be documented, conflicting, or unknown. A shared name, brand, address, telephone number, or marketing statement does not resolve ownership, onsite operation, or case routing.
| Evidence state | What is recorded | What remains unresolved |
|---|---|---|
| Snapshot identity | Exact source revision and endpoint verification date | A later source revision if not supplied |
| Aggregate count | Measured rows in each exact snapshot | Which physical rows account for any difference |
| Row identity | Deterministic matches using published fields and cemetery number | Unmatched, duplicate, renamed, reformatted, or conflicting rows |
| Lifecycle evidence | Current primary evidence addressing the specific event | Opening, closure, relocation, merger, split, licence, operation, capacity, service, or availability without that evidence |
| Chain evidence | Separate arranger, physical-facility, and case-specific authorization links | Ownership, onsite operation, or case routing when a link is missing |
Evidence limits and unresolved questions
The official PDF revision is useful for describing what was listed in that dated snapshot, including its measured 48 rows and 30-county coverage. It does not establish that every relevant facility is currently listed, that every listed row is currently operating, or that a listed facility offers a particular service or has particular capacity.
A missing row in one snapshot can have several unresolved explanations at the evidence level, including a row-identity problem, a formatting or naming difference, an incomplete source, or a source change whose underlying event has not been documented. The permitted conclusion is that the comparison is unresolved, not that a facility opened, closed, moved, merged, split, or lost a licence.
The source age is material because the endpoint checked August 26, 2026 served a revision dated December 11, 2024. The two dates must not be shortened into a claim that the listing is current, recently updated, active, licensed, complete, open, or available.
The same separation applies to relationships. A funeral firm’s name or address appearing near a crematory name does not establish ownership or onsite operation. Missing evidence leaves the relationship unknown and does not support an accusation, affiliation claim, or negative inference.
Questions people ask
The questions below apply the same evidence boundary to common interpretations of a changed row total. They distinguish a measured snapshot difference from a conclusion about a physical facility or its present status.
Evidence behind this page
Each point below is restricted to what the cited primary source supports. Administrative listing status is not a quality endorsement.
| Evidence | Supported point | Scope and limitation |
|---|---|---|
| Evidence 1 | Display documented, conflicting, or unknown for each evidence link and show the source and verification date supporting that state. | This is a conservative editorial evidence model, not a state-issued relationship status, legal conclusion, or guarantee that the documented route was ultimately used. |
| Evidence 2 | Keep an arranger-crematory relationship unknown until a current official record or case-specific primary document supports it. | This is a fail-closed editorial rule; do not publish an outsourcing accusation, ownership claim, onsite claim, affiliation, or negative inference from missing evidence. |
| Evidence 3 | Publish exact rows from the immutable validated PDF snapshot with the source revision date, verification date, measured row count, measured county coverage, source URL, and interpretation limit. | The measured 48 rows and 30 counties describe this dated PDF snapshot, not active-facility totals, current statewide completeness, quality, availability, public access, or a live operating-status roster. |
| Evidence 4 | Reproduce those exact published fields and identify each row by its cemetery number without enriching it from names, maps, marketing, or third-party sources. | A cemetery number is an administrative identifier as published in this PDF; it does not by itself prove current status, services, ownership, direct-to-public access, or an arranger relationship. |
| Evidence 5 | State listed in the official DOS PDF revision dated 2024-12-11 and verified at the current endpoint on 2026-08-26. | Do not shorten that wording to currently active, currently licensed, currently open, complete, or recently updated; stop publication if the source hash, filename, columns, control totals, or endpoint changes before review. |
Questions people ask
Does a higher crematory row count prove that facilities opened?
No. It proves only that the later measured snapshot contains a higher number of listing rows than the earlier measured snapshot, if both counts are exact and comparable. It does not identify the changed rows or establish an opening, operation, licence, service, capacity, or current availability.
Does a lower count prove closure, relocation, merger, or loss of licence?
No. A lower count does not by itself establish any of those events. The row difference remains unresolved without deterministic identity comparison, field-level change evidence, and current primary lifecycle evidence.
Can a count delta show which exact physical rows changed?
No. An aggregate difference cannot show the identity of the rows behind it. Exact row-level conclusions require the complete source revisions and deterministic comparison of the published fields, including the cemetery number and location fields.
How do duplicate, renamed, reformatted, added, removed, or unresolved rows affect comparison?
They prevent the count from being treated as a lifecycle result unless the row identities and changes are established. Unknown, missing, conflicting, incomplete, inaccessible, or unmatched evidence remains unresolved rather than being converted into an added or removed facility.
Can the dated snapshot counts establish current operation, capacity, services, or availability?
No. The 48-row and 30-county measurements describe the December 11, 2024 PDF snapshot. They are not active-facility totals, a live operating-status roster, or evidence of current capacity, services, or availability.
What happens when a paired revision or deterministic row-level comparison is absent?
The comparison remains unresolved. No delta interpretation, changed-row list, or lifecycle conclusion should be published when the exact paired revisions, deterministic row matching, field-level change evidence, or current primary lifecycle evidence is absent.
Primary sources
- New York State Department of Health, Opened Funeral Firms Reports Verified 2026-08-26
- New York State Department of Health, 10 NYCRR 77.5 Funeral Establishments Verified 2026-08-26
- New York State Department of State, Division of Cemeteries, Crematory Frequently Asked Questions Verified 2026-08-26
- New York State Department of State, Authorization for Cremation and Disposition Instructions Verified 2026-08-26
- New York State Department of State, Find a Crematory By County Verified 2026-08-26