Room control: conditions, schedules, and diagnostics
Conceptual AV coordination diagram; it does not represent a completed installation or construction drawing.

Intended use: ____________________

Affected zone and destinations: ____________________

Known devices and versions: ____________________

Expected / observed / unavailable state: ____________________

Who retains control: ____________________

Documented manual alternative: ____________________

Open question and next step: ____________________

Motorized screen or shade: identify requirements first
Condition for proceeding: obtain documentation for the installed variant and validation from the installation lead before defining movement actions.
____________________

Occupancy and shutdown: preserve the active meeting
Proposed criterion: lack of detection alone should not interrupt a meeting the user keeps active; verifying the logic requires a later authorized test.
____________________

Schedules and calendars: a booking does not confirm AV state
Document example: a booking ends at 6:00 PM and is extended to 6:30 PM. Who confirms closing, and what should the panel show meanwhile?
____________________

A scene completes only partly: record each destination
Diagnostic question: is evidence missing for sending, destination availability, or the result? Keeping those distinct avoids assigning a cause too early.
____________________

The panel works, but one device does not respond
Useful next step: “responds during use, unresponsive in standby,” or the actual observed pattern, is more precise than “will not connect.”
____________________

Synthetic record example, not a completed test
Destination	Command sent	Availability	Observed result
Main display	No send record	Image visible	Expected source visible
Table audio	No send record	To be confirmed	No change observed
Ambient light	No send record	No feedback	State unconfirmed