Description
Split a shared-tool deposit by household or tool count.
Community projects combine participation counts, access assertions, funding bases and shared-resource policies. Local allocation or coverage arithmetic can organize those records, while equitable access, actual contribution value and valid funding rights require evidence and the applicable rules.
Split a shared-tool deposit by household or tool count.
When to use this tool
Use Shared Tool Deposit Base Flag when checking one explicit community-project capacity, funding, access or scheduling convention.
How to use the tool and how it works
- Enter depositPerTool, tools, households, splitByHousehold. Use the units and conventions below.
- Run the tool. Correct any format, range, or cross-field input error before interpreting the output.
- Read totalDeposit, chargePerUnit. Use the output convention below.
Split a shared-tool deposit by household or tool count. Require depositPerTool >= 0 and positive whole tools/households; totalDeposit = depositPerTool*tools, chargePerUnit divides by households when requested, otherwise tools.1
| Input field | Meaning and units | Accepted input |
|---|---|---|
| depositPerTool | Deposit Per Tool | Required. Finite number; minimum 0. |
| tools | Tools | Required. Safe integer; minimum 1. |
| households | Households | Required. Safe integer; minimum 1. |
| splitByHousehold | Split By Household | Required. Boolean. |
| Output field | Interpretation | Returned shape |
|---|---|---|
| totalDeposit | Total Deposit | Required. Finite number. |
| chargePerUnit | Charge Per Unit | Required. Finite number. |
{
"input": {
"depositPerTool": 20,
"tools": 3,
"households": 6,
"splitByHousehold": true
},
"output": {
"totalDeposit": 60,
"chargePerUnit": 10
}
}Limitations and assumptions
- This is a supplied allocation, not a verified deposit policy, liability, affordability or legal payment obligation.
- 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
Use actual project records, participant needs and governing funding/resource rules to assess practical adequacy, fairness and eligibility.
References
Similar or alternative tools
- Volunteer In Kind Match Cap Gap
Value volunteer hours under a supplied in-kind cap.
- Community Project Match Funding Gap
Return required project match and its funding gap.