How Offer Of Judgment Analyzer rules vary in Maryland

What varies by jurisdiction

Run this scenario in DocketMath using the Offer Of Judgment Analyzer calculator.

Maryland’s Offer of Judgment procedure is governed primarily by Md. Rule 2-132. While the tool name stays the same, DocketMath’s Offer Of Judgment Analyzer for US-MD needs jurisdiction-aware logic—especially around timing and what counts as a valid written offer.

You can access the analyzer here: /tools/offer-of-judgment-analyzer.

Maryland’s core rule mechanics (Rule 2-132)

Md. Rule 2-132 sets the framework for filing a written offer to settle a claim for either:

• a specified dollar amount, or
• specified relief.

From the rule source provided, the key threshold concept is that the offer must be written and must specify a dollar amount or relief (not an estimate or a vague proposal). Source: https://www.courts.state.md.us/rules/civil/section132.html.

Timing: the jurisdictional “switch”

A major place where jurisdictions vary in offer practice is when an offer must be filed to trigger the rule’s post-judgment consequences. In Maryland, the analyzer needs to apply the rule’s operative timing approach to determine whether an offer is treated as timely (and therefore capable of driving the fee/award consequence logic).

Important note about claim types (as provided in your jurisdiction data):
No claim-type-specific sub-rule was found in the data you supplied. That means the calculator should treat the general/default timing period as the operative standard, rather than branching by claim category. In other words, for US-MD, DocketMath should not switch to different timing windows based on claim type based on the information available.

How inputs change outputs in the analyzer

Your litigation posture and your data entry determine whether the analyzer views an offer as “strong” or “risky.” Under Maryland’s Rule 2-132 framework, the most practical drivers are:

• Offer timing (was the “written offer” filed within the rule’s operative window?)
• Offer content (does the offer clearly specify a dollar amount or relief?)
• Judgment comparison (does the ultimate judgment “beat” the offer under the tool’s comparison logic?)

When any of these inputs change, the analyzer’s output can change—sometimes dramatically—because the underlying rule logic changes what counts as a favorable outcome.

Gentle disclaimer: DocketMath is a tool for analysis and planning, not a substitute for legal advice. Rules can be applied with nuance depending on the procedural posture and how dates/amounts are treated in your case.

What to verify

Before relying on DocketMath outputs, verify the inputs that are most likely to matter under Md. Rule 2-132. Use this checklist to make your results more dependable.

• The governing rule or statute for the jurisdiction.
• Any local rule overrides or administrative guidance.
• Effective dates and whether amendments apply.

1) Confirm your offer is a “written offer” with the right level of specificity

Rule 2-132 contemplates a written offer to settle a claim for:

• a specified dollar amount, or
• specified relief.

Action for DocketMath inputs

• If you’re making a monetary offer, enter a single stated number (e.g., 250000), not a range or estimate.
• If you’re making a relief offer, enter the specific relief in the form the analyzer expects (if the tool uses free text or a structured category, make sure it matches what the tool is built to recognize).

Why this matters: Maryland’s rule text (as provided) emphasizes specified terms, and the analyzer can only compare accurately if it can treat your entry as “specified.”

2) Verify the timing window you’re using (and don’t assume claim-type branching)

Offer timing is often the biggest source of errors in offer analysis.

Maryland default approach (based on your jurisdiction data):

• Use the general/default timing period.
• Do not select different timing rules by claim type because your supplied data did not identify a claim-type-specific sub-rule.

Action for DocketMath inputs

• Use the offer filing date (the date the written offer is actually filed), not the date negotiations began.
• Enter the offer date and the trial/judgment date (or whatever date the analyzer uses for its “comparison window”).
• Run the calculator and check whether it flags the offer as timely or untimely under the US-MD Rule 2-132 logic.

3) Confirm how you’re defining the “judgment comparison” number

Even with correct jurisdiction logic, the analyzer can only tell whether the judgment “beats” the offer if you provide the comparison value consistently.

Action for DocketMath inputs

• Choose the final judgment amount (or the tool’s expected equivalent, such as a net figure after offsets if the tool asks for that).
• Make sure the number reflects the same reality the court would treat as the relevant comparison point in your situation.

4) Keep “specified relief” structured and consistent (avoid ambiguity)

If you enter relief using text, keep it clear and specific so the analyzer can treat it as an “offer” of a defined kind.

Action for DocketMath

• Use a consistent description (e.g., “injunctive relief requiring X” rather than “appropriate relief”).
• If the tool supports categories, prefer categories over vague text.

Analyzer input/output map (quick reference)

Related reading

• Offer of Judgment Analyzer Guide for Alabama
• Offer of Judgment Analyzer Guide for Arizona
• Offer of Judgment Analyzer Guide for Colorado