Step-by-step

Run this scenario in DocketMath using the Treble Damages calculator.

This guide walks you through running Treble Damages in DocketMath for Michigan (US-MI) using jurisdiction-aware rules. You’ll set the inputs, confirm the calculation logic, and sanity-check the output against Michigan’s default statute-of-limitations framework.

1) Open the right tool in DocketMath

1. Start at the primary call-to-action: /tools/treble-damages
2. Select Michigan (US-MI) if the tool asks for a jurisdiction.
3. Confirm you’re on the Treble Damages calculator (not a different damages or remedies tool).

2) Gather the inputs the calculator expects

Before you enter any numbers, collect the items that typically drive the treble-damages result in DocketMath:

• Base damages amount (the pre-trebling amount the calculator expects)
• Dates required by the tool (commonly an event/accrual date and a filing/case date, depending on the UI)
• Any toggles or extra multipliers the UI might ask for (trebling is usually “multiply by 3,” but the calculator may still present related fields)

Tip: Use specific numeric values where possible. For example, enter $12,500 instead of a range. When you enter a dollar figure, DocketMath carries it through the trebling math automatically.

3) Enter the base damages

1. Find the Base damages input.
2. Enter the amount in dollars (example: 12500).

What you should expect:

• DocketMath will generally compute Treble damages = Base damages × 3.
• If the results area shows an intermediate multiplier, verify it is 3× before you rely on the total.

4) Add Michigan timing inputs (SOL-aware behavior)

Michigan includes a general statute of limitations used by the tool when no more specific limitations rule is configured.

For this Michigan run, DocketMath uses the general/default 6-year SOL period:

• 6 years
• **MCL § 767.24(1)
• Source: https://www.michigan.gov

Because the brief indicates no claim-type-specific sub-rule was found, the calculator should apply this general/default 6-year period. In other words, the tool run is intended to reflect the general SOL assumption, not a specialized one for a particular claim category.

How this can affect results:

• The tool may display a timely vs. time-barred style output (depending on UI design).
• Some tools also flag whether timing may affect the usable portion of damages (if DocketMath shows an “eligible period” or lookback-style concept).

5) Use the dates to determine the SOL window

Enter the dates the calculator requests, commonly:

• Event/violation (accrual) date
• Filing date (or another “case start” date field)

Then DocketMath compares the time between those dates to 6 years under MCL § 767.24(1).

How output changes when dates cross the SOL line

Conceptually, a SOL-aware calculator often behaves like this:

6) Review the calculation summary

After inputs are complete, review the results panel and look for:

• Treble damages total (expected to be base × 3)
• Michigan SOL/timing status (showing it’s using the general/default 6-year assumption per MCL § 767.24(1))
• Any breakdown items the UI provides (for example, base amount vs. trebled amount; or any timing/eligibility indicators)

If you see language like “Using Michigan general SOL (6 years) per MCL § 767.24(1),” treat that as confirmation that the tool is applying the jurisdiction default described in this brief.

7) Export or record your output

If DocketMath offers copy/export buttons, save:

• The treble damages total
• The dates you used
• The SOL/timing status shown by the tool

This makes it easier to rerun the tool later if you need to:

• update the base damages input, or
• correct an event/accrual date or filing date you entered.

Common pitfalls

Treble damages math is often simple, but SOL-aware interpretation can make outputs feel confusing. These are the most common issues to watch for when running Michigan (US-MI) in DocketMath using MCL § 767.24(1) (general/default 6-year SOL).

Mis-entering the base damages figure

• Entering a number that already includes trebling (which would effectively triple twice).
• Entering a figure that isn’t clearly “pre-treble” as the calculator expects.
• Mixing up net vs. gross depending on what you sourced the amount from.

✅ Fix: Ensure your Base damages input is explicitly the pre-trebling amount.

Getting the “wrong” event/accrual date into the calculator

SOL hinges on time. Even a small date shift can flip the “within 6 years / outside 6 years” timing result.

✅ Fix: Use the date that matches the tool’s label (for example, “event date” or “accrual date” exactly as shown in the UI).

Assuming a claim-type-specific SOL applies when none is configured

This brief is explicit:

• No claim-type-specific sub-rule was found
• Therefore, DocketMath should use the general/default 6-year period under **MCL § 767.24(1)

Pitfall: If a real-world cause of action might have a different limitations analysis, a tool run that relies on the default general SOL can produce a timing flag that doesn’t match that more nuanced framework—because the tool is not configured to apply a specialized sub-rule for that scenario.

✅ Fix: Treat the tool’s SOL output as “what happens under the general/default rule used by the calculator,” not as a definitive statement about any specific claim category.

Treating the treble number as “automatically usable”

Even if the treble calculation (base × 3) is mechanically correct, DocketMath may still:

• mark the run as time-barred, and/or
• indicate that timing may affect damages treatment (if the UI includes such messaging).

✅ Fix: View the treble amount and the timing/SOL status as separate pieces of information.

Using inconsistent date formats

If the UI is strict about date formatting, manual typing can introduce errors.

✅ Fix: Use the built-in date picker when available.

Try it

Ready to run a Michigan treble-damages calculation in DocketMath? Use this quick sequence.

Quick start checklist

Example walkthrough (illustrative)

1. Base damages: $8,000
2. Treble calculation: $8,000 × 3 = $24,000
3. SOL logic (general/default):

   • If the event date is within 6 years of the filing date, the tool should show timing as within SOL under the general/default period.
   • If it’s more than 6 years, the tool should flag outside SOL under MCL § 767.24(1).

Use the DocketMath UI wording for the exact labels it uses (for example, “timely,” “outside SOL,” or similar).

Make a second run to test sensitivity

To validate your inputs quickly, run the calculator again and change only one variable:

• Change base damages or
• Change the event/accrual date or
• Change the filing/case date

Compare the outputs side-by-side. This is an efficient way to confirm:

• the calculator is applying ×3 as expected, and
• the tool’s SOL/timing status responds logically to your date changes using the Michigan general/default 6-year SOL.

If you want to jump straight in, start here: /tools/treble-damages

Related reading

• Browse the blog

Step-by-step

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

Capture the source for each input so another team member can verify the same result quickly.

When rules change, rerun the calculation with updated inputs and store the revision in the matter record.

Common pitfalls

• missing a required input
• using a stale rate or rule
• ignoring calendar or holiday adjustments
• skipping documentation of assumptions

Capture the source for each input so another team member can verify the same result quickly.

When rules change, rerun the calculation with updated inputs and store the revision in the matter record.

Try it

Open the Treble Damages calculator and follow the steps above: Run the calculator.

If an assumption is uncertain, document it alongside the calculation so the result can be re-run later.

Capture the source for each input so another team member can verify the same result quickly.

Related reading

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