Prove who can hear and answer each production call

Translate roles into specific conversations

List the conversations required for the production rather than starting with a list of available buttons. Identify who must address the whole team, who needs a focused working conversation and who needs a direct reply. State whether a recipient merely listens or must acknowledge. Keep the event’s authority structure in the run of show; this artifact tests whether its ordinary communication paths actually work.

Bind each role to the endpoint assigned for rehearsal and performance. A label such as camera operator is insufficient when several people use that role on different stations. Include substitute staff and shared positions where relevant. Document which conversations should not be audible at unrelated endpoints. Avoid using sensitive information as a test message, even when a route is described as private.

Separate hearing a call from reaching the caller

Clear-Com’s Arcadia workflow documentation distinguishes shared channels, one-to-one directs and group announcements whose replies become private. Those named workflows illustrate why an announcement and its reply need separate acceptance; other systems may implement them differently.

Use a short, neutral test exchange for each required relationship. Have the intended recipient identify the originating role and return an acknowledgement through the expected route. Ask other participating endpoints whether the exchange reached them when it should, or when it should not. Record one-way success separately from two-way success. Do not mark a team complete because one confident person answered on behalf of everyone without checking the remaining endpoints.

Test the role change that can break a working route

Include realistic substitutions, such as a relief operator taking over a station or a working group returning to the shared production conversation. Have the communications owner establish the intended configuration and observe what users can actually hear and answer. Check labels against behavior rather than assuming a renamed key or copied role inherited the correct assignment.

For each failure, preserve the direction of the problem. A missing outbound call, missing reply and unintended listener are different defects. Give the technician the originating endpoint, selected conversation and observed recipients. Avoid random button pressing during a live session or borrowing an unrelated channel as an undocumented workaround. Where a temporary alternate route is approved, test it and state who must use it, without presenting it as a replacement for venue emergency procedures.

Handover a usable communication map

Give each operator only the role instructions necessary to participate, supported by the full acceptance matrix retained by the production lead. The map should explain how to reach the intended team and how to acknowledge, without becoming a copied technical manual. Record outstanding gaps with their operational consequence: a delayed camera acknowledgement is more actionable than “intercom issue.”

Retest affected relationships after endpoint replacement, role reassignment or a routing change. Keep the last accepted configuration identifiable so a late change does not erase the evidence from rehearsal. During the event, report communication failures through the agreed alternate method and let the authorized owner manage corrections. The acceptance record establishes tested production paths, not guaranteed availability, confidentiality or suitability for safety-critical instructions.

Make the reasoning concrete.

A fictional conference has a stage team and three camera operators. Everyone hears a production announcement, but a replacement camera operator’s acknowledgement reaches only another camera position.

The production lead chooses the two-direction check and records the replacement station in the accepted map.

Take the questions into your next brief.

Use these prompts in your own notes. Nothing is submitted from this page.

1. Conversation

   Who must speak to whom, and for what production purpose?

2. Endpoint

   Which actual station is assigned to each role?

3. Reply

   Where should each acknowledgement arrive?

4. Isolation

   Which participating endpoints should not hear the exchange?

5. Change

   What replacement or reassignment invalidates the check?

Watch for the wrong conclusion.

• Equating a heard announcement with a functioning reply.
• Testing a role name without the assigned endpoint.
• Treating a production intercom check as emergency-system certification.

Sources & scope

Workflows, worksheets and fictional examples are original editorial analysis. Sources support only specifically attributed principles. Platform guidance can change; legal requirements depend on jurisdiction and context. No measured results or named human reviewer are claimed.

• Clear-Com Arcadia: Workflows →Primary product documentation, updated 4 March 2026 · Supports: Supports the named Arcadia distinctions between channels, directs and group replies. The acceptance workflow is original editorial analysis.