How to run Damages Allocation in DocketMath for New Mexico

Step-by-step

Use DocketMath’s Damages Allocation calculator to apportion total damages among multiple faulted parties in a New Mexico matter using jurisdiction-aware assumptions. This walkthrough focuses on how to run the tool, what to enter, and what to expect—without giving legal advice.

1) Start the right tool run

1. Go to DocketMath’s Damages Allocation calculator: /tools/damages-allocation
2. Confirm the jurisdiction setting is New Mexico (US-NM).

If you’re switching from a different jurisdiction, double-check the setting before you calculate—jurisdiction changes can affect how the tool applies caps and allocation logic.

2) Gather the inputs the calculator needs

Before you type anything, collect these figures for each defendant/party:

• Total damages (the dollar amount you’re allocating)
• Each party’s percentage of negligence/fault

  • In most allocation workflows, these percentages should sum to 100%
• Party names/roles (e.g., Defendant A, Defendant B, third-party defendant)
• Any amounts you plan to exclude (if your workflow uses them)

  • Only include amounts that match your case model (for example, if a particular category is treated outside the allocation base)

DocketMath’s output depends directly on the percentages you provide, so accuracy here matters.

3) Enter totals and percentages in DocketMath

In the calculator fields:

• Enter Total damages as a single number (e.g., 500000)
• For each party row, enter:

  • Percentage of fault (e.g., 25, 50, 25)
  • A label for the party (e.g., “Defendant A”)

If your fault percentages come from a verdict form, jury answers, or stipulation, map them 1:1 into the tool.

4) Use New Mexico’s default allocation model

For a New Mexico run, DocketMath applies the several-liability cap by fault percentage concept reflected in N.M. Stat. Ann. § 41-3A-1(A). In practical terms:

• A defendant is not liable for any amount in excess of the percentage of the total damages attributable to that defendant’s negligence or fault for causes of action to which several liability applies. N.M. Stat. Ann. § 41-3A-1(A)

New Mexico practice also references foundational principles around fault-based apportionment, including Scott v. Rizzo, 96 N.M. 682 (1981).

5) Review the computed allocations

After running the calculator:

• Review each party’s allocated damages.

  • You should generally see outcomes aligned with the concept of: allocated share tracks the party’s % fault, consistent with the statutory cap approach.
• Verify totals:

  • If your fault percentages sum to 100%, the allocated amounts should generally reconcile to your Total damages.
  • If they don’t, re-check your inputs (most mismatches come from a percentage that’s missing, rounded incorrectly, or entered in the wrong format).

6) Export or capture results for case documentation

Once the allocations look right:

1. Save/export results from DocketMath (if your UI offers a download or share option).
2. Copy the output numbers into your work papers or drafting notes.
3. Keep an audit trail of:

   • The Total damages you entered
   • The fault percentages used for each party
   • Confirmation that the run was New Mexico / US-NM
   • Any notes about the model assumptions you relied on

7) Confirm the default “no claim-type-specific sub-rule” behavior

DocketMath’s New Mexico run uses the general/default allocation model when no claim-type-specific sub-rule is detected.

Common pitfalls

Most allocation errors aren’t arithmetic—they’re input problems or jurisdiction/model mismatches. Watch for these common issues when running New Mexico (US-NM) in DocketMath:

• Fault percentages not totaling 100%

  • Example: 20% / 35% / 40% totals 95%
  • Fix: correct the percentages or confirm whether an “other fault” / remaining attribution category should be included in your model.

• Entering decimals vs. whole-number percentages

  • Example: entering 0.25 when the tool expects 25
  • Fix: follow the UI’s expected format (often whole-number percentages like 25, 50, 25).

• Using the wrong “Total damages” base

  • “Total damages” should match the stage and base you intend to allocate.
  • Fix: ensure your Total damages input is consistent with how your model treats offsets/credits (if any) in your workflow.

• Assuming one defendant pays 100%

  • Under N.M. Stat. Ann. § 41-3A-1(A), the several-liability cap concept means a defendant’s liability is tied to their fault percentage for causes of action where several liability applies.
  • Fix: rely on the tool’s jurisdiction-aware cap behavior and don’t force an all-or-nothing payment assumption into the inputs.

• Wrong jurisdiction setting

  • If you previously ran a different jurisdiction, it’s easy to forget to switch back.
  • Fix: confirm US-NM before you compute.

• Ignoring default-model behavior when a special theory may apply

  • If a claim requires a different treatment than the default model, a standard run may not match your required allocation structure.
  • Fix: if you know the legal theory changes applicability, ensure the tool configuration and inputs reflect that before using results.

Try it

Ready to run your first New Mexico damages allocation in DocketMath? Use this quick checklist:

• Open /tools/damages-allocation
• Set jurisdiction to New Mexico (US-NM)
• Enter Total damages (one number)
• Enter each party’s percentage of fault
• Ensure fault percentages sum to 100%
• Run the calculator
• Confirm outputs:

  • Each defendant’s allocated amount tracks the fault share
  • Totals reconcile to your Total damages
• Save results for your records

Then compare the computed shares to your case’s fault findings. If something looks “too high” or “too low,” stop and revisit the fault percentages first—most discrepancies trace back to mis-entered inputs.

Related reading

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