How to calculate Offer Of Judgment Analyzer in Idaho

Quick takeaways

• In Idaho, the key fee-shifting framework for covered civil actions is Idaho Code § 12-120, which authorizes the court to award a reasonable attorney’s fee to the prevailing party.
• DocketMath’s Offer Of Judgment Analyzer helps you model how your offer amount, expected judgment amount, and attorney-fee estimates can affect the likely net outcome.
• There’s no claim-type-specific sub-rule identified for this calculator. That means this analyzer relies on the general/default approach tied to the § 12-120 prevailing-party concept, rather than a specialized timing or category switch.
• The analyzer is most useful when you have:

  • a realistic attorney-fee estimate for at least one side,
  • a clear damages/judgment expectation, and
  • enough case context to choose (or stress-test) the prevailing-party scenario your model is based on.

Inputs you need

Before you run DocketMath’s Offer Of Judgment Analyzer (US-ID), gather the inputs that drive the math. Depending on the tool’s exact field labels, you should expect to provide inputs like the following:

• Case jurisdiction: Confirm US-ID (Idaho).
• Expected judgment amount (or damages basis):

  • Example: a claimed amount of $150,000, or a forecasted judgment of $120,000.
• Offer amount: The specific amount you’re modeling as the offer (e.g., $100,000).
• Your side’s estimated attorney’s fees:

  • Usually based on hourly rate × hours, or another estimate you’ve already built.
• Opposing side’s estimated attorney’s fees (optional but useful):

  • Helps you model what fee-shifting could mean if the prevailing-party outcome flips.
• Prevailing-party scenario you want to model:

  • Because § 12-120 is framed around the prevailing party, the scenario you select affects who receives (or effectively bears) the fee award in the model.
• Timing assumptions (if prompted by the tool):

  • Enter facts you’re assuming for the estimate and stay consistent.
  • Because no claim-type-specific sub-rule was found for this calculator, treat timing values as scenario parameters rather than a specialized rule switch.

Quick checklist (fill before you start)

How the calculation works

DocketMath’s Offer Of Judgment Analyzer translates your entered numbers into a modeled financial outcome. For Idaho (US-ID), the calculator’s fee logic is anchored to Idaho Code § 12-120, which states (in relevant part) that:

• “In any civil action, the court shall award as part of the judgment a reasonable attorney’s fee to the prevailing party …”
• Source: https://legislature.idaho.gov/statutesrules/idstat/Title12/T12CH120/SECT12-120/

What the calculator is doing (conceptually)

1. Anchoring to the § 12-120 fee-shifting concept

   • The tool uses the prevailing-party framework to model whether a fee award would flow to one side.
   • Per the content brief requirement, there is no claim-type-specific sub-rule identified for this calculator. So the analyzer uses the general/default approach tied to § 12-120 rather than a specialized category rule.

2. Using your scenario to determine fee responsibility

   • You choose (or the tool helps you choose) the prevailing-party assumption.
   • Once the model determines who is “prevailing,” it applies your attorney-fee estimate to calculate the modeled fee impact.

3. Combining fee impact with the offer/judgment relationship

   • Your offer amount and expected judgment amount drive the modeled “net difference” logic.
   • In practice:

     • If the model’s expected judgment is significantly different from the offer, the net outcome you see will reflect that difference alongside the modeled fee award.
     • If your estimates change (especially fees), the modeled net result can move meaningfully—so it’s best to iterate.

Using DocketMath to model outcomes efficiently

A practical workflow is to run several variations:

• Baseline run: Use your best estimate of attorney fees and your best-guess judgment amount.
• Higher-fee run: Increase fees by ~20% to reflect extended litigation or less favorable efficiency.
• Lower-fee run: Decrease fees by ~15% to reflect faster resolution assumptions.

This is especially helpful because § 12-120 refers to “reasonable” attorney’s fees, and “reasonable” can depend on the court’s view of what is supportable. Treat the calculator output as a scenario model, not a guarantee.

Output types you should look for

Depending on how DocketMath presents results, you may see items such as:

• Modeled net difference between the offer and the expected judgment
• Estimated attorney-fee award (or fee obligation) based on the prevailing-party assumption
• Combined impact (damages/judgment component + modeled fees)

Common pitfalls

Here are the most common ways people accidentally make their Offer of Judgment modeling less useful—along with how to avoid them.

• missing a required input
• using a stale rate or rule
• ignoring calendar or holiday adjustments
• skipping documentation of assumptions

1) Getting the prevailing-party assumption backwards

• If the model assumes you’re the prevailing party but your scenario suggests the opposite outcome, you’ll flip the fee direction.
• With § 12-120, that can be a major change, not a minor rounding difference.

Fix: Run two versions—one where you prevail and one where the other side prevails—then compare.

2) Treating “reasonable attorney’s fees” as one guaranteed number

• § 12-120 requires reasonable fees.
• Courts may question hours, rates, or work performed.
• If you input overly optimistic fee estimates, your model can look too favorable.

Fix: Use ranges or stress-test (e.g., ±15–20%) so you see sensitivity.

3) Mixing up settlement math with judgment math

• Offers and judgments can involve different components (resolved claims, reductions, negotiation terms).
• If your “expected judgment amount” is not defined consistently (for example, whether it already accounts for negotiated reductions), your results may mislead.

Fix: Be explicit about what your “expected judgment” includes. Keep your offer/judgment assumptions aligned.

4) Assuming a claim-type-specific rule applies when none is loaded

• The brief requirement is clear: no claim-type-specific sub-rule was found.
• That means you should not expect the analyzer to apply a specialized category rule for different claim types.

Fix: Treat this as general/default § 12-120 prevailing-party modeling.

5) Running only one scenario

• One run can hide risk.
• If outcomes swing widely when you adjust fees, that’s real decision information.

Fix: Run at least 3 scenarios: baseline, higher-fee, lower-fee.

Sources and references

• Idaho Code § 12-120 (attorney’s fees; prevailing party) — Idaho Legislature (codified statutes)
  https://legislature.idaho.gov/statutesrules/idstat/Title12/T12CH120/SECT12-120/
  Relevant excerpt used in this guide: “In any civil action, the court shall award as part of the judgment a reasonable attorney’s fee to the prevailing party…”

Next steps

1. Enter your numbers once, then iterate

   • Run with your best estimate.
   • Re-run with attorney-fee assumptions adjusted (for example, ±15–20%).

2. Stress-test prevailing-party uncertainty

   • If you’re unsure who would be treated as the prevailing party, run:

     • a “you prevail” version, and
     • an “opponent prevails” version.
   • Compare how the fee-direction change affects net outcome.

3. Confirm Idaho jurisdiction is correctly selected

   • Ensure the tool is set to US-ID so you’re using Idaho-specific logic.

4. Document your assumptions

   • Write down how you calculated your fee estimate (hours × rate) and what your expected judgment amount includes.
   • This improves consistency as your strategy evolves.

To start right away, use:

• **Offer Of Judgment Analyzer

Related reading

• Offer of Judgment Analyzer Guide for Alabama
• Offer of Judgment Analyzer Guide for Arizona
• Offer of Judgment Analyzer Guide for Colorado