How to run Damages Allocation in DocketMath for Michigan

Step-by-step

Run this scenario in DocketMath using the Damages Allocation calculator.

This guide explains how to run Damages Allocation in DocketMath for Michigan (US-MI). The workflow focuses on jurisdiction-aware setup and how the time horizon affects the allocation results. This is a practical walkthrough—not legal advice.

1) Start the Michigan Damages Allocation calculator

1. Go to the primary call-to-action: /tools/damages-allocation
2. Confirm the jurisdiction is set to Michigan (US-MI).

   • If DocketMath asks you to choose a jurisdiction, select US-MI so the calculator uses Michigan time rules.

2) Enter the timeline and claim window (Michigan defaults)

In Michigan, the general statute of limitations (SOL) period is 6 years, using the general/default rule in:

• MCL § 767.24(1) (general/default SOL period)
  Source: https://www.michigan.gov

Important clarity: No claim-type-specific sub-rule was found from the jurisdiction data you’re using, so DocketMath should use the general/default 6-year period as the default horizon. The steps below assume that default applies.

What you typically enter in the tool Depending on the UI, you’ll see fields like:

• Event date / accrual start date (start of the damages window you’re analyzing)
• Filing date (or an end date against which the tool measures inclusion)
• Allocation basis period (e.g., allocate based on the SOL window vs. custom dates—choose the SOL-based/default option if you want the Michigan default behavior)

How outputs change

• The end of the allocation window typically becomes event/accrual start date + 6 years.
• If the filing date is earlier than that 6-year point, the allocation window usually truncates to the filing date.
• If the filing is later (beyond the 6-year point), results usually compress into the portion that falls within the 6-year horizon.

3) Provide your damages inputs

Next, add the damages amounts you want allocated. The interface typically supports one of these patterns:

• Total damages amount (allocate one overall number across time buckets)
• Damages categories (allocate multiple categories separately, then summarize by bucket)
• Allocation method / weighting options (e.g., time-proportional vs. user-defined weighting, if available)

How outputs change

• A single total generally produces a single time-bucket table.
• Multiple categories usually produces:

  • Category-level allocation breakdowns
  • Combined totals per time bucket (depending on the display/export options)

4) Review the time buckets and Michigan horizon behavior

After you run the calculation, review the time buckets section carefully. You’re checking both the dates and the arithmetic.

What to look for:

• Does the schedule cover up to 6 years from the event/accrual start (or end earlier if the filing date truncates the window)?
• Are bucket boundaries aligned to the dates you entered (so you don’t accidentally shift by a day due to formatting)?
• Do bucket totals reconcile to your inputs?

  • For example, if you entered a total damages amount, the sum across buckets should match (within any rounding rules shown by the tool).

If the tool lets you choose bucket size (monthly/quarterly/yearly):

• Choose the bucket granularity that matches your reporting needs.
• Note: bucket size generally changes how the allocation is displayed, but it should not change the underlying 6-year horizon.

5) Export or copy the allocation results

When the results look correct:

1. Use the tool’s export / download / copy option (if present).
2. Save outputs with a clear filename, for example including:

   • US-MI
   • the event/accrual start date
   • the filing date
   • a version tag like v1

This is especially useful because you’ll likely rerun the tool during scenario testing.

6) Validate your scenario before sharing

Do a quick consistency check before relying on the output:

• Are date fields in the correct format?
• Did you enter the filing date earlier than the event/accrual date?
• Does the allocation window reflect a 6-year horizon consistent with MCL § 767.24(1) (given the “general/default” assumption)?

If you want to cross-check the setup workflow, revisit:

• /tools/damages-allocation (Damages Allocation entry point)

Common pitfalls

These are common issues that can distort a Michigan Damages Allocation run in DocketMath.

• Using a non–6-year window for the default scenario

  • Michigan’s general/default SOL is 6 years under MCL § 767.24(1).
  • If you override the horizon without aligning your inputs to that override, allocations may include time outside the expected default window.

• Confusing “event date” with “filing date”

  • Swapping these can cause the tool to generate buckets that start or end incorrectly, leading to truncation errors or overstated periods.

• Assuming a claim-type-specific SOL rule without basis in the configured data

  • In the provided jurisdiction data, no claim-type-specific sub-rule was identified.
  • If you expect a different SOL by claim type, the tool may still apply the general/default 6-year logic, creating mismatch between your expectations and the output.

• Damages totals not matching category sums

  • If the interface asks for both a total and category amounts, ensure your numbers reconcile according to the tool’s intended input logic.

• Bucket granularity without a date-boundary check

  • Monthly vs. quarterly buckets can make it easier to miss that the allocation stops (or starts) one bucket earlier/later due to boundary handling.
  • Always confirm the displayed horizon aligns with the intended 6-year limit.

Frequent error to avoid: updating the event/accrual date or filing date but exporting results from a prior run. Because allocations are date-dependent, exporting a stale run can produce a “plausible” table that corresponds to the wrong horizon.

Try it

1. Open /tools/damages-allocation.
2. Set jurisdiction to Michigan (US-MI).
3. Enter:

   • an event/accrual start date
   • a filing date
   • your damages amount(s) (total and/or categories)
4. Run the calculation.
5. Confirm the tool is applying a 6-year general/default SOL horizon derived from MCL § 767.24(1) (as the default, since no claim-type-specific override was identified).
6. Review the output table:

   • verify the bucket range reaches up to 6 years (or stops earlier if the filing date truncates the window)
   • confirm bucket totals match the input totals (allowing for any tool rounding)
7. Export the results for your records (include US-MI and your key dates in the filename).

Quick self-check idea

• Set filing date = event/accrual date: the allocation window should be minimal.
• Then move the filing date forward by several years: included time should expand toward the 6-year limit.

Related reading

• Damages Allocation Guide for Alabama — Comparative Fault Rules
• Damages Allocation Guide for Alaska — Comparative Fault Rules
• Damages Allocation Guide for American Samoa — Comparative Fault Rules