How to calculate pre/post-offer damages split in Indiana

Quick takeaways

• Indiana’s pre/post-offer damages split is driven by Offer of Judgment timing under Ind. Trial R. 68—the rule allows an offer “more than ten [10] days before the trial begins.”
• DocketMath’s pre-post-offer-damages calculator helps you allocate damages accrued before the offer versus accrued after the offer, using your dates to match the rule’s structure.
• Based on the rule text you provided, no claim-type-specific sub-rule was found, so use the general/default timing (“more than ten days before trial begins”) as your governing rule language.
• Your split will be most accurate when you provide: (1) the offer service date, (2) your damages accrual window (start/end and/or schedule), and (3) whether your numbers include interest and/or costs.

Inputs you need

To calculate a pre/post-offer damages split in Indiana using DocketMath, gather these inputs first.

Core dates

• Offer date (service date): the date you served the offer on the adverse party.
• Trial begin date (optional, but recommended): used to validate the “more than ten [10] days before trial begins” requirement under Ind. Trial R. 68.
• Cutoff date for the split: typically the offer date for your accrual-period accounting (pre = before offer; post = on/after offer, depending on your accrual convention).

Damages amounts by accrual period (preferred)

• Damages accrual window start date (the first date damages begin accruing for your model).
• Damages end date (e.g., last day you count for the damages model, judgment date, or other measurement date).
• Either:

  • Pre-offer damages total (accrued from start through the day before the offer date under your convention), and
  • Post-offer damages total (accrued from the offer date through the end date),
    or
  • an accrual schedule/rate that DocketMath can apply across the date range (for example, daily rent/penalty, hourly work logs, or per-invoice timing).

Interest and costs treatment (for your accounting categories)

Ind. Trial R. 68 references offers “with costs then accrued.” Even though this article focuses on splitting damages, it matters practically to keep your categories consistent:

• Whether your damages figure includes interest
• Interest rate and interest accrual method (if applicable)
• Whether costs are included in your “damages” subtotal or tracked separately

A practical approach is to decide upfront:

• Split damages into pre/post buckets, and
• Track costs separately (or, if you truly must include costs in a single figure, treat that combined number consistently across pre/post calculations).

How the calculation works

This section shows a jurisdiction-aware workflow aligned with Ind. Trial R. 68 and the general/default timing language you provided.

1) Validate the offer timeline (Indiana default rule)

Ind. Trial R. 68 provides (in substance) that:

• “At any time more than ten [10] days before the trial begins, a party… may serve… an offer… .”
  (The rule text also references “costs then accrued.”)
  Source: Ind. Trial R. 68, Indiana Trial Rules (Offer of Judgment) — https://www.in.gov/courts/rules/trial_proc/index.html#_Toc89177571

Because your note indicates no claim-type-specific sub-rule was found for this excerpt, treat the “more than ten [10] days before trial begins” rule language as the general/default timing.

Practical validation check (strict “more than 10”):

1. Compute the day difference between trial begin date and offer service date.
2. Confirm it is > 10 days (not ≥ 10).

If your offer is served within 10 days of trial, your pre/post damages split can still be calculated as a modeling exercise, but you should flag that the offer timing may not meet the rule’s “more than ten” requirement.

Common date error to avoid: anchoring on the filing date rather than the service date. The rule uses “serve upon the adverse party,” so the service date should be your cutoff anchor in the DocketMath inputs.

2) Choose the pre/post cutoff used for the split

For a damages split, DocketMath typically allocates damages into two buckets based on your accrual date ranges:

• Pre-offer damages: damages accrued before the offer date (often: start → day before offer)
• Post-offer damages: damages accrued on/after the offer date (often: offer date → end date)

Because your damages may accrue in different ways, decide which convention matches your underlying damages model:

• If your daily damages are “per day of accrual,” then:

  • pre = all full days before offer date
  • post = offer date through end date
• If your schedule is per “event date” (e.g., each invoice date), then:

  • pre = events dated before offer
  • post = events dated on/after offer

DocketMath will follow the dates you provide. The accuracy of the legal-economic split is therefore mostly a question of correct date alignment to your accrual method.

3) Feed the accrual structure into DocketMath

Open DocketMath’s tool:

• /tools/pre-post-offer-damages

Then provide one of these input styles:

Option A: Provide totals

• Enter pre-offer damages and post-offer damages directly (if you already calculated them).

Option B: Provide a schedule/rate and dates

• Enter:

  • damages start date
  • damages end date
  • accrual rate / formula (or daily/hourly schedule)
• DocketMath applies your model across dates and sums the pre and post portions.

DocketMath’s output should correspond to your date-based bucket design:

• Pre-offer damages
• Post-offer damages
• Total (if you provided total-consistency inputs)

4) Treat “with costs then accrued” consistently

Ind. Trial R. 68’s reference to “costs then accrued” is a reminder that the “offer moment” matters for costs.

For your workflow:

• If you only need a damages split, keep costs out of the damages buckets.
• If your downstream analysis uses a combined number, define that combined number clearly (for example: “damages only” vs “damages + interest” vs “damages + interest + costs”), and use the same definition for both pre/post.

This prevents a frequent mismatch where one team splits damages but another team includes costs “somewhere else,” leading to inconsistent totals.

5) Use the outputs downstream (without overstating legal conclusions)

Once you have the pre/post damages numbers, you can use them to compare scenarios (different damages end dates, different interest treatments, etc.). Keep the analysis framed as calculation support tied to Ind. Trial R. 68’s offer timing structure—avoid presenting the calculator output as a substitute for legal advice.

Common pitfalls

• Wrong anchor date (service vs filing): Ind. Trial R. 68 speaks in terms of serving the offer; use the service date when setting the cutoff.
• Off-by-one day: Double-check whether your pre bucket excludes the offer date (common) or includes it (less common). Align your convention with how your damages accrue.
• Using “≥ 10” instead of “more than 10”: The rule language is “more than ten [10] days”. Use a strict > 10 calculation against the trial begin date.
• Mixing costs into damages: Since the rule text references “costs then accrued,” combining costs into “damages” can distort what your pre/post buckets represent.
• Inconsistent interest treatment: If your damages input already includes interest, don’t apply interest a second time via an accrual rate schedule.
• Assuming claim-type-specific timing applies: Your note indicates no claim-type-specific sub-rule was found here. Use the general/default timing unless you later confirm a different rule applies to your specific claim type.
• Overlapping date ranges: If both pre and post include the offer date, you’ll double count. Ensure the pre/post ranges are complementary under your convention.

Sources and references

• Ind. Trial R. 68 (Offer of Judgment) — Indiana Trial Rules (Offer of Judgment)
  https://www.in.gov/courts/rules/trial_proc/index.html#_Toc89177571
  (Key excerpt language: offers may be served “more than ten [10] days before the trial begins”; rule also references “costs then accrued.”)

Next steps

1. Go to the calculator: /tools/pre-post-offer-damages
2. Enter:

   • Offer date (service date)
   • Trial begin date (so you can validate the “more than ten [10] days” timing from Ind. Trial R. 68)
   • Damages start/end dates and your accrual method (or pre/post totals if you already computed them)
3. Confirm your accounting categories:

   • damages-only vs damages+interest vs inclusion of costs
4. Run the calculation and save:

   • Pre-offer damages
   • Post-offer damages
   • any totals DocketMath outputs
5. If your strategy requires revisiting timing alignment, update only the relevant date fields and