Description
Preserve missing administrative response clocks with explicit definition flags.
Quality records separate measured results, reference values, acceptance rules, and supporting evidence. Arithmetic consistency and record coverage can be checked against supplied criteria without establishing traceability, approving a method, or deciding product conformity.
Preserve missing administrative response clocks with explicit definition flags.
When to use this tool
Use it for capa response unknown clock token when the required inputs and conventions are already available.
How to use the tool and how it works
- Enter openedTime, responseTime, responseKnown, targetDuration. Use the stated units and boundary conventions.
- Run the calculation. Correct any input error before interpreting a result.
- Read elapsedDefined, elapsed, remaining. Inspect any known, defined, inclusion, or boundary flags before interpreting numeric values.
Require nonnegative targetDuration and, when responseKnown, responseTime>=openedTime. Return elapsed=responseTime-openedTime and remaining=targetDuration-elapsed only for known responses; otherwise both are zero with elapsedDefined false.1
| Input field | Meaning and units | Accepted input |
|---|---|---|
| openedTime | Opened Time | Required. Finite number. |
| responseTime | Response Time | Required. Finite number. |
| responseKnown | Response Known | Required. Boolean. |
| targetDuration | Target Duration | Required. Finite number. |
| Output field | Interpretation | Returned shape |
|---|---|---|
| elapsedDefined | Whether response timing is known; zero times are placeholders when false. | Required. Boolean. |
| elapsed | Elapsed | Required. Finite number. |
| remaining | Remaining | Required. Finite number. |
{
"input": {
"openedTime": 10,
"responseTime": 18,
"responseKnown": true,
"targetDuration": 10
},
"output": {
"elapsedDefined": true,
"elapsed": 8,
"remaining": 2
}
}Limitations and assumptions
- Unknown-response zeros are placeholders, not evidence of immediate response or remaining time. No current observation time is used to age an unanswered item.
- 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 capa response unknown clock token, check the source records and the supplied rule before comparing the result with another method. Use a separate evidence or method review when arithmetic consistency alone cannot establish the required conclusion.
References
Similar or alternative tools
- CAPA Action Due Overdue Day Gap
Calculate capa action due overdue day gap from explicit caller-supplied inputs.
- CAPA Effectiveness Review Gap
Inspect supplied CAPA review scheduling metadata without determining effectiveness or compliance.