How to run Treble Damages in DocketMath for Nebraska

Step-by-step

This guide walks you through running Nebraska “treble-like” discretionary damages in DocketMath using the treble-damages calculator and jurisdiction-aware rules for Nebraska (US-NE). Nebraska’s approach under Neb. Rev. Stat. § 59-1609 is a discretionary increase, not an automatic trebling.

Start by opening the calculator:

• /tools/treble-damages

1) Confirm the jurisdiction is set to Nebraska (US-NE)

In the calculator’s jurisdiction selector, choose:

• US-NE (Nebraska)

This matters because the rule engine applies Nebraska’s damages framework under:

• Neb. Rev. Stat. § 59-1609 (discretionary increase; not an automatic treble; and includes a cap for qualifying claims)

2) Enter the inputs the “treble-damages” calculator asks for

Next, enter the figures the treble-damages calculator requests (the labels may vary by UI, but they typically include a base amount and one or more controls that determine how the statutory increase logic is applied).

Use this checklist to ensure your inputs match the calculator’s expected “scenario” structure:

• Base damages amount (the starting figure the calculator applies the statutory increase logic to)
• Any trigger/category selector that corresponds to whether the claim falls into the statutory framework described in Neb. Rev. Stat. § 59-1609
• Optional toggles that distinguish between plain damages versus statutory increase mode (if your UI provides them)

Important: If the screen includes a multiplier-looking option, treat it as a tool setting, not as proof that Nebraska uses a guaranteed ×3 rule. The tool’s Nebraska logic should reflect Neb. Rev. Stat. § 59-1609 (discretionary increase).

3) Verify the Nebraska rule interpretation is being used

After entering values, check the calculator’s rule summary or jurisdiction logic area (if present). You’re looking for language indicating that the calculation is using Nebraska’s framework under:

• Neb. Rev. Stat. § 59-1609

You should expect the modeled output to reflect:

• A discretionary increase (not automatic trebling)
• A cap that can limit the increased amount in the qualifying scenario

4) Run the calculation and review the output

Click Calculate (or the equivalent).

Then review the output fields the calculator shows, such as:

• Base amount (your input)
• Increased damages amount (the statutory-increase computation as the tool models it)
• Any cap-related messaging (if the qualifying condition applies)

5) Record your assumptions for later changes

Write down what you entered so the result is easy to reproduce and audit, for example:

• Jurisdiction: US-NE
• Rule mode: § 59-1609 discretionary increase (as shown/selected in the tool)
• Base damages: (your input)
• Cap behavior: (whether the tool indicates the cap applies in your selected scenario)

This helps when you adjust inputs to test different outcomes.

Common pitfalls

Running a damages calculator is easiest when you watch for mismatches between the tool’s UI and Nebraska’s actual structure under Neb. Rev. Stat. § 59-1609.

Pitfall 1: Assuming “treble” is automatic in Nebraska

A common mistake is assuming Nebraska automatically multiplies damages by 3.

Nebraska’s framework in Neb. Rev. Stat. § 59-1609 is a discretionary increase, so the calculator should not be interpreted as a guaranteed automatic ×3 computation.

Pitfall 2: Not selecting the scenario that triggers cap behavior

Your output may be limited by a cap when the statutory framework in Neb. Rev. Stat. § 59-1609 applies in the qualifying way.

Quick checks:

• Does the calculator’s scenario/trigger selection correspond to the qualifying framework referenced in Neb. Rev. Stat. § 59-1609?
• Does the results panel mention or imply that a cap is being applied?

Pitfall 3: Changing inputs without tracking what changed

Damages modeling is sensitive to your base amount and to any scenario/trigger selection.

Use a simple log:

• If you change the base damages amount, the increased amount will typically change.
• If you change the trigger/category (or whether the statutory increase logic applies), the entire increased calculation can change.
• If the cap is triggered, increasing the base amount further may not increase the final result past the tool’s capped figure.

Pitfall 4: Treating tool “multiplier” controls as proof of Nebraska’s legal rule

Even if the UI includes a multiplier-like control, don’t infer Nebraska has an unconditional trebling rule. Instead:

1. Confirm the calculator is using Neb. Rev. Stat. § 59-1609 logic.
2. Match your interpretation to what the tool says about discretionary increase and any cap behavior.

Try it

If you want to validate your workflow quickly, run two short tests in DocketMath and compare how the output changes under Nebraska’s § 59-1609 framework.

Mini test plan (2 runs)

1. Run A (baseline)

   • Set jurisdiction to US-NE
   • Enter your best estimate for the base damages amount
   • Select the scenario/trigger option in the tool that corresponds to the Nebraska framework under Neb. Rev. Stat. § 59-1609

2. Run B (stress test)

   • Keep all other selections the same
   • Increase only the base damages amount

What you should observe under Nebraska rules

• If the tool indicates cap behavior is active for your selected scenario under Neb. Rev. Stat. § 59-1609, then increasing the base amount should eventually lead to a flattened/capped increased-damages result.
• If the cap behavior is not active for your selected scenario, the increased amount should generally continue to scale according to the tool’s discretionary-increase logic under Neb. Rev. Stat. § 59-1609.

Map outputs to what they mean

As you review results, align tool labels to the Nebraska framework you’re modeling:

• Discretionary increase: reflected in how the calculator computes the “increased damages” figure under Neb. Rev. Stat. § 59-1609
• Cap behavior: reflected by any cap messaging and/or capped increased amount in the qualifying scenario
• Base amount: your starting input before the increase logic is applied

Want to start now? Use:

• /tools/treble-damages

Related reading

• How to calculate Treble Damages in Texas — Full how-to guide with jurisdiction-specific rules
• How to calculate Treble Damages in Philippines — Full how-to guide with jurisdiction-specific rules
• Worked example: Treble Damages in Philippines — Worked example with real statute citations