How to run Damages Allocation in DocketMath for Indiana
6 min read
Published April 15, 2026 • By DocketMath Team
Step-by-step
This guide walks you through running Damages Allocation in DocketMath for Indiana (US-IN) using jurisdiction-aware rules. The key Indiana input that affects allocation timing is the general statute of limitations (SOL) period that DocketMath uses for this flow.
Note: This article explains how to use DocketMath and how Indiana rules can affect calculation inputs/outputs. It is not legal advice.
1) Open the correct calculator
- Go to the primary CTA: /tools/damages-allocation.
- Confirm you’re using the Indiana (US-IN) jurisdiction context in the tool (if the interface provides a jurisdiction selector).
2) Enter case basics that affect allocation logic
In the Damages Allocation calculator, you’ll typically provide case dates and damage-related figures. For SOL-filtering and “lookback” calculations, consistency matters: small date mismatches can change which parts of damages are included versus excluded.
Use a checklist as you enter information:
- ☐ Jurisdiction: Indiana (US-IN)
- ☐ Key date(s): enter the dates the tool asks for (for example, an event/accrual date and/or filing date—use the exact prompt wording)
- ☐ Damage categories: select/enter the categories you want allocated (the tool’s prompts determine the exact fields you’ll see)
3) Use the correct Indiana statute of limitations rule (general/default)
DocketMath uses jurisdiction-aware rules. For Indiana, this guide uses the general/default civil limitations period.
- Indiana Code § 35-41-4-2: 5 years (general SOL period)
Because the brief states that no claim-type-specific sub-rule was found, the calculator should apply the general 5-year period for this flow. In practical terms, that means DocketMath will treat the 5-year window as the default limitations rule unless the tool offers a way to override or specify a different limitations logic.
Statute reference (as used in this calculator configuration):
- Indiana Code § 35-41-4-2 (general SOL period of 5 years)
Source: https://law.justia.com/codes/indiana/2022/title-35/article-41/chapter-4/section-35-41-4-2/
4) Confirm how the calculator treats damages timing
Damages allocation outputs typically depend on whether the tool:
- limits recoverable damages to a lookback window (based on the SOL),
- prorates amounts by time periods, and/or
- flags amounts outside the limitations window as excluded/non-recoverable.
Before running the calculation, check the tool’s options/toggles for terms like:
- lookback period
- SOL cut-off
- time-window filtering
- limitations period (or similar)
If there is a place to set limitations logic, ensure it aligns with the general 5-year SOL under IC § 35-41-4-2.
5) Run the allocation
When your inputs are complete:
- Click Calculate (or the tool’s equivalent).
- Review outputs for items such as:
- total allocated damages
- category-by-category allocation
- any SOL-based exclusions (for example, “outside limitation period” or similar language)
If the tool provides a breakdown of excluded time ranges, treat that as part of the result—not just a note.
6) Interpret results using the “what changed” test
To verify the output is behaving as expected, do a controlled test:
- Change only one input (e.g., adjust the filing date or whichever date determines the start/end of the SOL lookback).
- Re-run the calculation.
- Confirm the output moves in the direction you expect.
Common patterns with SOL-based filtering:
- If the start of the damages window moves closer to the filing date within the 5-year period, you should typically see:
- greater allocated amounts (or fewer exclusions)
- If the damages timeline shifts earlier so more falls outside 5 years, you should typically see:
- less recoverable allocation (or more exclusions)
7) Export or capture the allocation breakdown
If DocketMath offers an export option, download button, or copyable results panel:
- Save the allocation summary.
- Save the per-category breakdown.
- Save any SOL window notes/exclusion details shown by the tool.
This makes it easier to revisit inputs and compare results after adjusting dates.
Common pitfalls
Avoid these common mistakes—each one can produce confusing (and sometimes drastically different) Damages Allocation results in DocketMath.
Using the wrong limitations period
- For this Indiana Damages Allocation flow, the default is 5 years under Indiana Code § 35-41-4-2.
- Because no claim-type-specific sub-rule was found for this flow, the tool should default to the general 5-year period rather than applying a narrower rule.
Mismatched dates
- “Event date,” “accrual date,” and “filing date” (or whatever labels the tool uses) are not interchangeable.
- If you enter the wrong date into a prompt, the computed SOL lookback window shifts—and allocation can change significantly.
Assuming category names override SOL filtering
- Even if a damages category sounds “ongoing,” the calculator may still exclude amounts that fall outside the computed 5-year window.
- Category labels typically don’t override the date logic.
Skipping the SOL window/exclusion review
- Many calculators show a time window and/or exclusions list after calculation.
- If you skip that review, you may miss that a portion of claimed damages is filtered out due to the limitations window.
Expecting special rules without input support
- If you expected a claim-type-specific limitations rule, but the Damages Allocation flow (as configured here) does not support it, the tool will use the general/default 5-year period.
- Don’t assume the tool will “guess” the correct sub-rule unless there’s an explicit input or configuration option.
Warning: If your results include a large excluded/outside-limitations amount, don’t immediately assume the damages figures are wrong. First verify you entered the correct dates into the correct fields—the SOL window is often the #1 driver of unexpected outcomes.
Try it
- Select Indiana (US-IN) in the jurisdiction controls (if applicable).
- Enter the case date(s) and damage category totals requested by the tool.
- Ensure limitations logic is set to the general 5-year SOL under Indiana Code § 35-41-4-2 (default for this flow).
- Click Calculate.
- Run one quick adjustment to validate behavior—for example, shift a key date by 30 days and re-run to confirm the SOL-based inclusion/exclusion changes as expected.
