Common Damages Allocation mistakes in Arkansas

The top mistakes

Damages allocation errors cost time (and sometimes money) because they distort the numbers you feed into DocketMath’s damages-allocation calculator. In Arkansas, the timing rules you use to model claims matter too—especially if you’re deciding whether certain damages fall within the applicable statute of limitations (SOL) window.

Quick note: This is general information, not legal advice. If SOL timing is critical to your situation, consider speaking with a qualified attorney.

1) Using the wrong SOL period for the “overall” damages model

A common workflow error is applying a claim-specific SOL when the analysis needs the general/default period.

In Arkansas, the general/default SOL period is 6 years, stated in Ark. Code Ann. § 5-1-109(b)(2). If you don’t identify a more specific (claim-type-specific) SOL rule, you should treat 6 years as your default—rather than guessing a different timeframe.

What goes wrong in DocketMath inputs: You set the damages “window” using the wrong SOL start/end assumptions, which shifts what portion of the damages is treated as recoverable.

2) Allocating the full award to the wrong party or asset category

Damages allocation isn’t just “how much,” it’s “which bucket.” Typical mistakes include:

• Assigning future damages into a past-only category
• Mixing compensatory and punitive components when your worksheet or the tool expects them separately
• Treating settlement totals as if they break down the same way as judgments (or vice versa), when your inputs are not categorized in the same structure

Why it matters: If your spreadsheet collapses categories too early, the calculator can’t reliably mirror your intended allocation logic—so the output can look mathematically consistent while being substantively wrong.

3) Feeding inconsistent dates into the calculator

DocketMath’s damages-allocation approach depends heavily on your inputs. The most frequent data integrity issues are date-related:

• Using the accident/event date in one field and the filing date in another without realizing the tool expects a different “start” event
• Leaving a date blank and unintentionally triggering a fallback or default behavior
• Rounding dates inconsistently (e.g., using “May 1” in one place and an exact day elsewhere)

What happens to the output: Even small date shifts can change the modeled timing, which can change allocated totals and whether portions appear inside or outside your SOL-based window.

4) Double-counting overlapping components

Another frequent error is counting the same damages twice under different line items—especially when amounts are summarized from a narrative record.

Common double-count patterns:

• Lost wages included as both “earnings” and “earning capacity”
• Medical costs counted once as “out-of-pocket” and again as a “future treatment estimate”
• Interest modeled both within a damages line item and again as a separate add-on

How to catch it quickly: Double-check that your component totals match the documentary totals (within rounding). If they exceed the expected baseline, you likely have overlap.

5) Ignoring Arkansas-specific modeling constraints tied to SOL timing

Even if your dollar amounts are accurate, the SOL period affects whether the damages window you modeled is potentially recoverable.

Because the general/default SOL period is 6 years under Ark. Code Ann. § 5-1-109(b)(2), make sure your modeled “damages period” does not assume coverage beyond that default timeframe when you are using the default SOL.

Practical impact: A scenario can look reasonable on pure math allocation, but fail on timing if part of the window extends past the SOL you assumed.

6) Treating settlement and judgment components as interchangeable

DocketMath works best when you clearly label what you’re allocating. Before you enter numbers, confirm whether you’re allocating:

• amounts claimed,
• amounts requested,
• or amounts actually awarded/settled.

What goes wrong: If you input settlement figures as though they were already separated into the same components as the judgment package (or vice versa), your allocation structure can drift—leading to distorted category totals.

How to avoid them

Use a process that separates (1) timing, (2) category buckets, and (3) math reconciliation. That workflow prevents most allocation mistakes before they reach DocketMath.

Use a written checklist for inputs, document each source, and run a quick sensitivity check before finalizing the result. When two runs differ, compare inputs line by line and re-run with one variable changed at a time.

Step 1: Lock the SOL basis first (default to 6 years when no specific rule is identified)

Before entering dollar amounts, confirm your timing assumption:

• Default SOL period: 6 years
• Statutory basis: **Ark. Code Ann. § 5-1-109(b)(2)
• Calculator context rule of thumb: If you don’t have a claim-type-specific SOL rule identified, use the general/default 6-year period.

Then set the damages window to align with that SOL assumption so the calculator’s allocation reflects what you intend to model.

Step 2: Map your damages into the exact buckets your workflow supports

Before using the tool, write a short “bucket map,” for example:

• Past economic damages
• Future economic damages
• Past non-economic damages (if applicable)
• Future non-economic damages (if applicable)

If damages-allocation expects specific categories, follow that structure instead of forcing everything into one “total” bucket.

Step 3: Use consistent event dates and keep date formats uniform

Create a small input checklist:

This reduces the chance that a mismatched date shifts your allocation window.

Step 4: Reconcile totals with a “single source of truth”

After running DocketMath:

If the output doesn’t align with your underlying totals, fix category mapping and overlap before trusting the numbers.

Step 5: Run a “sensitivity check” on the SOL window

Because Arkansas’ default SOL is 6 years, small timing changes can alter which damages fall inside your modeled recoverability window.

Try two scenarios:

If the allocation swings dramatically, you likely have a date input issue or inconsistent assumptions that should be corrected.

Where DocketMath fits (and how to use it without corrupting your numbers)

DocketMath is designed to standardize damages math and allocation logic. The best results come when you start with your timing basis, enter clean inputs, and then verify output through reconciliation.

If you want to model allocations directly, use /tools/damages-allocation as your starting point:
You can begin at /tools/damages-allocation before finalizing your category assignments.

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