Skip to content

Main content

Community Event Travel Cost Share

Split an explicit event travel cost between a supplied subsidy fraction and equal participant contributions.

Loading tool…

Description

Split a supplied event travel cost between subsidy and equal participant shares.

Community records describe contributions, volunteer time, grants, notices, language requests and meeting participation. Person-minutes differ from elapsed task time, assigned in-kind values require a valuation basis, and a nominal seat count need not be a whole-person allocation. Supplied participation or permission flags do not verify actual access, consent or eligibility.

Split a supplied event travel cost between subsidy and equal participant shares.

When to use this tool

Use Community Event Travel Cost Share when you already have totalTravelCost, participantCount, subsidizedFraction and need to split a supplied event travel cost between subsidy and equal participant shares.

How to use the tool and how it works

  1. Enter totalTravelCost, participantCount, subsidizedFraction. Use the units and conventions below.
  2. Run the tool. Correct any format, range, or cross-field input error before interpreting the output.
  3. Read subsidyAmount, participantCostEach. Use the output convention below.

Require totalCost>=0, positive safe participantCount and subsidy fraction in [0,1]; subsidy=cost*fraction, each=cost*(1-fraction)/count.1

Input fieldMeaning and unitsAccepted input
totalTravelCostTotal Travel CostRequired. Finite number; minimum 0.
participantCountParticipant CountRequired. Safe integer; minimum 1.
subsidizedFractionSubsidized FractionRequired. Finite number; minimum 0; maximum 1.
Output fieldInterpretationReturned shape
subsidyAmountSubsidy AmountRequired. Finite number.
participantCostEachParticipant Cost EachRequired. Finite number.
json
{
  "input": {
    "totalTravelCost": 120,
    "participantCount": 6,
    "subsidizedFraction": 0.5
  },
  "output": {
    "subsidyAmount": 60,
    "participantCostEach": 10
  }
}

Limitations and assumptions

  • Equal sharing is an assumption. No attendance, eligibility, policy, currency, actual subsidy or fair allocation is verified.
  • 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 underlying meeting, funding, service and volunteer records with the applicable project rules. Use full budgets, schedules and participation evidence when evaluating delivery or fairness; local labels and arithmetic retain only the stated assumptions.

References

  1. Calculation and input contract: community-development/community-event-travel-cost-share — tool.io

Similar or alternative tools