Skip to content

Main content

Biosecurity Benign Delivery Receipt Count Gap Tool

Reconcile supplied benign delivery counts without sensitive inventory content.

Loading tool…

Description

Return delivery in-transit and usable-received counts.

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 delivery in-transit and usable-received counts.

When to use this tool

Use Biosecurity Benign Delivery Receipt Count Gap when checking the stated benign biosecurity record, inventory, support or authorization convention.

How to use the tool and how it works

  1. Enter dispatched, received, returned, damagedReceived. 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 inTransit, usableReceived, receivedShare. Use the output convention below.

Return delivery in-transit and usable-received counts. Require whole dispatched >= 1, received/returned within dispatch and damagedReceived <= received; inTransit = dispatched-received-returned, usableReceived = received-damaged, receivedShare = received/dispatched.1

Input fieldMeaning and unitsAccepted input
dispatchedDispatchedRequired. Safe integer; minimum 1.
receivedReceivedRequired. Safe integer; minimum 0.
returnedReturnedRequired. Safe integer; minimum 0.
damagedReceivedDamaged ReceivedRequired. Safe integer; minimum 0.
Output fieldInterpretationReturned shape
inTransitIn TransitRequired. Safe integer.
usableReceivedUsable ReceivedRequired. Safe integer.
receivedShareReceived Share Unit: 1.Required. Finite number.
json
{
  "input": {
    "dispatched": 100,
    "received": 80,
    "returned": 5,
    "damagedReceived": 3
  },
  "output": {
    "inTransit": 15,
    "usableReceived": 77,
    "receivedShare": 0.8
  }
}

Limitations and assumptions

  • Usability is only a supplied damage-count subtraction; custody, actual item condition, identity and safe delivery are not 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

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-benign-delivery-receipt-count-gap — tool.io

Similar or alternative tools