How to run Offer Of Judgment Analyzer in DocketMath for New York

Step-by-step

This guide shows how to run Offer Of Judgment Analyzer in DocketMath for New York (US-NY) using jurisdiction-aware rules tied to N.Y. C.P.L.R. § 3221 (Civil Practice Law and Rules—Offer of Judgment). The calculator helps you compare the economics of making (or receiving) an offer and the resulting potential cost-shifting.

1) Open the tool and confirm you’re in the correct jurisdiction

1. Go to the primary CTA: /tools/offer-of-judgment-analyzer
2. Select/confirm jurisdiction: New York (US-NY).
3. If the interface asks for role (offeror vs. offeree), pick the option that matches what you’re analyzing:

   • Offeror: you (the party making the offer)
   • Offeree: the other side (you’re evaluating what happens if you receive the offer)

2) Identify the offer timing rule that drives eligibility inputs

For New York, § 3221 provides a general/default timing window. It states that—except in a matrimonial action—a party may serve an offer:

• “at any time not later than ten days before trial”
  (N.Y. C.P.L.R. § 3221)

Your jurisdiction note says no claim-type-specific sub-rule was found, so treat this as the general default period unless your case is truly outside the “except in a matrimonial action” boundary.

This timing rule matters because the analyzer typically needs date inputs to determine whether your offer is positioned for the “not later than ten days before trial” requirement.

3) Enter the core inputs DocketMath needs

Most Offer Of Judgment Analyzer setups require a small set of numbers/dates. Use this checklist to make sure you’re feeding the calculator the inputs that drive the result.

Required-style inputs to enter (common across DocketMath calculators)

• Offer amount (e.g., a dollar amount; if property-based, enter a relevant value if the tool supports it)
• Offer date (the date the offer was served)
• Trial date (the scheduled trial date you’re working with)
• Party role (offeror or offeree)
• Expected/awarded judgment amount (what the court ultimately awards or what you’re comparing against)

Optional or scenario inputs (if DocketMath prompts them)

• Attorney fee assumptions (if the tool models cost shifting)
• Pre-judgment interest assumptions (if included in the output)
• Whether the offer is accepted (if the tool provides acceptance toggles)

If the UI labels differ, match the meaning—not the wording. The goal is always the same: the tool computes the economics using the § 3221 timing framework based on what you enter.

4) Choose the comparison scenario that matches your question

Decide which “story” you want the analyzer to simulate:

• Scenario A (offeror): “If we make an offer for $X, what is the downside if we don’t beat it?”
• Scenario B (offeree): “If they make an offer for $X, what is the risk if the eventual judgment is less favorable than the offer?”
• Scenario C (timing sensitivity): “If trial date moves, does our offer still qualify under the ‘10 days before trial’ rule in § 3221?”

In practice, you’ll get more useful output if you run multiple iterations that only change one variable, such as:

• offer amount
• trial date
• expected judgment amount

5) Run the calculation and review outputs

Once inputs are complete:

1. Click Calculate / Run analysis (wording depends on the UI).
2. Review the results, especially:

   • Eligibility check for the timing rule (based on “not later than ten days before trial” in N.Y. C.P.L.R. § 3221)
   • Net financial impact or cost-shift estimates
   • Break-even point (if provided): the judgment level where the outcome changes

How output changes when you change inputs

Use these cause-and-effect rules to interpret results:

6) Export or save your scenario notes

If DocketMath lets you save results or download them:

• Save at least 2–3 scenarios (for example, offer amounts like $50k, $75k, $100k)
• Record the offer date and trial date you used, since § 3221’s timing rule is date-driven

For repeat use, create a habit:

• keep dates consistent across scenarios
• change only the offer amount and/or expected judgment

This makes your results comparable and reduces confusion.

Common pitfalls

Offer Of Judgment analysis usually fails for procedural reasons before it fails mathematically. Watch for these issues specific to the New York timing framework in N.Y. C.P.L.R. § 3221.

Pitfall checklist (quick scan)

• Missing the trial date (the tool can’t test the “ten days before trial” condition)
• Offer date entered as the wrong event (e.g., “draft date” instead of service date)
• Forgetting the default timing rule:
  “Except in a matrimonial action, at any time not later than ten days before trial” (N.Y. C.P.L.R. § 3221)
  Since no claim-type sub-rule was found, treat this as the general default period
• Assuming property offers work like cash offers without confirming the tool’s expected input format
• Comparing against the wrong judgment number (for example, mixing settlement demand vs. expected award vs. final judgment)
• Running only one offer amount and concluding the result is “the” answer—use sensitivity testing instead

Timing nuance to operationalize in the calculator

Because § 3221 sets a hard deadline relative to trial, operationally reduce mistakes by:

• verifying the trial date you enter (scheduled vs. confirmed)
• verifying whether the tool expects the offer date as service date
• rerunning if the trial date changes by more than a few days

Even small date shifts can cause the tool to flag eligibility differently.

Try it

Ready to run a New York scenario in DocketMath?

1. Open the calculator: /tools/offer-of-judgment-analyzer
2. Set jurisdiction to New York (US-NY).
3. Enter:

   • Offer amount
   • Offer date
   • Trial date
   • Expected judgment amount
4. Run the analysis and review:

   • the timing eligibility check tied to N.Y. C.P.L.R. § 3221 (“not later than ten days before trial,” excluding matrimonial actions)
5. Test at least three offer amounts while keeping dates constant to see how the break-even point or net impact shifts.

If you want a structured approach, try this sequence:

• Run 1: offer at the amount you’re considering
• Run 2: increase offer by 25%
• Run 3: decrease offer by 25%

Then compare the outputs side-by-side to identify which offer levels reduce downside risk for your role (offeror vs. offeree).

Related reading

• How to calculate Offer Of Judgment Analyzer in Philippines — Full how-to guide with jurisdiction-specific rules
• Worked example: Offer Of Judgment Analyzer in Philippines — Worked example with real statute citations
• Inputs you need for Offer Of Judgment Analyzer in Philippines — Input checklist with sourcing guidance