Pre/Post-Offer Damages Split Guide for Maryland

What this calculator does

Run this scenario in DocketMath using the Pre Post Offer Damages calculator.

DocketMath’s Pre/Post-Offer Damages Split guide and calculator help Maryland plaintiffs and defendants separate a damages claim into two time-based buckets:

• Pre-offer damages: the portion of damages that accrued before a qualifying settlement offer date.
• Post-offer damages: the portion of damages that accrued on/after the qualifying settlement offer date.

That split matters in Maryland because the state’s settlement-offer regime can shift the financial consequences of refusing an offer after a certain point—commonly affecting how recoverable amounts are calculated and whether additional sums may be triggered.

For Maryland, the relevant framework in this guide is anchored on the offer-related timelines and limitation periods, including:

• Md. Code, Cts. & Jud. Proc. § 5-106 — 3-year limitations period for certain actions, with a stated exception structure (listed here as exception V2).

  • Source: https://codes.findlaw.com/md/courts-and-jud-pro-sect-5-106/?utm_source=openai
• Md. Courts and Judicial Proceedings § 5-205 — 3-year limitations period for certain civil actions (listed here as exception M4).

This guide is not legal advice. It’s a practical workflow for organizing numbers the way settlement-offer calculations typically require—so you can feed clean inputs into the DocketMath tool.

Output you’ll get from DocketMath (what to expect)

When you use the /tools/pre-post-offer-damages calculator, you’re effectively building a damages timeline. The output generally supports:

• a pre-offer damages total
• a post-offer damages total
• a combined damages total
• (depending on your entered structure) per-day/per-month accrual math that explains the split

To start, open the tool here: /tools/pre-post-offer-damages.

When to use it

Use the pre/post-offer split workflow when you have all (or nearly all) of the following:

• A known settlement offer date (the date you’ll use as the dividing line).
• Damages that accrue over time, such as:

  • ongoing wage loss or benefits
  • continuing medical expenses
  • certain recurring contractual damages
  • interest-like components that you model day-by-day
• A need to model damages consequences tied to whether the defendant accepted early (or the plaintiff rejected early).

In Maryland practice, timelines often show up alongside limitation period analysis—particularly the 3-year limitations period described in:

• Md. Code, Cts. & Jud. Proc. § 5-106 (3 years; exception V2)
• Md. Courts and Judicial Proceedings § 5-205 (3 years; exception M4)

Practical “use it” checklist

Use DocketMath’s calculator if you can check at least these:

Step-by-step example

Below is a concrete walkthrough in a Maryland-style pre/post-offer split. The numbers are simplified to show the mechanics clearly.

Scenario

• Damages accrue at a steady rate.
• You’re modeling for a settlement offer made on March 1, 2024.
• Damages begin on January 1, 2024.
• Damages are modeled through December 31, 2024.
• Rate: $200 per day (you can swap in your own structure).

Step 1: Identify the dates for the timeline

Step 2: Choose your split rule (inclusive/exclusive)

Most calculators implement one of these conventions. DocketMath’s approach is designed to be consistent—use the convention the tool uses, but here’s how to think about it:

• Pre-offer: accrual before the offer date
• Post-offer: accrual on/after the offer date

Step 3: Compute day counts (with a consistent convention)

Let’s compute counts using a “before vs. on/after” approach:

• Pre-offer period: 2024-01-01 through 2024-02-29

  • January 31 days + February 29 days (2024 is a leap year)
  • Total pre days = 60
• Post-offer period: 2024-03-01 through 2024-12-31

  • March 31 + April 30 + May 31 + June 30 + July 31 + Aug 31 + Sep 30 + Oct 31 + Nov 30 + Dec 31
  • Total post days = 306

Step 4: Apply the daily rate

• Pre-offer damages = 60 days × $200/day = $12,000
• Post-offer damages = 306 days × $200/day = $61,200
• Total modeled damages = $12,000 + $61,200 = $73,200

Step 5: Translate into DocketMath inputs

In DocketMath, you’ll typically enter:

• accrual start date: 2024-01-01
• offer date: 2024-03-01
• accrual end date: 2024-12-31
• accrual rate: $200/day

Once entered, the tool produces the pre and post totals based on its built-in split convention.

Step 6: Connect the numbers to Maryland context (without doing legal math)

Maryland includes a 3-year limitations framework in Md. Code, Cts. & Jud. Proc. § 5-106 and Md. Courts and Judicial Proceedings § 5-205—both listed here as 3 years with exceptions (V2 and M4, respectively). Those limitation rules can affect what damages you’re allowed to model or recover depending on the claim type and filing date.

This guide does not compute limitation outcomes; it helps you structure the damages split correctly once you’ve decided what time window you’re analyzing.

Common scenarios

The pre/post split looks different depending on how damages are generated. Here are frequent Maryland scenarios where a time split is useful.

1) Wage loss / benefits continuing over time

What you enter conceptually:

• start date: when the lost wages begin
• end date: when they stop (or model through)
• rate: daily or monthly loss amount

How the split behaves:

• Pre-offer bucket captures losses up to the day before the offer date (depending on convention)
• Post-offer bucket captures losses from the offer date forward

2) Medical expenses as dated charges

What you enter conceptually:

• list of charge dates and amounts (or convert to per-day accrual)
• offer date as the divider

How the split behaves:

• Each charge falls into pre or post based on its date
• This avoids the “steady rate” assumption

3) Contract damages modeled as performance shortfalls

What you enter conceptually:

• contract performance period start/end
• measure damages per month (or per unit)
• offer date divides the performance window

How the split behaves:

• Pre bucket = damages tied to performance completed before offer
• Post bucket = damages tied to performance after offer

4) Interest-like accrual components you model as day-based

If your damages calculation includes a component that grows over time (even if it’s not literally statutory interest), the split gives you a clean time segregation.

Example pattern:

• principal damages fixed
• additional time component = rate × time

Then:

• pre-offer portion of the time component lands in pre
• post-offer portion lands in post

Quick reference table: inputs to collect

Tips for accuracy

Small date issues can move dollars. Use these safeguards when entering values into DocketMath.

1) Standardize your date format

• Use YYYY-MM-DD consistently.
• Don’t mix “March 1, 2024” (locale format) with numeric formats.
• If your spreadsheet uses a different timezone/clock convention, convert to a date-only value before calculating.

2) Confirm the split convention once

Most errors come from whether the offer date is included in pre or **post

Related reading

• Pre/Post-Offer Damages Split Guide for Alabama
• Pre/Post-Offer Damages Split Guide for Arizona
• Pre/Post-Offer Damages Split Guide for California