Why Damages Allocation results differ in North Carolina

The top 5 reasons results differ

Run this scenario in DocketMath using the Damages Allocation calculator.

When you run DocketMath’s damages-allocation calculator for North Carolina (US-NC), you may see the output shift even when the fact pattern feels “the same.” In practice, the biggest drivers are timing inputs, how the calculator handles jurisdiction defaults, and how you enter damages categories.

Below are the top 5 reasons damages allocation results differ in North Carolina, grounded in the state’s default timing framework used by the calculator.

1. Different assumptions about the applicable limitations window

   • In this North Carolina default context, the general SOL period is 3 years.
   • If the calculator is given different timeline anchors (e.g., you enter a different “start” date or “as of” date), the allocation window changes and damages can move between periods/buckets.
   • Even small timeline differences can change totals and proportions after allocation.

2. When the SAFE Child Act concept is present but not claim-type-specific

   • The jurisdiction materials reference the SAFE Child Act concept, but no claim-type-specific sub-rule was found for this exact calculator configuration.
   • Practically, this means you should not assume a special limitations expansion will automatically apply.
   • If your run doesn’t clearly match the modeled inputs the calculator expects, DocketMath will generally fall back to the default/general 3-year assumption.

3. Start date discrepancies

   • Allocation models typically require a “start” date and an “end/as-of” date (or duration).
   • A one-day (or one-month) shift can change how many time segments are allocated, which can change category totals and the way amounts are distributed across outputs.

4. **Uneven damage categories (including blanks and rounding effects)

   • Results can differ when:

     • One or more categories are left blank (or effectively entered as zero),
     • Values are entered in different units (e.g., annual vs. total),
     • Rounding is applied after allocation rather than before.
   • If one scenario includes medical + wage losses and another includes only medical, the remaining categories absorb the allocation differently, which changes both totals and proportional outputs.

5. Different treatment of “already incurred” vs. “projected” amounts

   • If one scenario encodes damages as “incurred through today” while another encodes “total expected,” the effective coverage window can differ.
   • That can lead to different allocations because the calculator is effectively allocating across different portions of time.

Pitfall to watch: A common mismatch is expecting SAFE Child Act-specific timing to apply automatically. In this North Carolina calculator setup, no claim-type-specific sub-rule was found, so runs should generally use the default/general 3-year period unless your inputs clearly align with a scenario the calculator is built to model.

How to isolate the variable

The goal is to identify whether the discrepancy is coming from (a) timing inputs, (b) category inputs, or (c) assumptions/defaults. Use the steps below to isolate variables efficiently in DocketMath.

1. Lock the timeline

   • Keep these identical across runs:

     • Start date
     • End date / “as of” date (or duration)
     • Any coverage window inputs
   • Confirm the jurisdiction remains US-NC in both runs.

2. Change only one damages category at a time

   • Pick a single category (for example, medical or lost earnings).
   • Modify only that category between runs; leave everything else unchanged.
   • If the output lines that move are tied to a specific category, you’ve likely found the source of the difference.

3. Run a blank-to-filled audit

   • Run A: leave a category field blank (or zero, depending on how your workflow treats blanks).
   • Run B: fill that same category with the same numeric value you intended.
   • If results swing significantly, you’ve identified a missing-input/assumption effect.

4. Validate your expected SOL alignment

   • Use the default context: general SOL period = 3 years.
   • Remember: even though the SAFE Child Act concept appears in the jurisdiction materials, no claim-type-specific sub-rule was found for this calculator configuration—so don’t expect an enhanced period unless the modeled inputs clearly match.

Practical checklist (run in this order)

If you want to test and compare scenarios, start with: /tools/damages-allocation.

Next steps

1. Create a difference log

   • Write down exactly what changed between Run 1 and Run 2, including:

     • timeline dates used,
     • category values,
     • units (annual vs. total) or formatting differences.

2. Use a baseline run

   • Baseline should keep:

     • US-NC selected,
     • the default/general 3-year limitations assumption,
     • complete damages categories (no accidental blanks).

3. Re-run with minimal edits

   • Change one variable per re-run until the calculator output matches your expectation—or until you can point to the exact input that caused the shift.

4. Keep inputs consistent going forward

   • Copy the inputs into your notes so future comparisons don’t drift.

Disclaimer (gentle): This page explains why calculator outputs may differ and how to diagnose discrepancies. It does not determine what timing rules apply to any specific set of facts.

Related reading

• Damages Allocation Guide for Alabama — Comparative Fault Rules
• Damages Allocation Guide for Alaska — Comparative Fault Rules
• Damages Allocation Guide for American Samoa — Comparative Fault Rules