How to run Damages Allocation in DocketMath for Indiana

Step-by-step

This guide walks you through running Damages Allocation in DocketMath for Indiana (US-IN), using the tool’s jurisdiction-aware rules. The goal is to help you produce an allocation-ready breakdown of damages periods using Indiana’s default time periods driven by the statutes cited below—without giving legal advice.

1) Open the calculator for Damages Allocation (Indiana)

Start at: /tools/damages-allocation

• Open the DocketMath tool: Damages Allocation
• Select jurisdiction: Indiana (US-IN)

If your UI prompts for jurisdiction selection up front, confirm it shows US-IN before entering any numbers. Jurisdiction selection affects the rule-set used to map dates into statutory allocation periods.

2) Identify the damages amounts and the period you want to allocate

Before you touch the calculator, gather the inputs you’ll need. Damages Allocation in DocketMath works best when you can tie damages to a clear timeline.

Use this checklist:

• Total damages amount (or components, if splitting into categories)
• Start date for the damages window
• End date for the damages window
• Any sub-periods you already know (optional, if your interface supports it)
• Currency and rounding preferences (if the tool asks)

Even without sub-periods, a clean start and end date helps DocketMath map your range into the Indiana periods.

3) Enter the key timeline dates

In Indiana mode, the tool’s allocation logic uses the statutory timing framework in:

• Ind. Code § 34-51-2-1 (definitions and structure)
• Ind. Code § 34-51-2-6 (period-related allocation structure)
• Ind. Code § 34-51-2-7 (additional period framework)
• Ind. Code § 34-51-2-8 (period framework completion)

Practically, this means:

• The calculator will map your overall date range into statutory allocation periods.
• If your dates don’t land neatly on period boundaries, you may see partial-period allocations.

4) Enter damages amounts (and split them if needed)

Depending on your situation, you may enter:

• One total damages figure, or
• Multiple categories/components (e.g., different kinds of damages you want allocated separately)

When you input amounts:

• If you enter one total, DocketMath typically allocates that total across the statutory periods generated from your timeline.
• If you enter multiple categories, the tool allocates each category into the mapped periods, then sums results into a combined output (depending on the interface).

What changes in the output:

• More categories → more detailed line items (one per category per period, or equivalent table structure), with rolled-up totals.

5) Review the generated allocation table and totals

After you submit, do a quick review of what the tool produced:

• Confirm you see an allocation-by-period table.
• Check that each period includes:

  • The period label (or the corresponding date span)
  • The allocated amount for that period
• Verify the totals (e.g., sum across periods) match your expectations for the input total(s).

If the tool provides any summary or totals row, treat that as your checkpoint before exporting.

6) Adjust inputs and compare scenarios

DocketMath is intended for iteration. To see how the allocation behaves, try small controlled changes:

• Shift your start date by a few days
• Shift your end date by a few days
• Compare single-total input vs split categories (if available)

Why this matters: statutory allocation periods can create step-changes near boundary dates. A small change in dates close to a boundary can shift a larger share into a different period.

7) Save or export results for your workflow

If the UI offers export or saving:

• Export to PDF/CSV (depending on what’s available)
• Save to your case workspace (if that feature exists)

When you save, include a note (in your own workflow notes) that documents:

• Jurisdiction selected (Indiana (US-IN))
• The start/end date range entered
• Any scenario adjustments you ran (e.g., “start date moved +3 days”)

Common pitfalls

Even when the calculator runs correctly, these are the most common reasons outputs feel “wrong” or confusing.

Pitfall checklist

• Wrong jurisdiction selected (e.g., another state remained selected while entering dates)
• Start/end dates reversed or entered in the wrong order
• Using the wrong timeline start date (the start date often drives which periods get created)
• Entering damages as a single “total” when you actually need category-specific allocation
• Expecting the tool to infer dates from narrative text (it can’t—dates must be entered explicitly)
• Ignoring partial-period effects when your dates land between statutory boundaries
• Rounding too early—prefer rounding at the end (after the tool’s totals), if the tool allows

Quick date-alignment sanity check

Before finalizing:

• Confirm your overall date range matches the damages window you intend.
• Look at the generated periods:

  • If you see an unexpectedly very short period receiving a large amount, re-check whether your boundary dates are correct and consistently entered.

Try it

Ready to run the Indiana allocation now?

1. Go to the calculator: /tools/damages-allocation
2. Select Indiana (US-IN)
3. Enter:

   • Start date
   • End date
   • Damages amount(s)
4. Submit and review the allocation-by-period table
5. Modify dates by a few days to see how outputs change around statutory boundary points

When comparing scenarios, focus on:

• The total allocated amount (should align with your input total(s), and depending on how prorating is handled, may remain stable)
• The distribution across periods (this is where boundary changes most noticeably affect results)

If you want to understand the output structure quickly, run two scenarios:

• One with a single total
• One with split categories
  The difference typically makes it easier to see how DocketMath maps each amount into the period table.

Related reading

• How to calculate Damages Allocation in Philippines — Full how-to guide with jurisdiction-specific rules
• Worked example: Damages Allocation in Philippines — Worked example with real statute citations
• Inputs you need for Damages Allocation in Philippines — Input checklist with sourcing guidance

For Indiana statutory timing context used in this guide, see: https://iga.in.gov/laws/2024/ic/titles/34#34-51-2 (Ind. Code §§ 34-51-2-1, 34-51-2-6, 34-51-2-7, 34-51-2-8).