Direct answer and scope

Treat same-dated, different-content records as two preserved records with unresolved version context. Do not merge their fields, average their amounts, or decide that one is the operative copy solely because its effective date matches the other record.

The comparison should remain limited to the supported minimum fields: provider identity; GPL title; effective date; verification date; source URL or other source-location field; direct-cremation variant; container state; included services; outside charges; estimates; and unresolved fields. A field that is missing, unclear, or not aligned remains unresolved rather than being converted into a value.

The method can show where the records differ and which controlled rows cannot be compared. It cannot establish which document is current, whether a listed service or amount is available, whether either record is complete, or what a final charge would be.

How to use the supplied evidence

Begin with a separate identity block for each record. Preserve the provider identity exactly as documented, along with the document title and effective date. Add the date on which the record was verified and the source URL or source-location field associated with that record. These fields describe the evidence record; they do not resolve whether the document remains available or authoritative for a later purchase.

Next, preserve the service description at the level stated in each document. A direct-cremation entry should identify the exact variant being recorded and whether the container is supplied by the purchaser or is an alternative container described by the provider. Record the included services and containers as documented instead of treating similarly named packages as equivalent.

Record outside charges and estimates distinctly from stated service amounts. Do not turn an omitted, unclear, or unmatched amount into zero, an included item, or an exact total. Put the issue in unresolved fields and retain the supporting document for the next verification step.

This separation follows the document and pricing fields supported by the supplied federal and California guidance. It is a conservative normalization method for comparing records, not a regulator-issued completeness standard or a guarantee that a record contains every amount relevant to a transaction.

Decision framework

Use the following sequence for each pair of records. First, preserve both records and their individual identity, title, date, verification, and source fields. Second, identify the direct-cremation variant and container state in each record. Third, align only rows that describe the same controlled item or service. Fourth, place included services, outside charges, estimates, and unresolved fields into their corresponding record without filling gaps from the other document.

Only after that alignment should documented arithmetic be compared. A subtotal can be shown only for the same controlled rows and only from amounts actually documented in the evidence. If one record has an estimate, an outside charge, or an unresolved field where the other has a stated amount, the difference is an evidence difference as well as an arithmetic difference.

The controlled-row approach prevents a headline amount or package label from standing in for itemized services. It also keeps a lower documented subtotal from being treated as proof that the record is more complete, more suitable, higher quality, more available, or likely to produce savings. No conclusion about those matters follows from the subtotal alone.

Comparison from the supplied verified evidence
Comparison stepRecord ARecord BPermitted result
Identity and document fieldsPreserve provider identity, GPL title, effective date, verification date, and source fieldPreserve provider identity, GPL title, effective date, verification date, and source fieldKeep both records separate
Direct-cremation descriptionRecord exact variant, container state, and documented inclusionsRecord exact variant, container state, and documented inclusionsAlign only matching controlled rows
Charges and unresolved fieldsSeparate stated amounts, outside charges, estimates, and unresolved fieldsSeparate stated amounts, outside charges, estimates, and unresolved fieldsShow arithmetic only for aligned documented rows

Limits and what to verify next

A matching effective date does not establish that the two records contain identical information. It also does not establish present availability, current licence status, or the final amount of an outside charge. Those questions remain outside what the date field can prove.

Before relying on a comparison for a present decision, verify unresolved fields against current primary provider evidence. The verification should address the exact provider identity and document title, the effective date, the direct-cremation variant, the container state, included services, outside charges, estimates, and any field that could not be aligned.

Keep the source document and its verification date attached to the record being checked. If the primary evidence does not resolve an item, retain it as unresolved rather than borrowing a value from the other same-dated record. A comparison can expose an evidence gap without resolving that gap.

The supplied guidance supports itemized comparison and preservation of inclusion and evidence differences. It does not support a conclusion about a provider's present service availability, the completeness of either record, the quality or suitability of an option, or the final amount payable.

Questions people ask

The questions below apply to a conditional comparison in which both records are preserved and their supported fields are examined separately.

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 1Require provider identity, document type, effective date, verification date, and source URL in any future provider-price evidence record.A document date does not establish current availability, current license status, or the final amount of outside charges.
Evidence 2Record the exact direct-cremation variant, container state, documented inclusions, and source-dated amount rather than comparing unmatched package names.Do not infer which variant is available or suitable and do not supply a price absent from current primary provider evidence.
Evidence 3Use these fields as the minimum document-normalization schema for user entries and any future provider-evidence manifest.This is a conservative editorial methodology based on the cited document requirements, not a regulator-issued statistical standard or completeness guarantee.
Evidence 4Align two anonymous current documents by the same controlled rows and expose inclusion and evidence gaps before showing arithmetic differences.A lower documented subtotal does not prove completeness, availability, quality, suitability, savings, or a final price.

Questions people ask

How should two California cremation GPL records with the same effective date be compared if supported fields differ?

Preserve them as separate records, retain each record's identity and document fields, and align only the same controlled rows. Compare documented amounts only after recording variants, container states, inclusions, outside charges, estimates, and unresolved fields separately.

Which provider identity, GPL title, effective-date, verification-date, and source-URL fields should remain separate?

For each record, retain the provider identity, General Price List title, effective date, verification date, and source URL or source-location field. The effective date should not be used to merge the records or select one as the current copy.

How should direct-cremation variants, container states, included services, outside charges, estimates, and unresolved fields be aligned?

Record the exact direct-cremation variant and container state for each document, then preserve its included services, outside charges, estimates, and unresolved fields. Align only the same controlled rows; do not treat unmatched package names or missing amounts as equivalent.

Does a matching effective date establish identical content, current availability, or a final outside-charge amount?

No. A matching effective date does not establish identical content, present availability, current licence status, or the final amount of outside charges. Those points require current primary provider evidence where they remain relevant.

Can a lower documented subtotal establish completeness, quality, suitability, savings, or a final price?

No. A lower documented subtotal can be compared only for aligned rows with documented amounts. It does not establish completeness, availability, quality, suitability, savings, or a final price.

Which missing fields still require current primary provider evidence before comparison?

Verify any unresolved provider identity, GPL title, effective date, verification date, source field, direct-cremation variant, container state, included service, outside charge, estimate, or controlled-row amount against current primary provider evidence. Until resolved, preserve the field as unresolved and do not use it in a completed arithmetic comparison.

Primary sources

  1. Federal Trade Commission — Funeral Industry Practices Rule Verified 2026-08-26
  2. Federal Trade Commission — Complying with the Funeral Rule Verified 2026-08-26
  3. Federal Trade Commission — Funeral Costs and Pricing Checklist Verified 2026-08-26
  4. California Cemetery and Funeral Bureau — Consumer Guide to Funeral and Cemetery Purchases Verified 2026-08-26
  5. California Legislative Information — Business and Professions Code Article 5.5 Funeral Practices Verified 2026-08-26