Find the current window
Record when the existing request actually started and what duration is included. The planned stream start may not equal the package start. Use the service’s stated timing basis rather than calculating the end from an unrelated announcement time.
Ask how extensions work
Check whether the listing supports an extension, a new order or another process. Clarify whether the additional period can overlap and whether concurrency is allowed. Do not submit a second request with an assumed start time that the service has not accepted.
Keep periods itemized
Save separate references, charges and intended windows when more than one request is used. This makes it easier to identify a gap or overlap later. Review the stream’s remaining duration before purchasing additional time.
Decision checklist
| Decision | What to check |
|---|---|
| Current period | Actual start and included duration |
| Extension rule | Supported method and overlap conditions |
| Record | Separate references and intended windows |
Worked example
Suppose an illustrative package starts fifteen minutes after the broadcast begins. An extension calculated from the broadcast clock could overlap or leave a gap; the buyer should use the confirmed package window and supported extension process.
Example figures explain the decision; they are not current prices or promised results.