Worked example: Damages Allocation in Iowa

Example inputs

Run this scenario in DocketMath using the Damages Allocation calculator.

Below is a worked example of how DocketMath can allocate damages when you’re working in Iowa (US-IA) using the general/default statute of limitations (SOL) rules.

Scenario (what we’re allocating)

Assume an Iowa plaintiff brings a civil claim seeking:

• Compensatory damages (economic loss and related out-of-pocket amounts)
• Non-compensatory damages (a separate bucket that you may later map to specific heads of damages depending on the pleadings)

To demonstrate allocation mechanics (and how SOL timing affects outcomes), we’ll use one filing date and several “damage measurement” windows.

This is an educational example. It’s not legal advice, and actual accrual/limitations issues can be fact- and claim-dependent.

Facts and dates (US-IA)

Use these dates in the damages-allocation calculator logic (open it at /tools/damages-allocation):

• Date of filing (claim date): 2026-04-15
• Accrual/trigger date assumption (start of lookback): 2024-04-15
• Damage measurement windows:

  • Window A (within 2 years): 2024-07-01 through 2025-12-31
  • Window B (outside 2 years): 2024-01-01 through 2024-03-31

Damage amounts to allocate

Assume the following raw amounts are identified in your records:

We’ll allocate between “likely timely” and “likely SOL-barred” components based on the 2-year general SOL in Iowa Code §614.1.

DocketMath inputs (conceptual)

In /tools/damages-allocation, you’ll typically enter:

• Jurisdiction: US-IA
• SOL basis: General/default SOL
• General SOL period: 2 years
• Statute reference: Iowa Code §614.1
• Key dates: the date of filing plus the date(s) or windows that describe when the damages accrued or were measured

Important (default rule disclosure): This example uses the general/default SOL period because no claim-type-specific sub-rule was found for this example. That means the allocation below relies on Iowa’s general 2-year default in Iowa Code §614.1, not a specialized limitations rule.

For the example mechanics, we’ll assume the calculator treats Window A amounts as within the 2-year lookback (likely timely) and Window B amounts as outside it (potentially barred).

Example run

Let’s run the numbers.

Run the Damages Allocation calculator using the example inputs above. Review the breakdown for intermediate steps (segments, adjustments, or rate changes) so you can see how each input moves the output. Save the result for reference and compare it to your actual scenario.

Step 1: Apply the Iowa general SOL period (2 years)

Iowa Code §614.1 provides a 2-year general/default limitations period.

With the filing date set to 2026-04-15, the “lookback” boundary is based on the assumed trigger:

• Start of lookback: 2024-04-15
• Amounts tied to periods before 2024-04-15 are more likely to be treated as outside the 2-year window.

(That’s why the precise “accrual/trigger” assumption matters for what the tool flags as timely vs. potentially barred.)

Step 2: Allocate compensatory damages between Window A and Window B

You identified $120,000 total compensatory damages across both windows.

To keep the example concrete, assume the records break that $120,000 into:

• Window A share (within 2 years): $90,000
• Window B share (outside 2 years): $30,000

Step 3: Allocate non-compensatory damages

Non-compensatory damages in this example are only in Window A.

• Non-compensatory total: $45,000
• Window A share: $45,000
• Window B share: $0

Step 4: Produce allocation outputs

Here’s the allocation result you would expect a jurisdiction-aware tool like DocketMath to show under the general SOL approach.

What the tool is doing (mechanically)

DocketMath’s damages-allocation calculator is effectively answering:

“Given an Iowa general SOL of 2 years under Iowa Code §614.1, which portions of the damage timeline fall inside vs. outside the limitations window?”

So the output is not just “total damages”—it’s a timed allocation you can compare against the version of the claim or damages narrative you plan to present.

Pitfall to watch: The SOL boundary depends on your accrual/trigger assumptions and on how you map dates to each damage component. If your inputs reflect the wrong accrual concept, the “timely vs. barred” split can change even when the grand total stays the same.

Sensitivity check

Now let’s stress-test the result. In practice, it’s often the timeline inputs (not the final dollar totals) that drive differences in “timely” vs. “barred.”

To test sensitivity, change one high-impact input (like the rate, start date, or cap) and rerun the calculation. Compare the outputs side by side so you can see how small input shifts affect the result.

Sensitivity 1: Moving the filing date by 30 days

Change only the date of filing:

• Original filing: 2026-04-15
• New filing: 2026-05-15 (30 days later)

That shifts the lookback boundary approximately to:

• New start of lookback: ~2024-05-15

Consequence: Any damage component that falls between 2024-04-15 and 2024-05-15 could flip from “inside” to “outside.”

In our specific example:

• Window B is 2024-01-01 through 2024-03-31 → still outside
• Window A is 2024-07-01 through 2025-12-31 → still inside

Result: Allocation likely stays the same.

Sensitivity 2: Shifting part of Window A earlier (reclassify $ within timeline buckets)

Assume you later discover some compensatory loss should have been assigned earlier:

• Move $10,000 of compensatory from Window A to Window B
• Totals remain $120,000, but the split changes

New shares:

• Window A share: $80,000
• Window B share: $40,000

New outputs:

• Total timely (estimated) = $80,000 + $45,000 = $125,000
• Total potentially barred (estimated) = $40,000 + $0 = $40,000

Key takeaway: A $10,000 timing reclassification produces a corresponding $10,000 change in the “timely” bucket in this simplified example.

Sensitivity 3: Using a different SOL basis (confirm you’re on the right rule)

Because this example intentionally applies Iowa’s general/default 2-year SOL in Iowa Code §614.1, the result assumes no more specific limitations provision applies.

Quick checklist for sensitivity reviews

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