How to run Offer Of Judgment Analyzer in DocketMath for Alaska

Step-by-step

This guide walks you through running the Offer Of Judgment Analyzer in DocketMath for Alaska (US-AK). The analyzer helps you model the Alaska offer vs. outcome cost-shifting rule under Alaska Stat. § 09.30.065—it’s a practical calculation aid, not legal advice.

1) Open the tool for the right jurisdiction

1. Start at the primary call-to-action: **/tools/offer-of-judgment-analyzer
2. In the jurisdiction selector, choose Alaska (US-AK) so DocketMath applies Alaska’s offer-of-judgment cost rule.

2) Know the rule the analyzer is modeling (Alaska default)

Under Alaska Stat. § 09.30.065, the statute provides cost shifting when both of these conditions are met:

• One party offers to allow judgment to be taken for a specified amount, and
• The other party fails to obtain a judgment more favorable than the offer.

When the second condition happens, “the other party shall pay the costs incurred by the party making the offer.”

3) Enter the offer details (inputs that drive the result)

In the tool, enter the fields DocketMath provides (commonly: offer amount, outcome/judgment amount, and possibly costs incurred by the offeror).

Use these inputs carefully:

• Offer amount: the dollar amount offered.
• Outcome amount / judgment amount: the judgment the opposing party ultimately receives—this is what gets compared to the offer.
• Costs incurred by the offeror (if the tool requests it): the amount of costs the offeror incurred that could be shifted if the statute’s trigger is met.

If the calculator prompts for date-related inputs, only enter dates if you’re confident about them. If you’re unsure, leaving date fields blank is usually better than guessing, since incorrect dates can distort any timing logic the calculator may use.

4) Understand “more favorable” and how it affects the trigger

The triggering idea is simple: the opposing party must get a judgment more favorable than the offer to avoid the cost shift.

In a typical “threshold comparison” model:

• If Outcome > Offer, the opposing party is more favorable than the offer, and the tool will generally indicate no cost shift.
• If Outcome ≤ Offer, the opposing party did not obtain a more favorable judgment, and the tool will generally indicate a cost shift (based on whatever costs amount you provided and how DocketMath displays the result).

Because DocketMath may define the comparison using specific “basis” fields (for example, comparing a judgment amount directly to the offer amount, or using a net figure if the tool offers that structure), rely on the labels shown in the calculator rather than assuming the math is always “exact dollar comparison” without context.

5) Run the calculation and interpret the outputs

After you submit, review the results screens/panels. You should expect to see outputs that reflect:

• The comparison outcome (whether the judgment is treated as more favorable than the offer), and
• A cost-shift outcome or estimated cost impact (often using your costs incurred input).

Use an iterative workflow to understand sensitivity:

• Change the Outcome amount and rerun
  Watch for the moment the outcome crosses the “more favorable” threshold.
• Change the Offer amount and rerun
  See how raising or lowering the offer shifts which side meets the statutory comparison.
• Adjust the costs incurred value (if the tool allows) and rerun
  This typically changes the dollar impact even when the comparison (“more favorable” vs. not) stays the same.

6) Use the tool for scenario modeling (with the right expectations)

Treat the Offer Of Judgment Analyzer as a scenario model:

• Higher offer amounts usually make it harder for the opposing party to exceed the offer (so cost shifting may become more likely depending on the modeled structure).
• Lower offer amounts usually make it easier for the outcome to be “more favorable” (potentially reducing the likelihood of cost shifting).

That said, avoid using the calculator output as the only basis for decisions. Real-world outcomes can depend on case-specific details and legal interpretations. If you need guidance for a particular situation, consider speaking with a qualified professional.

Common pitfalls

Running the analyzer smoothly usually comes down to avoiding a few common input and interpretation issues:

Swapping these can invert the “Outcome > Offer” vs. “Outcome ≤ Offer” result. For example, if DocketMath asks for the judgment amount but you enter a different number (like a settlement figure or an interim number), the comparison can misrepresent the statute’s trigger. If DocketMath displays a cost-shift estimate using your costs input, missing that value can lead to an incomplete or misleading financial result. Based on the jurisdiction data provided here, no claim-type-specific sub-rule was found. For this Alaska run, the analyzer shouldn’t switch logic by claim type. If date inputs exist and you’re uncertain, leave them blank unless you can confidently match them to your scenario. Wrong dates can affect timing-related logic in some calculators.

Try it

You can quickly test the Alaska logic in a low-effort way, even if you don’t have perfect facts yet:

1. Go to /tools/offer-of-judgment-analyzer.
2. Set jurisdiction to Alaska (US-AK).
3. Enter:

   • An offer amount (e.g., 50,000)
   • A corresponding outcome/judgment amount
   • If prompted, an estimate of costs incurred by the offeror
4. Run the analyzer.
5. Do two small sensitivity checks:

   • Raise the outcome amount by 1–5% and rerun to see when the comparison flips to “more favorable.”
   • Lower the offer amount by 1–5% and rerun to see how the threshold changes the cost-shift output.

If the tool’s outputs behave as expected—cost shifting when the outcome is not more favorable than the offer—you’ll have a clearer understanding of how DocketMath is applying Alaska Stat. § 09.30.065 in this scenario model.

Related reading

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