Define what the device must contribute
Client laptops, tablets, cameras and demonstration computers can be integrated when the intended connection and operating requirements are compatible with the event system. Start with the job: sending a picture, supplying sound, receiving touch input or running an interactive application. Those jobs may require different connections, even when one device performs several of them.
Agree a handover point between the client and AV supplier. For example, the client may provide a tested HDMI output at the presentation desk while the supplier provides the onward route to the screens and sound system. Write down who supplies and checks the adapter that creates that output; leaving it between scopes is a common source of uncertainty.
Prepare a device integration sheet
| Field | What to provide | Why it changes planning |
|---|---|---|
| Device identity | Exact model, operating system and relevant application version | Output and software support vary within product families |
| Purpose | Slides, video, live camera, demonstration, touch or another task | Defines the required picture, sound and control paths |
| Connection | Intended port, adapter or dock model, and proposed destination | Connector appearance does not prove capability |
| Output requirement | Picture dimensions, frame rate, audio and number of distinct displays | Allows the team to check the complete configuration |
| Dependencies | Required accounts, network access, peripherals and permissions | Prevents a working local demonstration from failing after transfer |
| Operation | Named owner, control method, arrival time and fallback | Makes rehearsal and source changes manageable |
Check the port's function, not just its shape
USB-C is a connector description. VESA's support page explains that a selected USB-C port may not support the DisplayPort function expected by a display or accessory. Confirm the exact device port and the adapter or dock specification. A cable used successfully for charging does not establish the required video capability.
For multiple external pictures, check the actual computer limits and configuration. Apple states that simultaneous display support depends on the Mac model and each display's resolution and refresh rate. A dock with several sockets does not by itself prove the proposed computer can create all the independent pictures in the brief.
Also separate picture from control. If a client computer will drive a rented touch display, ask the team to identify the touch-data connection and application support as well as the video connection. Test the intended interaction with the real computer. A correct picture alone does not confirm a working touch demonstration.
Hypothetical example: a corporate laptop and a product demo
Suppose a presenter must use a company-managed laptop for a live product demonstration. The AV brief initially says “USB-C laptop”. Before rehearsal, the organiser obtains the exact model, a photo identifying the intended port, the dock model and confirmation that the application must use the corporate account.
The technical team agrees a compatible picture and audio handover. The device owner confirms network and account access with their IT team, and brings the authorised method of signing in. The rehearsal then tests the real application, the full audience output and the speaker's control arrangement. A local sample slide is insufficient because it does not exercise the application's dependencies.
If the demonstration cannot be made ready, the organiser and presenter agree a prepared recording or another approved fallback. That content must be tested too. Changing to an unapproved account or disabling company protections is not part of an AV connection plan.
Rehearse the changeover
Test what the audience sees when the device is connected, selected, disconnected and replaced by the next source. Confirm which screen carries the audience picture and which shows private notes or controls. Ask the owner to manage notifications and unnecessary personal material for the presentation, within the device's permitted settings.
For a camera, test the intended output and whether the required picture is free of unwanted interface overlays. For a tablet, verify the specific application's external-display behaviour rather than assume it mirrors every screen in the same way. Keep the scope limited to the actual models that have been checked.
Close the responsibility gaps
The device owner supplies the working device, authorised application access and agreed source content.
The named supplier provides the specified adapters, onward video and audio route, or clearly records any client-supplied items.
The organiser reserves enough rehearsal time and ensures the correct owner attends.
The team records the tested configuration and identifies changes that require another check.
The operator and presenter know when to use the agreed fallback.
Share the integration sheet with technical support before finalising control computers and supporting equipment. The aim is a defined, rehearsed interface between two responsibilities, with every required function accounted for.
Further reading
VESA's USB-C DisplayPort help and Apple's external-display guidance illustrate why exact port and model information matters.