Benefit Burden Person Share Tool

Description

Return both shares and benefitShare minus burdenShare.

An ethics record can document claims, responsibilities, disclosures, decisions, and supplied weights. A formatted label or arithmetic allocation does not resolve the ethical question or demonstrate that a process was fair.

Return both shares and benefitShare minus burdenShare.

When to use this tool

Use Benefit Burden Person Share when you need one explicit component of a documented ethical analysis.

How to use the tool and how it works

Enter personBenefit, totalBenefit, personBurden, totalBurden. Use the units and conventions below.
Run the tool. Correct any format, range, or cross-field input error before interpreting the output.
Read benefitShare, burdenShare, shareGap. Use the output convention below.

Require positive benefit and burden totals and each person's amounts within its corresponding total. Return both shares and benefitShare minus burdenShare.^[1]

Input field	Meaning and units	Accepted input
personBenefit	Person Benefit	Required. Finite number; minimum 0.
totalBenefit	Total Benefit	Required. Finite number; strictly above 0.
personBurden	Person Burden	Required. Finite number; minimum 0.
totalBurden	Total Burden	Required. Finite number; strictly above 0.

Output field	Interpretation	Returned shape
benefitShare	Benefit Share	Required. Finite number.
burdenShare	Burden Share	Required. Finite number.
shareGap	Share Gap	Required. Finite number.

json

{
  "input": {
    "personBenefit": 20,
    "totalBenefit": 100,
    "personBurden": 30,
    "totalBurden": 100
  },
  "output": {
    "benefitShare": 0.2,
    "burdenShare": 0.3,
    "shareGap": -0.09999999999999998
  }
}

Limitations and assumptions

Benefit and burden can use different units because their shares are dimensionless; no commensurate welfare scale, fairness criterion, or ethical verdict is inferred.
Inputs must satisfy both the field types and the cross-field conditions above. Invalid input causes an error; a successful false flag or documented placeholder is a different result.
Numeric calculations use binary floating point unless exact decimal-integer arithmetic is explicitly stated. No hidden measurement tolerance or decimal rounding is added; nonfinite or out-of-contract results are rejected. Numeric signed-zero results are exported as zero.

Alternative or Complementary methods

Review the complete context, affected perspectives, and decision process rather than treating the output as an ethical verdict.

References

Calculation and input contract: ethics/benefit-burden-person-share — tool.io

Similar or alternative tools

Service Charge Area Share
Divide unitChargeableArea by positive totalChargeableArea for allocationShare and multiply totalServiceCharge by that share for unitCharge.
Expenditure Share Good
Require goodExpenditure within positive totalExpenditure and divide for share.