Why Damages Allocation results differ in Michigan

The top 5 reasons results differ

Run this scenario in DocketMath using the Damages Allocation calculator.

If you’re seeing different Damages Allocation outputs in Michigan (US-MI) using DocketMath, it’s usually not because the calculator is “wrong”—it’s because small, jurisdiction-aware choices can change how damages get partitioned across parties or categories.

Michigan’s baseline general statute of limitations (SOL) period is 6 years, governed by MCL § 767.24(1). DocketMath uses this general/default period when no claim-type-specific sub-rule is identified (and no claim-type-specific sub-rule was found for this guidance), so your inputs around timing become especially important.

Here are the most common causes of divergent results in Michigan:

1. **Statute of limitations gating (6-year default vs. the event/accrual date)

   • Michigan’s general rule is 6 years under MCL § 767.24(1) (source: Michigan.gov).
   • If two runs use different “event” or “accrual” dates, DocketMath may treat portions of damages as time-barred and allocate only the remainder to the recoverable period, changing the output distribution.

2. Different “start point” inputs

   • Even if the same parties and categories are included, mismatches in date conventions can shift the recoverable window:

     • incident date vs. discovery/accrual date
     • date suit was filed vs. when damages began
   • A small shift in the SOL “start” can change the counted duration, which can alter both the recoverable share and category proportions (depending on the allocation method).

3. **Damage category definitions (what’s included/considered compensable)

   • Allocation often depends on how categories are mapped and normalized (for example: property vs. economic loss vs. related items).
   • Two analyses that claim to “include everything” can still diverge if one run:

     • assigns an item to a different category, or
     • uses slightly different category amounts (even when the totals appear close).

4. Allocation method assumptions

   • DocketMath’s allocation logic can yield different distributions if weighting factors differ or if the total damages inputs differ (even by small amounts). Common examples include differing assumptions about relative time, relative contribution, or how proration is applied.

5. Rounding, proration, and missing periods

   • If one run uses partial months/quarters and another uses discrete buckets (or slightly different boundaries), computed shares can drift.
   • Missing one category can also force normalization to re-scale the remaining totals, which makes other categories look “off” even if their underlying inputs were consistent.

Gentle note (not legal advice): The general SOL is 6 years under MCL § 767.24(1) when no claim-type-specific sub-rule is identified. If your inputs push damages outside that window, DocketMath may allocate a smaller portion to the recoverable period—even if everything else matches.

How to isolate the variable

Use a diagnostic approach: hold everything constant, then change one input at a time until the output changes. This makes it clear whether the discrepancy is driven by SOL gating, date conventions, categories, or allocation math.

• Freeze the jurisdiction and tool settings so both runs use the same rule set.
• Compare one input at a time (dates, rates, amounts) and re-run after each change.
• Review the breakdown to see which segment or assumption drives the difference.

Step-by-step isolation checklist

• Ensure DocketMath is using the general/default 6-year SOL under MCL § 767.24(1).

  • Recall: no claim-type-specific sub-rule was found, so the general period is the baseline.
  • Keep total damages and every category amount identical between runs.
  • Run #1: original date selection
  • Run #2: adjust by the smallest meaningful unit (e.g., +30 days), or swap incident vs. accrual/discovery date.
  • Allocation tables typically shift in two main ways:

    • recoverable share changes (SOL gating effect)
    • allocation across categories changes (category mapping/weights or normalization effect)

Quick diagnostic table

If changing only the gating date produces the entire divergence, focus on date selection and SOL timing, not category amounts.

Next steps

1. Run three controlled comparisons in DocketMath

   • Baseline (A)
   • Date-variant (B)
   • Category-variant (C)
2. Compare outputs with a “delta” mindset

   • Identify which numbers move most:

     • recoverable vs. time-barred buckets (SOL timing)
     • relative shares across categories (mapping/weights/normalization)
3. Document the exact inputs you used

   • Save:

     • the date used for SOL gating
     • each category amount
     • any weighting/proration settings

Pitfall to avoid: Don’t “fix” mismatched outputs by changing category numbers until the dates are consistent. In Michigan, divergence often comes from 6-year SOL gating under MCL § 767.24(1), especially when teams use different date conventions.

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