[{"data":1,"prerenderedAt":101},["ShallowReactive",2],{"content:en:article:multiVenue":3},{"article":4,"byline":100},{"key":5,"reviewStatus":6,"seo":7,"card":10,"eyebrow":13,"h1":11,"lead":14,"datePublished":15,"dateModified":15,"readingMinutes":16,"sections":17,"takeaways":92,"related":99},"articleMultiVenue","source",{"title":8,"description":9},"Managing background music across several venues","How to keep music consistent across several cafés, shops or hotels: one group schedule, local exceptions, sensible staff limits, remote status checks and a rollout plan.",{"title":11,"body":12},"Managing music across several venues","One group schedule, local exceptions and a way to see every venue from one place — without visiting each one.","Operations guide","With one venue, music is a small daily decision. With five, it becomes a brand question and a support question. Here is a practical way to keep several venues sounding right without driving between them.","2026-11-15",7,[18,27,36,48,55,63,72,81],{"id":19,"title":20,"paragraphs":21,"links":24},"problem","What changes when you add a second venue",[22,23],"In a single café the owner hears the music every day and fixes problems in passing. Add a second and a third location, and the music in each one starts to depend on the team on shift: their playlists, their volume, their idea of when to change the mood.","Two things suffer. The first is consistency — guests who visit more than one location experience a different brand in each. The second is visibility — when something goes wrong, nobody outside the venue knows until a guest or a staff member mentions it.",[25,26],"industryCafes","industryRetail",{"id":28,"title":29,"paragraphs":30,"links":33},"group","Start with one group schedule",[31,32],"Write one weekly schedule that describes how all your venues should sound: which moods play when, on which days. That is your standard. Most of the time every venue simply follows it.","Plan it for your most typical location rather than the most unusual one. Our guide to scheduling music by time of day walks through the planning step by step.",[34,35],"articleDayparts","featureScheduling",{"id":37,"title":38,"paragraphs":39,"bullets":42,"links":46},"exceptions","Handle differences as exceptions",[40,41],"Real venues are never identical. One branch is near a university and stays busy in the afternoon; one shop is in a shopping centre and keeps longer hours; one hotel has a bar the others don’t. Instead of maintaining a separate schedule for each, keep the group schedule and add exceptions where a venue really differs.","In Tunelay there are two levels: the group’s weekly schedule, and exceptions for a single location or a single date. The exception always wins, and it never affects the other venues. When the reason for an exception goes away, delete it and the venue falls back to the group standard.",[43,44,45],"Keep exceptions few and specific, and name them after their reason.","Review them every season — old exceptions are the main source of confusion.","Opening hours belong to each location, so the music stops at the right time everywhere.",[47],"industryHotels",{"id":49,"title":50,"paragraphs":51},"conventions","Agree on names, zones and roles before you scale",[52,53,54],"Before rolling out widely, agree on a few conventions. Name locations the way your team talks about them (“Riverside”, “Station kiosk”) rather than by street address, and use the same zone names everywhere — “Counter”, “Terrace”, “Bar” — so a schedule written for one venue reads correctly in all of them.","Zones are worth the effort only where the sound really needs to differ. A terrace, a separate bar or a treatment room usually justifies its own player and volume limit; two corners of the same room usually don’t. Fewer zones mean fewer devices to look after and fewer exceptions to keep track of.","Think about responsibilities as well. People who run a single venue rarely need to change the others, and head office rarely needs to adjust one venue’s volume. Decide early who edits the group schedule and who only looks after their own location.",{"id":56,"title":57,"paragraphs":58,"links":61},"limits","Give each venue the right amount of control",[59,60],"Head office sets the standard; the team on site deals with what is happening in the room right now. The trick is to give staff enough control to react without letting the standard drift.","A practical split: staff can pause, skip, adjust volume below a maximum you set per zone and switch to another approved mood until the next scheduled change. Settings and unpairing sit behind a manager PIN. Every staff action is logged, which is not about blame — it shows you where the schedule doesn’t fit a venue’s reality.",[62],"featureMultiLocation",{"id":64,"title":65,"paragraphs":66,"links":69},"visibility","See every venue from one place",[67,68],"The most useful thing a multi-venue setup gives you is a single view: which players are online, when each last checked in, what is playing and which ones need attention. That turns “is the music on in the north branch?” from a phone call into a glance.","Offline playback matters here too. If a venue’s connection drops, its music keeps playing from the device and the dashboard shows the player as offline until it reconnects — so you can tell a short outage from a tablet that has been switched off.",[70,71],"articleOffline","featureOffline",{"id":73,"title":74,"paragraphs":75,"links":78},"announcements","Use announcements sparingly and centrally",[76,77],"Recorded announcements — a closing reminder, a seasonal message, a last-orders call — are easier to manage centrally than to leave to each venue. Upload the recording once, schedule it for the venues and times where it belongs, and let the music dip underneath while it plays.","Keep them rare and short. A message that plays every ten minutes stops being heard and starts being resented, by guests and staff alike.",[79,80],"featureAnnouncements","industryBars",{"id":82,"title":83,"paragraphs":84,"bullets":86},"rollout","A simple rollout plan",[85],"Rolling out to several venues goes more smoothly in stages than all at once.",[87,88,89,90,91],"Start with one venue for a week and adjust the group schedule there.","Add the remaining venues with their own opening hours; pairing each player takes a couple of minutes with a six-digit code.","Set volume limits per zone and hand out manager PINs only to managers.","Add exceptions only after a venue has run on the group schedule for a while.","Check the dashboard daily for the first two weeks, then weekly.",{"title":93,"items":94},"In short",[95,96,97,98],"One group schedule is your standard; exceptions handle real differences.","Give staff limited controls and read the action log as feedback.","Use a dashboard to see every venue’s status without calling anyone.","Roll out in stages, starting with one venue.",[62,26,47,34],"By the Tunelay team",1794759563294]