If you've ever heard one music track that's clearly louder than the previous one in your hotel lobby, you've experienced the loudness problem. Background music programming for hotels requires careful attention to loudness — not just volume settings, but the loudness of the music files themselves and how perceived loudness varies across zones.

This guide explains LUFS (the modern standard for music loudness measurement), how it relates to dB(A) measurements you might take with a phone app, and how to set proper targets for different zone types in a hotel.

The guide is technical but operator-focused. Rafilis makes Rafilis Multizone, which lets you set per-zone volume targets — but the principles of loudness measurement apply regardless of your multi-zone software.

Three loudness terms you'll hear

LUFS (Loudness Units relative to Full Scale)

LUFS measures perceived loudness of audio content. It accounts for the fact that humans perceive low and high frequencies differently than mid frequencies, and that loudness perception integrates over time (a 5-second loud passage feels louder than a 5-millisecond peak).

LUFS is the standard for broadcast and streaming loudness normalization (Spotify, Apple Music normalize to -16 to -14 LUFS). When you see "loudness target" specified, it's usually LUFS.

For hospitality background music, target LUFS:

The lower the LUFS number (more negative), the quieter the music.

dB(A) — A-weighted decibels

dB(A) measures sound pressure level (SPL) at a specific location with frequency weighting that approximates human hearing sensitivity. It's what your phone SPL meter app reports.

For hotel zones, target dB(A):

RMS — Root Mean Square

RMS measures the average power level of an audio signal. It's the technical predecessor of LUFS — RMS measurements don't account for human perception as precisely, but they're simpler to calculate.

For everyday hotel music programming, LUFS is the practical standard. RMS is more relevant for audio engineers fine-tuning specific tracks.

Why these measurements matter

When you set a "volume" in your multi-zone software, you're setting an output level. The actual perceived loudness depends on:

  1. The music file's own loudness (LUFS of the file)
  2. The amplifier output gain (controlled by your software)
  3. The speaker SPL output (a function of amplifier power and speaker sensitivity)
  4. The listening position (closer = louder, farther = quieter)
  5. The room acoustics (reverberant rooms feel louder; absorbent rooms feel quieter)
  6. Ambient noise (more crowd = the music needs to be louder to be perceived the same)

Properly calibrated zones account for all six. The shortcut: use a phone SPL meter to verify the actual sound at typical listening positions matches your target.

Why LUFS matters: track-to-track consistency

If your music files have inconsistent loudness, guests will hear:

This is the "perceived volume varies wildly between tracks" complaint. The cause: different tracks have different LUFS values, so even at the same output volume, they sound different.

The fix: normalize your music library to a consistent LUFS target. Most multi-zone systems support per-track or per-playlist normalization. Some music services (Soundtrack Your Brand) do this automatically.

Target normalization levels:

After normalization, all tracks in a playlist feel like they have the same loudness — the only difference between them is musical character.

Measuring in your hotel

Tools

Measurement procedure

  1. Walk the property during peak service (e.g., 19:30 for dinner zones)
  2. Stand at typical guest positions (table height for dining zones, standing height for lobby)
  3. Measure for 30+ seconds to average out brief variations
  4. Note location, time, and dB(A) reading
  5. Compare to target for that zone type
  6. Adjust per-zone volume in your multi-zone software

Common findings:

Walk the same zones at different times

A zone might be at 65 dB(A) during peak dinner (correct) and 75 dB(A) during late-night cocktails (too loud). This is normal — different times need different volumes. Document the dB(A) reading at each time so you can verify the schedule is calibrated correctly.

What "too loud" looks like in reviews

Hotels with audio mistakes (see our 7 audio mistakes guide) consistently see:

The 5-8 dB difference between target and actual is small numerically but creates the difference between "feels right" and "feels off."

Practical calibration checklist

☐ Free phone SPL meter app installed
☐ All zones identified with target dB(A) range
☐ Music file library normalized to consistent LUFS
☐ Volume measured per zone during peak service
☐ Per-zone volume adjusted to target
☐ Different times of day measured separately
☐ Schedule has volume changes (-2 to +2 dB at transition times)
☐ Quarterly re-measurement to catch drift

Common loudness mistakes

1. Setting volume by ear from the kitchen. The kitchen is louder than guest areas; music sounds quieter there. Calibrate at guest positions.

2. Using consistent music files without normalization. Different tracks have different inherent loudness; without normalization, perception varies wildly.

3. Assuming dB(A) measurements transfer between zones. A spa at 58 dB(A) feels different from a lobby at 58 dB(A). Calibrate per-zone targets.

4. Ignoring time-of-day variation. Daytime lobby at 60 dB(A) is fine. Late-night lobby at 60 dB(A) feels too loud. Schedule volume reductions.

5. Equating "louder" with "better." More volume rarely improves background music. Less volume usually fixes complaints.

When to consider professional calibration

Most hotels can self-calibrate using phone SPL meters and the targets above. Hire a professional acoustician/AV engineer when:

Cost: €500-2,000 for a professional audio calibration visit covering 4-8 zones.

Loudness in hotel music programming is one of those operational details that's invisible when right and intolerable when wrong. The good news: it's measurable. With a phone app and 30 minutes of measurement per zone, any hotel can verify whether their music levels are appropriate — and most properties find adjustments worth making.