How to calculate Offer Of Judgment Analyzer in Texas

Quick takeaways

• Texas uses “Chapter 42 settlement offers” (Tex. Civ. Prac. & Rem. Code ch. 42) to shift post-offer costs and attorney’s fees when the judgment is significantly less favorable to the offeree than the rejected settlement offer.
• DocketMath’s Offer Of Judgment Analyzer (US‑TX) helps you model possible cost/fee-shift outcomes using (at minimum) the offer amount, the offer date, the final judgment amount, and whether the offer was accepted or rejected.
• The timing framework is tied to Tex. R. Civ. P. 167 alongside Chapter 42 (§§ 42.001–42.005). No claim-type-specific sub-rule is included here—this guide uses the general/default approach described by those authorities.
• The tool is most useful for scenario testing: try multiple judgment outcomes and offer amounts to see what most drives the result.

Inputs you need

Before you run DocketMath’s Offer Of Judgment Analyzer (US‑TX), gather the facts the calculator will need. If you don’t have a final number yet, you can still run a forecast using good-faith estimates.

Core inputs (typical)

• Offer amount
• Offer date
• Final judgment amount for the offeree (the court’s final judgment amount as reflected in your docket)
• Acceptance status

  • Accepted, or
  • Rejected / not accepted
• Who made the offer (offeror vs. offeree)

  • You want the tool to evaluate the outcome from the offeree’s perspective, because the statute’s shifting mechanism turns on whether the offeree did “significantly worse” than the rejected offer.

Timing-related inputs (sanity checks)

• Whether the offer was withdrawn (if applicable)
• Any key scheduling context you have (helpful for sanity-checking your offer window)

Even if the analyzer primarily uses the offer date, the goal is the same: make sure the offer fits within the procedural structure referenced by Tex. R. Civ. P. 167 and Chapter 42.

Optional inputs (depending on your case summary)

If your docket summary tracks these, consider inputting them where the tool allows:

• Attorney’s fees amount you expect to compare/model
• Taxable costs (if the tool separates or can estimate categories)

Texas authorities the analyzer is modeling

• Tex. Civ. Prac. & Rem. Code ch. 42 (§§ 42.001–42.005) — Chapter 42 governs “settlement offers” and how, after rejection, certain litigation costs and attorney’s fees can shift when the judgment is significantly less favorable to the offeree.
• Tex. R. Civ. P. 167 — Texas procedural rule related to the operation of offers and their consequences.

Source for Chapter 42 (statutory text): https://statutes.capitol.texas.gov/Docs/CP/htm/CP.42.htm

How the calculation works

DocketMath’s Offer Of Judgment Analyzer (US‑TX) follows the core Chapter 42 logic: it models whether the rejected-offer scenario crosses the statute’s threshold and then estimates whether post-offer fee/cost shifting is implicated.

At a high level, the calculation usually comes down to five steps:

1. Confirm the situation fits a Chapter 42-type rejected settlement offer analysis
2. Check timing consistency with Tex. R. Civ. P. 167 and Chapter 42’s framework
3. Compare the rejected offer to the final judgment using Chapter 42’s “significantly less favorable” threshold concept
4. Apply the acceptance/rejection logic (accepted offers generally don’t trigger the same post-rejection shifting analysis)
5. Estimate potential post-offer cost/fee shift exposure if the threshold is met

1) Threshold comparison: offer vs. final judgment

The heart of Chapter 42 analysis is a comparison between:

• the settlement offer amount (the one that was rejected), and
• the final judgment amount ultimately received by the offeree.

How inputs change the outcome

• If the final judgment is close to (or better than) the rejected offer for the offeree, the analyzer typically predicts little to no shift.
• If the final judgment is far below the rejected offer for the offeree, the analyzer becomes more likely to indicate that the threshold is met, which is where fee/cost shifting can be implicated.

Practical tip: If you’re unsure of the threshold inputs, run multiple scenarios. Even small changes to the judgment estimate can move the “significantly less favorable” evaluation.

2) Rejection vs. acceptance controls whether shifting is modeled

Chapter 42’s post-offer shifting mechanism is tied to a rejected offer scenario. So the analyzer uses your acceptance status to decide whether it should even look for threshold-triggered shifting.

A simple way to think about it:

• Accepted offer → the case posture is resolved on those terms; you typically won’t model the rejected-offer shifting the same way.
• Rejected / not accepted → the tool evaluates whether the final judgment is sufficiently unfavorable to the offeree relative to the offer.

3) Timing matters: the offer must be within the procedural structure

Texas also evaluates offers through timing rules in Tex. R. Civ. P. 167, in coordination with Chapter 42. The analyzer uses your offer date (and related inputs, if you provide them) to keep the model aligned with that procedural window.

4) Default period clarity (no claim-type-specific sub-rule in this guide)

This article uses the general/default period and structure from Tex. Civ. Prac. & Rem. Code ch. 42 (§§ 42.001–42.005) and Tex. R. Civ. P. 167.

Important clarification: No claim-type-specific sub-rule was found for purposes of this Texas how-to, so this guide does not introduce special category-based timing logic beyond the general framework.

That means:

• Use the general Chapter 42 + Tex. R. Civ. P. 167 approach for the analyzer baseline.
• If your case involves a unique procedural posture or special deadlines reflected in court orders, ensure your docket summary reflects those facts and then rerun the analyzer.

5) Interpreting the output

After you run the tool, read DocketMath’s results as:

• a scenario-based projection of whether Chapter 42 shifting is likely triggered, and
• an estimate of potential post-offer exposure depending on what inputs you provided.

Use it to answer:

• “If the judgment is $X, does rejecting an offer of $Y likely trigger shifting?”
• “How sensitive is the result if the judgment number changes?”
• “Which input is driving the outcome the most—offer amount or judgment amount?”

Common pitfalls

• Using a non-comparable “final judgment amount”

  • For example: entering a settlement figure, an interim order, or a partial award rather than the final judgment amount the court entered.

• Mismatching offeror/offeree perspective

  • Chapter 42 analysis is fundamentally about whether the offeree’s outcome is “significantly less favorable” than the rejected offer.
  • Double-check which party’s outcome you’re modeling in the analyzer.

• Ignoring timing constraints

  • If your offer date doesn’t align with the framework referenced by Tex. R. Civ. P. 167, the model’s scenario may not match real procedural treatment.

• Assuming any fee shifting is automatic

  • Chapter 42 is threshold-driven. If the judgment isn’t “significantly less favorable” to the offeree than the rejected offer, shifting may not be implicated.

• Failing to rerun after judgment updates

  • Once the court enters (or amends) the judgment amount, update the final judgment input and rerun.
  • A change at the margin can flip the threshold evaluation.

Sources and references

• Tex. Civ. Prac. & Rem. Code ch. 42 (Settlement Offers), §§ 42.001–42.005 (statutory text)
  https://statutes.capitol.texas.gov/Docs/CP/htm/CP.42.htm
• Tex. R. Civ. P. 167

Next steps

1. Open DocketMath’s Offer Of Judgment Analyzer (US‑TX): /tools/offer-of-judgment-analyzer
2. Enter at minimum:

   • Offer amount
   • Offer date
   • Final judgment amount
   • Accepted vs. rejected
   • Confirm offeror/offeree labeling
3. Run 2–3 scenarios to stress-test the outcome:

   • Scenario A: judgment at the low end of your estimate
   • Scenario B: judgment at your best estimate
   • Scenario C: judgment at the high end of your estimate
4. Review what changes the output most:

   • If the result flips primarily with the judgment number, your exposure is highly sensitive to trial/judgment outcome.
   • If it flips primarily with the offer number, your modeling suggests the rejected offer amount is the critical driver of the Chapter 42 threshold comparison.

Re-run the analyzer whenever there’s a substantive **