Hearing loop installation isn’t something the Equality Act 2010 spells out. Section 20 asks for reasonable steps to provide an auxiliary aid where a disabled person would otherwise be at a substantial disadvantage, and a loop is one common way to do that. What counts as reasonable depends on your building and your service.

This post is not legal advice. It sets out the statute wording we checked, the standard an installer should commission against, and what a good job looks like. We last checked the sources in October 2026.

What the Equality Act says about hearing loop installation

Section 20 sets out a duty made up of three requirements. The third is the one that matters here. Where a disabled person would, but for an auxiliary aid, be put at a substantial disadvantage, section 20(5) requires you to take such steps as it is reasonable to have to take to provide that aid. Section 20(11) adds that an auxiliary aid includes an auxiliary service.

Section 29 applies the duty to service providers, and section 29(7)(a) says so directly. Schedule 2 then says that for services, the reference to a disabled person in section 20(3), (4) or (5) is to disabled persons generally. In effect, you can’t wait for a named complaint before you think about it. That’s our reading, not the statute’s own phrase.

Paragraph 2(7) of the same schedule says a service provider needn’t take a step that would fundamentally alter the nature of the service or the nature of its trade or profession. The Act applies across Great Britain. It never uses the words “induction loop”, and no section prescribes a hearing loop. “Reasonable” gets judged case by case, so a village hall and a large auditorium will land in different places.

The Equality and Human Rights Commission publishes a statutory Code of Practice on services. A 2026 edition is now on GOV.UK, so check you’re reading the current one before you quote it to anyone.

Who a hearing loop helps, and where it falls short

A hearing loop installation helps people whose hearing aids or implants have a telecoil, and only those people. RNID says over 18 million adults in the UK are deaf, have hearing loss or tinnitus, and that figure includes tinnitus. It also estimates 2.4 million adults have hearing loss that makes most conversational speech hard to follow. Not all of them will have a telecoil, and not all of them will know how to switch it on.

The ABTT’s 2013 guide to hearing assistance in UK auditoria gives a fair summary of the trade-offs. Loops are comparatively easy to install, relatively low in cost and can be discreet. The downsides are electrical and magnetic noise, especially from lighting control equipment, audio quality that isn’t always good, and large or variable seating that is hard to cover. Infrared systems avoid the magnetic noise. They need line of sight, receivers, chargers and someone to manage them.

Bluetooth Auracast is the newer option. The Bluetooth SIG says loops and telecoils have long been the standard for assistive listening in public spaces, and that Auracast broadcast audio can send sound from PA systems and TVs straight to hearing aids, with supporting products now coming onto the market. We’d treat it as emerging and complementary. We aren’t giving dates, because we haven’t seen any we trust.

What BS EN IEC 60118-4 covers

The current designation we found is BS EN IEC 60118-4:2015+A1:2018, and BSI lists it as current, published 30 April 2018. We checked in October 2026 and found no newer edition. Its title is Electroacoustics, Hearing aids, Induction-loop systems for hearing aid purposes, System performance requirements.

The standard sets requirements for field strength in audio-frequency induction loops used with telecoil hearing aids. It also covers minimum frequency response, measurement methods, a check of magnetic background noise on site, the useful volume of the field and commissioning steps. It doesn’t cover loop driver amplifiers. Those fall under IEC 62489-1.

You’ll often see a “400 mA/m target” quoted. That’s a simplification. In the standard, 400 mA/m is the 0 dB reference. The long-term average speech level is about 100 mA/m, which is minus 12 dB against that reference. We haven’t quoted tolerances, background noise limits or measurement heights, because the secondary sources we read disagree. Read the standard or ask the installer to show you the figures they commissioned to.

What a good hearing loop installation includes

A good hearing loop installation starts with a survey, and a cable drum comes later. The installer should measure background magnetic interference with a field strength meter, look for metal in the floor and choose a loop type. A perimeter loop can spill a long way outside the room. A joint design guide from two loop manufacturers says up to four times the loop width. Phased array loops cut that spill, to about 1.2 m from the edge in that guide. It also says steel rebar or pan decking soaks up field at the top of the frequency range, and extra amplifier power won’t fix that.

Next comes the driver, matched to the loop and set up for any metal loss. Then cabling, kept clear of other cables. The same design guide gives 61 cm from parallel voice, data or mains wiring. Buried cable should be marked on the drawings.

Commissioning comes last, and it’s where jobs get skipped. The installer measures with a calibrated meter against BS EN IEC 60118-4, records the results and issues a certificate. Signs go up at each loop-served area so users know to switch to the telecoil setting. In our view, an installer who can’t show you the measured results hasn’t finished the job.

Where loops fail after handover

Most failures after a hearing loop installation are boring. The amplifier’s unplugged, or the source was never routed to it. Microphone gain was set for an empty, quiet room and nobody revisited it when the room filled. Someone fits new dimmers or screens after commissioning, and the interference changes. Then nobody can say what normal sounded like, because the test was never written down.

The fix is routine. Hearing Link guidance says a basic listening test should be done on a regular basis and before events, with a more thorough check normally done annually by a specialist loop supplier. If staff can’t say where the loop is and how to test it, you have a loop in name only. Fold the annual check into your AV maintenance contract so it doesn’t slip. Plan for the day it fails too. The ABTT guide says to tell staff and post notices when a loop is out of action before an event, so users aren’t left guessing at the door.

Questions to put to an installer

Before you sign, put these to the installer:

• Which loop type are you proposing, and why? What will the hearing loop installation cover and what won’t it?
• Will I get the measured results and a certificate at handover, with the standard and its edition named on it?
• Who tests the loop, and how often?
• What signs do you supply, and what should staff do when the loop fails before an event?
• What happens if we change the room later?

Floors matter in any hearing loop installation. Our places of worship page notes that metal in floors complicates loops, and the same applies in many modern meeting spaces. For a real example, the induction hearing loop in our Scottish Fire and Rescue Service Cambuslang auditorium covers the whole auditorium.

See our Meeting Room AV page for the wider audio picture. We design and install from Glasgow, and we’ll tell you straight if a loop isn’t what your room needs.

A meeting room booking system earns its money by freeing rooms that nobody turned up for. Microsoft Places can release a booked room automatically if nobody checks in, and the default window is 10 minutes. That only works if each room has a way to check in, and the panel, licence and network behind it are in place.

How a meeting room booking system stops ghost bookings

It asks people to confirm they’ve arrived, then releases the room if they don’t. Microsoft’s documentation describes four ways to check in: the Teams panel at the door, the join button on a Teams Rooms console, the Teams meeting chat, or email. The release window defaults to 10 minutes and can be changed. Microsoft’s example sets 20 minutes through a setting called PostReservationMaxClaimTimeInMinutes.

Three details catch people out. Changes can take up to 48 hours to apply. The panel check-in needs a recent Teams panel app version, which Microsoft lists. And licensing matters: Teams Premium bought before 1 April 2026, or a space licence (Teams Rooms or Shared Space) on the room. The page was updated on 25 August 2026.

Microsoft recommends limiting auto-release to rooms that have a panel or a Teams Rooms device. That’s sound advice, since a room with no way to check in can only release itself on a guess. In our view 10 minutes is tight for a boardroom hosting external guests who sign in at reception, so lengthen the window there.

We haven’t found a verified figure for how many bookings go unclaimed, and vendor percentages in search results don’t come with methods. Measure your own: compare booked hours with occupancy for a month before you buy any meeting room booking system.

What a meeting room booking system needs behind the wall

A booking panel is a small networked computer, and it needs a data point, power over Ethernet and a place on the right VLAN. Our room booking systems page describes door and desk panels that sync with Microsoft 365 or Google Workspace, with check-in and auto-release for ghost bookings. It also covers occupancy sensors.

In our experience the cabling is where budgets slip. A panel beside the door needs a cable run to that exact spot. On a new build that’s a line on the containment drawing. In an occupied office it’s surface trunking or a ceiling void and a night visit. Ask for the data point locations on the quote, and for the licences and network work to be priced as separate lines.

Sensors add a second signal. A booking says someone intends to use the room. A sensor says someone is in it. Combined, they let you release a room that nobody has entered, and they give you honest utilisation data. Ask what the sensor reports and where that data goes. Find out who can see it, and whether the occupancy figures are anonymous counts or tied to named people in the calendar. That changes the privacy conversation with your staff.

Security and the Windows 10 question

Rooms with Teams Rooms devices come with their own identity rules. Microsoft’s guidance on conditional access says the management feature needs a Teams Rooms Pro licence and Entra ID P1, which is included. It says not to require interactive MFA for room resource accounts, and to exclude them from any policy that needs a person to sign in. It also says to apply Intune compliance to both devices and resource accounts, so read the full Microsoft guidance with your identity team.

If your room PCs still run Windows 10, that’s a bigger issue than the booking layer. Microsoft doesn’t support Teams Rooms on Windows devices placed on ESU, and builds 10.0.19045 or lower need Windows 11 or a replacement. We cover that in our note on the Windows 10 ESU cost for AV PCs. Check the room accounts too, since Microsoft’s guidance treats them separately from the devices. Fix the PCs first, then add the meeting room booking system on top.

Why wireless presentation fails on a managed network

It usually fails because discovery doesn’t cross the network boundary. One vendor documents AirPlay discovery as using mDNS on UDP port 5353 at 224.0.0.251. That vendor’s knowledge base, written for one receiver product, says multicast typically doesn’t cross VLANs without an mDNS reflector or Bonjour gateway. Our own wireless presentation page says the same about multicast discovery.

That vendor page lists the other usual causes. Access point client isolation has to be off. Multicast has to be allowed on the client SSID. Blocked ports can leave you with a black screen or audio-only mirroring. The symptom is usually the same: the laptop doesn’t see the room, and the person presenting blames the receiver when the fault sits on the network behind it.

The fix is a network job, so settle it at design stage. Decide where the receivers live, which VLAN guests and staff join, and who runs the reflector. We haven’t checked in detail how Miracast and Google Cast behave across your network, so test every protocol your people use before sign-off.

Guests, BYOD and keeping a wired fallback

Wireless presentation often gets bought alongside a meeting room booking system, since both touch the same rooms and the same network. People bring whatever they have. AirPlay, Miracast, Google Cast and USB-C all turn up. Our wireless presentation page covers all four, including guest sharing that doesn’t need the visitor to join your corporate network.

Treat the receiver as a networked device. It has an address, firmware and a management page, so it belongs on your asset list and your update schedule. If you hold Cyber Essentials, ask your assessor how it should be scoped. Our guide to Cyber Essentials and Cyber Essentials Plus explains the two levels.

A visitor’s laptop may run any of those four, and not every receiver supports all of them, so check the protocol list against the devices your own people carry. Keep an HDMI or USB-C cable on the table for the day wireless lets you down.

What to ask a supplier before you buy

Start with the calendar. Find out which one the system syncs with, and whether it needs Microsoft 365 or Google Workspace licences on top. Then ask for the check-in method in each room, and who sets the release window. Each panel needs a data point, PoE and a VLAN, so ask what it wants on the wall.

On the wireless side, ask how guests present without joining the staff network, which protocols are supported and who tests them on your network. Ask what support costs and who answers when a panel goes blank. Our meeting room AV team can sit in on those calls. Get the answers in writing and compare them side by side. A supplier who can’t say how check-in works in a given room hasn’t thought about that room yet. Ask to see a live installation on a network like yours, with a guest laptop on it.

See our Room Booking Systems, Wireless Presentation and Meeting Room AV pages.

Why this is rarely a close call

If your organisation already runs on Microsoft 365, a certified Microsoft Teams Rooms system is almost always the right default, it integrates natively with the calendar, licensing and admin tools you already have. The same logic applies in reverse for organisations standardised on Zoom. Choosing the platform your staff don’t already use daily just adds a second login and a second set of habits to learn.

The bit that actually matters more: interoperability

Industry surveys now regularly put the share of meetings with at least one remote participant at 70% or more: and a meaningful share of those involve someone joining from a different platform than the room is built for. That’s why interoperability, not platform loyalty, has become the defining meeting-room AV priority: a well-specified room should let a Zoom-only external guest join a Teams-native meeting without anyone in the room noticing the difference.

Certified room hardware from Logitech, Yealink, Poly and others is increasingly built platform-agnostic for exactly this reason, the same physical camera and audio bar running Teams in one room and Zoom in the next, switched at the compute layer rather than the hardware.

Sizing the room correctly

Huddle rooms (2 to 6 people) generally need one all-in-one video bar and nothing more elaborate. Mid-size meeting rooms (6 to 14 people) benefit from a dedicated room PC or compute puck rather than relying on someone’s laptop. Larger boardrooms need multiple cameras or an auto-framing wide-angle system so remote participants aren’t staring at the back of someone’s head for an hour.