State date and timezone together
Write the complete broadcast date, local timezone and intended session window. Avoid a bare numeric offset if the team cannot confirm whether that offset applies on the actual event date.
Separate operational milestones
List the planned broadcast start, order-submission checkpoint and useful campaign segment individually. These are related events but should not be collapsed into one time that different team members interpret differently.
Confirm last-minute changes
Assign one owner to circulate schedule revisions and verify acknowledgement. A changed calendar entry should not be assumed to update a service order already submitted or a provider process that lacks documented scheduling support.
Decision checklist
| Decision | What to check |
|---|---|
| Time | Explicit date and named timezone |
| Milestones | Broadcast, submission and key segment |
| Changes | One owner confirms revised schedule |
Worked example
Hypothetically, a Cairo host and a London operator agree on a dated schedule written in Africa/Cairo time. The operator converts it for that date and confirms the submission checkpoint. Neither person relies on an undated instruction saying 8 p.m. tonight.
Example figures explain the decision; they are not current prices or promised results.