Training Version Effective Gap Tool

Description

Compare trainedVersion with taskVersion literally, return trainingDay-effectiveDay and taskDay-trainingDay.

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 trainedVersion with taskVersion literally, return trainingDay-effectiveDay and taskDay-trainingDay.

When to use this tool

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

How to use the tool and how it works

Enter trainedVersion, taskVersion, trainingDay, effectiveDay, taskDay. Use the units and conventions below.
Run the tool. Correct any format, range, or cross-field input error before interpreting the output.
Read versionMatches, trainingVsEffective, trainingLeadToTask. Inspect versionMatches before interpreting the associated values.

Compare trainedVersion with taskVersion literally, return trainingDay-effectiveDay and taskDay-trainingDay.^[1]

Input field	Meaning and units	Accepted input
trainedVersion	Trained Version	Required. Text; maximum UTF-16 length 8192.
taskVersion	Task Version	Required. Text; maximum UTF-16 length 8192.
trainingDay	Training Day	Required. Safe integer.
effectiveDay	Effective Day	Required. Safe integer.
taskDay	Task Day	Required. Safe integer.

Output field	Interpretation	Returned shape
versionMatches	Version Matches	Required. Boolean.
trainingVsEffective	Training Vs Effective	Required. Safe integer.
trainingLeadToTask	Training Lead To Task	Required. Safe integer.

json

{
  "input": {
    "trainedVersion": "v2",
    "taskVersion": "v2",
    "trainingDay": 110,
    "effectiveDay": 100,
    "taskDay": 120
  },
  "output": {
    "versionMatches": true,
    "trainingVsEffective": 10,
    "trainingLeadToTask": 10
  }
}

Limitations and assumptions

Day inputs are numeric coordinates and signed differences are retained; version match and timing do not establish competence, authorized work, or effective training compliance.
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

Calculation and input contract: gmp/training-version-effective-gap — tool.io

Similar or alternative tools

GMP Task Training Version Date Gap
Compare taskVersion and trainedVersion literally, return taskDay-trainingDay, and flag trainingAfterTask for a negative difference.
GMP Training Effective Date Overlap
Test effectiveDay inclusively within that window, compare requiredRole with trainedRoles, and return positive distance from the window or zero inside.