Select the California Funeral License File Before Matching an Establishment Record

Direct answer and scope

Use Funeral_Data00.xls as the documented source file for a candidate California funeral-establishment directory record in the August 25, 2026 snapshot. Within that file, require the exact Funeral Director Establishment category before treating a row as establishment-license evidence. A row from Cemetery_Data00.xls, a Funeral Director category row, or another category does not satisfy that source-and-category requirement.

The archived funeral file contained 6,137 records and had the SHA-256 checksum 62f35460f34dd8748672f889839c03dde187891922d0837f08b615b4bcf3be50. The separately archived cemetery file contained 6,688 records and had the SHA-256 checksum 20b784291214b01de0670e242d36971c050b5a0be481f87dcce8f900a0ce47a4. Both files were updated by DCA on August 1, 2026 and obtained for the fixed snapshot on August 25, 2026. These values identify the archived inputs used for the workflow; they do not turn the snapshot into a live source.

The control CSV reports 1,127 Funeral Director Establishment rows across all raw license statuses in that snapshot. The number is a control total for that category and those archived inputs. It is not a status-filtered count, a count of distinct businesses, a measure of consumer access, or a service measure. Any narrower count would require its own disclosed filter and coverage note.

How to use the supplied evidence

Start by confirming the archived filename, file update date, snapshot date, record total, and checksum. These provenance fields answer whether the candidate was drawn from the same fixed source artifact used by the directory workflow. A matching filename without a matching checksum is not the same archived byte sequence. A matching checksum identifies the archived file, but it does not show that every row remained unchanged in the live licensing system after August 1, 2026.

Next, inspect the license-type field and require Funeral Director Establishment exactly. Do not collapse that category into Funeral Director. The Cemetery and Funeral Bureau regulates funeral establishments and funeral directors as separate categories, and each category must be checked on its own terms. After the category is confirmed, retain the exact license number and raw status rather than translating the status into a broader editorial conclusion.

The documented public-disclosure layout also includes an individual-or-organization indicator, public-address fields such as City and County, dates, and raw license status. Preserve those values as supplied. City and County are components of the archived public address of record; they do not establish where arrangements, preparation, or other services occur.

For a current identity check, compare the candidate with the DCA license lookup and record the exact license type, license number, displayed status, and date of verification. A name by itself is not enough to connect records. If the lookup does not return an expected result, record the unresolved check rather than treating the absence as a definitive finding.

Decision framework

Accept a candidate for establishment-level matching only when the source artifact and category both pass. The source test requires Funeral_Data00.xls from the identified snapshot, supported by the corresponding update date, record total, and checksum. The category test requires an exact Funeral Director Establishment value. The identity test then uses the license number and other documented fields to distinguish the intended record from similarly named rows.

Withhold the match when the candidate comes from Cemetery_Data00.xls or another DCA file, even if a business name, city, county, or street information appears similar. Also withhold it when the row belongs to the Funeral Director category rather than Funeral Director Establishment. Similar fields can support further checking, but they do not merge separate datasets or regulatory categories into one identity.

Treat filename, checksum, layout, and category as independent controls. If the filename is known but the checksum is not, the exact archived input has not been established. If the file is established but its layout cannot be mapped to the documented fields, the row should not be normalized as though the mapping were known. If the category is missing, altered, or ambiguous, the candidate should remain unresolved rather than being reassigned from contextual clues.

Once those controls pass, preserve the row as snapshot evidence and perform a separate current lookup. Record the dates of the snapshot-based review and current lookup independently. This keeps the historical source claim distinct from what the licensing system displayed when the later check was performed.

Limits and what to verify next

A correct source-and-category match establishes only that the candidate corresponds to the documented establishment category in the identified monthly snapshot. The public-disclosure fields do not establish ownership connections, manager relationships, service offerings, service timing, consumer access, or quality. Those subjects require separate, appropriately matched evidence and should not be inferred from a name, address, category, or raw status.

Recheck the DCA license lookup before relying on a displayed status because the archived file is not real-time. Capture the exact license type, number, displayed status, and verification date from an identity-matched result. Status can change, and an expected result that is not found should remain an unresolved search rather than a categorical statement about the entity or its regulatory history.

A verification worksheet can keep the checks reproducible. Useful fields include the establishment license type and number, raw status, public address of record, any managing-director evidence field, the source references used, and separate dates for each check. The worksheet is an editorial recordkeeping aid; readers should recheck the relevant California sources for current information.

When any required source element remains uncertain, stop before creating an establishment match. Record whether the unresolved element is the filename, checksum, update date, snapshot date, record layout, category, license number, identity match, or current lookup. That approach preserves the distinction between verified snapshot fields and matters that still need confirmation.

Evidence behind this page

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