Description
Count skipped integers between increasing supplied delivery tickets.
Construction records combine revisions, dates, dimensions, rental periods, claims and financial balances. Revision numbers need not be consecutive, calendar offsets differ from business days, and recoverable length can depend on a strict cutoff. A supplied approval or readiness label is a record assertion rather than an engineering inspection or contractual determination.
Count skipped integers between increasing supplied delivery tickets.
When to use this tool
Use Slab Pour Ticket Sequence Gap when you already have previousTicket, currentTicket and need to count skipped integers between increasing supplied delivery tickets.
How to use the tool and how it works
- Enter previousTicket, currentTicket. Use the units and conventions below.
- Run the tool. Correct any format, range, or cross-field input error before interpreting the output.
- Read missingBetween. Use the output convention below.
Require nonnegative safe previousTicket and safe currentTicket at least previous+1; return current-previous-1.1
| Input field | Meaning and units | Accepted input |
|---|---|---|
| previousTicket | Previous Ticket | Required. Safe integer; minimum 0. |
| currentTicket | Safe integer strictly greater than previousTicket; gaps need not be one. | Required. Safe integer. |
| Output field | Interpretation | Returned shape |
|---|---|---|
| missingBetween | currentTicket-previousTicket-1, excluding both observed tickets. | Required. Safe integer. |
{
"input": {
"previousTicket": 17,
"currentTicket": 21
},
"output": {
"missingBetween": 3
}
}Limitations and assumptions
- Consecutive tickets give zero. No missing delivery, sequence ownership, concrete quality or actual record is inferred; a maximum-safe previous ticket leaves no valid successor.
- 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
Check controlled drawings, site measurements, schedules, approvals and the complete contract. Use the appropriate engineering assessment and actual billing or claim terms when a local scalar calculation or date comparison cannot establish suitability or entitlement.
References
Similar or alternative tools
- Subcontract Payment Certification Lag
Measure a payment certification date's signed gap from submission.
- Site Punch Item Age Day Count
Count calendar days since a supplied punch-item raised date.