How to run Settlement Allocator in DocketMath for Mississippi
6 min read
Published August 25, 2025 • Updated April 23, 2026 • By DocketMath Team
Trust release 4
This page has legal or numeric text that still needs claim-level inventory before we can treat it as verified.
Step-by-step
Run this scenario in DocketMath using the Settlement Allocator calculator.
You can run Settlement Allocator in DocketMath for Mississippi (US-MS) to generate jurisdiction-aware settlement allocation results using the default statute of limitations (SOL) rule in Miss. Code Ann. § 15-1-49. DocketMath uses this general/default SOL to help you understand whether claims may be treated as timely (or potentially time-barred) based on date timing—then it applies that timing lens to how you allocate settlement amounts.
Note (important): DocketMath uses the general/default SOL because no claim-type-specific sub-rule was found for this calculator setup in Mississippi. The governing period shown in the tool is 3 years, based on Miss. Code Ann. § 15-1-49. This means outputs will generally be driven by your input dates rather than claim-type tailoring.
1) Open the tool and select the calculator
Start at the primary CTA: /tools/settlement-allocator
- Click Settlement Allocator
- Choose Mississippi (US-MS) as the jurisdiction
If you’re working from a case workspace, double-check that the jurisdiction selection matches the underlying claims you’re allocating, since jurisdiction changes SOL timing logic and can affect allocation results.
2) Enter the dates DocketMath uses
Settlement Allocator relies on date inputs to model SOL timing. Enter what the tool requests, typically including:
- Event date: the date you’re treating as the triggering event for the SOL timeline in this analysis
- Filing date (or “suit commenced” date for SOL purposes): the date the tool uses as the comparison anchor
- Settlement/valuation date (if your workflow includes it and the UI provides the field)
How outputs change: the tool’s SOL indicators and allocation outputs will update based on the relationship between your event date and filing date (and any other date fields you provide), compared against the 3-year SOL window.
3) Confirm the SOL window applied for US-MS
With US-MS, DocketMath applies the Mississippi general/default SOL:
- General SOL Period: 3 years
- General Statute: Miss. Code Ann. § 15-1-49
Because this is the general/default period, the tool’s “timely vs. potentially time-barred” logic will compare your relevant dates (often event date → filing date, and possibly settlement/valuation timing depending on the calculator’s internal model) against the 3-year duration.
4) Add allocation inputs (so the tool can produce a breakdown)
Next, provide the settlement allocation inputs the tool uses to distribute the settlement amount. Common inputs include:
- Settlement total: the overall amount you want to allocate
- Claim components (or categories): the parts of the settlement you want split out (for example, damages categories)
- Any weights / starting assumptions / existing splits (if the interface supports them)
How outputs change: once you provide a settlement total and component structure, DocketMath recalculates an allocation distribution that reflects the jurisdiction-aware SOL timing lens. With a general/default SOL rule, differences you see are often primarily attributable to date timing rather than claim-specific SOL tailoring.
5) Review the allocation output and SOL timing indicators
After you run the calculation, review both:
- Allocation totals by component (how much each component receives)
- SOL-related flags or indicators (whether timing places components inside vs. outside the 3-year window, based on the tool’s comparisons)
- Any summary metrics the tool provides (for example, suggested allocation percentages or relative weighting)
Caution: Treat these outputs as analytical indicators, not legal conclusions. SOL application can involve nuance and additional fact development beyond what a calculator can assume.
6) Export or save the result for your records
To keep your work reproducible:
- Save the run (if the UI provides a save feature) with a clear label such as US-MS, § 15-1-49 default SOL
- Export the results (if the tool supports CSV/PDF or similar formats), especially if you need to attach or share outputs internally
This is useful when you later change dates and want to compare how the allocation and SOL indicators respond.
7) Iterate with “what-if” changes (fast checks)
A practical way to use Settlement Allocator is to run controlled variations to see how sensitive the outputs are to timing. For example:
- Change the event date by a small increment (days/weeks)
- Move the filing date forward or backward
- Rerun and compare component allocations and SOL indicators
Even modest timeline changes can affect whether the tool treats components as within the 3-year limitation period under Miss. Code Ann. § 15-1-49, which in turn can shift the allocation distribution.
Common pitfalls
Settlement Allocator is designed to be user-friendly, but a few issues can lead to misleading results—especially when the tool is using a general/default SOL rule.
**Using the wrong jurisdiction (US-MS vs. another state)
- The 3-year timing tied to Miss. Code Ann. § 15-1-49 is state-specific. Selecting a different jurisdiction changes the SOL window and can materially alter allocations.
Assuming a claim-type-specific SOL applies
- For this calculator setup, no claim-type-specific sub-rule was found. The tool uses the general/default 3-year SOL under Miss. Code Ann. § 15-1-49. If your internal analysis expects a specialized SOL for a specific claim type, you may need to reconcile that separately from the calculator output.
Entering dates in the wrong order
- If the tool expects event date → filing date but you reverse them, SOL comparisons will be incorrect and allocation outcomes may look inconsistent.
Using settlement date as the event date
- Settlement/valuation timing can matter contextually, but SOL timelines usually anchor to the triggering event and suit commencement. If you substitute settlement date for the event date, you may overstate timeliness.
Not rerunning after updating key facts
- If your timeline is still evolving, run at least two versions:
- an “earliest plausible” event date
- a “latest plausible” event date
- This helps show how robust (or fragile) the allocation appears to timing changes.
Over-interpreting SOL flags
- A calculator’s SOL indicator is one factor affecting an allocation model. It’s not a substitute for a full legal analysis.
Try it
Go to /tools/settlement-allocator to run Settlement Allocator for Mississippi (US-MS).
Quick test-drive checklist:
Then make one controlled change:
- Move the filing date forward by 30 days
- Rerun and compare allocations and SOL indicators
If the tool shows components shifting inside/outside the 3-year window, you’ll see how sensitive the allocation is to timing under Miss. Code Ann. § 15-1-49.
If you want additional context on tool workflows, you can browse more DocketMath tool content here: /tools/settlement-allocator
