Offer of Judgment Analyzer Guide for Indiana
8 min read
Published March 22, 2026 • By DocketMath Team
What this calculator does
Run this scenario in DocketMath using the Offer Of Judgment Analyzer calculator.
DocketMath’s Offer of Judgment Analyzer for Indiana (US-IN) helps you estimate the potential cost-shifting impact of an offer of judgment under Indiana’s offer-of-judgment framework.
At a high level, it translates a few key facts—like the offer amount and the final judgment amount—into an at-a-glance view of whether the offer could trigger cost consequences.
Because Indiana’s statute focuses on whether the offer was accepted and how the final judgment compares to the offer, the calculator is designed around the core statutory trigger:
- Ind. Code § 34-50-1-1 authorizes a party to serve an offer of judgment that can lead to consequences if it’s not accepted within the time provided by Rule 68 of the Indiana Rules of Trial Procedure.
- Statute language (summary): a party may serve an offer of judgment, and cost consequences can follow if it isn’t accepted within the Rule 68 timing.
The calculator primarily compares:
- Offer amount vs.
- Final judgment amount
to determine whether the scenario fits the statute’s cost-shifting structure, including the well-known limitation referenced in Indiana’s companion section:
- Ind. Code § 34-50-1-2 — the statute’s “liability for costs” provision applies only if:
- the offer was not accepted, and
- the final judgment is less than the offer.
Note: This guide explains how the analyzer thinks about the statutory trigger (especially the “final judgment less than the offer” condition in Ind. Code § 34-50-1-2). It does not provide legal advice and won’t capture every procedural detail of Rule 68 timing or any case-specific complications.
For quick orientation, here’s the “logic shape” the tool uses:
| Input you provide | Tool’s comparison | Output effect (conceptual) |
|---|---|---|
| Offer amount | Compared to final judgment | Determines whether the “final judgment < offer” condition is met |
| Final judgment amount | Compared to offer | Drives whether cost-shifting is potentially triggered under § 34-50-1-2 |
| Acceptance status / timing | Whether acceptance occurred within Rule 68 time | Determines whether the “not accepted” condition can be satisfied |
If you’re the plaintiff or defendant making strategic decisions, or you’re just trying to understand exposure, the analyzer is most useful once you have an actual offer figure and an eventual judgment number (or a credible forecast).
When to use it
Use DocketMath’s Offer of Judgment Analyzer in Indiana when you’re working with real offer numbers and need a structured way to estimate how cost exposure might change based on the outcome.
Consider using it in these moments:
- **Pre-trial evaluation (early settlement math)
- You know the projected range of recovery and want to see what happens if the case ends up below the offer threshold.
- Post-judgment review
- You have a final judgment figure and want to test whether the “final judgment less than the offer” trigger could apply.
- Multiple-offer comparisons
- If you’ve exchanged more than one offer, run the analyzer separately for each offer to see which one (if any) satisfies the statutory comparison condition.
- Mediation / settlement conference preparation
- When the settlement discussion centers on “offer amount vs. likely judgment,” the tool gives you a consistent calculation framework.
You’ll get the most reliable results when you can clearly define the two most important values:
- Offer of judgment amount
- Final judgment amount
Tie-in to the statutory structure:
- Ind. Code § 34-50-1-1 governs whether an offer can be served and how Rule 68 timing matters for acceptance.
- Ind. Code § 34-50-1-2 makes the cost-shifting condition more specific: final judgment must be less than the offer, and the offer must have been not accepted.
Warning: Don’t rely on the tool alone if your dispute involves special damage structures (e.g., segmented claims, different categories of awards, or disputes over what counts as the “final judgment amount”). In those settings, confirm what figure you’re inputting matches the judgment language in your docket.
Step-by-step example
Let’s walk through one concrete Indiana scenario and show how the calculator’s outputs change as you vary key inputs.
Scenario: Defendant served an offer; judgment came in lower
Assume:
- Case type: civil lawsuit in Indiana
- Offer of judgment amount: $50,000
- Rule 68 acceptance: the offer was not accepted within the required time
- Final judgment amount: $32,500
This fact pattern maps neatly onto the statutory condition in Ind. Code § 34-50-1-2, which applies when:
- the offer was not accepted, and
- final judgment is less than the offer.
Step 1: Enter the offer amount
- Input: Offer amount = $50,000
Step 2: Enter the final judgment amount
- Input: Final judgment = $32,500
Step 3: Confirm the “not accepted” condition in the tool
- Input: **Offer not accepted (within Rule 68 timeframe)
Even without entering every procedural detail, the calculator will effectively evaluate the key comparison:
- $32,500 < $50,000
→ “final judgment less than the offer” condition appears satisfied.
Step 4: Review the analyzer’s output
The analyzer should flag that the case fits the basic trigger structure associated with Ind. Code § 34-50-1-2.
At a practical level, you’ll typically see an output aligned to questions like:
- Does the offer threshold exceed the final judgment?
- Is the final judgment below the offered amount?
- Therefore, is the “final judgment < offer” trigger likely met?
Quick sensitivity check: what if judgment had come in higher?
Now change only the final judgment amount:
- Offer amount remains: $50,000
- Final judgment becomes: $62,000
- Offer still not accepted
Comparison:
- $62,000 > $50,000
→ final judgment is not less than the offer.
Under Ind. Code § 34-50-1-2, this would mean the cost-shifting condition (as to that offer and that outcome) would not satisfy the “final judgment less than the offer” limitation.
Run it again with the analyzer
You should observe the output flip from “trigger condition met” to “trigger condition not met,” demonstrating why the final judgment number is the pivot.
Common scenarios
Indiana cases often present recurring “offer math” patterns. Here are common scenarios you can model with DocketMath.
1) Plaintiff offers; defendant ends up with a smaller recovery
Typical structure:
- Offer amount: high enough to beat projected or actual award
- Final judgment: less than offer
- Offer not accepted
Impact:
- The statute’s final judgment < offer limitation (see Ind. Code § 34-50-1-2) becomes the central comparison.
2) Defendant’s offer is close, but judgment lands just above it
Example:
- Offer: $100,000
- Final judgment: $100,500
- Not accepted
Even a small difference matters:
- $100,500 is not less than $100,000
So, the limitation tied to “final judgment less than the offer” would not be satisfied.
3) Multiple offers in the same case
If multiple Rule 68 offers were exchanged, you may need to evaluate each one against the same eventual final judgment.
Checklist:
- Did the offer remain “not accepted” under the Rule 68 timeframe?
- Was the final judgment less than that specific offer amount?
Run separate calculator passes:
- Offer A vs. final judgment
- Offer B vs. final judgment
- Offer C vs. final judgment
4) Judgment includes disputed components
If your judgment includes multiple components (damages and perhaps other awards), the calculator needs a single “final judgment amount” input.
Practical approach:
- Use the amount stated in the judgment entry (or the amount your court treats as the final award figure).
- If you are entering numbers from a draft order or partial rulings, results can change later.
Pitfall: Entering a “pre-judgment estimate” instead of the final judgment amount can invert the outcome comparison. Because the key limitation in Ind. Code § 34-50-1-2 turns on whether the final judgment is less than the offer, even a few thousand dollars can change the result.
5) The acceptance/timing issue dominates
Even if the final judgment is lower than the offer, the statutory cost-shifting framework is tied to whether the offer was accepted within the Rule 68 timeframe referenced by Ind. Code § 34-50-1-1.
Tool guidance:
- If the offer was accepted (and accepted on time), the cost-shifting trigger linked to “not accepted” may not apply.
- If acceptance status is uncertain, run two versions:
- “not accepted” scenario (best-case for the party seeking cost consequences)
- “accepted” scenario (best-case for the party avoiding them)
Tips for accuracy
Getting consistent, usable outputs from DocketMath’s analyzer mostly comes down to input discipline.
Use judgment amounts from the docket, not assumptions
To align with the statute’s key limitation in Ind. Code § 34-50-1-2:
- Enter the final judgment amount you expect to be treated as the operative figure.
If you’re still before the end of trial, you can model likely outcomes, but treat early numbers as estimates.
Keep money values in one format
Use a single numeric standard:
- Don’t mix dollars and cents in different ways across runs.
- Ensure you’re inputting the same “unit” every time (e.g., total award amount, not a damages subtotal).
Treat “not accepted” as a first-order switch
The statutory framework in Ind. Code § 34-50-1-1 ties offer consequences to acceptance status within the timeframe referenced by Indiana’s Rule 68.
