Description
Calculate supplier corrective action response gap from explicit caller-supplied inputs.
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.
Calculate supplier corrective action response gap from explicit caller-supplied inputs.
When to use this tool
Use it for supplier corrective action response gap when the required inputs and conventions are already available.
How to use the tool and how it works
- Enter requestDay, responseDay, acceptedDay, suppliedDeadline, accepted. Use the stated units and boundary conventions.
- Run the calculation. Correct any input error before interpreting a result.
- Read responseLag, deadlineMargin, acceptanceLag. Inspect any known, defined, inclusion, or boundary flags before interpreting numeric values.
Require responseDay at least requestDay and, when accepted is true, acceptedDay at least responseDay. Return responseLag, suppliedDeadline-responseDay as deadlineMargin, and acceptanceLag, using zero when no acceptance is recorded.1
| Input field | Meaning and units | Accepted input |
|---|---|---|
| requestDay | Request Day | Required. Safe integer. |
| responseDay | Response Day | Required. Safe integer. |
| acceptedDay | Accepted Day | Required. Safe integer. |
| suppliedDeadline | Supplied Deadline | Required. Safe integer. |
| accepted | Accepted | Required. Boolean. |
| Output field | Interpretation | Returned shape |
|---|---|---|
| responseLag | Response Lag | Required. Safe integer. |
| deadlineMargin | Deadline Margin | Required. Safe integer. |
| acceptanceLag | Acceptance Lag | Required. Safe integer. |
{
"input": {
"requestDay": 100,
"responseDay": 108,
"acceptedDay": 110,
"suppliedDeadline": 110,
"accepted": true
},
"output": {
"responseLag": 8,
"deadlineMargin": 2,
"acceptanceLag": 2
}
} Limitations and assumptions
- An unaccepted response's zero acceptanceLag is a placeholder governed by accepted. Dates are numeric day indices; no supplier policy, deadline extension, or adequacy of the corrective action 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 supplier corrective action response gap, 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 Response Unknown Clock Token
Preserve missing administrative response clocks with explicit definition flags.