Description
Return travel*fraction+contact+documentation and contact divided by that total.
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 travel*fraction+contact+documentation and contact divided by that total.
When to use this tool
Use Extension Visit Travel Contact Time Share when checking the stated contact/travel, response or source-period convention.
How to use the tool and how it works
- Enter travel, contact, documentation, sharedTravelFraction. Use the units and conventions below.
- Run the tool. Correct any format, range, or cross-field input error before interpreting the output.
- Read allocatedTime, contactShare. Use the output convention below.
Require nonnegative travel/contact/documentation and sharedTravelFraction in [0,1], with positive allocated total. Return travel*fraction+contact+documentation and contact divided by that total.1
| Input field | Meaning and units | Accepted input |
|---|---|---|
| travel | Travel | Required. Finite number; minimum 0. |
| contact | Contact | Required. Finite number; minimum 0. |
| documentation | Documentation | Required. Finite number; minimum 0. |
| sharedTravelFraction | Allocated share of travel retained in the time budget, not the share subtracted. Unit: 1. | Required. Finite number; minimum 0; maximum 1. |
| Output field | Interpretation | Returned shape |
|---|---|---|
| allocatedTime | Allocated Time | Required. Finite number. |
| contactShare | Contact Share Unit: 1. | Required. Finite number. |
{
"input": {
"travel": 60,
"contact": 30,
"documentation": 10,
"sharedTravelFraction": 0.5
},
"output": {
"allocatedTime": 70,
"contactShare": 0.42857142857142855
}
} Limitations and assumptions
- Travel fraction is the allocated share retained, not a discount deducted; real schedules and work quality are not 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
Use verified clock, journey and source records with the governing service and reimbursement policies for actual performance or payment decisions.
References
Similar or alternative tools
- Extension Interpreter Contact Minute Share
Return session+interpreted-concurrent as uniquePersonMinutes and interpreted/session as interpretedShare.
- Farmer Training Practice Theory Time Split
Contact excludes breaks; practiceShare=practice/contact, while sessionMinutes adds breaks.