Find the current coverage boundary
Record the original package's stated duration and how its start is defined. The broadcast start, submission time and service start may differ, so use the definition attached to the selected listing.
Use the supported extension method
Ask whether an extension belongs to the existing order or requires a new request. Do not assume that placing another identical order queues it after the first; it could be treated as a separate concurrent request.
Confirm the revised total
Add the extra charge and intended time to the campaign record. Tell the host what is actually covered, and avoid presenting a requested extension as confirmed until the order system or support records it.
Decision checklist
| Decision | What to check |
|---|---|
| Boundary | Defined start and duration of package |
| Method | Continuation or separate new request |
| Overlap | Whether coverage periods run together |
Worked example
Hypothetically, a stream runs thirty minutes longer than planned. Before buying another thirty-minute package, the operator asks when that request would start. Two packages running simultaneously for thirty minutes would not provide the intended sequential one-hour coverage.
Example figures explain the decision; they are not current prices or promised results.