Direct answer and scope

The official crematory PDF publishes county, cemetery number, name, address, city, state, ZIP code, and telephone number. When two or more of those fields appear not to align, the conservative response is to preserve the exact values as published, identify the row by its cemetery number, and mark the internal conflict as unresolved. No individual field should be elevated merely because it appears more familiar or geographically plausible.

The cemetery number functions as the row’s published administrative identifier. It is useful for locating and distinguishing the row, but it does not independently establish present status, available services, ownership, direct public access, or a relationship with a funeral arranger. The other fields retain similarly limited roles: they report what the dated PDF says and do not independently settle facts outside that record.

The source’s revision and verification dates belong with the row interpretation. The endpoint remained reachable on August 26, 2026, while serving a PDF revision dated December 11, 2024. Reachability on the later date does not transform the older revision into evidence of a recent update or present facility conditions.

Comparison from the supplied verified evidence
Evidence componentPreserved stateInterpretation boundary
Exact row locatorPublished cemetery numberAdministrative row identifier only
County and street addressExact values from the dated rowNo location correction from plausibility
City, state, and ZIP codeSeparate published field valuesNo enrichment from outside sources
Telephone numberExact published field valueDoes not establish identity or services
Source revisionDecember 11, 2024Not evidence of a recent update
Endpoint verificationChecked August 26, 2026Confirms endpoint reachability on that date
Unresolved conflictConflicting or unknownNo corrected value or status conclusion

How to use the supplied evidence

Begin with the exact row from the validated PDF snapshot. Preserve its cemetery number, name, county, address, city, state, ZIP code, and telephone number exactly as published. Record the December 11, 2024 source revision and the August 26, 2026 verification date separately so that the age of the underlying record is not obscured by the later endpoint check.

Compare fields without normalizing away differences. A county-city mismatch, an address that appears inconsistent with the ZIP code, or a telephone field associated elsewhere with another name remains a field-level discrepancy. A map result, geocoding output, website, business profile, advertisement, submitter statement, or another directory row is not a substitute for the exact official row and should not overwrite it.

Keep facility evidence separate from arranger evidence. A shared name, brand, address, telephone number, or marketing statement does not independently establish that a funeral firm owns a crematory, operates one at the same location, or routes cases to it. A documented arranger-to-crematory chain requires distinct evidence for the arranger’s identity, the physical facility, and the case-specific authorization. Any unsupported link remains unknown.

Use explicit evidence states rather than implied resolutions. A link or field can be described as documented, conflicting, or unknown, with its supporting source and verification date. That classification is an editorial evidence model, not a state-issued relationship designation or a conclusion about what occurred in a particular case.

Decision framework

First, confirm that the exact row is present in the validated December 11, 2024 PDF snapshot and can be located by its published cemetery number. Next, retain each official field independently. Do not reconstruct the row from fragments found in other entries, even when names or contact details resemble one another.

Second, determine whether the apparent discrepancy exists within the official row or between that row and an outside source. An internal discrepancy should be recorded without choosing a preferred field. A difference involving an outside source should leave the official row unchanged because the allowed use of the PDF is to reproduce its exact published fields without enrichment from names, maps, marketing, or third-party material.

Third, examine whether current primary evidence expressly resolves the particular fields in conflict. Resolution evidence must address the specific row and values rather than rely on a same-name match or shared contact detail. If no such evidence is supplied, retain the original values and the unresolved state. Do not convert the mismatch into a conclusion about facility identity, a new address, a move, a status change, or a service relationship.

Finally, keep any arranger relationship analysis separate. Even a fully resolved facility address would not, by itself, document ownership, onsite operation, or case routing. Those links require their own current official record or case-specific primary document, and each missing link remains unknown.

Evidence limits and unresolved questions

The measured 48 rows across 30 counties describe only the dated PDF snapshot. Those figures do not represent a present count of active facilities, prove statewide completeness, or establish the availability, quality, public accessibility, or operating condition of any listed location. A row’s presence supplies a dated set of fields; it does not answer every question about the facility.

A blank, missing, inaccessible, partial, unmatched, stale, or conflicting field remains unknown for the unresolved point. It should not be transformed into a corrected address, a different county, a facility identity, or a present status. The same limitation applies when the exact source revision, filename, columns, control totals, or endpoint characteristics cannot be validated against the expected snapshot.

Questions about ownership, onsite cremation, affiliation, or case routing also remain separate from location-field reconciliation. Similar names, addresses, telephone numbers, brands, or promotional wording do not establish those relationships. Distinct arranger identity evidence, physical-facility evidence, and case-specific authorization evidence are required before a chain can be described as documented.

Evidence behind this page

Each point below is restricted to what the cited primary source supports. Administrative listing status is not a quality endorsement.

Claim-level evidence used on this page
EvidenceSupported pointScope and limitation
Evidence 1Display 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 2Keep 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 3Publish 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 4Reproduce 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 5State 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

What happens if county, city, state, ZIP, or address fields appear inconsistent?

Each value remains attached to the exact dated row as a separate evidence state. The row should be identified by its published cemetery number, and the inconsistency remains unresolved unless current primary evidence specifically reconciles the conflicting fields. The source revision and verification date should remain visible with that interpretation.

Can the directory silently select the field that looks most plausible?

No. The allowed use of the official PDF is to reproduce its exact published fields without enriching them from names, maps, marketing, or third-party sources. Apparent plausibility does not supply primary evidence for replacing one official field with another value.

Can a map, geocoder, website, or business profile overwrite the official row?

No. Those materials cannot overwrite the exact county, address, city, state, ZIP code, or telephone value published in the official row. If an outside value differs, the discrepancy remains separate and unresolved rather than becoming a substituted official value.

Does a field conflict prove that the facility moved, closed, or lacks a licence?

No. The dated PDF fields and cemetery number do not independently establish present status. The snapshot’s row count and county coverage also do not establish active-facility totals or current operating conditions. A conflicting location field therefore remains a conflict, not evidence of a broader status conclusion.

Can a corrected-looking value establish service area, operation, or current availability?

No. A value that appears corrected does not establish services, operating condition, public access, ownership, or an arranger relationship. Shared names, addresses, telephone numbers, brands, or marketing statements also do not independently document ownership, onsite operation, or case routing.

What happens when exact row, revision, field states, or primary resolution evidence are missing?

The affected point remains unknown or unresolved. No corrected value, facility identity, relationship, location, or present status should be derived from missing evidence. Where an arranger-to-crematory chain is at issue, arranger identity, physical-facility evidence, and case-specific authorization must remain separate, and every unsupported link stays unknown.

Primary sources

  1. New York State Department of Health, Opened Funeral Firms Reports Verified 2026-08-26
  2. New York State Department of Health, 10 NYCRR 77.5 Funeral Establishments Verified 2026-08-26
  3. New York State Department of State, Division of Cemeteries, Crematory Frequently Asked Questions Verified 2026-08-26
  4. New York State Department of State, Authorization for Cremation and Disposition Instructions Verified 2026-08-26
  5. New York State Department of State, Find a Crematory By County Verified 2026-08-26