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

Step-by-step

Running the Offer Of Judgment Analyzer in DocketMath for New Jersey is mostly about entering the right date inputs and case context so the analyzer can apply N.J. Ct. R. 4:58 correctly. This walkthrough is designed to be practical and jurisdiction-aware, using the DocketMath tool workflow:

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

Before you start, confirm what rule framework you’re using. In New Jersey, Rule 4:58 governs offers of judgment and is stated as applicable to all civil actions.

Rule citation: N.J. Ct. R. 4:58 (as published at https://www.njcourts.gov/rules/r4.html#r4-58) provides that an offer of judgment “can be made in writing by any party in…” and that the rule “is applicable to all civil actions.”
Important: No claim-type-specific sub-rule was found in the material you provided—so treat the period/timing framework as the general/default civil action mechanism under Rule 4:58, not a specialized schedule for a particular claim type.

1) Open the tool

1. Go to **/tools/offer-of-judgment-analyzer
2. Select Jurisdiction: New Jersey (US-NJ) if the UI prompts you.
3. Skim the prompts and confirm they match a civil action offer-of-judgment scenario (not, for example, a different type of post-judgment calculation).

2) Gather the key dates and amounts

Collect the inputs first so you don’t have to guess later. The analyzer’s results will depend heavily on timing and comparison amounts under N.J. Ct. R. 4:58.

Typical items to have on hand:

• Offer amount (the dollar figure stated in the written offer)
• Offer date (when the offer was served)
• Acceptance information (e.g., accepted or no acceptance; some tools ask whether it was accepted)
• Judgment amount (the amount the rule compares against)
• Judgment date or any tool-specific date needed to determine the comparison timing
• Any additional timing field the tool requests (for example, a “deemed rejected” date, if applicable in the tool)

If you’re missing a field, use the tool’s required/optional structure rather than trying to fill gaps from memory. Accurate inputs matter because the analysis hinges on when the offer was made and what result followed.

3) Enter inputs in DocketMath

In the Offer Of Judgment Analyzer:

• Make sure you’re using the New Jersey (US-NJ) mode.
• Enter the offer amount and all date fields exactly as your documents reflect them.
• If the tool asks for a judgment amount, enter the figure the tool is designed to compare to the offer.
• If the tool asks who is being analyzed (for example, offeror vs. offeree, or “your position”), select the option that matches your scenario.

This step is where “direction” matters: cost-shifting can look very different depending on whether the analyzer is evaluating the party who made the offer versus the party who received it.

4) Use the “default period” timing (general civil action)

Because Rule 4:58 is described in your provided rule text as applicable to all civil actions and no claim-type-specific timing sub-rule was identified, the analyzer should be set up to follow the general/default civil action timing mechanism.

So, in practical terms:

• Treat N.J. Ct. R. 4:58 as the governing framework for your civil action.
• If the tool includes an offer period or similar timing parameter, use the general/default period option that corresponds to Rule 4:58 for civil actions rather than any claim-type-specific option (since none was identified from the provided rule data).

5) Run the analysis

Click Analyze (or the tool’s equivalent) once all required inputs are complete.

DocketMath should generate outputs tied to the interaction between:

• the offer (amount and date), and
• the case outcome (judgment amount and timing fields)

When you review results, look for:

• Whether the analyzer indicates the offeror/offeree’s position is treated as favorable based on the comparison
• Any breakdown of cost-shifting categories the tool calculates (if provided)
• Any computed thresholds, ranges, or totals derived from your inputs

6) Review outputs and adjust inputs to test scenarios

Use the tool like a scenario simulator:

• If the judgment amount you entered was an estimate, correct it and re-run.
• If you’re testing a “what if” strategy, change offer amount and observe whether the threshold changes the result.
• If you identify a corrected offer date from service records, update the date and re-run—small date changes can sometimes affect whether the offer falls within the timing framework the analyzer applies.

A good workflow is to change one variable at a time so you can tell what caused the output to change.

7) Export or record your results

If the tool offers exporting (PDF/CSV/copy output), save your run so you can compare iterations.

As a minimum, record:

• the offer amount
• the offer date
• the judgment amount
• the scenario selection (who made the offer / perspective)
• any key timing settings used (e.g., default period selection)

Gentle reminder: this is an analytical workflow to support understanding of possible outcomes under N.J. Ct. R. 4:58, not legal advice.

Common pitfalls

Even with a jurisdiction-aware tool, most user errors come from mismatched dates, incorrect comparison figures, or assumptions about how the rule is segmented.

Common pitfalls to watch for:

• Using the wrong jurisdiction profile

  • If you run under a non–New Jersey setting, the calculator may apply the wrong timing/cost logic.
• Assuming claim-type-specific timing

  • Based on the rule text provided, N.J. Ct. R. 4:58 is treated as applicable to all civil actions, and no claim-type-specific sub-rule was identified. Avoid switching to claim-type-specific periods unless you have a clear rule basis.
• Using a rounded or incorrect judgment amount

  • If the judgment entered is not the amount you used, the analyzer’s “beat the offer” type comparison may flip.
• Confusing offer service date with filing date

  • The analyzer typically needs the offer service/offer date as the trigger, not the date it was filed.
• Selecting the wrong perspective

  • Some analyzers depend on whether you’re evaluating the offeror or offeree. Double-check that your selection matches your scenario direction.
• Leaving recommended/required outcome fields blank

  • If the UI marks a field as recommended (or required for full calculation), fill it rather than relying on defaults.

Try it

Ready to run a New Jersey scenario in DocketMath? Start here:

• **/tools/offer-of-judgment-analyzer

Quick checklist before you click Analyze:

Tip: If you want a smoother workflow, keep your case docket entries open while entering dates, then re-check the offer service date and judgment date before running.

After your first run, adjust one variable at a time:

• Change offer amount → see whether the result crosses a threshold
• Change judgment amount → observe whether the comparison flips
• Change offer date by the smallest corrected amount → confirm sensitivity

Related reading

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