Skip to content

Main content

GMP Task Training Version Date Gap Tool

Audit supplied task/training version and date metadata without determining personnel qualification.

Loading tool…

Description

Compare taskVersion and trainedVersion literally, return taskDay-trainingDay, and flag trainingAfterTask for a negative difference.

Good manufacturing practice records connect materials, actions, people, and source evidence. A local check can expose missing or inconsistent metadata, but it cannot authenticate a record or replace quality-system review.

Compare taskVersion and trainedVersion literally, return taskDay-trainingDay, and flag trainingAfterTask for a negative difference.

When to use this tool

Use GMP Task Training Version Date Gap when you need a literal manufacturing-record or source-support diagnostic.

How to use the tool and how it works

  1. Enter taskVersion, trainedVersion, trainingDay, taskDay. 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 sameVersion, daysSinceTraining, trainingAfterTask. Inspect sameVersion, trainingAfterTask before interpreting the associated values.

Compare taskVersion and trainedVersion literally, return taskDay-trainingDay, and flag trainingAfterTask for a negative difference.1

Input fieldMeaning and unitsAccepted input
taskVersionTask VersionRequired. Text; maximum UTF-16 length 8192.
trainedVersionTrained VersionRequired. Text; maximum UTF-16 length 8192.
trainingDayTraining DayRequired. Safe integer.
taskDayTask DayRequired. Safe integer.
Output fieldInterpretationReturned shape
sameVersionSame VersionRequired. Boolean.
daysSinceTrainingDays Since TrainingRequired. Safe integer.
trainingAfterTaskTraining After TaskRequired. Boolean.
json
{
  "input": {
    "taskVersion": "v2",
    "trainedVersion": "v1",
    "trainingDay": 100,
    "taskDay": 130
  },
  "output": {
    "sameVersion": false,
    "daysSinceTraining": 30,
    "trainingAfterTask": false
  }
}

Limitations and assumptions

  • Time uses supplied numeric day coordinates; no effective document version, training content, worker competence, or authorized task execution is verified.
  • 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.
  • Numeric calculations use binary floating point unless exact decimal-integer arithmetic is explicitly stated. No hidden measurement tolerance or decimal rounding is added; nonfinite or out-of-contract results are rejected. Numeric signed-zero results are exported as zero.

Alternative or Complementary methods

Use the controlled record system to verify identity, provenance, approvals, and complete audit history. Treat local flags as prompts for investigation rather than release or compliance decisions.

References

  1. Calculation and input contract: gmp/gmp-task-training-version-date-gap — tool.io

Similar or alternative tools