Description
Measure a supplied delivery delay relative to a promised timestamp.
Consumer records distinguish events, choices, prices, quantities and supplied survey scales. A unit-price comparison requires comparable goods and quantity units, while a reversed score retains the original scale bounds. An observed time gap or selected option does not establish motivation, causation, consent or the fairness of a commercial practice.
Measure a supplied delivery delay relative to a promised timestamp.
When to use this tool
Use Delivery Promise Delay Value when you already have promisedTimestampSeconds, deliveredTimestampSeconds and need to measure a supplied delivery delay relative to a promised timestamp.
How to use the tool and how it works
- Enter promisedTimestampSeconds, deliveredTimestampSeconds. Use the units and conventions below.
- Run the tool. Correct any format, range, or cross-field input error before interpreting the output.
- Read delaySeconds, late. Inspect late before interpreting the associated values.
Return delivered-promised seconds and late=delivered>promised.1
| Input field | Meaning and units | Accepted input |
|---|---|---|
| promisedTimestampSeconds | Promised Timestamp Seconds | Required. Finite number. |
| deliveredTimestampSeconds | Delivered Timestamp Seconds | Required. Finite number. |
| Output field | Interpretation | Returned shape |
|---|---|---|
| delaySeconds | Delay Seconds | Required. Finite number. |
| late | True strictly after the promised timestamp; equality is not late. | Required. Boolean. |
{
"input": {
"promisedTimestampSeconds": 1000,
"deliveredTimestampSeconds": 1120
},
"output": {
"delaySeconds": 120,
"late": true
}
} Limitations and assumptions
- Equality is not late and early deliveries give negative delays. Matching clocks are assumed; no transaction, legal promise or service quality is 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
Review the original transaction, interface, survey and event records for a behavioral conclusion. Use the complete study design and applicable commercial terms when interpreting comparisons; local flags and ratios do not estimate demand or verify an actual customer experience.
References
Similar or alternative tools
- Subscription Renewal Notice Window Gap
Measure a subscription renewal date's signed gap from a supplied notice date.
- Product Trial To Repeat Gap
Measure nonnegative calendar days between a supplied product trial and repeat purchase.