Skip to content

Main content

Biosecurity Document Owner Approval Window Tool

Audit supplied document owner/approval timing fields.

Loading tool…

Description

Compare a document owner and approval window.

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.

Compare a document owner and approval window.

When to use this tool

Use Biosecurity Document Owner Approval Window when checking the stated benign biosecurity record, inventory, support or authorization convention.

How to use the tool and how it works

  1. Enter owner, approvedOwner, approved, approvalDay, expiryDay, eventDay. 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 ownerMatches, timeMatches, matches. Inspect ownerMatches, timeMatches, matches before interpreting the associated values.

Compare a document owner and approval window. Require expiryDay >= approvalDay; ownerMatches uses literal equality, timeMatches includes both endpoints, matches also requires approved true.1

Input fieldMeaning and unitsAccepted input
ownerOwnerRequired. Text; maximum UTF-16 length 8192.
approvedOwnerApproved OwnerRequired. Text; maximum UTF-16 length 8192.
approvedApprovedRequired. Boolean.
approvalDayApproval DayRequired. Safe integer.
expiryDayExpiry DayRequired. Safe integer.
eventDayEvent DayRequired. Safe integer.
Output fieldInterpretationReturned shape
ownerMatchesOwner MatchesRequired. Boolean.
timeMatchesTime MatchesRequired. Boolean.
matchesMatchesRequired. Boolean.
json
{
  "input": {
    "owner": "A",
    "approvedOwner": "A",
    "approved": true,
    "approvalDay": 100,
    "expiryDay": 120,
    "eventDay": 110
  },
  "output": {
    "ownerMatches": true,
    "timeMatches": true,
    "matches": true
  }
}

Limitations and assumptions

  • A matching record does not authenticate approval, identity, appropriate document scope or actual legal authority.
  • 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-document-owner-approval-window — tool.io

Similar or alternative tools