How to run Damages Allocation in DocketMath for North Carolina

6 min read

Published April 15, 2026 • By DocketMath Team

Step-by-step

Run this scenario in DocketMath using the Damages Allocation calculator.

This guide walks you through running Damages Allocation in DocketMath for North Carolina (US-NC) using the calculator at /tools/damages-allocation. The goal is to apply jurisdiction-aware defaults and interpret outputs consistently with North Carolina’s general limitations-period setup.

Note: This walkthrough focuses on tooling and jurisdiction-aware defaults inside DocketMath. It’s not legal advice, and it doesn’t replace case-specific research.

1) Open the calculator in DocketMath

  1. Go to /tools/damages-allocation
  2. Select or confirm the jurisdiction as North Carolina (US-NC).

2) Confirm which limitations period DocketMath will use (North Carolina default)

For this US-NC configuration, DocketMath uses North Carolina’s general limitations period:

  • General SOL Period: 3 years

DocketMath may prompt for a “claim-type” or “rule set.” For this jurisdiction configuration, no claim-type-specific sub-rule was found, so the tool uses the general/default 3-year period.

Warning: If your matter truly depends on a special limitations rule tied to a particular claim type, DocketMath’s “default” may not match that scenario. In that case, adjust inputs and/or the rule set to reflect the specific rule you’re using for your analysis.

3) Enter the damages inputs you want allocated

Damages Allocation is meant to split a total damages amount into categories you select/enter, then produce allocation-aware outputs.

In DocketMath, you’ll typically provide some combination of:

  • Total damages (overall amount), and/or
  • Category amounts (breakdown of the total), and/or
  • Allocation method parameters the interface requests (if applicable)

Practical rule of thumb:

  • If the UI lets you enter category amounts, prefer that—because the tool can compute allocation percentages from the breakdown.
  • If the UI instead asks for a total plus percent splits, use that approach only if you already know the percentage allocations you want the calculator to apply.

4) Add timing-related inputs so the jurisdiction-aware rules can apply

Even though the calculator is labeled Damages Allocation, limitations-window logic can still affect which portions are considered “within” the relevant time frame—depending on the tool’s methodology.

Enter the timing fields the calculator requests. Common examples include:

  • Relevant event date (e.g., occurrence/injury date tied to the analysis)
  • Filing date (or another “as-of” date used by the tool)

With US-NC selected, DocketMath’s default timing window uses the 3-year general SOL period unless you’ve configured a different rule set via the tool’s settings.

5) Review the jurisdiction-aware rules used by the calculation

Before running, confirm the tool settings reflect:

  • General SOL Period: 3 years
  • No claim-type-specific sub-rule identified in this configuration
  • Default rule approach rather than a specialized rule for a narrower claim category

To keep your run auditable, record the inputs you used—especially:

  • the date fields,
  • the total and/or category amounts, and
  • how you populated categories (so you can rerun quickly with changed assumptions).

6) Run the calculation and interpret the allocation results

After you submit inputs, review the results for:

  • Allocation totals by category
  • Percentage splits (if shown)
  • Any output that indicates a limitations-window adjustment (for example, amounts flagged as within vs. outside the window)

Sanity-check approach:

  • If you entered $100,000 total and your category amounts sum to $100,000, the tool’s category totals should reconcile to that same total.
  • If timing adjustments are applied, expect “within-window” totals to be equal to or lower than your overall totals (based on what portions fall inside the 3-year window).

Tip: Treat the output as a calculation based on your inputs and DocketMath’s configured defaults—not as an authoritative legal conclusion about claim viability, enforceability, or coverage.

7) Iterate with scenario testing (fast reruns)

DocketMath is designed for quick iteration. Rerun the calculator after small input changes to see how outputs shift.

Common scenario variations:

  • Change the filing/as-of date by days or weeks to observe whether the 3-year window moves portions of damages into or out of the included period.
  • Adjust category amounts to identify which category drives the biggest change in allocation totals.

If the tool supports it, note which scenario you’re testing; otherwise, copy the output or export results so you can compare runs.

8) Tie outputs back to North Carolina context (without over-claiming)

While the calculator’s limitations behavior here is based on the general 3-year SOL period, it’s also helpful to keep your overall documentation grounded in reliable jurisdiction materials.

For context around North Carolina’s victim support approach (not limitations rules, but often relevant to case documentation workflows), you can reference:

For this DocketMath run specifically, the governing limitations parameter is:

  • General 3-year period
  • No claim-type-specific sub-rule found for this configuration

Common pitfalls

Avoid these issues when running Damages Allocation for US-NC in DocketMath:

  • Assuming a specialized limitations rule is applied
    • This configuration uses the general/default 3-year SOL period because no claim-type-specific sub-rule was found.
  • Entering inconsistent amounts
    • If category totals don’t add up to your total (or if you enter totals differently than you think), percentages and totals will reflect the values you actually entered.
  • Using dates that don’t match the tool’s required logic
    • If the tool expects an event/occurrence date and a filing/as-of date, but you substitute another date type, the windowing math may shift.
  • Rerunning scenarios without tracking what changed
    • Even a small date adjustment can flip whether some amounts are treated as within the relevant period (depending on the tool’s methodology).
  • Over-interpreting output language
    • Outputs show calculation results based on your inputs and DocketMath’s configuration. They don’t guarantee legal outcomes in a specific case.

Pitfall: If you later determine you need a different limitations period than the general 3-year window, rerun with the correct rule setup (or document why you used the default).

Try it

Ready to run your first allocation?

  1. Open the calculator: /tools/damages-allocation
  2. Set jurisdiction to North Carolina (US-NC).
  3. Use the default limitations window = 3 years (general/default; no claim-type-specific sub-rule in this setup).
  4. Enter:
    • Damages totals and/or category amounts
    • The key date fields the tool requests (event/occurrence and filing/as-of dates)
  5. Click Calculate.
  6. Compare:
    • Category totals vs. your input totals
    • Within-window vs. overall totals (if the tool applies timing-based inclusion)

Quick calibration test:

  • Run once with the filing date exactly 3 years after the event date.
  • Run again with the filing date moved forward by 30 days.
  • Confirm the output changes in the direction you expect as the window shifts.

Related reading