Description
Calculate authority question response deadline gap from explicit caller-supplied inputs.
A regulatory record check applies a supplied rule to labels, dates, identifiers, or amounts. Exact matches and clock boundaries matter, but a consistent record does not itself establish legal compliance. The governing jurisdiction, rule version, and authoritative evidence must be selected separately.
Calculate authority question response deadline gap from explicit caller-supplied inputs.
When to use this tool
Use it for authority question response deadline gap when the required inputs and conventions are already available.
How to use the tool and how it works
- Enter received, response, deadline, pausedDays, answered, today. Use the stated units and boundary conventions.
- Run the calculation. Correct any input error before interpreting a result.
- Read countedDays, remainingDays, overdue. Inspect any known, defined, inclusion, or boundary flags before interpreting numeric values.
Use response when answered is true and today otherwise. Subtract received and pausedDays for countedDays, calculate credited remainingDays, and mark overdue only when the credited evaluation time strictly exceeds deadline.1
| Input field | Meaning and units | Accepted input |
|---|---|---|
| received | Received | Required. Safe integer. |
| response | Response | Required. Safe integer. |
| deadline | Deadline | Required. Safe integer. |
| pausedDays | Paused Days | Required. Safe integer; minimum 0. |
| answered | Answered | Required. Boolean. |
| today | Today | Required. Safe integer. |
| Output field | Interpretation | Returned shape |
|---|---|---|
| countedDays | Counted Days | Required. Safe integer. |
| remainingDays | Remaining Days | Required. Safe integer. |
| overdue | Overdue | Required. Boolean. |
{
"input": {
"received": 100,
"response": 120,
"deadline": 125,
"pausedDays": 2,
"answered": true,
"today": 130
},
"output": {
"countedDays": 18,
"remainingDays": 7,
"overdue": false
}
}Limitations and assumptions
- Deadline must not precede received and evaluation must cover pausedDays. Pauses are a supplied day count; no authority-specific exclusions, business-day calendar, or legal decision is inferred.
- The field tables describe structural bounds; the mechanics also state cross-field requirements. Malformed input shapes, disallowed keys, and invalid domains cause input errors. Results must remain finite and within the declared output contract. A successful false flag or zero placeholder is distinct from an error.
- Numeric arithmetic uses binary floating point. Exact comparisons have no hidden tolerance or decimal rounding; negative zero is exported as zero. Decimal-text integer operations retain the exactness specifically stated above.
Alternative or Complementary methods
For authority question response deadline gap, check the source records and the supplied rule before comparing the result with another method. Consult the applicable authoritative rule when deciding eligibility, legal timing, fees, or obligations.
References
Similar or alternative tools
- Response Deadline Clock Offset
Compare supplied response/deadline clocks without selecting regulatory timelines or legal consequences.
- Authority Clock Stop Day Basis
Apply already resolved calendar/business clock-stop counts without interpreting agency timelines.