Settlement Allocator Guide for Indiana

What this calculator does

Run this scenario in DocketMath using the Settlement Allocator calculator.

DocketMath’s Settlement Allocator helps you allocate a settlement amount across multiple types of damages so you can document a reasonable breakdown for accounting, distribution, and reporting.

In Indiana, the allocation often matters because certain claims can be time-barred. This guide focuses on the settlement allocation workflow in Indiana while also flagging the statute of limitations (SOL) concept you may want to incorporate into your settlement records.

Key Indiana timeline (SOL reference point)

Indiana’s SOL rules depend on the claim type, but many settlement contexts reference the general criminal statute-of-limitations framework for specified offenses. For the SOL cited in this guide:

• Indiana Code § 35-41-4-2 sets a 5-year limitations period for the covered category referenced by that section.
  Source: https://law.justia.com/codes/indiana/2022/title-35/article-41/chapter-4/section-35-41-4-2/

  • Sub-rule: 5 years — exception V3

What “allocation” means in this tool

The allocator typically answers questions like:

• How much of the settlement is reasonably attributable to past damages vs. future damages
• How to reflect multiple damage categories (for example, medical costs, lost wages, property loss, or other agreed categories)
• How the portion tied to time could interact with an SOL timeline

Because you control the inputs, your output is only as accurate as your damage-category estimates and your timeline selections.

When to use it

Use DocketMath’s Settlement Allocator when you have a settlement figure but need a structured breakdown rather than a single lump sum.

Common triggers in Indiana (practical use cases)

• You’re finalizing a settlement agreement that references multiple categories of damages rather than one undifferentiated payment.
• You need a worksheet for:

  • internal accounting,
  • distribution among parties,
  • insurer documentation,
  • or reporting packages.
• You want to separate damages that accrued before a cutoff date from those estimated to occur after that cutoff.
• You’re building a record that ties damage periods to relevant timing rules, including the 5-year framework referenced by Indiana Code § 35-41-4-2.

Timing guardrail (why the 5-year reference shows up)

If your settlement negotiations touch conduct/damages that occurred over several years, the 5-year limitations framework in Indiana Code § 35-41-4-2 (with the referenced exception) can be a useful anchor for the “older vs. newer” split you document.

Step-by-step example

Below is a concrete example of how you might use DocketMath’s Settlement Allocator for an Indiana settlement workflow.

Example facts (invented for demonstration)

• Settlement total: $120,000
• Damages categories agreed in the settlement structure:

  1. Past medical expenses (incurred)
  2. Future medical expenses (estimated)
  3. Lost wages (past)
  4. Non-economic damages (agreed lump category)
• Key timeline reference:

  • You’re documenting a cutoff that aligns with a 5-year window for the relevant timing discussion tied to Indiana Code § 35-41-4-2.
• Timeline anchors:

  • Cutoff date for “past vs. future allocation”: January 15, 2020
  • Settlement negotiation date: February 1, 2025
  • (For allocation, you’re using the cutoff date primarily to split past vs. future components.)

Step 1: Enter the settlement total

• Total settlement amount: 120000

Output effect: The allocator uses this number as the ceiling for all category allocations. Every category allocation plus rounding adjustments must total to $120,000.

Step 2: Provide estimates by category

Enter your category estimates (these are the driver for the allocation math):

Your tool will convert these estimates into an allocation structure tied to the total settlement.

Step 3: Confirm the cutoff logic (timeline split)

If the tool asks you to select a cutoff for “past” vs. “future” (or similar), enter:

• Cutoff date: 2020-01-15
• SOL reference window (if used in the tool): 5 years and/or link to the logic discussed under Indiana Code § 35-41-4-2 (5-year period; exception V3 as reflected in the cited sub-rule).

Output effect: If you input dates, the tool can help you label components as “within” vs. “outside” a time window based on your cutoff rules. That label is for your recordkeeping; the allocator’s primary job is the mathematical breakdown.

Step 4: Review category outputs and totals

After running the allocator, review:

• Each category dollar amount
• Whether past/future labeling matches your intent
• Whether the total equals $120,000 after rounding

A common outcome might look like:

• Past medical: $38,000
• Future medical: $22,000
• Past lost wages: $28,000
• Non-economic damages: $32,000
• Total: $120,000

Step 5: Export or copy the allocation summary

If DocketMath provides a copyable breakdown (worksheet-style), capture:

• Settlement total
• Category allocation amounts
• Past/future labels (and any timeline references)

Common scenarios

Settlement allocations often come up in a few repeated patterns. Here are practical scenarios and how you’d typically adjust inputs in DocketMath.

Scenario 1: Lump-sum settlement, but agreement requires category breakdown

What changes: You’re still entering a single total, but you must allocate it across categories—even if the agreement doesn’t give you a hard math formula.

How to handle in the tool:

• Allocate based on your best documented estimate for each category.
• Mark which categories are time-sensitive (past/future) versus time-agnostic (for example, agreed non-economic amounts).

Scenario 2: Damages span more than 5 years

What changes: The “past vs. future” split (or “within vs. outside” a timeline window) becomes more significant.

How to handle in the tool:

• Use a clearly stated cutoff date and apply it consistently to past/future classification.
• For the Indiana timeline reference, you’ll likely want to reference the 5-year framework associated with Indiana Code § 35-41-4-2 (including the referenced exception V3 in the cited sub-rule).

Scenario 3: Multiple claim types with different timing treatment

What changes: Even if the settlement is one check, the allocation can reflect different claim components.

How to handle in the tool:

• Separate categories that you would document differently in a settlement file.
• Keep a consistent approach: the tool is easier to defend when every category has a clear reason for why it’s allocated that way.

Scenario 4: Partial settlement plus additional later amounts

What changes: If you have multiple settlement payments, allocate each tranche separately or allocate at least by the payment agreement terms.

How to handle in the tool:

• Run the calculator for each settlement portion if the agreement differentiates them.
• Otherwise, allocate once using the final total, but keep a memo explaining the timing rationale.

Tips for accuracy

Small input mistakes can cascade into a misleading allocation. Use these accuracy checks.

Input quality checklist

Practical guidance on category design

A good allocation worksheet usually follows a structure like:

• Direct financial losses (past and future separately if relevant)
• Indirect losses (if your settlement agreement uses a separate label)
• Non-economic damages (often treated as time-agnostic unless your agreement specifies otherwise)

This helps your output stay readable for distribution and for settlement documentation.

Reconcile with the outputs

After you run DocketMath:

• Confirm category totals add up to the settlement total.
• Scan for mismatches between **your

Related reading

• Settlement Allocator Guide for Alabama
• Settlement Allocator Guide for Arizona
• Settlement Allocator Guide for California