Description
Apply already resolved calendar/business clock-stop counts without interpreting agency timelines.
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.
Apply already resolved calendar/business clock-stop counts without interpreting agency timelines.
When to use this tool
Use it for authority clock stop day basis when the required inputs and conventions are already available.
How to use the tool and how it works
- Enter calendarElapsed, suppliedBusinessElapsed, stoppedCalendar, stoppedBusiness, useBusiness. Use the stated units and boundary conventions.
- Run the calculation. Correct any input error before interpreting a result.
- Read countedDays, stopCredit. Inspect any known, defined, inclusion, or boundary flags before interpreting numeric values.
Choose suppliedBusinessElapsed-stoppedBusiness when useBusiness is true, otherwise calendarElapsed-stoppedCalendar. Return the chosen stop credit alongside countedDays after validating feasible nonnegative counts.1
| Input field | Meaning and units | Accepted input |
|---|---|---|
| calendarElapsed | Calendar Elapsed | Required. Safe integer; minimum 0. |
| suppliedBusinessElapsed | Supplied Business Elapsed | Required. Safe integer; minimum 0. |
| stoppedCalendar | Stopped Calendar | Required. Safe integer; minimum 0. |
| stoppedBusiness | Stopped Business | Required. Safe integer; minimum 0. |
| useBusiness | Use Business | Required. Boolean. |
| Output field | Interpretation | Returned shape |
|---|---|---|
| countedDays | Counted Days | Required. Safe integer. |
| stopCredit | Stop Credit | Required. Safe integer. |
{
"input": {
"calendarElapsed": 20,
"suppliedBusinessElapsed": 14,
"stoppedCalendar": 5,
"stoppedBusiness": 3,
"useBusiness": true
},
"output": {
"countedDays": 11,
"stopCredit": 3
}
}Limitations and assumptions
- Business days have already been resolved by the caller. The tool does not calculate weekends, holidays, time zones, or an agency's clock-stop policy.
- 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 clock stop day basis, 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
- Regulatory Workflow Clock Stop Duration
Calculate regulatory workflow clock stop duration from explicit caller-supplied inputs.
- Authority Question Response Deadline Gap
Calculate authority question response deadline gap from explicit caller-supplied inputs.