How to run Damages Allocation in DocketMath for Kansas

Step-by-step

This guide walks you through running Damages Allocation in DocketMath for Kansas (US-KS), using the jurisdiction-aware rules that correspond to Kansas’s general statute of limitations (SOL) for most covered damages calculations.

1) Open the Kansas Damages Allocation calculator

1. Go to the primary tool entry: **/tools/damages-allocation
2. Confirm you’re using the US-KS jurisdiction preset (Kansas).
3. If the interface asks for a “jurisdiction” or “state” selection, choose Kansas (US-KS).

2) Enter the case timeline inputs

Damages allocation typically depends on how long between key dates the underlying claims are measured against. Enter dates exactly as your record reflects them.

Common date fields you may see in DocketMath include:

• Event/Accrual date (start of the damages measuring period)
• Cutoff/filing date (when you’re evaluating timeliness)
• Additional “last date” / end date fields (if the tool requests a final measurement boundary)

Because DocketMath is jurisdiction-aware, the Kansas default SOL period will be applied to the timeline logic for this run.

3) Use the Kansas SOL rule that DocketMath applies

For Kansas, the general/default SOL period referenced by the calculator is:

• General SOL Period: 0.5 years
• General Statute: K.S.A. § 21-6701
• Source: https://www.kslegislature.gov/li/s/statute/021_000_0000_chapter/021_067_0000_article/021_067_0001_section/021_067_0001_k.pdf?utm_source=openai

In practice, this means DocketMath will constrain the damages measurement window using a half-year default when no more specific rule is selected or found.

4) Provide damages amounts by component (if the tool requests breakdowns)

Many damages allocation workflows require input totals or component amounts so the tool can allocate across eligible/ineligible periods.

If DocketMath asks for a breakdown, enter your figures in the units the tool expects (often dollars). Examples of fields you might see:

• Past damages vs. future damages
• Category-based amounts (if supported in the calculator UI)
• Period-based damages inputs (if the tool expects segmentation)

Tip: Keep track of the exact totals you enter so you can explain any differences between your total requested amount and the tool’s allocated results.

5) Review the allocation results and how outputs change

After you submit:

• DocketMath will output an allocation reflecting what portions fall inside vs. outside the Kansas 0.5-year default SOL window tied to K.S.A. § 21-6701.
• The allocation can change noticeably if your dates move near the half-year boundary.

How to sanity-check your run:

• Change the cutoff/filing date by ~30–31 days and re-run.
• If the “in-window” share shifts as expected, your dates are likely aligned with the tool’s date interpretation and the Kansas default logic.
• If nothing changes, it may indicate a date format issue or that the tool’s allocation logic isn’t date-driven for the specific layout you entered.

Gentle note: DocketMath is a computational aid, not legal advice. For interpretation of SOL application to your specific facts, consult a qualified professional.

6) Export or capture the output for your workflow

If DocketMath offers options such as copy/download/print:

• Use them to save the results alongside your inputs.
• Keep your date values and damages components so you can reproduce the same allocation later (especially after edits).

Common pitfalls

Here are the most common mistakes people make when running Damages Allocation in DocketMath for Kansas:

• Using the wrong SOL baseline

  • This run uses Kansas’s general/default SOL period: 0.5 years under K.S.A. § 21-6701.
  • If you expected a different, claim-type-specific SOL, the allocation may not match your expectations.

• Assuming the tool “finds” special rules automatically

  • In this article’s scenario, no claim-type-specific sub-rule was found, so the general period is applied.
  • If your claim type has a different statutory period, document that limitation and adjust your calculator inputs/workflow accordingly.

• Date entry errors

  • Swapping month/day order (e.g., interpreting 04/05 as April 5 vs. May 4)
  • Entering a “last payment date” when the tool expects an “accrual date”
  • Using a date format that the tool cannot parse

• Assuming the allocation is purely arithmetic

  • Damages allocation is often period-based: the SOL window/timeline drives eligibility, so time inputs can change outcomes even when the damages number stays constant.

• Misreading output categories

  • Tool outputs may label results with terms like “eligible” vs. “ineligible” (or similar).
  • Double-check the label definitions shown next to each output figure.

Try it

Use DocketMath’s /tools/damages-allocation to run a Kansas (US-KS) scenario with the default SOL rule from K.S.A. § 21-6701 (general SOL period 0.5 years).

A quick way to test and confirm your setup:

1. ✅ Start with one clean date set (Accrual date + Cutoff/filing date)
2. ✅ Enter a simple damages structure (one total, or the minimum breakdown required by the tool)
3. ✅ Run once and record:

   • the “allocated” total(s)
   • the “eligible” vs. “ineligible” split (or the equivalent categories the tool displays)
4. 🔁 Re-run with only one change:

   • shift the cutoff/filing date forward by 30–31 days
   • keep everything else identical

If your output changes around the half-year constraint, that’s a good sign your inputs align with the Kansas default SOL application in the calculator.

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