How to run Offer Of Judgment Analyzer in DocketMath for Kansas

Step-by-step

Run this scenario in DocketMath using the Offer Of Judgment Analyzer calculator.

This walkthrough shows how to run DocketMath’s Offer Of Judgment Analyzer for Kansas (US-KS) using jurisdiction-aware rules anchored to K.S.A. § 60-2204. (This is an informational guide—not legal advice.)

Before you start, set your expectation: Kansas uses the general/default offer period under the statute for this tool configuration. No claim-type-specific sub-rule was found in the jurisdiction data provided, so the analyzer should be treated as applying the statute’s general rule rather than a specialized timing rule for particular claim types.

1) Open the analyzer

1. Go to Offer Of Judgment Analyzer here:

   • /tools/offer-of-judgment-analyzer
2. Confirm the jurisdiction selector is set to Kansas (US-KS) (or select it if DocketMath prompts you).

If you don’t see a dedicated Kansas selector, look for a jurisdiction indicator near the top of the tool UI.

2) Enter the required amounts

DocketMath’s analyzer translates your inputs into an offer-vs.-outcome comparison. Use the fields the UI provides:

• Claimed/assessed money damages (case value)
  Enter the amount you expect a court could award in money damages.
  Why it matters: K.S.A. § 60-2204 applies in civil actions where a money-damages judgment may be rendered, and the tool uses your damages estimate as the anchor for comparison.

• Offer amount
  Enter the amount of the written offer of judgment you want the tool to evaluate.

• Offer date and/or timing inputs (if prompted)
  Provide the date you made the offer and any cutoff/timing date fields the UI requests.
  Why it matters: timing affects how an analyzer models the relevant procedural posture under the statute’s framework.

Scope check: K.S.A. § 60-2204 is scoped to civil actions where a judgment may be rendered for money damages. If your dispute is primarily equitable/injunctive rather than money-damages oriented, the analyzer’s output may not map cleanly to your situation.

3) Add litigation posture inputs (as prompted)

Depending on your DocketMath tool version and UI fields, you may see additional choices such as:

• Whether the offer was made in writing
• Who made the offer (plaintiff vs. defendant)
• An expected judgment outcome or similar field (sometimes phrased as “expected judgment amount” or “judgment result”)

If the UI asks for an expected judgment outcome, set it to the amount you want the analyzer to evaluate against the offer. Important: the same offer amount can lead to different results if you change your assumed judgment.

4) Run the calculation

Click Analyze (or the tool’s equivalent run button).

The tool should produce outputs that generally include:

• An offer favorable vs. not favorable determination under the Kansas rule framework
• A summary of the direction of consequences (e.g., how changing the offer might change modeled fee/cost outcomes)
• A breakdown showing how the result changes as you adjust inputs

5) Review results and adjust inputs (scenario-style)

Treat the analyzer like a scenario planner. A useful workflow is to change one input at a time, rerun, and compare.

• If the result looks close, adjust your expected judgment amount (not the offer) to see the tipping point.
• If the result is consistently unfavorable, adjust the offer amount and rerun to observe how much movement flips the modeled direction.

Quick scenario table (how outputs change)

6) Sanity-check the Kansas rule basis

Kansas’ statute is the foundation for this offer-of-judgment mechanism. The statute begins:

“In any civil action wherein a judgment may be rendered for money damages, any party may make a written offer of judgment…”
K.S.A. § 60-2204: https://www.ksrevisor.org/statutes/gs60/60-2204.html

That is the reason the analyzer is most meaningful when your dispute realistically involves money-damages.

Common pitfalls

Here are the most frequent issues when running the Offer Of Judgment Analyzer in DocketMath for Kansas (US-KS):

• Using the wrong jurisdiction setting (US-KS vs. another state)
  Offer-of-judgment rules vary by state. Always confirm Kansas is selected.

• Entering a non-money-damages number as “case value”
  Because K.S.A. § 60-2204 applies to actions where a money-damages judgment may be rendered, using a figure that represents only injunctive/equitable value can distort comparisons.

• Mixing up “offer amount” and “expected judgment”
  The tool needs the offer amount as its own input. “Claimed damages/case value” or “expected judgment amount” is typically the comparator. Keeping these distinct improves interpretability.

• Assuming claim-type-specific timing is automatically applied
  For this Kansas configuration, the content basis notes no claim-type-specific sub-rule was found, so it’s best to assume the analyzer is using the general/default period. Don’t expect specialized timing logic unless the UI explicitly indicates it.

• Changing multiple variables at once
  If you adjust both the offer amount and expected judgment amount in the same run, you won’t know which change caused the result to shift. Update one variable, rerun, compare.

Reminder: Analyzer outputs are not guarantees of what a court will do. They help you model outcomes based on your inputs and the Kansas rule framework.

Try it

Use this mini practice workflow to confirm your setup:

If the results respond in an intuitive way (e.g., increasing the offer tends to move the modeled direction toward “more favorable” relative to your expected judgment), your inputs and Kansas configuration are likely set up correctly.

Related reading

• Offer of Judgment Analyzer Guide for Alabama
• Offer of Judgment Analyzer Guide for Arizona
• Offer of Judgment Analyzer Guide for Colorado