Sonosfera was started by a salon operator who got caught out by PPL/PRS licensing letters and built the music platform they wished existed. The team behind this blog has spent years inside hair and beauty businesses, clinics, and hospitality venues — booking the bills, dealing with the licensing letters, and learning the hard way that most Spotify playlists don't work for a professional environment.
Short answer: A staff music policy is a short operating rule for who controls customer-facing playback, what may change during a shift and what staff should do when the sound is wrong. The owner defines the approved mood and exclusions; the shift lead may make bounded vibe or volume changes; everyone logs recurring problems instead of replacing the source with a personal account.
The template below is for cafés, salons, shops, restaurants, gyms and other venues. It is an operations template, not employment or legal advice. Adapt roles to your team and keep the finished policy to one page.
Copyable staff music policy
Customer-facing music policy
Purpose: Music supports the current customer activity without making speech, service or instruction harder.
Approved source: Use only the business's approved customer-facing music service and approved speaker zones. Personal streaming accounts and staff phones are never used for customer-facing playback. Any radio, download or fallback source requires documented confirmation that its service terms and rights position permit the intended business use.
Owner: The venue owner or appointed manager sets approved vibes, dayparts, exclusions and normal volume references.
Shift control: The shift lead may switch to an approved vibe or adjust volume when customer activity clearly differs from plan. Return to the normal schedule when the exception ends.
Volume rule: Customers and staff must be able to complete the venue's normal speech task—ordering, consultation, checkout, calls or instruction—without repeatedly raising their voices.
Unsuitable track: Do not rebuild the schedule during service. Skip or block it where the approved system allows, then record the time, zone and reason.
Requests: Customer requests do not override the approved source, exclusions or venue concept unless the manager has defined a request policy.
Escalation: Report recurring timing, volume, zone or content problems to the music owner at the next review. Urgent customer-safety or service issues are corrected immediately.
Replace the role names and protected speech task. Do not add rules the team cannot actually follow.
Why a venue needs a music policy
Without ownership, background music becomes a taste contest. One person turns it up, another changes the source, and a third tries to repair the day by choosing a new playlist. The result is not necessarily bad taste; it is an uncontrolled operating surface.
Rule 1: separate brand decisions from shift decisions
The owner or music lead should decide the durable layer:
what the venue should feel like;
approved vibe range;
explicit-content boundary;
daypart schedule;
room or zone jobs;
sources that may be used;
treatment of customer requests.
The shift lead should handle the immediate layer: a room that is unusually quiet, an event that runs late, a consultation area that needs a lower level, or an unsuitable track. That split preserves consistency without making the team helpless.
Rule 2: protect the room's main job
Write one observable priority. A café protects ordering and conversation. A salon protects consultations. A gym protects staff instruction at reception and on the floor. A shop protects customer questions and checkout.
When music competes with that job, reduce the level or switch to an approved calmer vibe. Use the ten-minute volume checklist rather than debating personal preference.
Rule 3: control the source
List what the venue allows. If the business has selected one customer-facing service, staff should not swap to personal accounts because a favourite playlist feels easier. Outside sources also have their own terms and licensing position; this policy does not decide those questions.
Keep the rule operational:
approved source stays connected during trading hours;
personal logins are not used for customer-facing playback;
staff do not upload, import or connect outside music without owner approval;
DJ, live music or event playback is treated as a separate use case;
failures follow a documented fallback, not improvised account sharing.
Staff need to know which actions are ordinary and which require escalation. A simple responsibility table works:
Action
Owner/manager
Shift lead
Other staff
Define brand sound
Yes
Recommend
Give feedback
Set dayparts
Yes
Report exceptions
No
Adjust approved vibe
Yes
Yes, when needed
Ask shift lead
Adjust volume
Set reference
Yes, protect service
Ask shift lead
Change music source
Yes
Only under fallback
No
Block unsuitable track
Review rules
Yes where available
Report
Do not claim technical permissions your product does not enforce. The policy describes operational authority; configure actual access controls only where the system supports them.
Rule 5: make unsuitable tracks easy to handle
One track can be wrong without the whole plan being wrong. Record the zone, time and reason: explicit content, abrupt energy, wrong seasonal context, harsh dynamics or poor brand fit.
Sonosfera's current product copy says a track can be banned so it does not play in the venue again, and customer-facing playback is explicit-free. That supports a clean response within Sonosfera playback. It does not guarantee anything about music from other sources.
Rule 6: use a short review loop
Review exceptions weekly during the first month, then less often once the system is stable. Group them by cause:
timing: a daypart begins too early or late;
volume: one period or area repeatedly competes with speech;
zone: two spaces need different sound at the same time;
content: repeated tracks or moods do not fit;
control: staff do not understand who owns the decision.
Change the smallest rule that addresses the pattern. Use the dayparting guide for timing and the multi-zone guide for room conflicts.
How Sonosfera fits the policy
Sonosfera's visible product copy supports remote vibe and volume control, room visibility, track banning and explicit-free customer-facing playback. The remote is not described as remote playlist picking, so this template does not tell staff they can choose arbitrary playlists from the phone.
That boundary belongs in the handover. A truthful policy is better than a longer policy built around controls the team does not have.
Frequently asked questions
Can staff play their own music in a business?
Only if the owner has approved the source, rights position and customer-facing fit. A practical policy keeps personal accounts out of normal venue playback and treats exceptions separately.
Who should control background music at work?
The owner or appointed manager should define the durable rules. One shift lead should handle approved vibe and volume adjustments during service, with other staff reporting issues to that person.
What should staff do when a song is unsuitable?
Skip or block it where the approved system allows, then log the time, zone and reason. Do not replace the entire source or redesign the schedule in the middle of service.
Should a business accept customer song requests?
Only under a defined request policy. Requests should not override explicit-content rules, brand boundaries, source restrictions or the needs of the wider room.
Put the rule in the shift handover
A good staff music policy makes four things obvious: approved source, decision owner, protected customer activity and escalation route. Copy the template, replace the role names and test whether a new starter can follow it without explanation.
