Identify the agreed trigger
Read whether the request begins at submission, at an agreed time or after the broadcast is available. A time written in a notes field is not necessarily a supported scheduling feature. Ask for clarification before relying on advance preparation.
Communicate the change precisely
Record the original schedule, revised schedule and time zone. If a request is already active, provide its reference when asking about the delay. Do not assume the included duration automatically moves with the creator’s updated announcement.
Review the remaining usefulness
If the revised broadcast no longer fits the service conditions, ask about the available treatment before placing another request. Keep the first request’s status and any charge adjustment in the record. A replacement should be a deliberate decision, not an automatic duplicate.
Decision checklist
| Decision | What to check |
|---|---|
| Trigger | What starts the request or duration |
| Schedule | Old and new times in one zone |
| Resolution | Handling of an already active request |
Worked example
Suppose an illustrative stream moves from 19:00 to 20:30. The buyer should confirm how the selected offer handles that change before assuming a one-hour package remains unused until the later broadcast begins.
Example figures explain the decision; they are not current prices or promised results.