Inputs you need for Damages Allocation in Indiana

Inputs you will need

Damages allocation in Indiana starts with one decision: what claims and damages are you allocating and when did the underlying acts occur. In DocketMath, the “damages-allocation” calculator works best when you provide a clean set of dates and amounts that match how you’re splitting damages in your case workflow.

Below is an input-checklist tailored to Indiana’s general/default statute of limitations (SOL) period for damages allocation timing. Indiana’s general/default SOL period is 5 years, and the general statute is Indiana Code § 35-41-4-2. The general/default period applies unless you have a claim-type-specific rule. Based on the jurisdiction data provided, no claim-type-specific sub-rule was found, so you should treat 5 years as the governing baseline for SOL timing.

Checklist of inputs to gather:

Practical note: The calculator should follow your inputs. Because no claim-type-specific sub-rule was found in the jurisdiction data provided, the tool should treat Indiana’s 5-year default as the applicable SOL timing baseline under Ind. Code § 35-41-4-2.

Where to find each input

Use this “data sourcing map” to ensure you aren’t running DocketMath with incomplete or mismatched numbers.

Most inputs live in the case file, contracts, or docket entries. Dates usually come from the triggering event notice; rates and caps come from governing documents or statute; and amounts come from the ledger or judgment. Record the source for each value so the run is reproducible.

1) Key event dates (start of the clock)

Pull event dates from sources that reflect the relevant conduct timeframe you’re allocating:

• Complaints / charging information (if you’re using a criminal-case workflow)
• Incident reports
• Internal timeline notes that cite specific dates
• Demand letters or final communications (if your allocation process tracks those dates)

If you have multiple events:

• Identify the earliest date that starts your allocation universe for SOL timing.
• Collect later dates if your damages allocation spans different periods (for example, “early” versus “later” damages).

Indiana SOL anchor for timing:

• 5-year period referenced in Ind. Code § 35-41-4-2 (general/default SOL).

2) Amounts to allocate (the arithmetic core)

Pull totals and sub-totals from the place where your damages numbers are already documented and reconciled:

• Damage worksheets
• Billing summaries
• Expert reports or internal damage models
• Settlement demand calculations (if you’re using them as the baseline)

Reconciliation check before you run DocketMath:

• Total damages = sum of allocated sub-amounts
• If totals don’t match, correct the underlying math first—DocketMath will reflect the structure you enter.

3) Allocation method settings (how the tool divides)

Inside DocketMath → damages-allocation, choose the setup that matches your allocation logic:

• Category-driven allocation (for example, property damage, loss-related items, or other buckets)
• Party-driven allocation (for example, co-defendant split, insurer split, or internal buckets)

Alignment tip:

• If your existing spreadsheet uses certain buckets, map those buckets to DocketMath’s expected inputs so you don’t have to translate categories after the fact.

Run it

Start at /tools/damages-allocation and enter the inputs you collected. If you already have a case timeline, you can often reuse the same dates.

Gentle disclaimer: This is a workflow tool for organizing and modeling assumptions. It isn’t a substitute for legal advice, and SOL timing can turn on case-specific details.

Practical run sequence (fastest to validate)

1. Set the jurisdiction to Indiana (US-IN) in DocketMath.
2. Apply the SOL baseline as the default

   • Use 5 years from Ind. Code § 35-41-4-2 as the general/default SOL period.
   • Because no claim-type-specific sub-rule was found in the jurisdiction data you provided, don’t override this baseline unless you have a separate, case-specific basis in your workflow.
3. Enter the earliest event date

   • This is the date most likely to determine whether a portion of damages falls inside versus outside the 5-year SOL window in your model.
4. Enter any later event dates (if your allocation spans multiple events)

   • This helps the output reflect timing differences across the allocation universe.
5. Enter the amounts

   • Total damages and each allocated sub-amount (matching your chosen category/party buckets).
6. Run the calculator and review outputs.

How outputs change when you adjust inputs

Use these quick “cause-and-effect” checks to confirm the run makes sense:

• Earlier event date

  • Moving it back can cause more damages to fall outside the 5-year baseline window (as reflected in your model).
• Later event date

  • Moving it forward can cause more damages to appear within the 5-year window.
• Total vs. sub-totals mismatch

  • The output will mirror the structure entered. If totals don’t reconcile, fix the source math first.
• Different allocation buckets

  • Changing categories/parties can reorganize output, which can affect how you summarize results—even if the overall total stays the same.

For quick navigation, you can jump directly into the tool here: /tools/damages-allocation.

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