Almost every hotel plays music. Lobby ambience, restaurant background, a banquet hall on a wedding night. Almost none of them budgeted for it as a licensable act, and the way most owners learn otherwise is a notice, an inspection, or a demand letter arriving during wedding season.
Quick answer (for the impatient)
Playing recorded music in a commercial space is a public performance, which is a different right from owning or streaming the music.
There can be two separate licences, because the recording and the underlying composition are distinct rights held by different bodies.
Your Spotify or Apple Music subscription does not cover this. Those are personal-use licences and generally say so explicitly.
Why your streaming subscription doesn't help
This is the single most common misunderstanding, and it's an entirely reasonable one. You paid for the music, so surely you can play it. But what a consumer subscription licenses is personal listening. Playing the same track to a room of paying guests is a public performance — a separate right, not included, and the terms of service of most consumer services say this in plain language.
The commercial-use question is the whole thing. A hotel that would never dream of using unlicensed software often runs an entire property's audio on a personal account without registering that these are the same kind of decision.
Why two licences
A piece of recorded music contains two separable rights: the sound recording — the specific master you're playing — and the underlying musical work and lyrics. In India these are typically administered by different organisations, which is why hoteliers who have obtained one licence are sometimes surprised to receive a demand from another body.
That surprise is not necessarily a scam, and it's also not automatically legitimate. Which brings us to the part worth being careful about.
Handling a demand letter
This area attracts both genuine enforcement and opportunistic collection. Sensible practice on receiving a demand:
Verify the body's standing to administer the rights it claims, for the current period. The status of these organisations has been litigated and has changed over time.
Ask what repertoire the demand covers. A licence covers a body's catalogue, not all music that exists.
Don't pay a walk-in demand on the spot. Legitimate licensing is administrative and survives you taking a week to verify it.
Get advice before signing a multi-year commitment, particularly one covering banquets, where tariffs are often event-based and can be large.
The banquet exposure
Rooms and lobbies are usually tariffed on area or room count. Banqueting is different — event-based tariffs for weddings and functions can be substantially larger, and a hotel that hosts fifty weddings a year has a materially bigger exposure than its lobby music suggests. If you host events, price this into what you charge rather than discovering it afterwards.
Worth knowing: where a client brings their own DJ or band, the licensing question doesn't automatically transfer to them. Clarify responsibility in your banquet contract rather than leaving it ambiguous.
Where we're honest about the limits of this post
No tariffs, body names as definitive authorities, or licensing requirements stated as settled here. The administration of music rights in India has been subject to litigation and regulatory change, and which organisations are validly entitled to license what has genuinely shifted. Take advice from an IP lawyer before either paying a demand or ignoring one.
A realistic hotel example: what the team sees during a working shift
Picture Lakeview Residency, an independent property where the same manager may answer a booking query, approve a rate, settle a guest account and help a new employee before lunch. The question behind Playing Music in Your Lobby Is a Licensable Act. Most Hotels Find Out From a Notice. does not arrive as a neat software task. It arrives while somebody is waiting, another department needs an answer and the record must still make sense at the end of the day.
The first useful observation is this: Playing recorded music in a commercial space is a public performance , which is a different right from owning or streaming the music. The manager should translate that statement into a visible hand-off. Who starts the action? Which record do they open? What information must already be present? Who checks the result? If any answer depends on one experienced employee remembering an exception, the process is not yet reliable.
The second observation is equally practical: There can be two separate licences , because the recording and the underlying composition are distinct rights held by different bodies. At Lakeview Residency, the team would test this with one ordinary case and one awkward case. The ordinary case confirms the expected path. The awkward case exposes missing permissions, incomplete data, unclear ownership or a decision that still happens in a private message. Both tests matter because hotel operations rarely fail on the clean example shown in a demonstration.
The third observation is about the downstream record: Your Spotify or Apple Music subscription does not cover this. Those are personal-use licences and generally say so explicitly. A completed action should leave enough context for the next person to understand what happened without reconstructing the story from calls and chat messages. That does not mean collecting every possible field. It means keeping the few facts that change the decision, the status, the responsible role and the next action together.
Rollout checklist: move from a good idea to a repeatable process
Use this checklist before the team treats the workflow as normal operating procedure. It deliberately separates product reachability from management discipline: software can make a record available, but the property still decides who owns it and how exceptions are handled.
Name the owner. Choose the role responsible for starting and completing the process. "The office" or "the front desk" is too vague when several people share a shift.
Confirm access. Test with the real role and tenant configuration, not an unrestricted demonstration account. Check enabled modules, feature permissions and the property or outlet context.
Define the minimum input. Agree which guest, room, date, amount, document or operational detail must be present before somebody can act.
Run the normal case. Complete one realistic example from beginning to end and ask the next team member to explain the result using only the saved record.
Run the exception. Try a correction, cancellation, missing value, late change or disputed instruction that genuinely occurs at the property. Record the fallback if the product path does not cover it.
Check the hand-off. Make sure the relevant people in front desk, reservations, housekeeping and accounts can see the status they need without receiving unnecessary access to unrelated records.
Write the fallback. If the system is unavailable or the case sits outside the verified path, state who records the temporary decision and who reconciles it later.
Review after live use. Ask staff where they paused, duplicated work or returned to a spreadsheet. Fix the process before adding more fields or automation.
Decision table: evidence to collect before you approve the workflow
A manager does not need a large transformation project to evaluate this topic. A short evidence review is enough to distinguish a reachable workflow from an attractive claim. Use the table during a property review and write the answer in plain language.
Review point What to verify Evidence to keep Decision if it fails
Reachability The responsible role can open and complete the path in the correct tenant and property context. A completed test record and the role used. Do not announce the workflow; check provisioning and permissions.
Data quality The minimum information needed for the decision is present, understandable and current. The input checklist and one reviewed example. Fix the collection step before adding automation.
Ownership One role owns the next action and another can review where separation is appropriate. The operating owner and escalation path. Assign responsibility before rollout.
Exception handling A correction, cancellation or disputed case has a documented path. The tested exception and fallback note. Keep the process in controlled trial use.
Downstream hand-off The next department sees the status it needs without manual re-entry or excessive access. A hand-off check by the receiving role. Use a documented interim hand-off and reconcile it.
The honest AXOIX limit and what to review after the first live cycle
The first review should focus on behaviour, not vanity metrics. Ask the people who performed the work where they hesitated, what they entered twice and which decision still escaped into a phone call or personal message. Compare the saved record with what actually happened. If they differ, find the earliest point where context was lost.
Then separate a training problem from a product boundary. A training problem means the verified path exists but the team did not understand the trigger, required input or next action. A configuration problem means the module, property context or permission is not available to that role. A product boundary means the audited path does not support the case. Those three diagnoses require different responses; calling all of them "user error" guarantees a repeat.
Keep the limitation visible while reviewing this article: Verify the workflow and its applicability before relying on it. That boundary is part of the buying and rollout decision, not a footnote to remove from the sales conversation. Where the workflow is usable, test it honestly. Where it is partial, keep the manual control explicit. Where applicability depends on law, policy or professional judgement, confirm it with the appropriate adviser.
FAQ
What if I only play music in the lobby?
A lobby is a public commercial space. Area is usually a tariff input, not an exemption.
What about a live band rather than recordings?
Live performance engages the underlying composition rights. Different route to the same question.
Can I use royalty-free music instead?
Yes, and for many properties that's the cleanest answer — provided the licence genuinely permits commercial public performance. Read those terms rather than trusting the phrase "royalty-free."
How should a hotel test this before rolling it out?
Use the real tenant, property context and staff role. Complete one ordinary case and one exception from start to finish, then ask the receiving role to verify the saved result without relying on a private message.
What should the team do if the verified product path does not cover its case?
Keep a documented manual control, name the person responsible for reconciliation and avoid describing the unsupported step as automated. Recheck module provisioning and permissions before concluding that a capability is absent.
The bottom line
Music licensing is small money handled badly and large money handled by surprise. Decide your position deliberately — licence properly or move to genuinely commercial-cleared music — rather than defaulting into a personal streaming account and hoping.
See how the full licence set maps out, how compliance records stay current, or pricing.
Track every licence and renewal. Start free →
Comments