Description
Subtract local-minus-UTC offsets from both local numeric times, then return UTC coordinates, receive-minus-release duration and nondecreasing order flag.
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.
Subtract local-minus-UTC offsets from both local numeric times, then return UTC coordinates, receive-minus-release duration and nondecreasing order flag.
When to use this tool
Use Chain Of Custody Timezone Order Check when you need a supplied clock-offset or custody-time comparison.
How to use the tool and how it works
- Enter releaseLocalSeconds, receiveLocalSeconds, releaseUtcOffsetSeconds, receiveUtcOffsetSeconds. Use the units and conventions below.
- Run the tool. Correct any format, range, or cross-field input error before interpreting the output.
- Read releaseUtcSeconds, receiveUtcSeconds, transitSeconds, ordered. Inspect ordered before interpreting the associated values.
Subtract local-minus-UTC offsets from both local numeric times, then return UTC coordinates, receive-minus-release duration and nondecreasing order flag.1
| Input field | Meaning and units | Accepted input |
|---|---|---|
| releaseLocalSeconds | Release Local Seconds | Required. Finite number. |
| receiveLocalSeconds | Receive Local Seconds | Required. Finite number. |
| releaseUtcOffsetSeconds | Local-minus-UTC offset in seconds at release. | Required. Finite number. |
| receiveUtcOffsetSeconds | Local-minus-UTC offset in seconds at receipt. | Required. Finite number. |
| Output field | Interpretation | Returned shape |
|---|---|---|
| releaseUtcSeconds | Release Utc Seconds | Required. Finite number. |
| receiveUtcSeconds | Receive Utc Seconds | Required. Finite number. |
| transitSeconds | Transit Seconds | Required. Finite number. |
| ordered | Ordered | Required. Boolean. |
{
"input": {
"releaseLocalSeconds": 10000,
"receiveLocalSeconds": 11000,
"releaseUtcOffsetSeconds": 3600,
"receiveUtcOffsetSeconds": 3600
},
"output": {
"releaseUtcSeconds": 6400,
"receiveUtcSeconds": 7400,
"transitSeconds": 1000,
"ordered": true
}
}Limitations and assumptions
- Inputs use seconds with a common numeric origin. Named zones, dates and daylight-saving transitions are not parsed, and order alone does not establish custody integrity.
- 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
Similar or alternative tools
- Custody Clock Offset Gap
Return receivedAt minus receivedClockOffset minus releasedAt plus releasedClockOffset.
- Evidence Package Seal Share Tool
Count literal package/seal verification records; no chain-of-custody adequacy finding.