Why Damages Allocation results differ in Kansas

The top 5 reasons results differ

Run this scenario in DocketMath using the Damages Allocation calculator.

When you run DocketMath’s Damages Allocation calculator for Kansas (US-KS), it’s common to see different totals even when the underlying claim description seems “the same.” In most cases, the differences come from jurisdiction-aware rules interacting with your date inputs and allocation inputs—not from the calculator “making up” different math.

Here are the top 5 reasons results differ specifically in Kansas:

1. Your “start date” accidentally shifts the damages window

   • Kansas uses a general/default statute of limitations (SOL) period of 0.5 years (see K.S.A. § 21-6701).
   • If your data uses different date meanings across runs (for example, filing date vs. demand date vs. loss/accrual date), the SOL truncation can cut a slightly different portion of the damages window, changing the allocated total.

2. The calculator is using the general SOL because no claim-type-specific sub-rule was found

   • For this Kansas ruleset, no claim-type-specific sub-rule was found, so the tool falls back to the default SOL above.
   • Practically, that means two cases with different underlying legal theories can still end up with similar SOL treatment in the calculator—unless you adjust inputs or the applicable ruleset changes.

3. “Damages by category” inputs don’t match the allocation structure

   • Damages allocation often depends on how you provide inputs (e.g., whether the calculator treats principal vs. interest vs. fees as separate components).
   • If one run separates categories and another run bundles them, the allocation distribution can shift because the calculator allocates based on the structure you give it.

4. Interest timing assumptions change totals

   • Small changes to interest-related inputs can materially affect outputs, such as:

     • the interest start date
     • whether interest is included in the allocable base (as modeled by the tool)
     • any modeling assumption (e.g., if the setup uses simple vs. compounding interest based on inputs)
   • Even a modest timing change can alter how much of the interest falls inside vs. outside the SOL-truncated window.

5. Rounding and segmentation boundaries

   • When the damages window is split into segments (often by month or similar intervals), rounding can cause small—sometimes noticeable—differences.
   • If the SOL cutoff lands near the edge of a segment, truncation can “snap” the calculation to a slightly different set of segments.

Pitfall to avoid: If you compare two outputs without confirming the exact date fields you entered (e.g., loss date, accrual start, window start, filing/demand date), it’s easy to misinterpret normal SOL truncation as a “disagreement” between runs.

How to isolate the variable

Use this quick isolation workflow in DocketMath (calculator: damages-allocation) while keeping Kansas (US-KS) constant.

• Freeze the jurisdiction and tool settings so both runs use the same rule set.
• Compare one input at a time (dates, rates, amounts) and re-run after each change.
• Review the breakdown to see which segment or assumption drives the difference.

Step-by-step isolation workflow

• accrual/loss start (or the date you treat as damages beginning)

  • allocation window start
  • filing/demand date (or whichever date the tool uses as the SOL reference point)
  • Example: shift the allocation window start by 30 days while keeping everything else identical
  • Separate vs. bundle components (principal/interest/fees) in the same way across runs

What to look for in outputs

Kansas default SOL note: This run uses the general/default SOL period of 0.5 years because no claim-type-specific sub-rule was found. If your inputs or the configured ruleset change later, results may change even with the same numeric values.

Kansas SOL anchor (tool context)

For this Kansas run, DocketMath’s damages-allocation behavior is anchored to the general SOL period of 0.5 years in K.S.A. § 21-6701:

• 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

Next steps

1. Create a “golden run” and save it

   • Preserve the exact input values that produced your most trusted output (dates + category breakdown + any interest settings).

2. Validate date normalization across runs

   • Ensure your dates mean the same thing in every run:

     • the date you treat as accrual/loss start
     • the date you treat as allocation/window start
     • the date you treat as filing/demand (the SOL reference point)
   • With a 0.5-year default SOL window, even a 15–30 day mismatch can change truncation.

3. Rerun with one controlled change at a time

   • This makes the cause testable:

     • SOL cutoff effects vs.
     • interest timing effects vs.
     • category-structure effects.

4. Avoid assuming claim-type-specific behavior unless the tool is configured for it

   • Since this Kansas ruleset is using the general/default SOL (no claim-type-specific sub-rule found), your output may not reflect specialized treatment unless the calculator/ruleset is aligned accordingly.

If you want to reproduce your numbers, run the calculator here: /tools/damages-allocation.

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