Inputs you need for Damages Allocation in Nebraska

5 min read

Published April 15, 2026 • By DocketMath Team

Inputs you will need

To allocate damages in Nebraska with DocketMath, you’ll typically supply a small set of “case facts” that let the calculator apply Nebraska timing/eligibility rules (including the general statute of limitations). Even when your damages allocation work is not exclusively about timeliness, SOL-related eligibility inputs can change what claims (or portions of claims) are included in the allocation base—so the numbers you enter can directly affect the output.

Start by gathering these inputs up front:

Nebraska SOL baseline for eligibility (default/general):
DocketMath uses the general/default limitations period reflected in Neb. Rev. Stat. § 13-919 as the timing framework. Based on the jurisdiction data provided for this workflow, the general SOL period is 0.5 years.

Importantly, no claim-type-specific sub-rule was found, so the general/default period is the one reflected here. If you later determine a more specific limitations rule applies to your claim type, you should rerun DocketMath with that updated rule (or with the appropriate claim-type settings, if available in your workflow).

Gentle reminder: This is an eligibility/timing input for an allocation workflow. It’s not legal advice—use it to structure analysis and then validate with qualified counsel or authoritative sources if needed.

Where to find each input

Use existing documents in your matter. Avoid adding new assumptions about dates or totals unless your team has an internal policy for doing so.

Most inputs live in the case file, contracts, or docket entries. Dates usually come from the triggering event notice; rates and caps come from governing documents or statute; and amounts come from the ledger or judgment. Record the source for each value so the run is reproducible.

1) Date of injury or occurrence

Common places:

  • Complaint allegations / statement of facts
  • Incident report or medical records intake date
  • Contract or project timeline documentation (if the “occurrence” is tied to performance)

Tips for accuracy:

  • Confirm whether you should use the first date of injury vs. the last date of injury (especially for continuing harm).
  • Keep date formatting consistent (day/month/year vs. month/day/year) so DocketMath interprets the dates correctly.

2) Date suit was filed

Common places:

  • Electronic filing confirmation (e.g., the filing stamp)
  • Court docket entry for the complaint
  • Summons/compliance paperwork

Consistency check:

  • If your team uses a “case evaluation date,” confirm whether your workflow treats it as the “filed” date for this run. For SOL eligibility, DocketMath needs a filing date proxy that your process intends to use.

3) Damages category totals

Common places:

  • Your damages spreadsheet
  • Expert reports (if you have separate lines for economic vs. non-economic)
  • Settlement demand or internal valuation memo

If you have only one combined number:

  • You may still be able to enter totals, but you’ll lose category-level distribution. If DocketMath supports category inputs, consider splitting at least economic vs. non-economic so outputs can be more actionable.

4) Allocation method flags

Common places:

  • Your internal allocation SOP
  • Prior DocketMath runs (if you standardize the method)

Why it matters:

  • Output changes when you switch allocation logic (for example, proportional allocation by category totals vs. another method).

5) SOL eligibility assumption (general/default)

Nebraska general limitation framework referenced here:

State this clearly in your workflow:

  • Use the 0.5-year general/default SOL period because no claim-type-specific sub-rule was found for this scenario.

Run it

Open DocketMath → Damages Allocation using: **/tools/damages-allocation

Then enter the inputs you collected above into the matching fields.

Enter the inputs in DocketMath and run the Damages Allocation calculation to generate a clean breakdown: Run the calculator.

What DocketMath is likely to do with these inputs

Based on the Nebraska/default timing framework you provided, the calculator will generally:

  • Assess whether the suit filing date falls within the 0.5-year general/default SOL period tied to Neb. Rev. Stat. § 13-919.
  • Use that timing gate to determine which portions of your damages categories are included in the allocation base.
  • Apply your selected allocation method (often proportional to category totals) to produce an allocation output.

How outputs change when you change inputs

Input you adjustTypical effect on allocation output
Injury/occurrence date moves laterMay improve eligibility (shorten elapsed time) and can increase included/allocated amounts
Filing date moves earlierLikely increases eligibility and included allocation totals; later filing can reduce eligible share
Split between economic vs. non-economic changesCategory distribution shifts (even if the overall total is similar), depending on the allocation method
Economic total increases (holding non-economic constant)Economic category share increases under proportional allocation approaches
You rerun with a different SOL assumptionEligibility changes can cause allocation totals to drop or expand materially

Pitfall to avoid: If you enter an “event date” that’s actually the date you noticed harm (rather than the date harm occurred), you could cross the 0.5-year threshold and change which amounts are treated as eligible.

Quick pre-flight checklist before you run

When you’re ready, run the calculation and save the output. If the record supports multiple plausible date choices, do a “what-if” run by swapping dates and comparing how eligibility and allocation totals change.

Related reading