Rundown Backtime from Air Calculator

Backtime actual ordered rundown durations from caller fixed UTC hard out, retaining per-item start/end across midnight; contiguous whole-second schedule, no inferred breaks, live variability or broad package-runtime duplicate.

Description

Backtiming derives a contiguous rundown from its fixed hard-out.

Backtiming derives a contiguous rundown from its fixed hard-out. Midnight crossings require complete UTC dates.^[1]

Enter whole-second UTC hard-out1900–2199, aligned nonempty unique item IDs and integer durations0–86400 seconds. Preserve order and return each UTC start/end and total; resulting dates must remain in supported range.

When to use Rundown Backtime from Air Calculator

Use Rundown Backtime from Air Calculator when you need to evaluate the supplied records under the calculation and evidence rules below. No breaks, variability or omitted items are inferred.

Prepare the actual editorial, source, layout, timing or audience records requested. Supply explicit house-policy limits and preserve missing evidence.

How to use Rundown Backtime from Air Calculator and understand its results

Prepare the actual editorial, source, layout, timing or audience records requested. Supply explicit house-policy limits and preserve missing evidence.
Enter hardOutUtc, rundownItemIds, itemDurationSeconds using the field table and calculation rules, then run the tool.
Read backtimedItemStartUtc, backtimedItemEndUtc, totalScheduledSeconds. The explanation below defines the units, signs, ordering and any flags or placeholder values.
If the tool reports an input issue, correct the values and run it again. Apply the stated assumptions when interpreting a successfully returned result.

Input field	Meaning	Value type; see rules below	Requirement
hardOutUtc	Hard out utc	string	Required
rundownItemIds	Rundown item ids	list of string	Required
itemDurationSeconds	Item duration seconds	list of number	Required

firstStart=hardOut−sum(durations); each end=start+duration

Units, indexing, boundary conditions and exceptional cases are defined in the calculation rules above.

Output field	Meaning	Value type
backtimedItemStartUtc	Backtimed item start utc	list of string
backtimedItemEndUtc	Backtimed item end utc	list of string
totalScheduledSeconds	Total scheduled seconds	number

json

{
  "input": {
    "hardOutUtc": "2025-01-01T12:00:00Z",
    "rundownItemIds": [
      "A",
      "B"
    ],
    "itemDurationSeconds": [
      30,
      60
    ]
  },
  "output": {
    "backtimedItemStartUtc": [
      "2025-01-01T11:58:30Z",
      "2025-01-01T11:59:00Z"
    ],
    "backtimedItemEndUtc": [
      "2025-01-01T11:59:00Z",
      "2025-01-01T12:00:00Z"
    ],
    "totalScheduledSeconds": 90
  }
}

Limitations and assumptions

No breaks, variability or omitted items are inferred.

Numeric inputs, where present, must be finite. Follow the calculation-specific rules for overflow, underflow and exceptional cases. Numeric lists are limited to 10,000 entries; string lists to 128 strings of at most 128 characters each. The rules above may impose smaller limits. Extremely large text inputs are rejected. Missing required fields, extra fields, wrong value types and violations of the calculation rules are input errors.

Alternative or Complementary methods

Use Sign Off Hard Out Countdown Seconds Calculator: Hard-out planning compares remaining wall-clock time with estimated sign-off duration. Negative slack remains useful evidence. For a complementary task, use Folio Deadline Section Pagination Order Lookup: Section deadlines and folio collisions are separate production concerns. Deadline sorting should preserve ties and original-index collision witnesses.

References

Rundown Backtime from Air Calculator — tool.io

Similar or alternative tools

Sign Off Hard Out Countdown Seconds Calculator
Hard-out planning compares remaining wall-clock time with estimated sign-off duration. Negative slack remains useful evidence.
Folio Deadline Section Pagination Order Lookup
Section deadlines and folio collisions are separate production concerns. Deadline sorting should preserve ties and original-index collision witnesses.