Skip to content

Main content

Extension Travel Shared Leg Credit Tool

Calculate extension travel shared leg credit from explicit caller-supplied inputs.

Loading tool…

Description

Return outbound+return minus sharedLeg only when creditShared; report credited distance separately.

Extension-service time budgets distinguish contact, travel, closed cases, credited pauses and source-validity periods. Allocated person-time differs from elapsed time, while half-open source periods differ from closed deadline checks. A supplied deadline or pause is not automatically an official service requirement.

Return outbound+return minus sharedLeg only when creditShared; report credited distance separately.

When to use this tool

Use Extension Travel Shared Leg Credit when checking the stated contact/travel, response or source-period convention.

How to use the tool and how it works

  1. Enter outbound, returnTravel, sharedLeg, creditShared. 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 countedDistance, credit. Use the output convention below.

Require nonnegative outbound/return/shared distances and sharedLeg<=both legs. Return outbound+return minus sharedLeg only when creditShared; report credited distance separately.1

Input fieldMeaning and unitsAccepted input
outboundOutboundRequired. Finite number; minimum 0.
returnTravelReturn TravelRequired. Finite number; minimum 0.
sharedLegShared LegRequired. Finite number; minimum 0.
creditSharedCredit SharedRequired. Boolean.
Output fieldInterpretationReturned shape
countedDistanceCounted DistanceRequired. Finite number.
creditCreditRequired. Finite number.
json
{
  "input": {
    "outbound": 20,
    "returnTravel": 30,
    "sharedLeg": 10,
    "creditShared": true
  },
  "output": {
    "countedDistance": 40,
    "credit": 10
  }
}

Limitations and assumptions

  • The supplied credit prevents one stated overlap from counting twice; actual journeys or reimbursement eligibility are not 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

Use verified clock, journey and source records with the governing service and reimbursement policies for actual performance or payment decisions.

References

  1. Calculation and input contract: agricultural-extension/extension-travel-shared-leg-credit — tool.io

Similar or alternative tools