A recurring broadcast team receives very different kinds of requests. A title correction for next month, a guest preparation question and a problem during a live programme should not travel through one undifferentiated promise of “support”. Define the request categories and response arrangements that the series actually needs.
This is a scope discussion, not an assumption that every producer offers continuous cover. Ask what support is available, during which agreed windows and through which route. Record the specific arrangement without turning a preferred response time into an unsupported guarantee.
Describe urgency through the affected event
A useful request states the episode, the activity currently blocked and the next decision time. “Urgent” alone does not explain whether a live audience is affected or whether a planner would simply like a quick answer. Give organisers language that helps the receiving person distinguish those situations.
Keep a live operating route for the named event team, where agreed. Routine preparation messages should not interrupt that route unless they concern the programme currently being delivered. Conversely, an on-air problem should not depend on someone discovering a message in a general planning thread.
Clarify who decides when urgency is disputed. The person raising the request may not know its production effect. A designated operational owner can assess the situation and direct it appropriately, while the business owner retains authority over programme priorities.
Make availability visible
Support categories are useful only if someone is assigned to them. Identify the agreed live window, the ordinary preparation contact and the fallback communication route if a message is not acknowledged. Do not invent an escalation ladder that names people who have never accepted the responsibility.
Consider the buyer's side too. A producer may ask an urgent question because a client decision is needed. The arrangement should show who can answer during live delivery and who handles ordinary preparation. Otherwise the support expectation runs in only one direction.
Include enough episode context when escalating a request that the receiver need not search several planning threads. A concise statement of the affected action and its decision deadline is more useful than forwarding a long conversation with no explanation of what is now required or who has already authorised it.
A hypothetical support distinction
A customer broadcast programme uses the same team for monthly episodes. During one live event, a different department sends a message marked urgent requesting a new title for an episode several weeks away. The agreed process routes that request to the preparation queue, leaving the live contact focused on the current programme. Later, a guest readiness issue is escalated with the affected episode and immediate decision clearly stated, so the team can assess it without guessing.
Test the routes with realistic requests
Try a few scenarios: a future scope question, a near-term approval gap and a live interruption report. Ask the organiser to select the route and describe the information to include. Acceptance means each request reaches an appropriate available owner with its actual urgency understood. Review misrouted requests after the series begins, improving the categories rather than encouraging everyone to label ordinary work as an emergency.
Discuss suitability
Contact Live Images to discuss the proposed broadcast, audience and delivery requirements. Confirm suitability, scope and availability for the specific brief.
Editorial note
Original commissioning guidance prepared with AI assistance. Hypothetical examples are invented, not Live Images projects. This unpublished resource makes no service, legal or performance guarantee.