Skip to content

Main content

Inquiry Reopen Time Offset Tool

Calculate inquiry reopen time offset from explicit caller-supplied inputs.

Loading tool…

Description

Add open-before-closure and reopened-to-answer durations; separately return closed gap and optionally include it in countedDuration.

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.

Add open-before-closure and reopened-to-answer durations; separately return closed gap and optionally include it in countedDuration.

When to use this tool

Use Inquiry Reopen Time Offset when checking the stated contact/travel, response or source-period convention.

How to use the tool and how it works

  1. Enter firstOpened, closed, reopened, answered, includeClosedGap. 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 activeDuration, closedGap, countedDuration. Use the output convention below.

Require firstOpened<=closed<=reopened<=answered. Add open-before-closure and reopened-to-answer durations; separately return closed gap and optionally include it in countedDuration.1

Input fieldMeaning and unitsAccepted input
firstOpenedFirst OpenedRequired. Finite number.
closedClosedRequired. Finite number.
reopenedReopenedRequired. Finite number.
answeredAnsweredRequired. Finite number.
includeClosedGapInclude Closed GapRequired. Boolean.
Output fieldInterpretationReturned shape
activeDurationActive DurationRequired. Finite number.
closedGapClosed GapRequired. Finite number.
countedDurationCounted DurationRequired. Finite number.
json
{
  "input": {
    "firstOpened": 0,
    "closed": 10,
    "reopened": 20,
    "answered": 30,
    "includeClosedGap": false
  },
  "output": {
    "activeDuration": 20,
    "closedGap": 10,
    "countedDuration": 20
  }
}

Limitations and assumptions

  • Only the supplied two active intervals are modeled; no business calendar or service-level requirement is 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

  1. Calculation and input contract: agricultural-extension/inquiry-reopen-time-offset — tool.io

Similar or alternative tools