How to run Settlement Allocator in DocketMath for Nebraska
6 min read
Published June 11, 2025 • Updated April 23, 2026 • By DocketMath Team
Trust release 4
This page includes a legal claim or source that failed the current primary-source review.
Step-by-step
Run this scenario in DocketMath using the Settlement Allocator calculator.
Here’s how to run Settlement Allocator in DocketMath for Nebraska (US-NE) using jurisdiction-aware rules. This walkthrough assumes you’re allocating amounts across settlement components and want DocketMath to apply Nebraska’s default/general limitation period logic.
Note (timing rule used): This guide uses Nebraska’s general/default limitation period. In the provided jurisdiction data, no claim-type-specific sub-rule was found, so the same general period applies rather than switching based on claim category. Always verify the dates and assumptions used for your specific matter.
1) Open the tool
- Go to: /tools/settlement-allocator
- If the interface asks you to confirm jurisdiction, make sure you select Nebraska (US-NE).
2) Enter settlement inputs
Settlement Allocator typically requires the information needed to distribute settlement value. Use the fields that match your scenario, such as:
- Total settlement amount (the pool being allocated)
- Payment timing / date basis (the tool may anchor the limitation analysis using dates you provide)
- Allocation weights or categories (if your layout includes components or categories)
Date entry tip: If the tool asks for dates, enter real calendar dates (for example, 2026-04-15) rather than relative terms like “6 months ago.”
3) Confirm the limitation period logic (Nebraska default)
DocketMath should apply Nebraska’s general limitation period based on the jurisdiction-aware rules:
- General SOL period: 0.5 years
- General statute: Neb. Rev. Stat. § 13-919
How this affects your output: the 0.5-year period is used to determine what portion of your timeline is treated as within versus outside the limitation window (depending on how the tool maps your date inputs to its internal logic). Because 0.5 years is relatively short, results can change noticeably when your dates move near the cutoff.
Gentle disclaimer: This is an informational walkthrough of how to run the calculator. It’s not legal advice, and tool outputs should be reviewed for fit to your specific facts and documentation.
4) Review how outputs change when you adjust dates
To understand what’s driving the allocation, change one input at a time—usually the date that the tool uses as the limitation “anchor”—and compare results.
In practical terms, you may see output shifts like:
| If you change… | Effect you’ll usually see in outputs |
|---|---|
| Move the limitation anchor date earlier (more time before filing/payment) | A larger portion may be treated as within the limitation window |
| Move the limitation anchor date later (closer to or beyond the cutoff) | A smaller portion may be treated as within the limitation window |
Because the period is 0.5 years, even several months can be enough to move your results across a threshold.
5) Export or capture the allocation results
Once the calculator produces allocations:
- Screenshot key results (amounts by category/component, if shown)
- If the tool supports it, export/download the report for your working papers
- Keep your inputs next to your outputs so you can reproduce results when you adjust dates or component weights
Pitfall to avoid: Don’t enter inconsistent dates across fields (for example, an “offer” date in one place and a different “trigger” date in another) unless you understand which date each field contributes to the limitation analysis.
Common pitfalls
Settlement Allocator is typically straightforward, but Nebraska’s 0.5-year general period can make the tool more sensitive to small timeline differences.
- missing a required input
- using a stale rate or rule
- ignoring calendar or holiday adjustments
- skipping documentation of assumptions
1) Assuming claim-type-specific limitation periods are included
Nebraska has multiple limitation rule concepts, but based on the provided jurisdiction data:
- The tool uses the general/default period
- No claim-type-specific sub-rule was found
- Result: allocations follow the same 0.5-year period rather than switching based on claim category
If your matter depends on different limitations for different claims, you’ll want to validate whether the calculator can represent that (or whether you need a different workflow).
2) Using relative timing without confirming date conversion
If you enter relative timing (if supported) like “6 months ago,” confirm how DocketMath converts it into a specific calendar anchor date. A mismatch in conversion can shift your allocation across the limitation threshold.
3) Forgetting to apply Nebraska as the active jurisdiction
If you accidentally run the tool under a different jurisdiction:
- You may get a different limitation period than 0.5 years
- Your Nebraska allocation output becomes less useful for your Nebraska work product
Always confirm:
- The jurisdiction selector shows **Nebraska (US-NE)
- The limitation rule displayed aligns with Neb. Rev. Stat. § 13-919 and 0.5 years
4) Changing multiple inputs at once
When testing, don’t change everything simultaneously. If you do, you won’t know whether changes came from limitation timing, component weights, or the settlement total.
- Change one variable
- Run
- Capture results
- Change the next variable
Try it
You can quickly test the Nebraska default behavior and confirm how sensitive the allocation is to your timeline inputs.
Open the Settlement Allocator calculator and follow the steps above: Run the calculator.
If an assumption is uncertain, document it alongside the calculation so the result can be re-run later.
Quick checklist (before you run)
Two-run experiment (recommended)
- Run A: Use your best estimate of the limitation anchor date.
- Run B: Move that anchor date by ~3 months later (or earlier).
Then compare:
- Total allocated treated as within vs. outside the limitation window
- Component/category allocations (if the tool breaks allocations down)
Because the limitation period is 0.5 years, a ~3-month change is often enough to show meaningful differences. If your results don’t change after you update dates, check:
- Whether you edited the correct date field
- Whether that field is actually used for limitation analysis
- Whether the tool updated after your changes (and whether you exported/saved the updated output)
