// INSIGHTS
Running an on-site event IT helpdesk that holds
6 min read
An event IT desk is not a service desk with a nicer backdrop. There is no next business day. A speaker whose laptop will not hand over to the switcher has four minutes, not four hours. The work is inventory, radios, ratios and a runbook written before anyone lands in the city. We staff these desks in India and the UAE, and the difference between a calm show and a bad one is almost always decided in the two weeks before load-in.
Desk anatomy
A working desk has three physical positions and one roving pair. Position one is the walk-up counter, sited where delegates already queue, usually beside registration. Position two is the speaker-ready room, which is a separate discipline and should never be merged with the walk-up desk. Position three is the technical bench behind the counter with tools, spares and a printer, out of delegate sightline.
The roving pair carries a kit bag and covers session rooms, exhibitor stands and kiosk faults. They are the only people authorised to touch anything cabled to a switcher during a live session, and they work in pairs so that one person can hold a radio while the other has both hands on a connector.
For a 2,000-delegate conference with six breakout rooms and forty exhibitor stands, that is typically six to eight people per show day. Fewer than six and the walk-up queue starves the roving pair. More than ten and you are paying for people who cannot get to a fault faster than the ones already there.
Desk numbers we plan around
Staffing the floor
Two overlapping shifts
A 14-hour day runs 06:00 to 16:00 and 12:00 to 22:00 with a four-hour overlap across the busiest block. Single-shift coverage produces mistakes after hour nine, reliably.
Radio for live, chat for context
Anything time-critical goes on a dedicated radio channel separate from production and security. WhatsApp groups are for photos of faulty cables and handover notes, never for a room-down call.
Three triage tiers
Tier one is anything blocking a live session or a queue, targeted at three minutes to a person on site. Tier two is delegate device help at fifteen minutes. Tier three is everything logged and handled between sessions.
A named escalation path
Every tier one has one named engineer and one named client-side decision maker on the sheet. Escalation without a name attached to it is just shouting into a radio.
Cutover sequence
Write the runbook two weeks out
Room-by-room kit list, IP plan, SSIDs, radio channels, contact tree, and a one-page failure card per room. It gets printed, because a runbook that only exists on a cloud drive fails at the same moment everything else does.
Set the upload deadline and enforce it
Presentations due at the speaker-ready room by 18:00 the previous evening, or two hours before the session for same-day arrivals. Late decks get accepted, but on a separate queue with a stated risk.
Rehearse the laptop-to-switcher handover
Every speaker who insists on their own machine does a two-minute test at the ready room with the exact adapter and resolution they will use in the hall. Most failures are USB-C dongles and scaling, both of which surface in that test.
Stage the spares crate
HDMI and USB-C in three lengths, display adapters for every port in circulation, chargers, AA and camera batteries, two spare laptops imaged and logged in, two spare access points, a spare badge printer with ribbons, and clickers.
What usually goes wrong
Badge reprints. Nobody budgets for them and they consume more desk time than any other single task. Name spellings, job title changes, walk-in upgrades and printers jamming in dusty halls all land at the same counter. On a 2,000-delegate event we plan for four to seven percent reprints on day one and staff a dedicated reprint position for the first three hours, otherwise the queue for a reprinted badge blocks the queue for an actual fault.
The second recurring problem is environmental. Outdoor and tented venues in a 45C summer will thermally throttle laptops and shorten access point life. Monsoon humidity gets into connectors. Dust kills printer feed rollers within a single show. In UAE venues the climate is managed but the in-house ISP is often a monopoly with a day rate that can exceed the entire IT staffing line, and it needs to be priced in at proposal stage rather than discovered at load-in. In India the equivalent surprise is a last-mile fibre order that was promised in ten days and arrives after the show, which is exactly why we carry bonded backup uplinks on multiple carriers and never treat a single venue circuit as the plan.
Common questions
Can the venue's in-house AV team cover IT support?
They cover the rooms they are contracted for, which is usually the stage, the projection and the audio. They do not own registration hardware, kiosks, signage players, badge printers or delegate device support. Those are the things that generate most of the tickets, so they need a separate desk with its own staffing.
What response time should we actually write into a scope?
Three minutes on site for anything blocking a live session or a queue, fifteen minutes for delegate device issues, and same-session resolution or a documented workaround for everything else. Those are achievable with correct ratios and a stocked spares crate. Committing to tighter numbers without both is dishonest.
How much does an on-site IT team cost per day in India?
A six to eight person team for a mid-size conference typically runs INR 2.5 to 6 lakh per show day, depending on city, seniority mix and whether network engineering is included. Load-in and rehearsal days are usually charged at a reduced rate. Equipment, connectivity and spares are quoted separately.
Put a desk on your floor before the queue forms
Send us your floor plan, delegate count and show dates and we will return a staffing plan with a runbook outline.
