Skip to content

Main content

Biosecurity Audit Record Retention Window Tool

Audit explicit record-retention timing and hold/removal flags.

Loading tool…

Description

Return record-retention due day under a supplied hold rule.

Biosecurity administration records training assertions, custody, access purposes, inventories and document handling. Local counts, time checks and permission predicates describe supplied metadata; they do not authenticate people or items, enforce access or establish actual protective conditions.

Return record-retention due day under a supplied hold rule.

When to use this tool

Use Biosecurity Audit Record Retention Window when checking the stated benign biosecurity record, inventory, support or authorization convention.

How to use the tool and how it works

  1. Enter createdDay, observationDay, retentionDays, hold, removed. 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 dueDay, remainingDays, dueUnderRule, retainedBeyondRule. Inspect dueUnderRule, retainedBeyondRule before interpreting the associated values.

Return record-retention due day under a supplied hold rule. Require nonnegative whole retentionDays and observation >= created; dueDay = created+retention, dueUnderRule means observation >= due and not hold, retainedBeyondRule additionally requires not removed.1

Input fieldMeaning and unitsAccepted input
createdDayCreated DayRequired. Safe integer.
observationDayObservation DayRequired. Safe integer.
retentionDaysRetention DaysRequired. Safe integer; minimum 0.
holdHoldRequired. Boolean.
removedRemovedRequired. Boolean.
Output fieldInterpretationReturned shape
dueDayDue DayRequired. Safe integer.
remainingDaysRemaining DaysRequired. Safe integer.
dueUnderRuleLocal retention-rule predicate; the tool performs no deletion.Required. Boolean.
retainedBeyondRuleRetained Beyond RuleRequired. Boolean.
json
{
  "input": {
    "createdDay": 100,
    "observationDay": 140,
    "retentionDays": 30,
    "hold": false,
    "removed": false
  },
  "output": {
    "dueDay": 130,
    "remainingDays": -10,
    "dueUnderRule": true,
    "retainedBeyondRule": true
  }
}

Limitations and assumptions

  • No record is removed; the rule and hold are assertions rather than legal retention, deletion or privacy advice.
  • 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

Verify actual records, permissions and conditions through the responsible organization's procedures; use qualified risk assessment and appropriate professional oversight for practical decisions.

References

  1. Calculation and input contract: biosecurity/biosecurity-audit-record-retention-window — tool.io

Similar or alternative tools