How Offer Of Judgment Analyzer rules vary in Colorado

What varies by jurisdiction

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

An Offer of Judgment (often described as an “offer of settlement” in Colorado’s statute framework) can shift reasonable attorney fees and costs—but the rules you need can vary based on (1) the jurisdiction and (2) how the offer is structured and presented in the case record.

In Colorado, the governing provision discussed in this DocketMath workflow is C.R.S. § 13-17-202. The statute provides that in certain civil actions, when a plaintiff makes an offer of settlement and the case proceeds to judgment, the court shall award reasonable attorney fees and costs based on whether the final judgment is more favorable than the offer.

DocketMath’s Offer Of Judgment Analyzer is designed to turn the statutory trigger into calculations you can sanity-check. However, because different jurisdictions can implement different standards and because the statute’s trigger depends on procedural facts, the analyzer’s results are driven by the inputs you enter—especially:

• Who made the offer (and whether that aligns with Colorado’s “plaintiff makes an offer” framing)
• The offer and judgment comparison you’re asking the tool to evaluate
• The relevant dates (to keep the tool aligned with the procedural posture)

At a high level, the kinds of “jurisdiction variation points” you should expect when switching states (or when moving between different tool rule sets) include:

• Whether the statute applies to your case posture and pleading posture
  While C.R.S. § 13-17-202 is framed broadly as “in any civil action,” in practice you still need to confirm the offer mechanism matches what the statute contemplates for the case type and posture.

• Which party can make the offer under the statute
  Colorado’s provision is written around the plaintiff making the offer. If the party making the offer in your case is not the plaintiff (or if the litigation posture differs), double-check that the statute pathway being used matches your scenario.

• Timing requirements tied to when the offer is made and when the comparison is made
  In an analyzer, the “analysis timeline” depends on procedural milestones you select (often offer date vs. judgment date). A mismatch here can change the tool’s interpretation.

• Whether there are special sub-rules for certain claim categories
  For this Colorado topic, no claim-type-specific sub-rule was found in the jurisdiction data provided. That means this article treats C.R.S. § 13-17-202 as the general/default rule for the fee-and-cost shifting analysis described here, rather than layering extra claim-type timing logic.

Important limitation (read this):
DocketMath can only apply the rule set you select and the inputs you provide. If your case facts point to a different statutory carve-out or a separate Colorado rule, the analyzer won’t “discover” it automatically without the correct rule information.

If you want to run the jurisdiction-aware calculation, use: /tools/offer-of-judgment-analyzer

What to verify

Before relying on any analyzer output, verify these items against the docket and the actual text of the offer. This is a practical way to avoid feeding the tool facts that don’t match what the statute requires.

• The governing rule or statute for the jurisdiction.
• Any local rule overrides or administrative guidance.
• Effective dates and whether amendments apply.

1) Confirm the governing Colorado statute matches your workflow

For Colorado fee-and-cost shifting tied to offers, the relevant provision referenced here is C.R.S. § 13-17-202. The jurisdiction data states:

“In any civil action, if the plaintiff makes an offer of settlement... the court shall award reasonable attorney fees and costs...”

That “plaintiff makes an offer” language is a key setup detail. Make sure your case posture aligns with the statute pathway being evaluated.

2) Validate the offer date and the judgment date you use for comparison

Even with the statute framework aligned, calculations can change if the tool is given the wrong milestone dates.

Verify you have:

• Offer date (the date the offer was made/served, as reflected in the record)
• Judgment date (the final judgment date you intend to compare against)

If you enter a “date that looks right” (like a filing date) but the controlling record treats another date as operative, the analyzer output can shift.

3) Confirm the amount being compared: offer vs. judgment figure

Offer-of-judgment analysis typically turns on whether the ultimate judgment is more favorable than the offer. To support that comparison, verify:

• The offer amount exactly as stated in the offer
• Whether the offer amount includes components relevant to the comparison (for example, how it treats damages, interest, and/or costs—depending on the offer’s drafting and the tool’s inputs)
• The judgment amount you plan to use as the comparator in DocketMath

4) Confirm the “offering party” alignment (plaintiff vs. defendant)

Because your inputs can affect rule pathway logic in the analyzer, double-check that:

• The offer document reflects the offering party the statute contemplates (Colorado’s provision focuses on plaintiff)
• You select the same offering party in DocketMath setup
• The tool’s jurisdiction is set correctly to US-CO

5) Don’t assume claim-type-specific exceptions exist (unless you find the exact rule)

Based on the jurisdiction data you provided, no claim-type-specific sub-rule was identified for this Colorado approach. That means your baseline assumption should be:

• Use the general/default C.R.S. § 13-17-202 pathway in the analyzer

If your situation involves unusual statutory elements or a separate Colorado statute that might control, use the tool as a baseline and then verify whether an additional rule should be applied. (The analyzer won’t automatically apply a carve-out unless the rule set is explicitly included.)

Gentle disclaimer: This is an educational, workflow-focused checklist—not legal advice.

Using DocketMath to see how outputs change (practical inputs → output impact)

DocketMath’s Offer Of Judgment Analyzer (US-CO) is most useful when you treat its inputs like levers and confirm that the results track the facts in the record.

Inputs that commonly change results

• Offer amount: A higher or lower offer can materially affect whether the judgment is treated as more favorable under the comparison logic.
• Judgment amount used for comparison: If you input a different judgment figure than the one the court actually used (or the figure you intended), you can flip the “more favorable” result.
• Dates: Changing offer/judgment dates can alter which milestone the analyzer compares.
• Offering party selection: If the tool thinks the wrong party offered, the analysis framework may not match the statute’s trigger.

Outputs you should expect to interpret

• A fee/cost shifting outcome tied to the statutory comparison trigger
• A summary of the comparison performed (offer vs. judgment)
• Assumptions and inputs the tool used based on what you entered

Practical approach for internal review:

• Run Scenario A using the offer amount exactly as written.
• Run Scenario B using the judgment figure you plan to use as the comparator.
• Compare how sensitive the result is to those inputs. High sensitivity often signals you should verify the record details (offer drafting, judgment components, and operative dates).

Sources and references

Start with the primary authority for Colorado and confirm the effective date before relying on any output. If the rule has been amended, update the inputs and rerun the calculation.

• Primary authority reference

Related reading

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