What 'Hypercare' Means When a New Studio Goes on Air

Hypercare is a trade term for the period straight after a studio, gallery or workflow goes live, when extra technical cover is kept in place rather than withdrawn at handover. Nothing about it is exotic. It simply recognises that a system which passed every test on the bench behaves differently once real presenters, real deadlines and a real audience are involved.

I come at this as an acoustics engineer, so I tend to hear the problems before I see them. A room that measured well empty can sound different once a full crew, a monitor wall and a studio audience of guests are in it. Hypercare is the agreed window in which somebody who knows the installation stands close by and deals with what turns up.

The term borrows from other industries, but in television it has a practical meaning: named people, a known length of time and a clear way to reach them.

A studio is tested in pieces: cameras, routing, intercom, lighting, room treatment. Live use tests all of them at once, under time pressure, with people who are still learning where everything is. Small faults that never showed up in testing tend to surface in the first few programmes.

Typical examples are an intercom channel that was patched but never assigned to the right position, a talkback level that suits an engineer but drowns out a presenter's earpiece, or a lighting preset that looks right on a monitor but flares on a particular camera. None of these is a design failure. They are the normal friction of a new system meeting a new crew.

Having support in the building means such faults are fixed in minutes and noted for the record, instead of becoming a reason for a producer to lose confidence in a room that is actually sound.

• Unassigned or mislabelled intercom channels
• Monitoring levels that suit the gallery, not the floor
• Presets that need adjusting once real guests sit down

On-site support during broadcasts means an engineer attends the programme, usually from the first rehearsal through to the end of transmission. They are not there to operate the show. The crew does that. They are there for the technical layer underneath it: watching signal paths, listening to the programme feed, and being ready if a device misbehaves.

The scope is agreed beforehand and written down: which programmes are covered, which hours, and who the engineer reports to. We keep a log of every fault and every adjustment, however small, so that patterns become visible. If the same fault appears twice, it is treated as a cause to remove, not an incident to repeat.

This is also where a clear fallback procedure earns its keep. Everyone on the floor should know what happens if a camera or a microphone fails, before it does.

Training for in-house crews is the other half of the picture. We run it in the studio the crew will actually use, on the desks and cameras they will actually operate, because a classroom explanation of a vision mixer rarely survives contact with the real panel.

Sessions are short and practical. A camera operator rehearses a handful of live moves with a presenter. A director's assistant learns the routing labels and the intercom groups. A sound operator hears what the room does to a voice and learns which microphone position keeps speech clean. People retain what they have done with their own hands.

Training is easiest to schedule in the weeks around opening, when the crew is motivated and the system is still fresh. It is worth repeating after staff changes, since knowledge held by one person leaves with them.

• Short sessions on the real studio equipment
• Role-specific practice rather than general lectures
• Refresher sessions after crew changes

There is no single correct length for hypercare, and anyone quoting one without looking at your programmes is guessing. A daily news bulletin reaches a stable routine faster than a weekly live show with changing guests, simply because the crew repeats the same actions more often.

A sensible approach is to define the end by condition rather than by date: cover steps down once several consecutive programmes have run without a technical fault needing an engineer's hand. Until then it continues at the agreed level, then lightens to being on call, then ends.

Whichever pattern you choose, agree it in writing before the first broadcast. That avoids awkward conversations later about whether support has ended, and it gives the production manager a clear point at which responsibility passes fully to the in-house team.

If a supplier offers hypercare, a few plain questions show whether it is real. Who exactly will attend, and have they worked on this installation? How quickly can they be reached outside the programme itself? What gets written down after each broadcast, and who receives it?

Ask also what is excluded. Support for the system you were handed is different from operating your programmes for you, and both are legitimate, but they are priced and planned differently. A clear answer on that boundary is a good sign.

Finally, ask how training is handed over. A supplier whose support leaves your crew more capable each week is working toward its own absence, which is the right direction.