Direct answer and scope

Delinquent and Inactive records are not automatically included or excluded merely because the source file contains those values. Every derived directory view must disclose its own literal rule: the exact license type in scope, each raw status accepted, each raw status excluded, and the treatment of blank or otherwise unmatched values. Without that declaration, the all-status source cannot answer whether a particular subset contains either category.

The scope begins with the official Funeral Director Establishment license type. For the August 25, 2026 snapshot, the all-status control contains 1,127 records of that type. The control includes every raw status represented in the source and is used to test whether the records accounted for by a subset and its exclusions reconcile to the source total. It is not a substitute for reporting the subset count or its filter.

The public-disclosure snapshot was obtained August 25, 2026, from Funeral_Data00.xls, which DCA updated August 1, 2026. The full file contained 6,137 records. Its archived bytes are identified by the SHA-256 checksum 62f35460f34dd8748672f889839c03dde187891922d0837f08b615b4bcf3be50. These provenance details identify the source used for normalization; they do not show that an individual record remained unchanged after the file update.

How to use the supplied evidence

Start with the source record without rewriting its status. Retain the exact DCA license type, license number, and raw status value. If a directory also uses a normalized label for display or filtering, document the mapping beside the original value. The raw value remains necessary because it lets a reader or auditor reproduce the decision without guessing what a normalized category means.

Next, record the snapshot date and DCA update date. DCA states that its public-disclosure files are refreshed automatically at the beginning of each month, so the file is a dated dataset rather than a live lookup. City and County may be used as the raw public-address fields documented in the archived record layout. Those fields should remain identified as address-of-record data and should not be expanded into claims about where services occur.

Then apply the declared filter to every in-scope establishment record. Count each included raw status, each excluded raw status, and any blank or unmatched value separately. The sum of those groups should reconcile to the 1,127-record all-status control. If it does not, the subset should not be treated as reconciled until the discrepancy is identified. Reconciliation confirms arithmetic coverage of the dated control; it does not validate every underlying field.

For an entity-level check, use an identity-matched official lookup result rather than a name match by itself. Capture the exact license type, number, displayed status, official source, and date checked. The California Cemetery and Funeral Bureau directs consumers to verify the license status of the funeral establishment and funeral director they plan to use. Because status may change, the lookup date is part of the evidence.

Decision framework

For each directory view, first name the filter question precisely. A view limited to one raw value must say which value it accepts. A view containing multiple values must list all of them. A view that excludes a value must name that exclusion directly. General labels are insufficient when they conceal how Current, Delinquent, Inactive, blank, or unmatched source values were handled.

Second, keep source classification separate from editorial interpretation. Current, Delinquent, and Inactive are documented raw status values. They may be used as literal filter inputs, but they should not be remapped into conclusions that the DCA dataset does not provide. The directory decision is therefore limited to whether a record satisfies the disclosed rule for a dated view.

Third, test coverage against the control. Begin with 1,127 all-status Funeral Director Establishment records, partition them according to the disclosed rule, and verify that included, excluded, blank, and unmatched groups account for the control total. Report the result as a reconciliation to the August 25, 2026 snapshot of the file updated August 1, 2026. A later snapshot requires a new control and a new reconciliation.

Finally, preserve uncertainty instead of forcing a record into a category. A blank status or a value outside the named rule should be reported as unmatched unless the rule expressly states another treatment. Changing or broadening the rule requires a newly documented subset count. This fail-closed approach prevents an unexplained source value from being silently absorbed into either side of the filter.

Limits and what to verify next

A status filter answers only a record-selection question. The public fields do not establish quality, availability, ownership links, manager relationships, or the services offered at an address. The public address of record also does not establish a service location or service area. These matters require separate, current evidence and should not be inferred from inclusion in or exclusion from a directory subset.

The snapshot checksum identifies the archived file bytes, while the update and retrieval dates identify the version used. Those controls do not prove that every record stayed current, complete, or correct after August 1, 2026. Before relying on an individual listing, match the identity carefully and check the establishment and funeral director through the official DCA lookup.

A verification worksheet may record the establishment license type and number, raw status, public address of record, any managing-director evidence field, official sources, and separate check dates. Such a worksheet is an editorial aid for preserving what was observed. Users should recheck official sources when making a current decision, particularly because a name match alone is insufficient and an absent lookup result does not establish the absence of other official records.

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 1Report an exact official license type, license number, displayed status, official lookup URL, and verification date for an identity-matched record.Status can change; a name match alone is insufficient, and an absent search result is not proof that no license, complaint, or enforcement record exists.
Evidence 2Use the exact documented DCA public fields, including the raw City and County values within the archived public-address record, and identify the data as a monthly public-disclosure snapshot.The files are not real-time; public address of record is not proof of a service location or service area, and the fields do not establish quality, availability, ownership links, or manager relationships.
Evidence 3Disclose the exact snapshot date, DCA file update date, filenames, record totals, and checksums as provenance for normalized directory records.This is an immutable snapshot rather than a live DCA view; the checksums identify archived bytes but do not prove that every record remains current, complete, or correct after 2026-08-01.
Evidence 4Report 1,127 only as the raw all-status Funeral Director Establishment control total for the 2026-08-25 snapshot of the file updated 2026-08-01.This is not an active-establishment count, unique-business count, open-to-consumers count, service-availability count, or quality measure; any subset requires an exact disclosed status filter and coverage note.
Evidence 5Preserve the exact raw status and disclose any normalized mapping, filter criteria, snapshot date, file update date, and coverage before reporting a derived subset.Do not silently map a raw value to active, open, available, approved, safe, or recommended, and do not call the all-status control total an active count.
Evidence 6Offer a printable blank worksheet that prompts the user to copy exact official fields and record when each check was performed.The worksheet is an editorial aid, not an official certificate, legal advice, an authentication service, or proof that an arrangement is suitable; users must recheck official sources.
Evidence 7Describe fixed-term display inventory with clear sponsor labeling and no influence on inclusion, license fields, status labels, or default ordering.This editorial rule is not a statutory safe harbor; launch requires California legal review, written advertiser terms, disclosure QA, and rejection of compensation tied to funeral procurement or disposition recommendations.

Questions people ask

Does this California funeral-directory view include Delinquent records?

Only a view whose disclosed rule expressly includes the raw DCA value Delinquent may count those records in its subset. The 1,127-record control includes all statuses and therefore cannot, by itself, establish whether Delinquent records appear in a narrower view. Check the view’s exact included and excluded values and its reconciliation to the dated control.

Does it include Inactive records or silently remove them?

Inactive must be named explicitly as included or excluded. It should not disappear through an unstated normalization or default rule. If the published filter does not explain how Inactive is treated, the subset cannot be reproduced from the supplied status evidence.

Why must every subset name its exact raw-status filter?

The DCA layout documents distinct raw values, while the control total combines all statuses. Naming the exact filter allows the subset to be reproduced and reconciled without converting a source value into a broader interpretation. The disclosure should also identify the snapshot date, source update date, and coverage.

Can the 1,127 all-status control total be called an active-establishment count?

No. It is the raw all-status Funeral Director Establishment control total for the August 25, 2026 snapshot of the file updated August 1, 2026. Any narrower count requires an exact disclosed status filter and coverage note.

What happens when an official raw status is blank or outside the disclosed rule?

The value should be preserved and accounted for separately as blank or unmatched unless the disclosed rule expressly defines another treatment. It should not be silently assigned to an included or excluded status category. All groups should still reconcile to the dated all-status control.

Can a filter decide whether a funeral business is open, available, safe, recommended, or legally compliant?

No. A filter determines whether a source record satisfies a declared rule for a dated directory view. DCA public-disclosure fields do not establish quality, availability, service location, ownership relationships, or manager relationships. For a current identity-matched record, verify the exact license type, number, displayed status, official source, and check date through the official lookup.

Primary sources

  1. California Department of Consumer Affairs — Advanced License Search Verified 2026-08-26
  2. California Department of Consumer Affairs — Public Information Licensee Lists Overview and Record Layout Verified 2026-08-26
  3. California Department of Consumer Affairs — Public Information Dataset Box Folder Verified 2026-08-26
  4. California Cemetery and Funeral Bureau — Frequently Asked Questions Verified 2026-08-26
  5. California Legislative Information — Business and Professions Code Section 7680, License Display Verified 2026-08-26
  6. California Legislative Information — Business and Professions Code Article 6, Disciplinary Proceedings Verified 2026-08-26
  7. Federal Trade Commission — Endorsement Guides Questions and Answers Verified 2026-08-26