How to calculate Offer Of Judgment Analyzer in Alaska

Quick takeaways

Run this scenario in DocketMath using the Offer Of Judgment Analyzer calculator.

• Alaska’s Offer of Judgment cost-shifting rule is governed by Alaska Stat. § 09.30.065. If you make an offer for a specified amount and the other side fails to obtain a judgment more favorable than your offer, the other side must pay the costs you incurred.
• The key comparison is “more favorable.” In DocketMath’s Offer Of Judgment Analyzer, you’ll typically compare the offer amount to the final judgment amount (using whatever “judgment total” figure matches your case workflow).
• The statute text provided indicates a default/general application—there’s no claim-type-specific sub-rule identified here. That means you apply the trigger generally rather than switching logic based on claim category.
• DocketMath’s Offer Of Judgment Analyzer converts the statutory trigger into a repeatable “what if” calculation workflow.

Inputs you need

To run the Offer Of Judgment Analyzer in Alaska (US-AK), collect inputs that match your case documents and keep definitions consistent.

Use this intake checklist as your baseline for Offer Of Judgment Analyzer work in Alaska.

• jurisdiction selection
• key dates and triggering events
• amounts or rates
• any caps or overrides

If any of these inputs are uncertain, document the assumption before you run the tool.

A. Offer details (made by one party)

• Offer amount (OA): the specified amount in your Offer of Judgment.
• Offer timing reference (optional for calculation, useful for records): some workflows track offer service dates for auditing and scenario documentation, even if the core comparison only needs OA vs. the final judgment.

B. Outcome details (what the other party ultimately got)

• Final judgment amount (FJ): the judgment figure you’re comparing to the offer.
• How you define “more favorable”: decide what number represents the judgment “more favorable” benchmark in your tool run. In most practical workflows, this is the total final judgment amount you enter as FJ. The goal is consistency: use the same definition every time you run a scenario.

C. Costs to apply if the trigger is met

• Costs incurred by the offering party (CI): the costs figure you want the tool to output as costs owed if the offer-shift trigger is met.

  • Practically, this should be the costs you can substantiate and that you treat as the “costs incurred” component for your internal calculation.
  • Alaska Stat. § 09.30.065 refers to “the costs incurred by the party making the offer.” So your CI input should reflect the costs you’re treating as that statutory bucket.

D. Optional workflow inputs (for clarity)

• Scenario label: e.g., “Trial outcome #1,” “Settlement outcome after mediation,” “Jury verdict.”
• Notes on what CI includes: such as filing fees, service costs, deposition transcripts—whatever your workflow includes—so you can reproduce results later.

Input-to-output checklist

How the calculation works

DocketMath’s Offer Of Judgment Analyzer implements Alaska’s statutory cost-shifting trigger as a comparison-based calculator.

DocketMath applies the Alaska rule set to the inputs, then runs the calculation in ordered steps. It validates the trigger date, applies rate or cap logic, and produces a breakdown you can audit. If you change any one variable, the tool recalculates the downstream outputs immediately.

Step 1: Apply the statutory trigger (Alaska Stat. § 09.30.065)

Alaska Stat. § 09.30.065 provides, in substance:

• If one party offers to allow judgment to be taken against the party for a specified amount, and

• the other party fails to obtain a judgment more favorable than the offer, then

• the other party shall pay the costs incurred by the party making the offer.

• Cited authority: Alaska Stat. § 09.30.065
  Source: https://law.justia.com/codes/alaska/2020/title-09.30.065/

Important for rule selection: Based on the statute text provided in your brief, no claim-type-specific sub-rule was found. That means you apply the statute’s default trigger generally rather than switching to separate categories.

Step 2: Determine whether the offer was “beaten”

The analyzer performs the same logical decision every time:

• If FJ is more favorable than OA → the trigger is not met → no offer-based cost shift under this rule.
• If FJ is not more favorable than OA → the trigger is met → cost shift applies.

In a typical numerical workflow, “not more favorable” often corresponds to a condition like:

• Trigger (typical): FJ <= OA
• Cost-shift result: Costs owed = CI

Because “more favorable” can be represented differently depending on your litigation context and how you define “judgment total,” treat this as a workflow definition problem: decide what number you enter as FJ so that “more favorable” means the same thing across scenarios.

Step 3: Compute the output amount (cost shift)

Once the trigger is evaluated:

• If the trigger is met: offer-shifted costs = CI
• If the trigger is not met: offer-shifted costs = $0 (for this cost-shifting component)

Worked examples (how outputs change)

Example 1: Offer not beaten → costs shift

• OA: $50,000
• FJ: $45,000
• CI: $8,250

Because FJ is not “more favorable” than OA in a typical numeric comparison, the trigger is met.

Output: Costs owed under the statute: $8,250

Example 2: Offer beaten → no costs shift

• OA: $50,000
• FJ: $60,000
• CI: $8,250

Because the opposing party obtained a result more favorable than the offer, the trigger is not met.

Output: Costs owed under the statute: $0

Example 3: Same offer/judgment, different costs → output tracks CI

• OA: $50,000
• FJ: $45,000
• CI: $3,100 (Scenario A)
• CI: $12,700 (Scenario B)

Trigger is met in both cases, so the tool’s output changes with the CI input.

• Scenario A costs owed: $3,100
• Scenario B costs owed: $12,700

That’s the practical benefit of the analyzer: once the trigger logic is established, the output tracks the cost figure you input.

Common pitfalls

1. Using the wrong comparison number

   • Problem: Entering a settlement figure, an interim order number, or a pre-trial estimate instead of the final judgment you compare against the offer.
   • Fix: Make sure FJ matches the judgment figure used for your “more favorable” comparison.

2. Assuming a special claim-type rule exists

   • Problem: Applying different logic based on the cause of action.
   • Fix: For this brief’s stated scope, no claim-type-specific sub-rule was found. Apply the default trigger described in the statute text.

3. Double-counting costs or including non-cost items

   • Problem: Treating attorney’s fees, overhead, or unsupported items as “costs incurred.”
   • Fix: Enter CI as the costs figure you can substantiate and that your workflow consistently labels as “costs incurred by the party making the offer.”

4. Interpreting “more favorable” inconsistently

   • Problem: In one run, you treat “more favorable” as “exceeds the offer,” but in another you treat it as “any improvement.”
   • Fix: Lock your “more favorable” definition and apply it consistently across scenarios.

5. Not documenting your definitions

   • Problem: Running a scenario but forgetting what FJ and CI represented.
   • Fix: Save scenario notes that define:

     • what FJ includes (and what it doesn’t),
     • what categories are included in CI.

Sources and references

• Alaska Stat. § 09.30.065 — Offer of judgment; costs if offer not beaten
  https://law.justia.com/codes/alaska/2020/title-09.30.065/

Start with the primary authority for Alaska and confirm the effective date before relying on any output. If the rule has been amended, update the inputs and rerun the calculation.

• Primary authority reference

Next steps

1. Open DocketMath’s Offer Of Judgment Analyzer:
   /tools/offer-of-judgment-analyzer
2. Enter your inputs:

   • **Offer amount (OA)
   • **Final judgment amount (FJ)
   • **Costs incurred (CI)
3. Run multiple scenarios to see how results change:

   • Keep OA the same, vary FJ to model different trial outcomes.
   • Keep FJ the same, vary CI to test sensitivity to your cost input.
4. Document your assumptions:

   • What number you used for FJ
   • What items you included in CI

Related reading

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