Skip to content

Main content

Archive Retention Trigger Gap Tool

Compare a supplied retention trigger and interval to a cutoff without selecting records policy.

Loading tool…

Description

Expiry=triggerAt+retention; remaining=expiry-cutoff.

Administrative workflow summaries depend on capacity, counted waiting, uncertain time envelopes, priority policies and delegated or retention intervals. A local predicate or deadline arithmetic does not establish a lawful fee, signature, retention decision or fair service priority. Boundary and denominator policies must be explicit.

Expiry=triggerAt+retention; remaining=expiry-cutoff.

When to use this tool

Use Archive Retention Trigger Gap when checking the stated administrative count, timing, priority or policy-boundary convention.

How to use the tool and how it works

  1. Enter triggerAt, recordAt, suppliedRetention, cutoff. 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 expiry, remaining. Use the output convention below.

Require triggerAt>=recordAt and nonnegative retention duration. Expiry=triggerAt+retention; remaining=expiry-cutoff.1

Input fieldMeaning and unitsAccepted input
triggerAtTrigger AtRequired. Finite number.
recordAtRecord AtRequired. Finite number.
suppliedRetentionRetention duration measured from triggerAt, not from recordAt.Required. Finite number; minimum 0.
cutoffCutoffRequired. Finite number.
Output fieldInterpretationReturned shape
expiryExpiryRequired. Finite number.
remainingSigned or clamped remainder under the exact convention specified above.Required. Finite number.
json
{
  "input": {
    "triggerAt": 20,
    "recordAt": 10,
    "suppliedRetention": 30,
    "cutoff": 40
  },
  "output": {
    "expiry": 50,
    "remaining": 10
  }
}

Limitations and assumptions

  • Retention begins at the supplied trigger rather than record creation; the tool does not determine lawful retention, deletion or preservation obligations.
  • 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

Review verified records and the governing organizational/legal requirements with responsible professionals for actual service, authority or retention decisions.

References

  1. Calculation and input contract: administrative-science/archive-retention-trigger-gap — tool.io

Similar or alternative tools