Some car-accident matters involve more than two drivers and one liability policy. Vehicle ownership, employment, contracts, passengers, multiple impacts, government or product issues, several policies, prior conditions, later events, disputed losses, and litigation can create separate questions that depend on different facts and sources.

A claim becomes multi-layered when one event presents separate party, responsibility, coverage, causation, loss, evidence, or procedural questions; complexity should be mapped by issue rather than used as a label for the whole file.

Create one issue row for each disputed question

  • Issue and legal or factual proposition being evaluated, without embedding the desired conclusion in the label
  • Parties, claims, defenses, policies, insureds, benefits, records, witnesses, custodians, and decision makers connected to the issue
  • Supporting source, conflicting source, missing source, authenticity or foundation question, and preservation status
  • Governing statute, rule, contract, policy, order, or other authority; version; factual predicates; and unresolved interpretation
  • Dependency, deadline, assigned reviewer, client decision, next action, completion evidence, and next review date

Map parties without assuming they belong in one lawsuit

North Carolina Rule of Civil Procedure 20 addresses permissive joinder of parties under specified conditions. A party map should identify drivers, owners, employers, contractors, vehicle or component companies, property controllers, government entities, estates, minors, insurers in their actual roles, and other participants. Joinder, jurisdiction, venue, immunity, capacity, service, and claim-specific requirements need separate review.

Build a policy and insured matrix

North Carolina G.S. 20-279.21 addresses motor-vehicle liability policies and related coverage subjects. For each possible policy, record the carrier, policy period, named insured, vehicle, driver, permission, coverage part, limit, deductible, endorsement, exclusion asserted, notice, claim number, reservation, denial, payment, exhaustion question, and source document. Do not treat the statute or a declarations page as a substitute for the complete policy and event-specific analysis.

Separate responsibility, causation, and loss

  • Responsibility: conduct, duty or standard asserted, ownership or agency, event sequence, alternative cause, and contributory-conduct allegation
  • Medical causation: baseline, event, symptoms, diagnosis, treatment, prior condition, later event, qualified opinion, and competing explanation
  • Loss: medical expense, wage or earning effect, property, transportation, household assistance, function, benefit, lien, repayment, and calculation source
  • Coverage: policy status and terms, insured identity, notice, cooperation, consent, reservation, priority, limits, and unresolved interpretation

Map evidence custodians and systems

Identify law enforcement, drivers, passengers, employers, vehicle owners, repair and tow facilities, insurers, medical providers, businesses, government bodies, phone or app providers, video systems, manufacturers, experts, and others who may control relevant material. For each, record what is sought, native format, date range, retention, access authority, request or process, response, and gap.

Convert the map into a discovery plan when a lawsuit is filed

Rule 26 addresses discovery scope, limits, sequence, protective orders, supplementation, experts, and related procedure. Link each proposed request, deposition, inspection, subpoena, expert question, or motion to an actual issue row. Track privileged or protected material, proportionality, objections, orders, production format, and supplementation rather than collecting data without a defined purpose.

Use dependencies to order the work

A policy question may depend on ownership or permission; a damages question may depend on medical causation; an expert review may depend on preserved vehicle data; service may depend on correct entity identity. Mark those dependencies so an unavailable predicate is resolved before later work is treated as complete.

Close or narrow issues explicitly

When an issue is resolved, record the source and decision. When it is narrowed, preserve the remaining question. When it is abandoned, state who authorized the decision and what related evidence or deadline remains. This prevents old assumptions from continuing to drive requests, valuation, or pleadings after the file has changed.

The related responsible-party mapping guide explains how to identify roles, relationships, and source records before deciding who may bear civil responsibility.

Rosensteel Fleishman Car Accident & Injury Lawyers provides information about North Carolina car-accident claims involving multiple issues. The map should make each question, dependency, source, and decision visible.

Sources