Choosing the right Damages Allocation tool for Idaho

Choose the right tool

Run this scenario in DocketMath using the Damages Allocation calculator.

Picking the right Damages Allocation approach in Idaho starts with one practical decision: what you’re allocating damages across (for example, multiple claims, multiple time periods, or different types of damages). In other words, you want your numbers and documentation to match the way DocketMath’s damages-allocation calculator is designed to work.

Why Idaho timing matters (before you allocate)

Before you finalize any allocation method, confirm whether the underlying case is still within Idaho’s general statute of limitations (SOL). If your filing date is outside the SOL, your allocation may be very detailed—but it may not ultimately support recovery.

In Idaho, the general SOL period is 2 years under Idaho Code § 19-403. Also, no claim-type-specific sub-rule was found in the materials provided, so this § 19-403 period is the default/baseline you should rely on unless you have a specific statute you can cite to override it.

When you should choose DocketMath (and the “damages-allocation” calculator)

Use DocketMath—specifically the damages-allocation workflow—when you need a repeatable way to split a total into evidence-aligned buckets, such as:

• Splitting a total damages figure into parts tied to your proof (different damage categories or different time windows)
• Producing an allocation you can explain clearly in discovery, negotiation, or settlement discussions
• Keeping inputs organized so updates are trackable (instead of rebuilding spreadsheets from scratch)

If your data is messy—different spreadsheets, inconsistent labels, or totals that don’t reconcile—DocketMath’s approach can help you normalize everything into a consistent set of allocation assumptions.

What to prepare for the calculator

To get reliable outputs, gather inputs first. The damages-allocation calculator generally works best when you have:

• Total amount you’re allocating (or enough components to reach a reliable total)
• Allocation basis (the rule that determines how the total is split—e.g., proportional shares, counts, or weights)
• Supporting inputs (evidence-based measures such as quantities or time periods that drive the allocation)

A practical tip: use stable “bucket” naming and consistent units:

• Keep the same label for the same damage bucket across drafts
• Use consistent units (e.g., days vs. hours)
• Tag whether a number is documented vs. an assumption you plan to support later

This makes it easier to update later and harder for reviewers to lose track of what changed.

Jurisdiction-aware rule: Idaho general SOL (2 years)

Because this page is jurisdiction-focused on Idaho, your jurisdiction-aware setup should reflect Idaho’s baseline SOL:

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

Even if your damages theory could be described under different claim labels, you should generally start with this default SOL period unless you can cite a specific statute that overrides it.

A simple workflow is to treat the SOL check as a filter:

• If the timing doesn’t work, don’t spend time perfecting an allocation that won’t change the recoverability analysis.
• If timing does work, then use DocketMath to structure damages clearly.

How outputs change when you adjust inputs

Even when you keep legal conclusions the same, the allocation output will change as soon as you change your allocation inputs. Understanding this helps you interpret the calculator results and revise efficiently.

To get the most from DocketMath, treat allocation inputs like version-controlled facts: update them only with a documented reason (new receipts, revised dates, corrected counts, or clarified documentation).

Why “tool selection” isn’t just software choice

Choosing the right tool is really choosing the right workflow for your case, such as:

• Calculator-first if your numbers are clean and reconcilable
• Documentation-first if evidence is fragmented and you must reconcile totals before allocating
• Timing gate-first in Idaho so you don’t allocate under an out-of-SOL theory

If you’re ready to follow the calculator-first path, start here: /tools/damages-allocation. (You can also browse the rest of the tooling via /tools.)

Next steps

1. Run the SOL gating check using Idaho Code § 19-403 (2 years).
   Use the general/default period as your baseline because no claim-type-specific sub-rule was identified in the provided materials.

2. Consolidate allocation inputs into one worksheet before using the calculator.
   Collect:

   • The total damages figure you plan to allocate
   • The allocation basis (weights, proportional measures, counts)
   • Each bucket’s supporting measure and units

3. Enter those inputs into DocketMath’s damages-allocation flow.
   While you input, note which numbers come directly from documents versus which are assumptions, and list the assumptions you intend to support later.

4. Create at least two allocation scenarios (if your evidence allows it).
   For example:

   • Scenario A: your current allocation basis
   • Scenario B: a revised basis tied to an updated time window or corrected counts
     This helps you discuss a realistic “allocation range” while staying evidence-grounded.

5. Map the calculator output back to the evidence trail.
   For each bucket, maintain a quick chain:

   • Bucket → supporting measure → document reference → units → date range

6. Freeze the version used for filings or settlement discussions.
   Once you select the scenario you plan to rely on, lock the inputs so internal review doesn’t drift the numbers.

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