Description
Calculate transfer targeting leakage share from explicit caller-supplied inputs.
A policy scenario makes eligibility bases, rates, thresholds, periods, and costs explicit. A calculated share or balance follows those assumptions. It does not select the governing policy or establish what caused an observed program outcome.
Calculate transfer targeting leakage share from explicit caller-supplied inputs.
When to use this tool
Use it for transfer targeting leakage share when the required inputs and conventions are already available.
How to use the tool and how it works
- Enter totalRecipients, ineligibleRecipients, totalTransfer, ineligibleTransfer. Use the stated units and boundary conventions.
- Run the calculation. Correct any input error before interpreting a result.
- Read recipientLeakage, amountLeakage, eligibleTransfer. Inspect any known, defined, inclusion, or boundary flags before interpreting numeric values.
Require positive integer totalRecipients, ineligibleRecipients within that count, positive totalTransfer, and ineligibleTransfer within that amount. Return recipientLeakage, amountLeakage, and eligibleTransfer=totalTransfer-ineligibleTransfer.1
| Input field | Meaning and units | Accepted input |
|---|---|---|
| totalRecipients | Total Recipients | Required. Safe integer; minimum 1. |
| ineligibleRecipients | Ineligible Recipients | Required. Safe integer; minimum 0. |
| totalTransfer | Total Transfer | Required. Finite number; strictly above 0. |
| ineligibleTransfer | Ineligible Transfer | Required. Finite number; minimum 0. |
| Output field | Interpretation | Returned shape |
|---|---|---|
| recipientLeakage | Recipient Leakage | Required. Finite number. |
| amountLeakage | Amount Leakage | Required. Finite number. |
| eligibleTransfer | Eligible Transfer | Required. Finite number. |
{
"input": {
"totalRecipients": 100,
"ineligibleRecipients": 10,
"totalTransfer": 1000,
"ineligibleTransfer": 200
},
"output": {
"recipientLeakage": 0.1,
"amountLeakage": 0.2,
"eligibleTransfer": 800
}
}Limitations and assumptions
- Recipient and amount leakage use different denominators. Ineligibility is supplied, not assessed, and these descriptive ratios do not establish fraud, causality, or program effectiveness.
- The field tables describe structural bounds; the mechanics also state cross-field requirements. Malformed input shapes, disallowed keys, and invalid domains cause input errors. Results must remain finite and within the declared output contract. A successful false flag or zero placeholder is distinct from an error.
- Numeric arithmetic uses binary floating point. Exact comparisons have no hidden tolerance or decimal rounding; negative zero is exported as zero. Decimal-text integer operations retain the exactness specifically stated above.
Alternative or Complementary methods
For transfer targeting leakage share, check the source records and the supplied rule before comparing the result with another method. Consult the applicable authoritative rule when deciding eligibility, legal timing, fees, or obligations.
References
Similar or alternative tools
- Benefit Cliff Discrete Income Gap
Calculate benefit cliff discrete income gap from explicit caller-supplied inputs.
- Benefit Reduction Taper Term
Apply a supplied disregard, taper and reduction cap without selecting a benefit policy.