Skip to content

Main content

Custody Clock Offset Gap Tool

Compare deidentified custody event clocks under explicit offsets without asserting chain-of-custody validity.

Loading tool…

Description

Return receivedAt minus receivedClockOffset minus releasedAt plus releasedClockOffset.

Custody timestamps may use different local offsets or clocks. Correcting them into one numeric reference enables an order check, but consistent chronology alone cannot establish who held evidence or whether its condition was preserved.

Return receivedAt minus receivedClockOffset minus releasedAt plus releasedClockOffset.

When to use this tool

Use Custody Clock Offset Gap when you need a supplied clock-offset or custody-time comparison.

How to use the tool and how it works

  1. Enter receivedAt, releasedAt, receivedClockOffset, releasedClockOffset. 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 correctedGap. Use the output convention below.

Return receivedAt minus receivedClockOffset minus releasedAt plus releasedClockOffset.1

Input fieldMeaning and unitsAccepted input
receivedAtReceived AtRequired. Finite number.
releasedAtReleased AtRequired. Finite number.
receivedClockOffsetReceived Clock OffsetRequired. Finite number.
releasedClockOffsetReleased Clock OffsetRequired. Finite number.
Output fieldInterpretationReturned shape
correctedGapCorrected GapRequired. Finite number.
json
{
  "input": {
    "receivedAt": 20,
    "releasedAt": 10,
    "receivedClockOffset": 3,
    "releasedClockOffset": 1
  },
  "output": {
    "correctedGap": 8
  }
}

Limitations and assumptions

  • Offsets follow recorded-minus-reference convention and all quantities share time units. A signed gap is retained without authenticating handover or clocks.
  • 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 original timestamps, offset conventions and documented handovers. Use a complete custody review rather than treating a nonnegative interval as proof of evidence integrity.

References

  1. Calculation and input contract: forensic-science/custody-clock-offset-gap — tool.io

Similar or alternative tools