How to calculate Offer Of Judgment Analyzer in Kansas

Quick takeaways

• Kansas’s offer-of-judgment framework is codified at K.S.A. § 60-2002 and focuses on two core ideas:

  1. prevailing-party costs, and
  2. an offer-triggered allowance tied to comparing the offer to the judgment.
• In DocketMath’s Offer Of Judgment Analyzer (US-KS), you’ll calculate consequences by entering your offer details (offer date/amount) and case outcome (the judgment you’re comparing against).
• The statute’s timing in this guide is treated as general/default because the provided jurisdiction data does not identify any claim-type-specific sub-rule. That means you should not branch into different timing rules based only on claim category.
• Use the analyzer to pressure-test scenarios (for example, “What if the offer was $75,000 vs. $90,000?”). Then confirm the final effect with the statute text and your case posture. This is informational only, not legal advice.

Inputs you need

Before you run DocketMath’s Offer Of Judgment Analyzer (US-KS), collect the facts needed to model K.S.A. § 60-2002 and the offer-versus-judgment comparison.

Core inputs (most common)

• Offer amount (the dollar figure offered)
• Offer date (the date the offer was made; timing can affect the analyzer’s operation)
• Who made the offer

  • Plaintiff made the offer
  • Defendant made the offer
• Judgment amount actually awarded (use the operative final number for comparison)
• Prevailing party (based on the judgment’s outcome)
• Costs basis / cost components to include in your estimate (if the tool supports modeling them), such as:

  • filing fees
  • taxable costs
  • other costs you want reflected in net exposure

Timing inputs (to match the Kansas workflow)

Even where the timing is “default,” you still need the right dates for an accurate comparison.

• Case filing date (optional for context; useful if your workflow needs it)
• Offer date relative to key procedural events (particularly if you’re testing whether the offer was made at a meaningful stage)

Optional inputs (for scenario testing)

• Multiple offer rounds (Offer #1, Offer #2, etc.)
• Alternative judgment numbers (for example, comparing a settlement assumption vs. an anticipated trial number)
• Assumed cost totals (to translate the analyzer’s result into net exposure)

Where to start in DocketMath

Use the analyzer entry point here:

• Primary CTA: /tools/offer-of-judgment-analyzer

How the calculation works

DocketMath’s Offer Of Judgment Analyzer (US-KS) models Kansas’s structure from K.S.A. § 60-2002 in two conceptual layers:

1. a prevailing-party costs baseline, and
2. offer-of-judgment consequences based on the judgment vs. the offer.

This matters because a change to one input (like offer amount or who made the offer) can shift where the scenario falls on the statute’s comparison.

1) Baseline: prevailing party costs

Kansas begins with a default costs rule and then allows additional “other costs” at the court’s discretion.

• K.S.A. § 60-2002(a):
  “Unless otherwise provided by statute, costs shall be allowed to the party in whose favor judgment is rendered.”
• K.S.A. § 60-2002(b):
  “Other costs may be allowed in the discretion of the court.”

In analyzer terms:

• The “baseline” typically reflects that the prevailing party is entitled to costs as a starting point.
• “Offer-triggered” consequences are then evaluated against that baseline to show an overall picture.

2) Offer-of-judgment consequences (judgment vs. offer)

K.S.A. § 60-2002(c) contains the offer-of-judgment mechanism. The jurisdiction dataset snippet you provided truncates the full subsection, but the structure is still clear at a high level: it creates a court allowance triggered by an offer, using a comparison between offer amount and the judgment.

DocketMath’s US-KS logic generally follows these moving parts:

Step A — Determine the comparison standard

• Identify the judgment amount used for comparison.
• Identify the offer amount.
• Apply the correct directionality:

  • If the plaintiff made the offer, compare the plaintiff’s recovery/judgment outcome to the plaintiff’s offer.
  • If the defendant made the offer, compare the plaintiff’s recovery/judgment outcome to the defendant’s offer.

Step B — Apply the offer trigger

The legal “incentive” goal is to shift risk by encouraging realistic offers. Practically, that means:

• when the final judgment falls on the “favorable enough” side of the offer, the statute’s offer-triggered consequences apply in the way specified in K.S.A. § 60-2002(c).

Step C — Compute the effect category

The analyzer typically presents:

• a baseline costs expectation (grounded in § 60-2002(a)), and
• an offer-triggered adjustment (grounded in § 60-2002(c)),
• plus a combined estimate so you can see net exposure.

Timing period: use the default rule (no claim-type-specific sub-rule shown)

Your jurisdiction dataset includes an explicit note:

• “No claim-type-specific sub-rule was found. The above is the general/default period. State this clearly in the content.”

So for this Kansas workflow:

• Treat the offer timing as general/default under the statute structure reflected here.
• Do not add claim-type branches (for example, treating personal injury and contract differently) unless you confirm additional Kansas-specific provisions beyond the data provided.

Common pitfalls

These are the most frequent reasons people get “off-looking” results from an offer-vs-judgment analyzer.

1) Reversing who made the offer

If you select the wrong offer maker, the comparison direction can flip.

Checklist:

• Confirm offer maker matches who served/sent the offer in the case
• Confirm the tool is comparing the correct side of the dispute to the correct offer

2) Using an imprecise or non-operative judgment figure

Kansas comparisons depend on the judgment number you enter.

Checklist:

• Use the final operative judgment amount (not an interim order)
• If there were amendments or later judgments, use the number that is controlling for purposes of the comparison

3) Ignoring the costs baseline implied by § 60-2002(a)

Because K.S.A. § 60-2002(a) allows costs to the prevailing party “as a matter of course,” omitting costs entirely can understate the real baseline effect.

Checklist:

• If you want net exposure, enter a reasonable costs estimate
• Keep “baseline costs” conceptually separate from “offer-triggered adjustments”

4) Treating discretionary costs as guaranteed

Subsection (b) says “other costs may be allowed in the discretion of the court,” which does not mean they will always be awarded automatically.

Checklist:

• Don’t model “other costs” as certain unless your scenario supports it

5) Creating claim-type-specific timing rules without confirmation

Because the provided data shows no claim-type-specific sub-rule:

Checklist:

• Apply the general/default timing period
• Don’t invent special deadlines unless you verify an additional Kansas provision that changes timing

Sources and references

• K.S.A. § 60-2002 (Offer of judgment; costs). Kansas Legislature Revisor.
  https://www.ksrevisor.org/statutes/chapters/ch60/060_020_0002.html
• DocketMath calculator: /tools/offer-of-judgment-analyzer

Next steps

1. Run a baseline scenario

   • Enter the final judgment amount, the offer amount, the correct offer maker, and (if supported) your costs estimate.

2. Test sensitivity with a few offer alternatives

   • Change only one variable at a time (often offer amount) to see where the trigger changes outcomes.
   • Keep prevailing party and costs inputs consistent while testing.

3. Validate timing inputs

   • Confirm the accuracy of the offer date.
   • Since this guide treats the timing as general/default (no claim-type-specific sub-rule provided), avoid introducing claim-type-specific deadlines.

4. Document your assumptions

   • Record the offer date/amount, judgment figure, prevailing party basis, and costs included—so you can compare results against later docket updates.

Related reading

• How to calculate Offer Of Judgment Analyzer in Philippines — Full how-to guide with jurisdiction-specific rules
• Worked example: Offer Of Judgment Analyzer in Philippines — Worked example with real statute citations
• Inputs you need for Offer Of Judgment Analyzer in Philippines — Input checklist with sourcing guidance