How to run Damages Allocation in DocketMath for Idaho

Step-by-step

This guide walks you through running Damages Allocation in DocketMath for Idaho (US-ID) using jurisdiction-aware rules. It also clarifies which Idaho statute controls the default statute of limitations (SOL) used by the calculator.

1) Open the calculator

1. Go to DocketMath’s Damages Allocation tool:

   • Primary CTA: **/tools/damages-allocation
2. Select Idaho (US-ID) if the tool asks for jurisdiction.

2) Enter the core date inputs

Damages allocation typically depends on two date inputs:

• When the event occurred (or the operative date the claim begins accruing)
• When the case was filed (or when damages are measured from)

In DocketMath, enter the relevant dates in the calculator fields (the labels will vary slightly). The fields generally map to “event/claim accrual” and “filing date.”

What to do

• Use the best-supported accrual/event date you have from your pleadings or factual timeline.
• Use the actual filing date (the date your action was commenced).

How outputs change

• If the filing date is more than the SOL period after the event/accrual date, the calculator will reduce or exclude damages outside the limitations window.

3) Confirm the Idaho default SOL period the tool uses

For Idaho, DocketMath’s jurisdiction-aware logic applies the general/default SOL period unless your scenario has a claim-specific rule configured in the tool. This guide uses the general rule because a claim-type-specific sub-rule was not found for this walkthrough.

Use the general statute of limitations:

• Idaho Code § 19-403 (general/default SOL period): 2 years

What this means in practice

• Damages allocation will effectively measure which portion of your claimed damages falls within the 2-year limitations window starting from the applicable accrual/event date used by the calculator.

4) Provide the damages figures (and verify allocation categories)

Next, enter your damages components (commonly things like):

• past damages vs. future damages
• totals by category (for example, economic loss, fees, or other sub-amounts)

If the calculator breaks damages into buckets, keep category totals consistent:

• Make sure each bucket amount is what you intend to allocate.
• Avoid double counting (for example, don’t include the same expense both as “past damages” and again inside a subcategory).

How outputs change

• After you input amounts and dates, the calculator computes how much of each damages bucket lies within the SOL window.

5) Review the allocation results (and what the SOL cut-off means)

After submission, you’ll see allocation outputs that split amounts into parts that fall inside versus outside the limitations window.

Focus on two outputs:

1. The allocated total — the damages portion that remains within the measured period
2. The SOL-adjusted window — the timeline the calculator uses to determine eligibility based on your dates

If the calculator shows “eligible” vs. “ineligible” amounts:

• Eligible is the part DocketMath treats as timely under Idaho Code § 19-403’s general 2-year limit
• Ineligible is what falls outside that period based on your inputs

6) Iterate with date accuracy (don’t treat the first run as final)

If you have competing accrual theories or uncertain operative dates, run multiple scenarios.

A simple iteration plan:

• Run 1: accrual/event date = Date A
• Run 2: accrual/event date = Date B
• Keep damages figures the same; only adjust the dates.

How outputs change

• Small date shifts near the boundary can materially change the allocated/excluded totals—especially if a significant portion of claimed damages is “past” and close to the 2-year cutoff.

7) Save or export your results

If the tool provides export options (PDF/CSV/copyable summary), export the output you plan to use.

When exporting, double-check:

• Jurisdiction label = **Idaho (US-ID)
• SOL basis = general 2-year period under Idaho Code § 19-403
• Dates match your case notes and the timeline used for accrual

Common pitfalls

Use this checklist to catch issues that often cause allocation results to look “wrong,” even when the calculator is working correctly.

• Using the wrong date pair
  Most errors come from entering a “notice date” instead of the accrual/event date used for SOL measurement.

• Assuming a claim-specific SOL without confirmation
  This walkthrough uses the general/default SOL period: 2 years under Idaho Code § 19-403.

• Double counting damages
  If you enter the same expense in two buckets, allocation may effectively include/exclude it twice.

• Mixing totals and component amounts
  For example, entering “Past damages total” and also entering individual subcomponents that sum to the same total.

• Boundary-date misunderstandings
  If your filing date is close to the end of the 2-year window, a one-day difference can move damages between allocated/excluded categories.

Pitfall example: If your damages span 18 months versus 26 months of activity, an accrual/event date that’s off by even a few months can substantially change the allocated result because the 2-year window is controlling.

Try it

If you want a quick sanity check before you rely on the output in a real workflow, use this mini test pattern.

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

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

A) Confirm SOL window logic before adding complex amounts

1. Enter a simple damages number (for example, a single “past damages total”).
2. Use dates that are clearly inside or outside the 2-year range:

   • Run X: accrual/event date = 18 months before filing date → expect most damages allocated
   • Run Y: accrual/event date = 30 months before filing date → expect a larger excluded portion

B) Then swap in real damages amounts

Once the allocation behaves as expected:

• Replace the placeholder damages amount with your actual category totals
• Keep the dates unchanged
• Export the final output you plan to reference

C) Verify Idaho SOL basis is displayed as the general rule

For Idaho, your run should reflect:

• 2-year general/default SOL period under Idaho Code § 19-403

The tool should align with that default because no claim-type-specific sub-rule was found for this walkthrough.

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