How to run Treble Damages in DocketMath for New Mexico

Step-by-step

This practical, jurisdiction-aware walkthrough shows how to run Treble Damages in DocketMath for New Mexico (US-NM). It’s focused on how to enter inputs and how the outputs change—not legal advice.

• Select New Mexico in the Treble Damages tool.
• Enter the trigger dates and any caps or rates.
• Run the calculation and save the output.

1) Start with the correct calculator and jurisdiction

1. Open DocketMath’s Treble Damages tool:
   Primary CTA: /tools/treble-damages
2. Confirm the jurisdiction is set to New Mexico (US-NM).
   DocketMath’s jurisdiction-aware rules use New Mexico’s general statute of limitations approach for timing assumptions.

2) Enter the base damages amount (the number you want trebled)

In the calculator, you’ll typically provide a base damages amount—the damages you intend to enhance (for example, “actual damages” before trebling).

• Enter the base amount as of the relevant modeling point (often “as claimed” before multipliers).
• If the tool supports multiple components, you can either:

  • enter a breakdown, or
  • combine components into a single base number if that’s what the tool expects.

What to expect in the output:

• Trebling generally produces a multiplied total (commonly base × 3) and shows the enhanced/trebled result in the results panel.

3) Verify the treble multiplier

• Check that the tool’s multiplier is set to 3× (or confirm the multiplier field if one exists).
• Keep the multiplier consistent across scenarios so you can compare results without mixing variables.

4) Add (or confirm) the statute of limitations timing window for New Mexico

For this New Mexico setup, DocketMath will use the general/default statute of limitations period because no claim-type-specific sub-rule was found for this treble-damages configuration.

Use these jurisdiction defaults:

• General SOL Period: 2 years
• General Statute: N.M. Stat. Ann. § 31-1-8

What the tool may ask you to enter:

• A relevant event date (often an accrual date or the date of the conduct/violation, depending on how you’re modeling)
• A filing date (the date the action would be brought, for modeling)

How outputs change based on timing:

• If filing date is within 2 years of the relevant event date, the SOL model should generally treat the claim as timely under the default rule.
• If filing date is more than 2 years after the modeled event date, the tool may reflect a limitations risk or a similar timing outcome—depending on how the calculator presents SOL results.

5) Review the results panel (treble math + SOL outcome together)

After you run the calculation, review both:

• Treble math: confirm the trebled total aligns with your base amount and the expected 3× behavior
• Timing/SOL output: confirm the tool is applying 2 years using N.M. Stat. Ann. § 31-1-8 as the governing default

If the trebled total seems off, re-check:

• your base amount input,
• any multiplier setting,
• and whether the tool expects the base amount to be “pre-treble” versus “already enhanced.”

6) Run “what-if” scenarios to pressure-test timing and damages

To make the model more useful, change one input at a time and compare results.

Try these scenario patterns:

• Timing sensitivity: move the relevant event date by ± 30–90 days, or move the filing date later by the same amount and rerun
• Damages sensitivity: keep dates fixed; adjust the base damages estimate upward/downward and rerun
• Consistency check: ensure that in every scenario, only one variable changes (date or base amount), so you can see what drives the output

Practical payoff: you’ll quickly see how sensitive the trebled total is to base damages and how close the case may be to the 2-year timing threshold.

7) Save or capture results for comparison

If DocketMath offers saving:

• Save a baseline run first.
• Save each additional scenario with a clear label (e.g., “Conservative base, timely within 2 years”).

If saving isn’t available:

• Record the key inputs (base amount, event date, filing date) and the output (trebled total and SOL/timing outcome) for each run.

Common pitfalls

Treble damages modeling is both math-heavy and timing-sensitive. These are common issues that can distort results in DocketMath for New Mexico:

This setup uses the general/default 2-year SOL from N.M. Stat. Ann. § 31-1-8 because no claim-type-specific sub-rule was found for this configuration.

A small shift can cross the 2-year line. Make sure the event/accrual date you enter matches the conduct or accrual concept you’re modeling, and that the filing date is the modeled filing time.

If the base damages estimate is off by 10%, the trebled number is typically off by a similar percentage—while the absolute dollar difference becomes larger because of the 3× multiplier.

If you change both dates and damages at the same time, you won’t know whether the SOL outcome or the treble total changed due to timing or money inputs.

A trebled total alone can be misleading. Whenever you review or present results, pair the treble output with the modeled event date, filing date, and the 2-year default rule from N.M. Stat. Ann. § 31-1-8.

Pitfall to watch: using the correct treble multiplier but pairing the wrong dates (event vs. filing) can flip the result from “timely” to “time-barred” (or vice versa), even if the damages math is correct.

Try it

Use this mini checklist before you click calculate:

Then run 2 scenarios:

Once you see results, compare:

• Trebled totals: do they behave like expected 3× multiplication of your entered base?
• SOL outcome: is the tool applying 2 years under N.M. Stat. Ann. § 31-1-8 as the governing default for this setup?

Related reading

• Treble Damages Calculator Guide for Alabama
• Treble Damages Calculator Guide for Arizona
• Treble Damages Calculator Guide for Colorado