Description
Return session+interpreted-concurrent as uniquePersonMinutes and interpreted/session as interpretedShare.
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 session+interpreted-concurrent as uniquePersonMinutes and interpreted/session as interpretedShare.
When to use this tool
Use Extension Interpreter Contact Minute Share when checking the stated contact/travel, response or source-period convention.
How to use the tool and how it works
- Enter sessionMinutes, interpretedMinutes, concurrentMinutes. Use the units and conventions below.
- Run the tool. Correct any format, range, or cross-field input error before interpreting the output.
- Read uniquePersonMinutes, interpretedShare. Use the output convention below.
Require positive session duration, interpreted time within session and concurrent time within interpreted time. Return session+interpreted-concurrent as uniquePersonMinutes and interpreted/session as interpretedShare.1
| Input field | Meaning and units | Accepted input |
|---|---|---|
| sessionMinutes | Session Minutes | Required. Finite number; strictly above 0. |
| interpretedMinutes | Interpreted Minutes | Required. Finite number; minimum 0. |
| concurrentMinutes | Concurrent Minutes | Required. Finite number; minimum 0. |
| Output field | Interpretation | Returned shape |
|---|---|---|
| uniquePersonMinutes | sessionMinutes+interpretedMinutes-concurrentMinutes under the supplied overlap convention. | Required. Finite number. |
| interpretedShare | Interpreted Share Unit: 1. | Required. Finite number. |
{
"input": {
"sessionMinutes": 60,
"interpretedMinutes": 30,
"concurrentMinutes": 20
},
"output": {
"uniquePersonMinutes": 70,
"interpretedShare": 0.5
}
}Limitations and assumptions
- The overlap is supplied; this bookkeeping convention does not measure interpreter quality, comprehension or accessibility.
- 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 Visit Travel Contact Time Share
Return travel*fraction+contact+documentation and contact divided by that total.
- Advisory Response Delay
Return elapsed=response-request and counted=elapsed-pause.