Inputs you need for Damages Allocation in Kansas
5 min read
Published April 15, 2026 • By DocketMath Team
Inputs you will need
To allocate damages in Kansas with DocketMath, you’ll typically need the same core facts regardless of claim theory. The main jurisdiction-aware input that affects timing is the general statute of limitations (SOL)—because it can limit how far back losses are counted in the allocation window.
Before you run the damages-allocation calculator, gather the following inputs:
- Kansas (US-KS)
- The date when damages began to accrue (or the earliest date you want included in your allocation)
- The date through which you’re allocating damages (often the last accounting date or “as of” date you’re using)
- Any dates and amounts needed to attribute damages across periods
- The aggregate dollar figure you want DocketMath to split across the calculator’s time buckets
- Choose the method DocketMath supports for splitting damages across periods (for example, proportional to time periods). Be consistent.
- Examples: credits, offsets, agreed reductions, or stipulations you want reflected in the allocation
- Confirm whether your “total damages amount” includes or excludes fees/costs, and keep that definition consistent with the rest of your damages package
Practical note (not legal advice): DocketMath can only allocate what you provide. If your “total damages amount” mixes damages and costs differently than your theory expects, the calculator output may still be internally consistent—but it won’t match your intended presentation.
Kansas SOL timing rule (default)
For this Kansas workflow, no claim-type-specific sub-rule was found, so the calculator should rely on the default/general period:
- General SOL period: 0.5 years
- Kansas general statute: K.S.A. § 21-6701
In plain terms for the calculator: if your losses begin before the SOL “lookback” window, DocketMath will allocate only within the window reflected by the dates you enter and the Kansas default SOL logic above.
Where to find each input
Use this map to locate (or reconstruct) each input from your case materials—so you can run the tool without rework.
| Input | Where to find it | What to double-check |
|---|---|---|
| Kansas selection (US-KS) | DocketMath “jurisdiction-aware rules” panel | Confirm you’re using Kansas (US-KS), not another state |
| Loss start date | Complaint allegations; demand letters; account statements; event chronology | Ensure it matches when harm began (not discovery), unless your documentation uses a discovery-based approach |
| Loss end date | Latest accounting date; termination date; spreadsheet “as of” date | Confirm it matches the scope you want allocated (avoid unintentionally including post-scope events) |
| Payment history/installments | Bank records; payment schedule; ledger; invoices; settlement correspondence | Watch for missing payments or duplicated entries |
| Total damages amount | Damages spreadsheet; settlement demand; expert report summary | Ensure the number matches the components you intend to allocate |
| Allocation method | DocketMath calculator settings | Switching methods can change period weighting and dollar distribution |
| Known adjustments/offsets | Settlement agreements; credit memos; stipulations | Determine whether adjustments reduce the total globally or are meant to apply per period |
| Fees/costs treatment | Billing statements; demand package; definitions of “damages” | Decide whether your “total damages amount” is “damages only” or “damages + fees/costs” |
Date-window sanity check (before you run)
Because Kansas uses a short default/general SOL period (0.5 years) for this workflow, make sure your entered dates align with the timing window you intend:
- Use 0.5 years as the default timing baseline under K.S.A. § 21-6701 (default only; no claim-type-specific rule identified here).
Warning (practical): If you enter a long historical loss horizon without considering the SOL window, the allocation can result in substantial portions being excluded based on the dates you provide and the default SOL timing logic.
Run it
Use DocketMath with damages-allocation for Kansas (US-KS). Start here:
Enter the inputs in DocketMath and run the Damages Allocation calculation to generate a clean breakdown: Run the calculator.
Capture the source for each input so another team member can verify the same result quickly.
Step-by-step
- Open the tool and select:
- Jurisdiction: **Kansas (US-KS)
- Enter the loss start date and loss end date.
- Input your total damages amount.
- Make sure this matches your definition (damages only vs. damages + fees/costs).
- Choose the allocation method.
- Enter payment history and any adjustments/offsets, if prompted by the tool.
- Run the calculation and review the period-by-period outputs.
How outputs change based on inputs
These “cause-and-effect” checks help you validate that the output matches your intent:
- Move the loss start date forward (closer to the end date)
- Outcome: you generally reduce the “stale” portion outside the SOL lookback window, so more allocation shifts into more recent periods.
- Move the loss end date forward (later “as of” date)
- Outcome: you generally expand the overall allocation span, which can add allocation into later buckets.
- Change whether fees/costs are included in your total damages amount
- Outcome: the time windows stay the same, but the dollar amounts in each bucket will rebalance based on the updated total.
- Alter adjustments/offsets
- Outcome: allocated amounts reflect net damages (as entered), so some periods may decrease more than others depending on how the tool applies timing to the adjustments.
Kansas SOL rule applied (default only)
Because no claim-type-specific sub-rule was found, treat this as the baseline timing logic for the tool run:
- General/default SOL period: 0.5 years
- Statute: K.S.A. § 21-6701
If your strategy requires a different limitation period than the general rule, ensure your inputs and documentation align accordingly—otherwise the allocation may reflect the general/default SOL window rather than the specialized period you intended.