Spreadsheet checks before running Damages Allocation in Nebraska

What the checker catches

Run this scenario in DocketMath using the Damages Allocation calculator.

Running a Damages Allocation spreadsheet in Nebraska without a quick front-end review can lead to avoidable downstream errors. The DocketMath damages-allocation calculator assumes your underlying timeline facts and totals are internally consistent. This spreadsheet checker validates those assumptions so you can catch issues before allocation math propagates them into incorrect line items.

Below are the main issues the checker targets for Nebraska (US-NE), using Neb. Rev. Stat. § 13-919 as the default/general SOL reference.

Important note (no claim-type-specific sub-rule found): Your jurisdiction data indicates no claim-type-specific SOL sub-rule was found. That means the checker applies the general/default SOL period of 0.5 years from Neb. Rev. Stat. § 13-919 rather than switching SOL periods based on a claim label (e.g., “tort,” “contract,” or “fraud”).

1) Statute of limitations (SOL) window mismatches

The checker verifies that your spreadsheet’s “key date” and damages timing align with the general/default SOL period (0.5 years) tied to Neb. Rev. Stat. § 13-919.

Jurisdiction data used by the checker:

• General SOL Period: 0.5 years
• General Statute: Neb. Rev. Stat. § 13-919
• Source: https://law.justia.com/codes/nebraska/chapter-13/statute-13-919/

What it catches:

• When the spreadsheet assumes a SOL period different from 0.5 years without a supported alternative rule
• When the damages period you’re allocating appears to fall partially outside the general/default SOL window implied by your inputs
• When a change in a single “relevant date” (accident/occurrence date, filing date, or other key date) creates a new inclusion/exclusion boundary but the sheet isn’t updated consistently

Gentle caution (not legal advice): If your spreadsheet uses a claim-type-specific SOL assumption that isn’t supported by the rule set loaded here, the allocation may reflect damages that should be time-barred under the general rule in Neb. Rev. Stat. § 13-919.

2) Date logic errors (the silent spreadsheet killers)

Date problems are one of the most common ways allocations drift without obvious errors. The checker looks for relationship issues such as:

• Occurrence/trigger date vs. filing/relevant date ordering problems
• Damages period start date occurring after the as-of / damages period end date
• As-of cutoffs that don’t align with the SOL window behavior implied by your 0.5-year default
• Blank or non-date cells being treated like empty values (or accidentally converted), which can cause the tool to compute a different time span than you intended

Even if a spreadsheet “runs,” these date mismatches can change the computed damages time window that drives the allocation.

3) Unit and aggregation inconsistencies

The checker also verifies internal consistency across totals and components—because a spreadsheet can be numerically valid while still logically off.

It checks for:

• Whether component amounts sum to the provided totals (and flags when they don’t)
• Whether percentage-based allocations sum to 100% (when your model is percentage-driven)
• Whether currency/date formatting issues cause numbers to be treated as text
• Whether subtraction direction creates unintended negative damages outputs

4) Input completeness and field hygiene

Before the allocation is computed, the checker confirms that key fields are populated and consistent with the Nebraska rule set being applied (general/default SOL via Neb. Rev. Stat. § 13-919):

• Damages period start date
• Damages period end date (or an as-of date)
• Claim filing key date / relevant date used to evaluate the inclusion of damages within the 0.5-year default window
• Totals or category amounts you plan to allocate

If any of these are missing or malformed, the checker aims to stop you early—so you don’t end up allocating based on incorrect assumptions.

When to run it

Best practice: run the checker immediately before you launch the DocketMath /tools/damages-allocation calculator, and then again after any edits to dates, totals, or categories.

Run the checker before importing a spreadsheet into the Damages Allocation workflow. It is especially helpful when you have multiple entries or when a teammate provided the inputs.

Recommended workflow (Nebraska, US-NE)

1. Enter or import dates: Add the occurrence/trigger date(s), the damages period start/end dates (or as-of date), and your claim filing/relevant key date.
2. Run the checker: Confirm the time window lines up with the general/default SOL period of 0.5 years under Neb. Rev. Stat. § 13-919.
3. Run allocation: Use DocketMath /tools/damages-allocation after the checker reports no blocking issues.
4. Re-run after edits: If you change any date or any totals/categories, re-run the checker so you don’t rely on stale assumptions.

Quick “triggers” to re-run the checker

Re-check whenever you:

• adjust a date by even a few days
• change what portion of damages you treat as “past”
• update category totals (even if percentages appear unchanged)
• copy the sheet to a new version (formatting can silently change how fields are interpreted)

Pitfall to watch: If a spreadsheet cell is converted from “Date” to “Text,” the checker/tool may treat it as blank or differently parsed—leading to a widened or narrowed computed allocation window.

Try the checker

Use DocketMath’s damages-allocation calculator as the final step, but treat the checker as your preflight step—especially while your spreadsheet is still being finalized.

Upload the spreadsheet, review the warnings, and then run the calculation once the inputs are clean: Try the checker.

Primary CTA

• Run the tool: /tools/damages-allocation

What to verify in your inputs

Before computing, confirm your spreadsheet/tool fields reflect these essentials:

Nebraska rule reminder (how SOL is treated here)

• The checker uses Neb. Rev. Stat. § 13-919 as the general/default SOL reference.
• Because no claim-type-specific sub-rule was found, it does not switch SOL periods based on claim label.
• For multi-category damages, the checker focuses on consistency—it helps ensure your timeline inputs and totals align with the 0.5-year general/default framework, rather than rewriting your theory.

Gentle disclaimer: This tool and checker are designed to help you validate spreadsheet logic and time-window assumptions. They are not a substitute for legal advice or for a full review of case-specific 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