How to run Offer Of Judgment Analyzer in DocketMath for Alabama

Step-by-step

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

Below is a practical walkthrough for running Offer Of Judgment Analyzer in DocketMath for Alabama (US-AL). This guide focuses on how to operate the calculator and how Alabama’s Rule 68 timing rule affects the analysis—without providing legal advice.

1) Open the tool

Start at the primary call to action:

• /tools/offer-of-judgment-analyzer

If you’re already in DocketMath, you can also navigate from your dashboard, then select Offer Of Judgment Analyzer.

2) Confirm jurisdiction is set to Alabama

In the tool settings or jurisdiction selector, choose:

• US-AL — Alabama

DocketMath uses jurisdiction-aware logic, so this step ensures the analyzer applies the correct version of Ala. R. Civ. P. Rule 68 timing rules.

3) Enter the key offer details

Most Offer Of Judgment Analyzer workflows require you to enter the offer information and what you’re comparing it against. Use the tool’s fields to enter:

• Offer amount (the money “allow[s] judgment to be taken” for)
• Offer date (the date the offer was served)
• Comparison value (often the final judgment amount, or a target recovery number you want to compare)
• Prevailing-side baseline / perspective (if the UI asks which side the “win” should be measured from)

Because each calculator UI can label inputs differently, match the underlying concepts:

• the offer you served,
• the result you’re comparing to (judgment or expected outcome),
• and the timing inputs needed for the Rule 68 eligibility check.

4) Add Alabama Rule 68 timing inputs (eligibility depends on date)

Alabama’s Rule 68 includes a timing requirement that affects whether an offer is eligible under the rule’s mechanism.

Rule 68 timing concept (Alabama):
Ala. R. Civ. P. Rule 68 provides that:

“At any time more than 14 days before the trial, a party may serve upon the other party a written offer to allow judgment to be taken against the party making the offer for the money or property or to the effect specified in the offer, with costs then accrued.”
— Ala. R. Civ. P. Rule 68 (source: https://alabama.rules.org/civil/rule68)

Important note about claim types: Your jurisdiction data did not identify a claim-type-specific sub-rule. That means you should use the general/default period for the timing check: more than 14 days before the trial.

In the tool, this typically means you’ll provide either:

• offer date and trial date (or a scheduled trial date), or
• a computed “days before trial” field if the UI offers it.

How outputs can change: The analyzer’s results can flip based on this eligibility test. If the offer is not “more than 14 days” before trial per the tool’s calculation, the output may mark the Rule 68 timing portion as failing or non-eligible—even if the offer-vs-outcome math still appears.

5) Enter cost-related numbers if the tool asks

Rule 68 also references “costs then accrued.” Even though your primary goal may be offer-vs-outcome, many Offer Of Judgment Analyzer tools model cost impacts when you provide cost inputs.

From the rule text (same citation as above), the mechanism includes:

• “with costs then accrued.”

If DocketMath asks for any of the following, enter the most defensible numbers you have:

• costs accrued at the time of the offer,
• estimated costs/fees/expenses used for modeling, or
• a costs figure tied to the baseline judgment.

If you don’t have precise cost data, you can still run the analysis, but understand that outputs that depend on costs will be less precise and more sensitive to your estimates.

6) Run the calculation and review the outputs

After entering the inputs, click Analyze (or the tool’s equivalent button).

When you review results, look for sections such as:

• Rule 68 timing eligibility check (e.g., pass/fail or eligible/ineligible based on “more than 14 days before trial”)
• Offer-vs-outcome comparison (whether the modeled outcome is more favorable than the offer, depending on how the tool defines “beats”)
• Costs impact summary (if costs were part of the model)

Practical tip: DocketMath’s outputs are driven by your entered:

• offer date
• trial date
• comparison value
• and any cost-related fields you entered

Changing one of these can change both timing eligibility and offer-vs-outcome conclusions. Treat reruns like “what-if” experiments.

7) Iterate with what-if scenarios

Use the analyzer to test variations. Common iterations include:

• adjusting the offer amount
• changing the offer date (if you want to see how close to the 14-day threshold the offer lands)
• updating the trial date assumption (if the UI uses a scheduled date that might have changed)
• adjusting the comparison value to reflect different potential judgment outcomes

When rerunning, compare against your prior output to identify which inputs are most sensitive.

8) Capture a decision-ready summary from your runs

Before exporting or copying results, capture a short summary for your top scenarios, such as:

• Offer amount
• Offer date
• Trial date assumption
• Timing eligibility outcome under Ala. R. Civ. P. Rule 68
• Offer-vs-outcome conclusion
• Any modeled cost-related figure(s) (if the tool includes them)

This makes it easier to reference your analysis later, regardless of how you document the scenario internally.

Common pitfalls

Even strong inputs can yield confusing or misleading outputs if you miss a Rule 68 assumption or mismatch how the tool interprets fields. Watch for these issues:

• Using a trial date that makes the offer fall inside (or right at) the threshold

  • Alabama’s default timing threshold is: “more than 14 days before the trial.”
  • If the offer date is exactly 14 days before trial (or later), the tool may treat it as not satisfying “more than,” depending on its date-difference logic.

• Assuming a special claim-type timing rule exists

  • Your jurisdiction data indicates no claim-type-specific sub-rule was found.
  • That means you should apply the general/default period for timing eligibility.

• Mixing up the tool’s “comparison value”

  • Some calculators compare an offer to the final judgment, others compare it to an expected recovery or a threshold.
  • Enter the number you truly want to compare, and keep it consistent across reruns.

• Leaving cost-related fields blank when the tool uses them

  • Rule 68 references “costs then accrued.”
  • If the calculator asks for costs and you enter 0/blank, cost-impact outputs may look smaller than they would be with realistic cost figures.

• Swapping dates or using the wrong date field

  • Offer date vs. trial date are the two dates that drive the timing eligibility check.
  • Double-check formatting (month/day/year) and ensure you’re entering the intended dates.

Gentle warning: If DocketMath marks the Rule 68 timing as “not more than 14 days before trial” (or similar), the timing eligibility portion may be treated as failing under Ala. R. Civ. P. Rule 68. Don’t ignore that signal—timing eligibility often matters to how the offer mechanism is evaluated.

Try it

Use DocketMath’s Offer Of Judgment Analyzer with a quick sample workflow:

• Set jurisdiction: US-AL
• Enter:

  • Offer amount: the number you want to model
  • Offer date: the service date you’re analyzing
  • Trial date: the scheduled (or assumed) trial date used by the tool
  • Comparison value: the judgment amount (or outcome target) you want to compare against
• Run the analysis

Then run two short sensitivity tests—changing only one variable at a time:

1. Timing sensitivity test

• Move the offer date earlier by ~7–10 days and re-run.
• Watch whether the timing eligibility check changes from ineligible to eligible under Ala. R. Civ. P. Rule 68 (“more than 14 days before the trial”).

1. Outcome sensitivity test

• Keep dates constant, but adjust the comparison value higher/lower to reflect different possible judgment outcomes.
• Observe how the offer-vs-outcome conclusion shifts.

If the tool offers an export or results-copy option, save your top scenarios with clear labels, such as:

• “Scenario A: earlier offer date”
• “Scenario B: higher comparison value”
• “Scenario C: updated trial date”

This creates a clean audit trail of what changed and what the output did in response.

Related reading

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