Common Damages Allocation mistakes in Kansas

The top mistakes

Run this scenario in DocketMath using the Damages Allocation calculator.

When you use DocketMath’s damages-allocation calculator for a Kansas matter, the biggest problems usually aren’t arithmetic errors—they’re allocation mistakes that cascade into wrong totals, wrong timing, and wrong claim coverage. Below are the most common mistakes we see when teams apply Kansas timing rules and spreadsheet-style reasoning to damages.

1) Using the wrong Kansas statute of limitations (SOL) period (timing window)

Kansas has a general SOL period of 0.5 years, governed by K.S.A. § 21-6701. In this guidance, there’s no claim-type-specific sub-rule identified beyond the general/default period—so treat K.S.A. § 21-6701 as the default SOL rule for timing purposes.

What goes wrong in practice

• Teams apply a longer “typical” SOL they’ve seen in other states.
• Or they treat SOL as an afterthought at the allocation stage (e.g., reducing totals informally rather than using SOL to define the recoverable window).

Why it matters for allocation If your time window is wrong, your allocation timeline is wrong too—any “recoverable amounts by period” outputs will inherit that error.

2) Aggregating all damages into one bucket too early

Another frequent error is combining distinct components—like economic loss, non-economic impacts, and other tracked components—into a single total, and only then allocating.

Common failure mode

• The output may still “sum” correctly, but the model becomes less defensible and less useful for scenario comparisons.

Impact on DocketMath If DocketMath is fed category-level inputs, aggregating prematurely removes the ability to test how outputs change when:

• you adjust dates, or
• you switch scenarios where certain categories appear/disappear.

3) Mixing “incurred” dates with “discovered” dates (or mixing date logic across rows)

Even when the calculator focuses on allocation totals, input datasets usually include date ranges. A very common error is using inconsistent date bases—e.g., mixing:

• “incurred on” vs. “discovered on”
• “last payment” vs. “first injury/impact” (depending on how the dataset is built)

Why it matters Kansas timing analysis is date-sensitive. If your date logic is flipped or inconsistent, you can allocate recoverable amounts to the wrong periods.

4) Applying SOL thinking only after running the full allocation

Teams sometimes compute allocations for the full dataset, then later “wave the SOL wand” and reduce totals informally.

Why this goes wrong

• It can produce inconsistent results across scenarios.
• It may be hard to trace which portions were actually within the Kansas window versus outside it.

Better approach Use the SOL window to determine what portion of the damages timeline is within the recoverable period before final allocation conclusions are made.

5) Not distinguishing “pre-window” versus “within-window” components

A subtle spreadsheet problem is failing to split damages that fall before the SOL window from those that fall within it.

Results

• Recoverable totals can be overstated because “pre-window” amounts are still included in allocation outputs.
• Or, if splitting is attempted but done inconsistently, you can undercount.

How to avoid them

You can prevent most of these mistakes by keeping your workflow jurisdiction-aware, date-consistent, and category-structured. Here’s a practical checklist you can apply when using DocketMath.

Use a written checklist for inputs, document each source, and run a quick sensitivity check before finalizing the result. When two runs differ, compare inputs line by line and re-run with one variable changed at a time.

Step 1: Lock Kansas’s default SOL period and make it explicit in your process

For Kansas, use the general/default period:

• K.S.A. § 21-6701
• General SOL period: 0.5 years

Important: No claim-type-specific sub-rule was found here, so you should keep the analysis anchored to the general/default period rather than branching into other SOL lengths.

DocketMath workflow tip

• Record a “SOL baseline” note alongside each calculation run so the timing rule is consistent across runs.
• When you run scenarios, keep the SOL baseline constant unless you’re intentionally testing what happens under a different window assumption.

Source: K.S.A. § 21-6701 (Kansas Legislature)
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

Step 2: Keep categories separated until the final reporting stage

In DocketMath (damages-allocation):

• Maintain separate line items per damages component (each economic category you track, each non-economic category you track, etc.).
• Only combine totals at the reporting stage.

Why this helps

• If you change the SOL window or date boundaries, you can immediately see which categories are driving the changes.
• You avoid the “black box” effect caused by aggregating everything early.

Step 3: Use one consistent date basis across the dataset

Pick a single date method for timeline allocation inputs and apply it consistently:

• If you intend to measure the timeline using incurred dates, use incurred dates everywhere.
• Don’t mix incurred and discovered dates in the same allocation run unless your model explicitly supports separate tracks.

Quick validation

• Sort rows by your chosen date field and verify the timeline “flows” logically over time.
• Watch for inversions (e.g., later periods appearing to contain earlier impacts due to date-field mixing).

Step 4: Split your timeline into at least two buckets: pre-window and within-window

Before final totals:

• Identify the SOL window using Kansas’s default 0.5-year period.
• Allocate amounts that fall within the window separately from those that fall before it.

Checklist

Step 5: Use DocketMath sensitivity runs to catch date mapping errors early

DocketMath is especially useful when you test sensitivity. Try two runs that differ only by a boundary input (for example, a one-record or one-day shift in the SOL boundary).

What to watch

• Recoverable totals should change in a controlled, explainable way.
• Large swings often indicate date-mapping problems (incurred vs. discovered) or mis-bucketed rows (pre-window vs. within-window).

Gentle note: This is not legal advice. SOL and allocation issues can be fact-specific, so treat the calculator workflow as an analytical aid and confirm key assumptions with qualified counsel or authoritative guidance.

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