Offer of Judgment Analyzer Guide for New York

What this calculator does

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

DocketMath’s Offer of Judgment Analyzer (New York) helps you evaluate the practical impact of an offer of judgment under N.Y. CPLR § 3220. In plain terms, the tool compares the financial outcome if (1) the case value lands above your opponent’s offer versus (2) your side receives less than the offer—then estimates how post-offer costs and fee-shifting exposure can change based on the timing and direction of the offer.

Because this is an analyzer (not a predictive model), it focuses on the statutory mechanics of CPLR 3220, especially the offer period and the consequences after the offer.

Statutory anchor: the offer window (default rule)

Under N.Y. CPLR § 3220, “Any party may serve an offer of judgment upon any other party…” and the offer is structured to trigger post-offer consequences based on how the matter resolves relative to the offer. The statute governs the timing and effect of that offer, including the concept that the offer is open for a defined period before the consequences attach.

Source: N.Y. CPLR § 3220
https://www.nysenate.gov/legislation/laws/CPL/3220

What you enter, what you get

Use the calculator to convert your litigation facts into a structured comparison:

• Inputs you provide

  • Offer amount
  • Offer date (or filing/serving date, depending on your workflow)
  • Judgment amount (or projected recovery you want to compare)
  • Whether the offer is “to you” or “from you” (the tool uses this to interpret direction)
  • Any cost/fee assumptions you want the calculator to model (if your workflow includes them)

• Outputs you get

  • A relative outcome (e.g., “judgment exceeds offer” vs “judgment below offer”)
  • A timeline check for the offer window under the default § 3220 mechanics
  • A scenario-based estimate of which party is more exposed to adverse post-offer cost consequences

For best results, treat the calculator like a litigation spreadsheet: you’re stress-testing scenarios using your numbers, not trying to “forecast” a judge’s decision.

Primary CTA: /tools/offer-of-judgment-analyzer

When to use it

DocketMath’s Offer of Judgment Analyzer is most useful when you’re dealing with the decision point around an offer—particularly when you want to quantify the risk of proceeding without settling.

Consider using it when you want to:

• Evaluate whether to accept an offer you received
• Assess whether an offer is worth making given the amount you expect to recover
• Compare settlement posture across multiple numbers (e.g., offer at $50,000 vs $75,000)
• Sanity-check timing for your offer window under the default § 3220 rule
• Run “what-if” scenarios before filing or responding to offer paperwork

Timing matters: don’t skip the date fields

The calculator’s utility drops if you enter dates loosely. In practice, small differences in the offer date can affect whether the statute’s offer window has run when the relevant event occurs.

Checklist for when to use it:

Step-by-step example

Below is a practical walkthrough you can mirror in DocketMath. This example uses a straightforward structure to show how the calculator’s output changes as your judgment outcome moves relative to the offer.

Example setup (New York)

Assume:

• Offer amount: $60,000
• Offer served: March 1, 2026
• Your expected judgment: you want to test two possibilities:

  1. $75,000 judgment (you do better than the offer)
  2. $45,000 judgment (you do worse than the offer)

You want to understand which side tends to face more adverse post-offer consequences under N.Y. CPLR § 3220 and whether the outcome clears the offer threshold.

Step 1: Choose direction in the tool

In DocketMath, indicate whether the offer is:

• From the other party to you, or
• From you to the other party

This direction matters because it changes what “winning relative to the offer” means for the analysis.

Step 2: Enter the offer amount

• Enter: $60,000

Step 3: Enter the offer date

• Enter: 03/01/2026

The tool uses the default CPLR 3220 mechanics (general offer window described in the statute) to evaluate when the offer’s statutory consequences begin to matter.

Step 4: Compare scenario A — judgment above the offer

• Enter judgment: $75,000

Typical result interpretation:

• The tool should identify that the judgment exceeds the offer amount.
• Depending on direction (who made the offer), the output will generally indicate which side is more favorably positioned relative to the offer threshold under CPLR 3220’s post-offer consequence framework.

Step 5: Compare scenario B — judgment below the offer

• Enter judgment: $45,000

Now the relative comparison flips:

• The tool should identify that the judgment is below the offer amount.
• The output should shift to the other direction’s relative exposure.

Step 6: Review the timeline check

Finally, review any timeline element the tool displays:

• Whether the offer window aligns with the relevant event date you input
• Whether the offer was effectively open when it mattered

If the timeline check fails, your numbers might be fine, but the offer consequences may not apply the way you assumed.

Common scenarios

Offer of judgment analysis often repeats in patterns. Here are common scenarios you can model in DocketMath, along with what to watch for.

1) Offer made “to” the plaintiff (and the defendant expects a low recovery)

• Direction: Defendant → Plaintiff
• Offer amount: set based on expected low exposure
• Tool use: test if your judgment (or projected recovery) is likely above or below the offer

Key model question:

• Will the final outcome land above $X?

2) Offer made “to” the defendant (and the plaintiff expects meaningful recovery)

• Direction: Plaintiff → Defendant
• Offer amount: set based on a valuation of the claim
• Tool use: determine how much “margin” you need so that likely judgment clears the offer threshold

Key model question:

• Is there enough value such that the judgment likely exceeds the offer?

3) High-uncertainty damages (you want multiple offer levels)

Instead of one number, run several offers:

• $25,000
• $50,000
• $75,000

The tool will show how the relative outcome changes and which direction becomes more favorable.

Checklist:

4) Timing uncertainty (service date questions)

Some teams struggle with “what date counts” for the offer. DocketMath can help you model:

• If the offer date is March 1 vs March 5, how does the timeline check behave?

What to do:

• Use the earliest credible service date if you’re trying to be conservative about timing; use the later date if your workflow argues that the offer is not effective until later.

5) Settlement negotiations with conditional numbers

Offers sometimes evolve (e.g., “I’ll settle for $X if paid by a certain date”). If your offer is conditional, the analyzer may not capture every nuance of how conditions affect enforceability. Use the calculator for amount/timing framing, then match the output to the actual offer language your court filing uses.

Tips for accuracy

To get outputs you can trust, focus on data quality and consistent assumptions.

Use precise monetary numbers

• Enter offer and judgment amounts in the same units (dollars, not rounded “ballpark”)
• If you’re modeling future totals, decide whether your numbers include:

  • Interest
  • Specific costs
  • Any statutory fee components

If you’re uncertain, run two versions:

Don’t mix offer direction

A common error is entering the correct amount but selecting the wrong direction (who made the offer). Direction flips the interpretation of “above offer” vs “below offer.”

Accuracy checklist:

Confirm you’re using the default CPLR 3220 period

This guide applies the default period under N.Y. CPLR § 3220. If you are working with a specialized posture and you

Related reading

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