Description
Calculate capa action due overdue day 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 capa action due overdue day gap from explicit caller-supplied inputs.
When to use this tool
Use it for capa action due overdue day gap when the required inputs and conventions are already available.
How to use the tool and how it works
- Enter openedDay, dueDay, closedDay, closed, today, extensionDays. Use the stated units and boundary conventions.
- Run the calculation. Correct any input error before interpreting a result.
- Read ageDays, effectiveDueDay, overdueDays. Inspect any known, defined, inclusion, or boundary flags before interpreting numeric values.
Require nonnegative integer extensionDays, dueDay>=openedDay, and the selected end day at least openedDay. Select closedDay when closed, otherwise today; calculate age, extended due day, and overdueDays=max(0,end-effectiveDueDay).1
| Input field | Meaning and units | Accepted input |
|---|---|---|
| openedDay | Opened Day | Required. Safe integer. |
| dueDay | Due Day | Required. Safe integer. |
| closedDay | Closed Day | Required. Safe integer. |
| closed | Closed | Required. Boolean. |
| today | Today | Required. Safe integer. |
| extensionDays | Extension Days | Required. Safe integer; minimum 0. |
| Output field | Interpretation | Returned shape |
|---|---|---|
| ageDays | Age Days | Required. Safe integer. |
| effectiveDueDay | Effective Due Day | Required. Safe integer. |
| overdueDays | Overdue Days | Required. Safe integer. |
{
"input": {
"openedDay": 100,
"dueDay": 120,
"closedDay": 125,
"closed": true,
"today": 130,
"extensionDays": 3
},
"output": {
"ageDays": 25,
"effectiveDueDay": 123,
"overdueDays": 2
}
}Limitations and assumptions
- The due day is not overdue. Ignored closedDay or today values do not affect the selected clock, and business-day calendars or the validity of an extension are not 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 capa action due overdue day 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 Effectiveness Review Gap
Inspect supplied CAPA review scheduling metadata without determining effectiveness or compliance.
- CAPA Response Unknown Clock Token
Preserve missing administrative response clocks with explicit definition flags.