Damages Allocation reference snapshot for Idaho

Rule or statute summary

For Idaho, the general statute of limitations (SOL) for damages claims is 2 years, governed by Idaho Code § 19-403. In this jurisdiction snapshot, DocketMath’s damages-allocation model uses that default 2-year window for timing-related damages allocation constraints because no claim-type-specific sub-rule was found in the provided materials. Treat this 2-year period as the baseline unless you have a separate, identified Idaho rule that applies to your specific claim type.

What the 2-year SOL means in practice

• The SOL generally affects how long you have to file after a claim accrues.
• In a damages allocation model, that usually translates into whether certain damages categories (or portions) are treated as within the allowable period versus time-barred/excluded (depending on how the calculator is configured and how you enter component dates).

What DocketMath typically needs to allocate damages

• Accrual / key event date(s) (e.g., incident date, discovery date, or another trigger you are modeling)
• Filing or cutoff date (the date you’re testing against for timeliness)
• Damages components (e.g., medical expenses, lost wages, property loss)
• Timing structure for each component

  • One-time (single invoice date or single event date), or
  • Ongoing / periodic (time spans, pay periods, monthly charges, etc.)

Pitfall to keep in mind

• If your situation actually falls under a different, claim-type-specific Idaho limitations rule (not identified here), relying on the general 2-year default could lead you to over-include damages that may be disputed in real litigation (e.g., because the true accrual trigger differs, or because a specialized provision applies).

Citations

• Idaho Code § 19-403 — General SOL period: 2 years
  Source: https://law.justia.com/codes/idaho/title-36/chapter-14/section-36-1406/?utm_source=openai

How to interpret this citation in your workflow

• Use § 19-403 as the default limitations anchor when you do not have a more specific Idaho SOL provision identified.
• Per the note in your brief—“No claim-type-specific sub-rule was found”—this snapshot does not introduce alternate SOL windows. So the calculator’s outputs reflect a general/default 2-year approach.

Quick reference

Use the calculator

Use DocketMath (tool name: damages-allocation) to translate SOL timing into modeling inputs and outputs.

Primary CTA: Open the Idaho damages allocation calculator

Run the Damages Allocation calculation in DocketMath, then save the output so it can be audited later: Open the calculator.

1) Set the jurisdiction context and dates

• Jurisdiction: US-ID (Idaho)
• Accrual / event date: the date your model uses as the start of the limitations analysis
• Filing date or cutoff date: the date you are testing as the filing/timeliness reference point

DocketMath will apply the 2-year SOL as the general/default window in this snapshot.

2) Enter damages components (and timing granularity)

For each damages component, provide:

• The component amount, and
• Timing information, such as:

  • One-time date (e.g., the invoice date for a medical bill), or
  • A date range / period (e.g., lost wages from March 1 to June 30)

This matters because the calculator typically allocates based on whether component dates fall inside vs. outside the relevant SOL window.

3) Run a “what-if” date sensitivity check

Because SOL constraints are date-driven, rerunning with small changes can show how sensitive the allocation is:

• Run once with your best-estimate accrual/event date.
• Then rerun shifting the accrual/event date:

  • +30 days
  • -30 days
  • (Optional) ±6 months

Compare how totals change—especially for components near the SOL boundary.

4) Interpret outputs as a modeling aid (not legal advice)

This snapshot and calculator structure can help you organize the timing logic, but they can’t guarantee correctness for your specific situation. SOL outcomes can depend on facts and legal issues such as:

• the true accrual trigger,
• potential tolling or exceptions,
• and whether a specialized SOL provision applies (not identified in this snapshot).

Gentle reminder: Use the results as a reference snapshot, and confirm key timing assumptions with qualified legal resources if needed.

Example input set (for orientation)

• Accrual/event date: 2024-03-01
• Cutoff/filing date: 2026-03-15
• Damages components:

  • Medical: invoices across 2024-03 to 2024-11
  • Lost wages: 2024-04 to 2025-02
  • Property damage: invoice 2024-03-20

With a 2-year general SOL, DocketMath will test whether each component’s timing falls within the 2 years preceding the cutoff date (using your entered date assumptions) and allocate accordingly.

Output elements you should expect Depending on your calculator configuration, you may see:

• Timing eligibility for each component (within vs. outside the SOL window)
• Allocated totals (based on your component/date inputs)
• A summary of dates used by the model

Checklist to reduce input mismatches

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