A settlement evaluation can change as records arrive, errors are corrected, treatment develops, work information is verified, coverage is identified, responsibility evidence is tested, liens are clarified, or an offer introduces new terms. Replacing one number with another loses the reason for the change. A versioned log preserves the facts and assumptions that supported each evaluation at that time.

A settlement-evaluation change log should identify the version, evaluation date, changed fact or assumption, source, affected category, calculation or legal issue, reviewer, direction of change, unresolved dependency, and next review trigger.

Freeze a baseline before recording changes

  • Evaluation version, date, purpose, reader, claim stage, records included, records excluded, governing assumptions, and open questions
  • Responsibility facts, claimed injuries, treatment status, past expenses, wage evidence, property issues, coverage, liens, costs, offers, and release terms separated into fields
  • Documented fact, qualified opinion, calculation, estimate, allegation, disputed point, unknown, and scenario labeled differently
  • No baseline called a final value or promise when evidence, treatment, coverage, responsibility, or payment terms remain incomplete

Record each new source and what it changes

  • Source name, creator, date, custodian, version, completeness, authentication issue, date received, and location in the file
  • Specific prior field affected, old entry, new entry, reason, calculation impact, and person making the change
  • Correction to a bill, wage figure, incident date, party identity, policy number, treatment plan, or offer term preserved rather than silently overwritten
  • New source that does not change the evaluation also logged so the review history shows it was considered

Separate medical-expense proof from medical conclusions

North Carolina Rule of Evidence 414 limits evidence offered to prove past medical expenses to amounts actually paid for satisfied bills and amounts actually necessary to satisfy incurred but unsatisfied bills. A charge, adjustment, payment, refund, balance, collection record, and future estimate should therefore remain distinct.

  • Provider, service date, billed amount, adjustment, payer, payment, refund, balance, status, and source
  • Billing correction linked to the earlier version and to every subtotal it affects
  • Medical diagnosis, causation, prognosis, permanence, and future treatment traced to their qualified sources rather than inferred from billing activity
  • Disputed service, unrelated condition, missing record, later event, or inconsistent date held as an unresolved issue

Update responsibility and coverage as different dimensions

G.S. 20-279.21 addresses required motor-vehicle policy provisions, including liability and uninsured or underinsured motorist coverage. The existence or limit of a policy is not the same question as legal responsibility, documented loss, collectability, or the amount a particular source may pay.

  • Each potentially responsible person or entity, theory asserted, evidence supporting or weakening it, status, and disputed fact
  • Policy or other payment source, insurer, named insured, vehicle, coverage type, policy period, limits information, reservation, denial, exhaustion, and verification source
  • Coverage change recorded without automatically changing the underlying loss calculation
  • Responsibility change recorded without assuming that insurance is available for every category or amount

Treat settlement communications as their own version stream

Rule 408 addresses compromise offers and negotiations and limits specified uses of that evidence. A claim file should preserve proposals and responses in the correct context rather than mixing negotiation figures into source records or treating an offer as an admission.

  • Demand or offer date, sender, recipient, amount, included claims, excluded claims, conditions, release scope, payment timing, confidentiality, costs, liens, and expiration
  • Counteroffer and response linked to the exact proposal being answered
  • Gross figure separated from estimated net amount and from nonmonetary terms
  • Expired, withdrawn, superseded, rejected, accepted, disputed, or awaiting authority shown explicitly

Use summaries that remain traceable

Rule 1006 addresses summaries used to prove the content of voluminous writings, recordings, or photographs when its requirements are met. A working evaluation summary should likewise identify the originals behind each entry and calculation. It cannot supply missing proof or resolve a disputed assumption.

  • Source ID and page, extracted fact, formula, unit, subtotal, reviewer, review date, and link back to the original
  • Change log showing which rows and totals moved between versions and why
  • Scenario sensitivity kept separate from verified calculations
  • Arithmetic, duplicate-entry, omitted-period, inconsistent-unit, and stale-source checks completed before comparing versions

Set evidence-based review triggers

  • New medical record or qualified opinion, treatment milestone, corrected bill, wage confirmation, liability evidence, coverage response, lien update, offer, release draft, or court event
  • Trigger owner, expected date, missing dependency, follow-up, and the version that must be revisited
  • Material and nonmaterial changes separated by their actual effect rather than by the volume of new documents
  • Final decision record states which version and sources were reviewed without implying a guaranteed result

The related guide to building a loss-and-damages source ledger after a North Carolina car accident covers the underlying source inventory. This page owns the separate version, changed input, evaluation effect, negotiation term, and review-trigger history.

Rosensteel Fleishman Car Accident & Injury Lawyers provides general information about Charlotte car-accident claims. A settlement evaluation is fact-specific and may change as evidence, law, coverage, and terms develop.

Sources