Abstract background illustration for How to calculate pre/post-offer damages split in Texas

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

7 min read

Published June 4, 2026 • By DocketMath Team

Under review

missing_or_unverified_packet

Quick takeaways

  • Texas uses a pre/post-offer framework tied to Tex. Civ. Prac. & Rem. Code § 42.004 for how certain litigation costs may shift when a settlement offer is made and evaluated.
  • In DocketMath, you calculate the pre/post-offer damages split by separating damages that accrue before the offer date from those that accrue after the offer date, then applying Texas-style cost-shifting logic from the verified rule set for § 42.004.
  • Texas offer cost-shifting in the DocketMath rules uses threshold parameters reflected in the verified set: 80% (claimant threshold) and 120% (defendant threshold), plus a guardrail that litigation costs awarded cannot exceed the claimant’s recovery.
  • If your damages model includes interest, DocketMath can help keep interest rate logic aligned with the verified Texas finance rules tied to Tex. Fin. Code § 304.103 and Tex. Fin. Code § 304.003 (using the verified rate boundaries in the rule set).

Note: This guide explains how to compute the pre/post-offer damages split and how it typically feeds into Texas-style cost-shifting analysis. It is not legal advice.

Inputs you need

Before you run DocketMath → /tools/pre-post-offer-damages, gather these inputs. Keeping them organized will make the pre/post split deterministic.

Core offer split inputs

  • Offer date (the date the settlement offer was made)
  • Judgment date / damages measurement endpoint (i.e., what date your damages totals run through)
  • Total claimed damages and/or a damages schedule with dates so you can allocate amounts to “pre” vs. “post”

Amount inputs used for § 42.004 thresholds (as implemented in DocketMath rules)

  • Offer amount
  • Claimant’s recovery (in many workflows this is the final judgment amount; if you also model an estimate, keep both values)
  • Which side is treated as the claimant vs. defendant for threshold evaluation (this matters for applying the verified 80% / 120% trigger logic correctly)

Interest-related inputs (only if your damages model includes interest components)

If you are modeling interest as part of damages, also gather:

  • A prejudgment interest rate basis consistent with the Tex. Fin. Code § 304.103 logic in your workflow
  • A post-judgment interest rate basis consistent with the Tex. Fin. Code § 304.003 logic in your workflow
  • Any contract-specified rate you plan to reconcile within the verified rule set behavior (the verified rules include logic consistent with “lesser of” contract rate vs. the applicable upper boundary described in the verified set)

How the calculation works

DocketMath calculates the pre/post-offer damages split in Texas using a repeatable workflow:

  1. Allocate damages by time relative to the offer date
  2. Compute pre-offer and post-offer totals
  3. Feed those outputs into the Texas offer-cost shifting analysis driven by § 42.004 logic as captured in the verified DocketMath ruleset
  4. Apply the verified guardrail that shifted costs cannot exceed the claimant’s recovery

1) Split the damages timeline at the offer date

Start with your damages schedule (or the best-available time-series approximation). Create two buckets:

  • Pre-offer damages: amounts that accrue before the offer date
  • Post-offer damages: amounts that accrue on/after the offer date (use the same “on/after” convention everywhere in your inputs)

Example (quarterly figures):

Time periodAmountFalls before offer?Goes into bucket
Jan–Mar 2024$120,000YesPre
Apr–Jun 2024$95,000Split if offer date falls mid-periodSplit accordingly
Jul–Sep 2024$140,000NoPost

If you have only a single total amount (no dates), you’ll need an allocation assumption. DocketMath can still produce a split, but the accuracy of the split depends on how well your allocation reflects when damages accrued.

2) Produce the split totals

After allocation:

  • Pre-offer total = sum of all amounts in the pre bucket
  • Post-offer total = sum of all amounts in the post bucket
  • Sanity check: Pre + Post ≈ your modeled total damages (allowing for rounding)

If the totals don’t reconcile, downstream threshold/cost-shifting interpretation can be misleading—even if the threshold math is correct.

3) Apply Texas jurisdiction-aware cost-shifting triggers (thresholds)

Texas’s offer-cost shifting framework is tied to how the final outcome compares to the offer. In the verified DocketMath Texas ruleset for § 42.004, the key threshold parameters include:

  • Claimant threshold percent: 80
  • Defendant threshold percent: 120

In practice, DocketMath uses your entered offer amount and claimant’s recovery to decide which cost-shifting branch applies. Because DocketMath needs to know who is treated as the claimant vs. defendant for threshold evaluation, double-check that your “role” configuration matches your scenario.

4) Enforce the “costs awarded cannot exceed the claimant’s recovery” constraint

Even when the math suggests a cost-shifting amount, the verified rules include a guardrail:

  • Litigation costs awarded cannot exceed the claimant’s recovery

So if you see outputs that appear “large,” confirm whether the calculation is correctly applying that recovery ceiling.

5) Interest components (optional, but common in damages models)

If your damages model includes interest, treat it as a separate modeling layer from the pre/post split:

  • The pre/post-offer split answers: when did damages accrue relative to the offer date?
  • The interest logic answers: how does damages/amount grow under the applicable interest rules?

DocketMath’s verified rules include interest-rate logic tied to:

  • Tex. Fin. Code § 304.103 for prejudgment interest rate behavior
  • Tex. Fin. Code § 304.003 for post-judgment interest rate behavior

And the verified rule set behavior includes:

  • interest rate boundaries using 5% and 15% bounds (as reflected in the verified rules)
  • for some contract-related scenarios, a “lesser of contract rate or 18%” concept is included in the verified rule set configuration

Warning: Allocating interest amounts to the wrong bucket (pre vs. post) can distort the split you rely on for offer-cost-shifting analysis. Keep your “when” logic (accrual timing) distinct from your “rate/interest” logic.

Common pitfalls

  • Inconsistent “on the offer date” handling

    • If you put amounts “on the offer date” into different buckets across your schedule and DocketMath inputs, Pre + Post won’t reconcile.
    • Fix: pick a convention (e.g., “on/after” = post) and apply it consistently.
  • Forgetting the recovery ceiling for shifted litigation costs

    • The verified rule set includes the constraint that shifted litigation costs awarded cannot exceed the claimant’s recovery.
    • Symptom: outputs seem inflated; root cause is often missing or incorrect recovery inputs/roles.
  • Reversing claimant vs. defendant threshold roles

    • The verified 80% / 120% logic depends on who is being evaluated as the claimant vs. defendant.
    • Symptom: DocketMath triggers the wrong cost-shifting branch.
    • Fix: confirm the role mapping before running.
  • Interest-rate basis drift

    • If your model uses a different interest-rate basis than the verified Texas finance logic used by DocketMath, the interest component can change your modeled totals and affect the split you feed into the offer analysis.
    • Fix: ensure your interest settings reflect the same statute-driven logic your workflow is meant to follow.
  • Time-series damages that don’t sum

    • A split that doesn’t add up to the modeled total can lead to confusion in downstream comparisons.
    • Quick check: Pre + Post ≈ total.

Sources and references

Next steps

  1. Open DocketMath’s calculator: /tools/pre-post-offer-damages
  2. Enter:
    • offer date
    • your damages timeline (or best-available allocation approach)
    • offer amount and modeled claimant recovery
    • confirm claimant vs. defendant role mapping for threshold evaluation
  3. Run the calculation and verify:
    • Pre + Post equals your modeled damages total (within rounding)
  4. If your model includes interest:
    • confirm your interest settings align with the verified Texas finance logic used by DocketMath (for prejudgment and post-judgment components)
  5. Record the split totals and the threshold/cost-shifting outcome for your analysis workflow.

Related reading