How to run Treble Damages in DocketMath for Michigan

Step-by-step

Below is a jurisdiction-aware way to run Treble Damages in DocketMath for Michigan (US-MI) using the treble-damages calculator. This walkthrough focuses on what to enter, how to interpret outputs, and how Michigan’s treble-damages rule is represented in the tool.

1) Open the Michigan treble-damages calculator

Start at the primary CTA:

• /tools/treble-damages

Once you’re in the tool, confirm you are using the Michigan jurisdiction mode (US-MI).

2) Confirm the Michigan treble rule the tool is applying

For Michigan, the core anti-lockout/forcible entry treble damages authority referenced by the tool is:

• Mich. Comp. Laws § 600.2918(1)

DocketMath’s Michigan setup uses a multiplier of 3 and a minimum damages floor. In other words, when the tool calculates Michigan treble damages, it applies the following verified configuration values:

• Multiplier (treble_multiplier): 3
• Minimum damages (minimum_damages): 200
• Treble availability rule (treble_available): false for one sub-branch in the tool’s internal logic (so don’t assume every workflow path will behave identically unless you follow the tool’s Michigan path/inputs)

3) Enter the base amount (the “single” damages figure)

The treble calculator needs a base damages number—the amount before applying the “× 3” multiplier.

A practical way to think about it:

• Enter the amount you want treated as the “single” figure that the tool will multiply by three under the Michigan configuration above.

Checklist for the base amount:

• Use the number you want multiplied (the “single” amount), not an already-trebled total
• Enter it as a numeric value in the tool’s field(s)
• If you have multiple damage components, add them together first and enter the combined total once

4) Run the calculation and observe Michigan-specific adjustments

After you enter the base amount, click Calculate (or the tool’s equivalent action).

DocketMath applies the Michigan treble framework in two key ways:

1. Trebling: the base amount is multiplied by 3
2. Minimum damages: if the trebling result would be less than the configured minimum, the tool enforces $200 as the minimum output

Quick sanity checks:

• If your base amount is large, expect roughly 3 × base
• If your base amount is small, expect the output may show $200 due to the minimum floor

5) Review the output fields for what changed because of “treble”

When you review results, confirm the tool is behaving as expected. Look for output elements that separate or explain:

• the base figure you entered
• the multiplier effect (×3)
• any minimum adjustment (showing 200 when triggered)

A useful mental model:

• Final output ≈ base × 3, but not less than 200 given the tool’s verified Michigan settings.

6) Export/share (if your workflow uses it)

If your workflow includes exporting (PDF), generating a share link, or copying results, do that immediately after you run the calculation. That reduces the risk of mismatch if you later change inputs and the tool re-applies the multiplier/minimum.

Common pitfalls

Treble damages calculations often go wrong because the inputs don’t match what the calculator is designed to represent. For US-MI in DocketMath, the verified configuration includes both a 3× multiplier and a $200 minimum, plus internal “treble availability” path logic for at least one sub-branch.

Watch for these common issues:

1. Forgetting the minimum damages floor

   • Verified tool setting: minimum_damages = 200
   • Result: small base inputs can produce $200 instead of 3 × base

2. Assuming treble is always applied without checking the tool’s selection path

   • Verified tool setting: treble_available = false for one internal sub-rule branch
   • Result: depending on what you select or how the tool routes logic, you may not see the exact same behavior you expect—so follow the tool’s Michigan flow carefully

3. Entering an already-trebled figure as the “base”

   • Because the tool applies multiplier: 3, if your “base” already includes a prior ×3, the calculator will effectively treble again
   • Quick check: if your base is already around three times what you believe the underlying “single” amount is, you may be double-counting

4. Mixing components and losing arithmetic consistency

   • If you have multiple damage components, add them first
   • Then enter the combined total once as the base amount

5. Using the wrong jurisdiction mode

   • The calculator is jurisdiction-aware
   • For these results, ensure you’re set to US-MI before calculating

Try it

Use DocketMath’s calculator with a controlled test first so you can confirm how the Michigan multiplier and minimum behave before inputting your real numbers.

Quick test plan (2 runs)

1. Run A (to observe minimum behavior)

   • Enter a small base amount
   • Expectation: the tool may return $200 because the verified minimum is 200

2. Run B (to observe pure trebling)

   • Enter a larger base amount
   • Expectation: the result should reflect the ×3 multiplier (verified: treble_multiplier = 3)

What you should look for in the output

After each run, check:

• The multiplier applied is 3
• The final output equals 3 × base when the base is large enough to avoid the minimum
• The final output hits 200 when the base is small enough to trigger the minimum floor
• No unexpected adjustments show up beyond what the verified configuration implies (multiplier/minimum behavior)

If the outputs don’t match these expectations, revisit:

• the jurisdiction selection (US-MI)
• what you entered (base vs. already-trebled amount)
• the calculator’s Michigan logic path/inputs that can route to different sub-branch behavior

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