How to run Offer Of Judgment Analyzer in DocketMath for Indiana

Step-by-step

Below is a practical walkthrough for running Offer Of Judgment Analyzer in DocketMath for Indiana (US-IN) using jurisdiction-aware rules grounded in Ind. Trial Rule 68.

1) Open the tool from the primary CTA

1. Go to: /tools/offer-of-judgment-analyzer
2. Confirm the analyzer page loads the input fields and the Calculate button.

2) Select Indiana jurisdiction (US-IN)

Look for a Jurisdiction or State selector in the tool settings.

• Choose: Indiana (US-IN)

DocketMath will apply the Indiana rule set, including the default timing language in Ind. Trial Rule 68, which governs offers “at any time more than ten [10] days before the trial begins.”

3) Enter the required inputs

Exact labels can vary by tool version, but the analyzer generally needs the core values that drive the comparison between:

• what you offered
• what the final judgment ultimately awarded
• and the tool’s timeline logic (whether the offer qualifies and how the response window is treated)

Use Indiana-aware date inputs where available:

• Offer date (date the offer was served)
• Trial start date (the date used for the “before trial” check)
• Date of judgment / final outcome date (where the UI prompts)
• Offer amount (money offer) and/or other specified terms if the tool supports non-monetary effects
• Final judgment amount (what the court ultimately awarded)
• Costs-at-issue (if the tool includes cost handling fields)

If the tool allows you to enter both “judgment” and “costs,” prefer values that match the judgment record you’re analyzing to avoid overstating or understating exposure.

4) Make sure the Indiana “timing” rule is satisfied

Indiana’s general rule is not a claim-type carve-out. In other words, the content below assumes the default/baseline language in Ind. Trial Rule 68 applies.

Per Ind. Trial Rule 68 (default timing framework):

• A party defending against a claim may serve an offer “at any time more than ten [10] days before the trial begins.”
• Then it uses a ten (10) day response window:

  • if the offeree does not accept “within ten [10] days after …” service, the rule’s consequences may apply (the remainder of the sentence governs the effect of failure to accept).

How this matters in DocketMath:
If your offer date is too close to the trial start date, the analyzer may:

• flag the offer as outside the qualifying period, or
• calculate consequences in a way that depends on the tool’s timeline assumptions.

5) Choose the role (offeror vs. offeree) if the UI provides it

Many Offer of Judgment calculators depend on which side made the offer and which side is assessing exposure.

If DocketMath asks:

• Are you calculating for the offeror or the offeree? Select the option that matches your analysis.

Quick orientation:

• If you served the offer, you’re usually assessing how the rule could shift exposure depending on the final outcome.
• If you received the offer, you’re usually assessing how rejecting the offer could affect costs or other specified effects.

6) Run the calculation

1. Click Calculate (or the tool’s equivalent button).
2. Review any validation messages first—especially those tied to:

   • the “more than ten (10) days before trial begins” requirement
   • the response window (often represented as “within ten (10) days after service”)
   • missing or mismatched judgment and costs inputs

7) Interpret the output

DocketMath will typically show:

• a comparison between the offer terms and the final judgment terms
• an estimated consequence driven by the Indiana Trial Rule 68 framework
• a summary you can use for case evaluation

If the analyzer produces multiple scenarios, make sure you focus on the scenario tied to the actual dates you entered.

8) Adjust inputs and rerun (fast iteration)

When your dates or amounts change, the results can change quickly—especially around the 10-day thresholds.

Try one controlled edit and recalculate:

• Adjust the offer amount (for example, increase/decrease in steps to see where the output changes)
• Adjust the offer date (move it earlier or later to test whether it remains more than ten (10) days before trial begins)
• Replace placeholder numbers with the actual award and actual costs once available

Common pitfalls

These are the errors that most often cause Offer of Judgment Analyzer results to look “wrong” in Indiana.

1) Offer served within 10 days of trial start

Indiana Trial Rule 68’s general timing requirement is explicit: the offer must be served “more than ten [10] days before the trial begins.”
If your offer is served on (or too near) the trial window, the analyzer may treat the offer as outside the qualifying period.

2) Confusing “trial begins” with unrelated docket dates

Cases often include multiple key dates (pretrial conference, status hearings, jury selection, etc.). The rule keys off the date the trial begins.

Checklist:

• I entered the trial start date, not a pretrial date
• The trial start date matches the docket event I’m relying on

3) Ignoring the 10-day response window after service

Trial Rule 68 also includes a “within ten [10] days after …” acceptance window.
If the tool asks for an acceptance/rejection date and you leave it blank, results may rely on assumptions.

Checklist:

• I supplied the dates the UI requests to support the tool’s “within ten (10) days after service” logic
• My acceptance/outcome timing doesn’t contradict the dates I entered elsewhere

4) Forgetting costs handling fields

Costs are often central to how these mechanisms play out.

Checklist:

• Costs inputs match the costs referenced in the judgment or the record you’re analyzing
• I’m not mixing “costs accrued” vs. “total costs” without matching the tool’s field definitions

5) Assuming claim-type-specific sub-rules exist (when the default applies)

For this Indiana implementation, the analysis assumes the general/default rule applies. The provided Trial Rule 68 excerpt shows a baseline framework and does not identify claim-type-specific timing exceptions within the excerpt cited here.

Pitfall:

• Treating the rule as if it has claim-type-specific timing exceptions when the general/default language governs can lead to incorrect timing inputs and outcomes.

Try it

Use this quick “sanity test” workflow to validate your data before relying on the output.

1. Confirm jurisdiction: set Indiana (US-IN).
2. Enter dates first:

   • Offer date: pick a date clearly more than 10 days before trial start (example: trial starts on a Monday; choose an offer served the prior week, at least 11+ days earlier).
   • Trial start date: use the actual docket event date where the trial begins.
3. Enter amounts:

   • Offer amount
   • Final judgment amount
4. Choose role (if available):

   • offeror vs. offeree must match your analysis
5. Run the calculation.
6. Make one controlled adjustment:

   • Move the offer date closer to trial by 1–3 days and recalc.
   • If results flip or validation warnings appear, that’s expected—the “more than ten (10) days before the trial begins” condition is sensitive.

If you see a validation warning, don’t override it blindly—fix the date logic and recalculate.

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