Skip to content

Main content

Deviation Detection Closure Gap

Count signed calendar days from a recorded deviation detection to closure without deciding closure adequacy.

Loading tool…

Description

Measure signed calendar duration between deviation detection and closure.

Quality assurance links actions, evidence, document versions, responsible roles and controlled dates. A recorded closed or approved label differs from verified completion and effectiveness. Due-date margins and missing-training flags organize supplied records while substantive review, competence and applicable quality obligations remain separate questions.

Measure signed calendar duration between deviation detection and closure.

When to use this tool

Use Deviation Detection Closure Gap when you already have detectedDate, closedDate and need to measure signed calendar duration between deviation detection and closure.

How to use the tool and how it works

  1. Enter detectedDate, closedDate. Use the units and conventions below.
  2. Run the tool. Correct any format, range, or cross-field input error before interpreting the output.
  3. Read signedCalendarDays. Use the output convention below.

Parse real UTC dates; return closedDate-detectedDate in days, retaining negatives.1

Input fieldMeaning and unitsAccepted input
detectedDateDetected DateRequired. Text; maximum UTF-16 length 8192. Real proleptic Gregorian YYYY-MM-DD; four-digit years 0000-9999 accepted.
closedDateClosed DateRequired. Text; maximum UTF-16 length 8192. Real proleptic Gregorian YYYY-MM-DD; four-digit years 0000-9999 accepted.
Output fieldInterpretationReturned shape
signedCalendarDaysSigned Calendar DaysRequired. Finite number.
json
{
  "input": {
    "detectedDate": "2026-10-28",
    "closedDate": "2026-11-01"
  },
  "output": {
    "signedCalendarDays": 4
  }
}

Limitations and assumptions

  • The tool does not verify closure, root cause, effectiveness or required response time.
  • Inputs must satisfy both the field types and the cross-field conditions above. Invalid input causes an error; a successful false flag or documented placeholder is a different result.

Alternative or Complementary methods

Review the controlled action, training, agreement and evidence records for actual completion and effectiveness. Reconcile versions, named responsibility and approval history rather than inferring a verified quality status from one marker or calendar gap.

References

  1. Calculation and input contract: quality-assurance/deviation-detection-closure-gap — tool.io

Similar or alternative tools