Impact Calculator Guide for Indiana

What this calculator does

Run this scenario in DocketMath using the Impact calculator.

DocketMath’s Impact Calculator for Indiana (US-IN) helps you estimate the practical impact of multiple persons acting with a common intention. It’s built around a key concept reflected in Indian Penal Code, 1860, Section 34:

“Acts done by several persons in furtherance of common intention.”

That provision treats certain acts as attributable where multiple people share a common intent and participate in the furtherance of that intent.

How this calculator frames “impact”

The calculator is designed to help you structure an analysis workflow, not to replace case-specific legal judgment. You’ll typically input:

• the number of participants you want to model,
• the nature/degree of alleged participation (as structured categories),
• and the “common intention” factor you’re trying to represent.

What the calculator output is (and isn’t)

• ✅ Output: a numeric “impact” score and an explanation of which inputs drove it.
• ❌ Not output: a guaranteed legal outcome, a sentencing range, or a definitive liability determination.

To start using it, go directly to /tools/impact-calculator.

When to use it

Use the Impact Calculator guide when you want to model how group conduct with shared intent may change the way impacts are understood. It can be useful in these contexts:

• Case review and issue spotting
  You’re mapping how multiple alleged actors might be connected through a single plan or shared purpose.
• Evidence organization
  You’re sorting facts into categories like “participant role,” “coordination indicators,” and “purpose alignment.”
• Preliminary intake
  You need a consistent method to quantify and compare different factual theories.

Best-fit use cases

Check the boxes that match what you’re trying to do:

When not to use it

Avoid relying on the calculator when:

• you need a jurisdiction-specific sentencing computation for a specific Indiana statute (this tool is not a sentencing engine),
• the facts don’t involve multiple persons or a shared-intent theory,
• you’re trying to answer a question that depends on facts not represented in the inputs.

A gentle disclaimer: the calculator is for planning and structured analysis. It does not provide legal advice or a substitute for evaluating actual filings and governing authorities.

Step-by-step example

Below is a practical walkthrough showing how DocketMath’s impact-calculator changes output when you adjust inputs connected to common intention.

Example setup (hypothetical)

Imagine you’re reviewing a narrative where three people are alleged to have acted together toward a shared objective. You’re not trying to compute a legal conclusion—you’re trying to understand how the structure of the theory influences the calculator score.

Inputs you would enter

1. Number of participants: 3
2. Role category (per participant): choose a structured level for each person (for modeling, you might select):

   • Participant A: “active involvement”
   • Participant B: “supportive involvement”
   • Participant C: “limited involvement”
3. Common intention factor: a numeric slider or category representing how strongly the theory describes shared intent
4. Consistency factor: how aligned the conduct is across participants (e.g., “high alignment” if the story describes coordinated steps)

Run the calculator

After you submit, DocketMath returns:

• an Impact Score (numeric)
• a breakdown of drivers (e.g., participant count, role weighting, and the “common intention factor” you selected)
• a plain-language explanation of what the score represents

Interpreting the example results

Now test sensitivity by changing only one input.

Scenario change: reduce participants from 3 to 2

• Participants: 3 → 2
• Keep role categories and common intention factor the same.

Expected effect on impact score: it should drop, because fewer actors are being modeled under the shared-intent structure.

Scenario change: keep participants at 3, but lower common intention

• Common intention factor: “high” → “moderate”

Expected effect: the score should decrease more sharply than you might expect, because the tool treats “common intention” as a central driver of group attribution.

How the Section 34 concept fits into the model

The calculator’s logic is anchored to the core idea in Indian Penal Code, 1860, Section 34:

• When several persons act in furtherance of common intention, the acts are treated as connected through the shared purpose.

In the tool, that connection is represented through your common intention factor and how consistently you map each participant’s role to that shared purpose.

Source for Section 34 text: https://www.indiacode.nic.in/bitstream/123456789/1673/1/A1860-45.pdf

Common scenarios

Here are common patterns people try to model with the Impact Calculator. Use these as input guides so your entries reflect the story you’re working with.

1) Multiple actors with a coordinated plan

Typical facts you might have:

• participants act in a synchronized sequence,
• one person’s actions support another’s,
• the narrative frames conduct as part of a single objective.

How to model:

• choose higher common intention input,
• weight active roles higher than limited roles,
• keep “consistency/alignment” high.

2) Participants present, but roles are unclear

Typical facts:

• several people are named,
• but descriptions of intent coordination are thin,
• actions are described without a unifying purpose.

How to model:

• reduce common intention input,
• use a mix of “limited involvement” and “supportive involvement,”
• keep “alignment” lower.

3) Clear shared intent, uneven participation

Typical facts:

• a shared objective is described clearly,
• one person is the driver,
• others provide varying levels of support.

How to model:

• set common intention high,
• assign role categories with meaningful separation,
• expect the impact score to reflect strong linkage even with uneven roles.

4) Several participants, but only one person’s conduct is central

Typical facts:

• others are present,
• but their conduct is described as peripheral,
• there’s little evidence they furthered the main act in a coordinated way.

How to model:

• keep participant count higher if they’re alleged actors,
• lower “consistency/alignment,”
• mark most participants as “limited involvement.”

5) Reframing the theory: “common intention” vs. independent action

This scenario is often used to test competing narratives.

Model A (common intention):

• higher common intention input
• higher alignment score
• roles mapped as supportive or active steps

Model B (independent action):

• lower common intention input
• lower alignment
• roles mapped as independent or incidental

If your calculator outputs move significantly between Model A and Model B, that tells you your analysis is sensitive to the shared-intent characterization—exactly the kind of fact-pattern distinction you’d want to scrutinize.

Tips for accuracy

Use these practices to get more reliable, more consistent results when you run DocketMath’s Impact Calculator.

Calibrate your inputs to the Section 34 concept

Section 34 turns on “common intention” and action “in furtherance”. Your goal is to reflect that structure, not to guess outcomes.

When entering inputs, ask:

• Did the narrative describe a shared objective?
• Are actions portrayed as supporting steps toward that objective?
• Are multiple participants described as acting with purpose alignment, not mere coincidence?

This is grounded in the text of Indian Penal Code, 1860, Section 34:
https://www.indiacode.nic.in/bitstream/123456789/1673/1/A1860-45.pdf

Use consistent role mapping across scenarios

If you run multiple comparisons (e.g., two competing theories), keep role categories consistent:

• Participant A: same role category across runs
• Participant B: same role category across runs
• Participant C: same role category across runs

That way, differences in impact score can be attributed to the inputs you intended to test (like common intention), not to accidental categorization changes.

Check the “default period” behavior

Because no claim-type-specific sub-rule was found, the calculator uses a general/default period. That means:

• you shouldn’t expect the tool to automatically change timing/impact logic based on claim type,
• any difference in output comes from your input changes.

Run at least one sensitivity test

A good analysis habit is to do two runs that differ by only one variable:

• Run 1: your baseline inputs
• Run 2: change only the common intention factor (or only alignment)

If the score is stable across small changes, your conclusions may rely more on participant count/role weighting. Conversely, if the score drops sharply when you reduce common intention, your internal analysis should focus on whether the facts truly support shared intent.

Track your assumptions in a simple table

Even if you’re not writing a formal memo, a short table makes the outputs easier to interpret later.

Related reading

• Impact Calculator Guide for Alabama — Complete guide
• Impact Calculator Guide for Arizona — Complete guide
• Impact Calculator Guide for California — Complete guide