Damages Allocation rule lens: Kansas

5 min read

Published April 15, 2026 • By DocketMath Team

The rule in plain language

Run this scenario in DocketMath using the Damages Allocation calculator.

In Kansas, the Damages Allocation lens starts with one governing time rule: the general statute of limitations (SOL) for many damages claims.

Kansas provides a general SOL in K.S.A. § 21-6701. Using the jurisdiction data for this lens, the general/default SOL period is 0.5 years—which is about six months. In practical terms, for many common damages scenarios covered by this general rule, you generally allocate damages to a six-month recoverable timeframe.

Important: No claim-type-specific sub-rule was found for this damages allocation lens. That means this article uses K.S.A. § 21-6701’s general/default period as the starting point for the time window used in allocation—unless you later identify a more specific SOL rule that applies to the particular claim type.

Scope note (not legal advice): This lens is about the time window that may be SOL-eligible for damages allocation. It does not determine whether liability exists, nor does it replace the need to confirm whether a different (claim-specific) SOL rule applies to your facts.

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

Why it matters for calculations

Damages allocation is where SOL rules become “math rules.” Even when damages accrue over time, the SOL often determines how far back (and therefore which portions) of the damages period are potentially recoverable under the general/default rule.

With Kansas’s general SOL period of 0.5 years (six months) under K.S.A. § 21-6701, your allocation approach typically looks like this:

  1. Choose a reference point used by your model/workflow (often the filing date, depending on how your spreadsheet or DocketMath inputs are set up).
  2. Back-calculate 0.5 years to define the potentially recoverable time window.
  3. Allocate damages only to the portion of the loss that falls within that SOL window.

How the time window changes the numbers

In many damages models, allocation depends on one or both of these timing concepts:

  • Accrual timing (e.g., daily/weekly/monthly loss amounts)
  • Event timing (e.g., when payments were made or harm occurred)

If your recoverable window is six months, then:

  • Losses occurring outside the prior six months are generally excluded from the SOL-eligible allocation.
  • Losses occurring inside the prior six months are generally included, subject to the rest of your allocation logic in DocketMath.

Example (conceptual, to show the impact)

Assume damages accrue at a steady rate:

  • Rate: $1,000 per week
  • Kansas general SOL window: 0.5 years ≈ 26 weeks (depending on the tool’s conversion/rounding)

Then the SOL-limited allocation amount is approximately:

  • $1,000 × 26 = $26,000

If the time window were longer (for example, if a different rule applied), the allocated amount could increase proportionally. That’s why, in SOL-driven allocations, the selected SOL period is often the biggest driver of the result.

What to watch for in Kansas specifically

Because this lens uses the general/default period (and there is no claim-type-specific sub-rule included here), you should sanity-check three common calculation disruptors:

  • A different SOL for a specific cause of action (which could change the window)
  • Accrual differences based on the facts (which affects which dates fall inside/outside the window)
  • Tolling/extension arguments (which can shift the effective window)

Pitfall to avoid: Assuming the general/default six-month SOL automatically applies to every damages scenario can cause the calculated allocated damages to be too low (if a longer specific SOL applies) or too high (if a shorter/different rule applies). The calculator can only reflect the SOL rule you input—so your inputs should reflect the correct rule for the claim type.

Use the calculator

DocketMath’s damages-allocation calculator turns the Kansas SOL lens into a repeatable workflow. Use it to model how much damages fall within the 0.5-year general/default SOL period under K.S.A. § 21-6701.

Run the Damages Allocation calculation in DocketMath, then save the output so it can be audited later: Open the calculator.

Step-by-step: inputs that affect outputs

Check these inputs in your worksheet/workflow (and in DocketMath):

  1. Jurisdiction

    • Select **Kansas (US-KS)
  2. **SOL rule used (time window)

    • Use general/default SOL period: 0.5 years
    • Source: K.S.A. § 21-6701
    • Reminder: no claim-type-specific sub-rule was found/added for this lens
  3. Reference dates

    • Provide the date(s) the calculator needs to establish the SOL window—commonly:
      • a relevant filing/reference date, and
      • the start/end dates of the damages accrual you’re modeling
  4. Damages accrual pattern

    • Choose how losses are structured, for example:
      • a one-time amount tied to a date
      • recurring payments by date
      • a rate-based pattern (daily/weekly/monthly)
  5. Include/exclude logic

    • Apply the SOL window to allocate:
      • include amounts inside the recoverable window
      • exclude amounts outside it

What outputs to expect

After you run the calculator, you’ll typically see:

  • Allocated damages within the SOL window
  • Excluded damages outside the SOL window
  • Possibly a breakdown by date ranges (depending on how you input accrual)

Because the window is time-based, shifting a reference date by even a few weeks can materially change the allocated totals when accrual is rate-based.

Primary CTA (start here)

Run the Kansas damages allocation lens in DocketMath here:

  • /tools/damages-allocation

Where the Kansas rule fits (lens setup summary)

This calculator setup is built around the following rule summary:

ItemKansas value used in this lens
StatuteK.S.A. § 21-6701 (general SOL)
Period0.5 years (general/default)
Claim-type-specific sub-ruleNone applied/found for this lens

Related reading