<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:wfw="http://wellformedweb.org/CommentAPI/" xmlns:dc="http://purl.org/dc/elements/1.1/" >

<channel><title><![CDATA[Red & Black Music - Incidents]]></title><link><![CDATA[http://redandblackmusic.weebly.com/incidents]]></link><description><![CDATA[Incidents]]></description><pubDate>Mon, 23 Feb 2026 16:06:46 +0000</pubDate><generator>Weebly</generator><item><title><![CDATA[Slow Payment and Risk to Booking]]></title><link><![CDATA[http://redandblackmusic.weebly.com/incidents/slow-payment-and-risk-to-booking]]></link><comments><![CDATA[http://redandblackmusic.weebly.com/incidents/slow-payment-and-risk-to-booking#comments]]></comments><pubDate>Fri, 02 Jan 2026 10:09:07 GMT</pubDate><category><![CDATA[Payments]]></category><guid isPermaLink="false">http://redandblackmusic.weebly.com/incidents/slow-payment-and-risk-to-booking</guid><description><![CDATA[    Hi LD,Please find attached a revised invoice addressed to Brunning and Price Limited, now including the organisation name, address, and postcode. I have also added a note to the invoice: &ldquo;Payment required to secure artist availability on 31/12/2025.&rdquo;I would like to politely draw attention to the fact that my original invoice, sent on 2nd November, was not acknowledged, and the 30-day payment policy was never mentioned to me&mdash;either in writing or during my phone call with you [...] ]]></description><content:encoded><![CDATA[<div>  <!--BLOG_SUMMARY_END--></div>  <blockquote>Hi LD,<br /><span></span>Please find attached a revised invoice addressed to Brunning and Price Limited, now including the organisation name, address, and postcode. I have also added a note to the invoice: &ldquo;Payment required to secure artist availability on 31/12/2025.&rdquo;<br /><span></span>I would like to politely draw attention to the fact that my original invoice, sent on 2nd November, was not acknowledged, and the 30-day payment policy was never mentioned to me&mdash;either in writing or during my phone call with you on Tuesday. I regret that I cannot commit to this or any booking without receiving full payment in advance.<br /><span></span>I have not included a due date on this invoice, as payment is necessary to confirm the artist&rsquo;s availability for the requested date. Please note that both enquiries are still active, and bookings will be secured on a first-payment basis. To manage my schedule and prior commitments, if the other client pays first, I may no longer be available for 31/12/2025, which could affect this booking. I hope you appreciate that, in live performance work, time-sensitive matters like these are unavoidable and require prompt action to secure specific dates.<br /><span></span>I look forward to receiving payment so that this booking can be fully secured.<br /><span></span>Thanks,<br /><span></span>RD<br /><span></span></blockquote>  <div class="paragraph" style="text-align:left;">Title<br />Slow Payment and Risk to Booking<br /><br />Description<br />The artist&rsquo;s payment for the NYE 2025 booking at The Highdown Hotel was delayed due to administrative onboarding issues. Despite invoices and supplier forms being sent in advance, the hotel accounts department reported non-response from the artist. The delay created a risk that the booking could be lost, as the artist had other offers for the same date and required upfront payment to secure the booking. Miscommunication between the venue, LMM, and the artist compounded the delay.<br /><br />Action Taken<br />Artist repeatedly sent invoices and completed the supplier form.<br />Followed up via email and phone calls to confirm receipt and clarify payment details.<br />Communicated with LMM to escalate and ensure the booking was secured.<br /><br />Resolutions<br />Payment of &pound;[amount] was received 02/12/2025.<br />Booking was confirmed and marked as contracted on all systems.<br />Artist was able to prepare for and perform the event as planned.<br /><br />Notes Comments<br />At one point, the hotel incorrectly stated that the artist was not responding; this was clarified immediately by the artist.<br />The delay highlights the importance of clear communication and confirmation of supplier onboarding for timely payment.<br />The situation underscores that without proactive follow-ups, misunderstandings could have resulted in losing the booking.<br /><br />Reported<br />Reported Date: 01/01/2026<br />Reported By (Individual): RD<br />Reported By (Organisation): R<br /><br />INDIVIDUALS<br /><br />Involved, Responsive, B, Accounts<br />Involved in payments processes.<br /><br />Involved, Responsive, C, Accounts<br />Involved in payments processes.<br /><br />Responsible, Passive, HSS, Client<br />Away and didn't relay messages regarding the urgency of the invoice.<br /><br />Involved, Active, LD, Accounts<br />Orchestrated the final payment.<br /><br />Impacted, Active, RD, Artist<br />Sent multiple invoices, filled in supplier form and phoned venue to confirm payment.<br /><br />Involved, Active, SJM, Agent<br />Helped expedite payment by noting booking fee was paid up front.<br /><br />ORGANISATIONS<br /><br />LMM<br />Agent overseeing booking.<br /><br />THHG<br />Venue and client.<br /><br />READ MORE...<br /><br />This incident was triggered by the following developments...<br /><a href="http://redandblackmusic.weebly.com/developments/implementation-of-up-front-payments-for-employment-agency-contracts-2025">Implementation of Up-Front Payments for Employment Agency Contracts (2025)</a></div>]]></content:encoded></item><item><title><![CDATA[Miscommunication Regarding Meals Provision at Highdown Hotel NYE Booking]]></title><link><![CDATA[http://redandblackmusic.weebly.com/incidents/miscommunication-regarding-meals-provision-at-highdown-hotel-nye-booking]]></link><comments><![CDATA[http://redandblackmusic.weebly.com/incidents/miscommunication-regarding-meals-provision-at-highdown-hotel-nye-booking#comments]]></comments><pubDate>Fri, 02 Jan 2026 00:00:00 GMT</pubDate><category><![CDATA[Fulfilments]]></category><guid isPermaLink="false">http://redandblackmusic.weebly.com/incidents/miscommunication-regarding-meals-provision-at-highdown-hotel-nye-booking</guid><description><![CDATA[    They did feed me but the parameters weren't clear and there was a moment where they tried to charge me. No matter-I'll make sure my show advance covers this more explicitly in future to avoid any confusion. Thanks very much for the booking! The punters were all extremely nice and engaging with the music. The night went well (despite the ..ahem..venue comms!) and we managed to hit all the right notes. The Oliver Price set was actually spot on. Everyone seemed to enjoy it, dancing, singing alo [...] ]]></description><content:encoded><![CDATA[<div>  <!--BLOG_SUMMARY_END--></div>  <blockquote>They did feed me but the parameters weren't clear and there was a moment where they tried to charge me. No matter-I'll make sure my show advance covers this more explicitly in future to avoid any confusion. Thanks very much for the booking! The punters were all extremely nice and engaging with the music. The night went well (despite the ..ahem..venue comms!) and we managed to hit all the right notes. The Oliver Price set was actually spot on. Everyone seemed to enjoy it, dancing, singing along. Hope you had a wonderful Christmas and a musical New Year's Eve!<br /><span></span></blockquote>  <div class="paragraph" style="text-align:left;">Title<br />Miscommunication Regarding Meals Provision at Highdown Hotel NYE Booking<br /><br />Description<br />RD performed at The Highdown Hotel on 31 December 2025 for a New Year&rsquo;s Eve event (booked via LMM, ref LMM26560). The agency contract listed &ldquo;Food &amp; Drink for Performers: yes&rdquo;. In advance, multiple attempts were made to secure written confirmation of arrangements; communication from the client (HSS) was minimal and largely unanswered.<br />Upon arrival on 31 December, RD was verbally told by hotel staff that &ldquo;breakfast is on us&rdquo;. A meal was provided mid-afternoon, but no evening meal was communicated or offered, and there was confusion among staff regarding entitlement. After the performance, RD asked staff whether he needed to inform them in the morning that he was the musician for breakfast and was told they already knew.<br />On 1 January 2026, after breakfast, RD was presented with a bill of approximately &pound;22. When RD stated he was the musician and had been told breakfast was included, the waitress responded that the hotel had already provided a room and a meal and needed to cover overheads. RD expressed discomfort with the lack of communication and explained that had he known breakfast wasn&rsquo;t included, he would have made alternative arrangements. After reiterating that he had been verbally assured breakfast was provided, the waitress relented and said &ldquo;ok&rdquo;, leaving the bill behind and walking away. No manager intervened and RD left feeling shaken.<br /><br />Action Taken<br />RD calmly explained the basis for his expectation that breakfast was included.<br />He cited both the contract wording and the explicit verbal reassurance given on arrival.<br />He remained professional and avoided escalation, though emotionally distressed.<br />When the staff member withdrew the charge, RD left the premises.<br /><br />Resolutions<br />The breakfast charge was ultimately not enforced.<br />No further dispute occurred at the hotel.<br />RD notified LMM and provided a factual account of events, without hostile tone.<br />No further action is currently required or intended.<br /><br />Notes Comments<br />This incident appears rooted in poor client communication, unclear internal hotel policies, inconsistent staff messaging, and lack of written confirmation prior to the event. It caused significant distress despite the performance itself being extremely successful.<br /><br />Reported<br />Reported Date: 02/01/2026<br />Reported By (Organisation): R<br /><br />INDIVIDUALS<br /><br />Responsible, Passive, HSS, Client<br />Didn't respond to show advance e-mails or specify meal arrangements in advance. There on the morning, didn't engage with the situation.<br /><br />Impacted, Active, RD, Artist<br />Charged for breakfast, didn't pay on the basis that hotel was providing food for musicians as part of the deal.<br /><br />Observer, Responsive, SJM, Agent<br />Booking agent, responded&nbsp;<br /><br />Involved, Responsive, TBC, Venue<br />Waitress responsible for handing the bill. Tried to uphold that the breakfast was chargeable.<br /><br />Responsible, Passive, TBC, Venue<br />Water from the previous day who said "breakfast is on us".<br /><br />ORGANISATIONS<br /><br />LMM<br />Agent overseeing booking.<br /><br />THHG<br />Venue and client.<br /><br />READ MORE...<br /><br />This incident triggered the following developments...<br />Maintaining Integrity of Show Advance Template and Preventing Loss of Critical Information</div>]]></content:encoded></item><item><title><![CDATA[Payment Irregularities and Lack of Transparency – Nova Boss @ The Stroud Hotel / Jazz Stroud (NW, SVA)]]></title><link><![CDATA[http://redandblackmusic.weebly.com/incidents/payment-irregularities-and-lack-of-transparency-nova-boss-the-stroud-hotel-jazz-stroud-nw-sva]]></link><comments><![CDATA[http://redandblackmusic.weebly.com/incidents/payment-irregularities-and-lack-of-transparency-nova-boss-the-stroud-hotel-jazz-stroud-nw-sva#comments]]></comments><pubDate>Mon, 20 Oct 2025 09:38:27 GMT</pubDate><category><![CDATA[Payments]]></category><guid isPermaLink="false">http://redandblackmusic.weebly.com/incidents/payment-irregularities-and-lack-of-transparency-nova-boss-the-stroud-hotel-jazz-stroud-nw-sva</guid><description><![CDATA[    [07/06/2025, 11:51:58] RD: Hi NW it wasn&rsquo;t about the dates as such, it&rsquo;s more about how the communication around confirmations was handled. When dates are agreed I need to be able to trust that they&rsquo;ll hold especially when it involves hiring musicians. Going forward to keep things clear I&rsquo;d need any future bookings to be confirmed with payment upfront. Totally understand if that&rsquo;s not possible.[07/06/2025, 12:00:14] NW SVA: &lrm;Missed voice call, &lrm;Tap to ca [...] ]]></description><content:encoded><![CDATA[<div>  <!--BLOG_SUMMARY_END--></div>  <blockquote>[07/06/2025, 11:51:58] RD: Hi NW it wasn&rsquo;t about the dates as such, it&rsquo;s more about how the communication around confirmations was handled. When dates are agreed I need to be able to trust that they&rsquo;ll hold especially when it involves hiring musicians. Going forward to keep things clear I&rsquo;d need any future bookings to be confirmed with payment upfront. Totally understand if that&rsquo;s not possible.<br /><span></span>[07/06/2025, 12:00:14] NW SVA: &lrm;Missed voice call, &lrm;Tap to call back<br /><span></span>[07/06/2025, 12:07:55] NW SVA: Would be easier to chat RD.<br /><span></span>The Hotel holds the cash till the day so you would need to sign and collect on the day<br /><span></span>Apart from the gig on 25 May which SVA paid for.&nbsp;<br /><span></span>The last gig was paid by and organised through SVA and JS so needed to be invoiced for. every artist SVA works with is paid through invoicing.&nbsp;<br /><span></span>Anyway give me a call<br /><span></span>NW<br /><span></span>[07/06/2025, 12:11:23] NW SVA: I haven&rsquo;t actually cancelled any of your dates. I was looking to fill some new dates<br /><span></span>[07/06/2025, 12:13:09] NW SVA: Give me a call when you can. NW<br /><span></span>[07/06/2025, 12:55:35] RD: Hey NW I&rsquo;m in bham this weekend was out shopping earlier on my way to gig now. In any case it sounds like it&rsquo;s not going to work with the payments. Do appreciate you outlining it though.<br /><span></span>[07/06/2025, 13:21:43] NW SVA: &#128077;<br /><span></span>[07/06/2025, 13:24:14] NW SVA: Doors open in future so let me know if you&rsquo;re interested<br /><span></span></blockquote>  <div class="paragraph" style="text-align:left;">Title<br />Payment Irregularities and Lack of Transparency &ndash; Nova Boss @ TSH / JS (NW, SVA)<br /><br />Description<br />Between 07/06/2025 and 09/06/2025, following booking discussions for Nova Boss performances at TSH, Stroud, Gloucestershire, it became apparent that payment arrangements for artists booked through JS / NW (SVA) were unclear and potentially irregular.<br />In the course of conversation, NW stated that payments for hotel gigs could only be made directly by TSH, not by SVA or JS. This raised questions as to why bookings were being arranged through NW if he was not in a contractual position to administer payments.<br />This lack of financial transparency caused significant confusion and anxiety for RD (Nova Boss), as it appeared that NW was operating as an informal intermediary without formal authority or accountability.<br />Despite repeated attempts to clarify, no documentation, written agreement, or direct contact from the hotel was provided to confirm the financial structure of the engagement.<br />The revelation that JS did not hold artist funds in a dedicated or separate holding account, combined with the insistence that artists be booked &ldquo;through NW,&rdquo; created a perceived conflict of interest and undermined professional trust.<br />The uncertainty over who was legally responsible for payment &ndash; and whether any payment guarantee existed at all &ndash; led to the withdrawal of Nova Boss from the scheduled June 2025 performances at TSH.<br /><br />Action Taken<br />RD directly queried payment procedures with NW (SVA).<br />Upon learning that payments were issued directly from TSH, RD withdrew from the booking on ethical and professional grounds.<br />No financial transaction occurred; no deposit or contract was issued.<br />The incident was documented for reference.<br />Future policy established: Nova Boss will only contract directly with the paying entity or promoter holding a confirmed payment channel.<br /><br />Resolutions<br />Withdrawal communicated respectfully, without escalation or hostility.<br />Clarity obtained that NW / JS do not handle artist payments directly.<br />Nova Boss&rsquo;s position formalised: all future bookings to be confirmed in writing, directly with the paying party (venue or promoter).<br />No outstanding debt or contractual dispute.<br /><br />Notes Comments<br />This issue connects to a wider pattern of gatekeeping, whereby artists were required to communicate through NW even though he had no financial control or responsibility.<br />The arrangement placed artists in a precarious position, effectively liable to perform without clear payment assurance.<br />It also created potential reputational risk for TSH, as artists could perceive the venue to be disorganised or untrustworthy, despite the confusion originating externally.<br />The situation compounded emotional stress and undermined confidence in local music administration.<br />This incident highlights the necessity for clear financial governance in arts and event programming.<br />Any third-party acting as a booking coordinator should be formally authorised to handle or guarantee payments, or else artists must contract directly with the funding source.<br />In this case, the lack of clarity around financial responsibility and payment channels reflected poor administrative practice and avoidable opacity.<br />Nova Boss&rsquo;s withdrawal was therefore both ethically and professionally justified.<br />Moving forward, Nova Boss will continue to champion fair pay transparency and direct contracting as standard practice.<br /><br />Reported<br />Reported Date: 20/10/2025<br />Reported By (Individual): RD<br />Reported By (Organisation): R&amp;BM<br /><br />INDIVIDUALS<br /><br />Responsible, Passive, NW, Client<br />To communicate booking and payment terms transparently<br /><br />Observer, Responsive, NK, Guitar<br />Subject to same gatekeeping / uncertainty<br /><br />Impacted, Active, RD, Artist<br />To seek clarification on payment and ensure fair compensation<br /><br />ORGANISATIONS<br /><br />JS<br />To communicate booking and payment terms transparently<br /><br />TSH<br />To issue payments directly to artists</div>]]></content:encoded></item><item><title><![CDATA[Communication and Booking Irregularities – Nova Boss @ Jazz Stroud / The Stroud Hotel, Stroud, Gloucestershire]]></title><link><![CDATA[http://redandblackmusic.weebly.com/incidents/communication-and-booking-irregularities-nova-boss-jazz-stroud-the-stroud-hotel-stroud-gloucestershire]]></link><comments><![CDATA[http://redandblackmusic.weebly.com/incidents/communication-and-booking-irregularities-nova-boss-jazz-stroud-the-stroud-hotel-stroud-gloucestershire#comments]]></comments><pubDate>Mon, 20 Oct 2025 09:25:43 GMT</pubDate><category><![CDATA[Communication]]></category><guid isPermaLink="false">http://redandblackmusic.weebly.com/incidents/communication-and-booking-irregularities-nova-boss-jazz-stroud-the-stroud-hotel-stroud-gloucestershire</guid><description><![CDATA[    &#8203;[04/06/2025, 20:52:17] NW SVA: Thanks for that RD, they loved you &#128591;[04/06/2025, 21:34:35] NW SVA: Wanted to talk to you about more of the Sunday sessions and maybe getting some regular Sundays confirmed[05/06/2025, 09:25:02] RD: Hi NWHere are the Sundays we could doJune15, 29July13, 20August03, 10, 31[06/06/2025, 17:31:04] NW SVA: Sundays 15 and 29 are available[06/06/2025, 21:56:51] RD: Great let&rsquo;s do those15/06/202529/06/2025I&rsquo;ll get them booked in &#128077;[07/0 [...] ]]></description><content:encoded><![CDATA[<div>  <!--BLOG_SUMMARY_END--></div>  <blockquote>&#8203;[04/06/2025, 20:52:17] NW SVA: Thanks for that RD, they loved you &#128591;<br />[04/06/2025, 21:34:35] NW SVA: Wanted to talk to you about more of the Sunday sessions and maybe getting some regular Sundays confirmed<br />[05/06/2025, 09:25:02] RD: Hi NW<br />Here are the Sundays we could do<br />June<br />15, 29<br />July<br />13, 20<br />August<br />03, 10, 31<br />[06/06/2025, 17:31:04] NW SVA: Sundays 15 and 29 are available<br />[06/06/2025, 21:56:51] RD: Great let&rsquo;s do those<br />15/06/2025<br />29/06/2025<br />I&rsquo;ll get them booked in &#128077;<br />[07/06/2025, 00:48:14] NW SVA: RG got back to me on 29 and it&rsquo;s confirmed so can we confirm 15 June please<br />[07/06/2025, 06:07:28] RD: Hi NW thanks for counting on me but best if you get someone else in on these gigs.<br />[07/06/2025, 08:23:52] NW SVA: That would be a shame RD. The other dates in July and August look good apart from 10 Aug. The arrangement at the Stroud Hotel is now 200 plus lunch &lrm;&lt;This message was edited&gt;<br />[07/06/2025, 11:06:55] NW SVA: &lrm;Missed voice call, &lrm;Tap to call back<br />[07/06/2025, 11:47:40] NW SVA: Hi RD, I&rsquo;m sorry if you&rsquo;re feeling a bit frustrated. I sent out the available dates to a few people and when people respond it&rsquo;s a question of trying to create a balance and also inclusive but I&rsquo;m happy to free up 29 to ensure you remain part of the programme because I think what you&rsquo;re doing is pretty special. Let me know. NW &#128591;<br />[07/06/2025, 11:51:58] RD: Hi NW it wasn&rsquo;t about the dates as such, it&rsquo;s more about how the communication around confirmations was handled. When dates are agreed I need to be able to trust that they&rsquo;ll hold especially when it involves hiring musicians. Going forward to keep things clear I&rsquo;d need any future bookings to be confirmed with payment upfront. Totally understand if that&rsquo;s not possible.<br />[07/06/2025, 12:00:14] NW SVA: &lrm;Missed voice call, &lrm;Tap to call back<br />[07/06/2025, 12:07:55] NW SVA: Would be easier to chat RD.<br />The Hotel holds the cash till the day so you would need to sign and collect on the day<br />Apart from the gig on 25 May which SVA paid for.&nbsp;<br />The last gig was paid by and organised through SVA and JS so needed to be invoiced for. every artist SVA works with is paid through invoicing.&nbsp;<br />Anyway give me a call<br />NW<br />[07/06/2025, 12:11:23] NW SVA: I haven&rsquo;t actually cancelled any of your dates. I was looking to fill some new dates<br />[07/06/2025, 12:13:09] NW SVA: Give me a call when you can. NW<br />[07/06/2025, 12:55:35] RD: Hey NW I&rsquo;m in bham this weekend was out shopping earlier on my way to gig now. In any case it sounds like it&rsquo;s not going to work with the payments. Do appreciate you outlining it though.<br />[07/06/2025, 13:21:43] NW SVA: &#128077;<br />[07/06/2025, 13:24:14] NW SVA: Doors open in future so let me know if you&rsquo;re interested</blockquote>  <div class="paragraph" style="text-align:left;">Title<br />Communication and Booking Irregularities &ndash; Nova Boss @ JS / TSH, Stroud, Gloucestershire<br /><br />Description<br />Between 4&ndash;7 June 2025, communication and booking irregularities occurred in relation to Nova Boss&rsquo;s proposed performances at TSH under the JS / SVA programming, coordinated by NW (SVA).<br />These issues occurred despite a prior direct approach: Nova Boss first applied directly to TSH on 16/12/2023, following up again on 17/03/2024, with no response. Later developments revealed that NW was acting as an intermediary or &ldquo;gatekeeper&rdquo; for bookings at the hotel.<br />This added an element of irony and frustration, as none of the later issues would likely have arisen had communication been handled directly between the artist and venue.<br />On 04/06/2025, following a last-minute unpaid video shoot request from NW (accepted by RD as a goodwill gesture), NW invited Nova Boss to perform at the hotel&rsquo;s Sunday sessions.<br />RD submitted a list of available Sundays (June&ndash;August 2025) on 05/06/2025. NW confirmed 15 June and 29 June as available. On 06/06/2025, RD confirmed both dates for Nova Boss.<br />At 00:48 on 07/06/2025, NW messaged to say that 29 June had now been given to another musician (&ldquo;RG&rdquo;), but asked RD to confirm 15 June instead. This caused confusion and raised doubts about the reliability of the arrangements, as both dates had previously been confirmed.<br />Following this inconsistency and perceived lack of professional clarity, RD withdrew from the engagements on 07/06/2025 to protect Nova Boss&rsquo;s integrity and mental wellbeing.<br />NW later denied cancelling or mishandling bookings, but by that point the trust and working relationship had broken down.<br /><br />Action Taken<br />RD formally withdrew from all current and future bookings with NW / SVA on 07/06/2025.<br />Communications were documented and retained.<br />No public statement was made, and all interactions remained courteous to avoid reputational damage.<br />Subsequent related invitations (e.g., via RG or mutual contacts) were declined to maintain professional boundaries.<br /><br />Resolutions<br />Withdrawal communicated clearly and respectfully.<br />No fees exchanged; no financial obligations outstanding.<br />Matter closed without escalation or conflict.<br />Nova Boss to pursue bookings directly with venues to ensure professionalism, clarity, and emotional safety.<br /><br />Notes Comments<br />Initial direct contact with TSH (Dec 2023 and Mar 2024) predates the involvement of NW. The later &ldquo;gatekeeping&rdquo; dynamic created unnecessary barriers, confusion, and distress.<br />The inconsistency between confirmed dates and final allocations undermined confidence and contributed to emotional fatigue.<br />The unpaid nature of the 04/06/2025 video shoot, coupled with informal communication practices, further reinforced the perception of disorganisation and lack of respect for artists&rsquo; time.<br />This incident highlights the importance of transparent, direct communication between artists and venues. Delegating coordination to a third party without structure or accountability can lead to misunderstandings, unacknowledged labour, and emotional strain.<br />Nova Boss acted in good faith throughout, maintaining professionalism and goodwill. The experience has underscored the value of boundaries, self-respect, and direct relationships when managing live music engagements.<br />While regrettable, this outcome ultimately strengthened Nova Boss&rsquo;s resolve to uphold fair working practices and protect creative wellbeing.<br /><br />Reported<br />Reported Date: 20/10/2025<br />Reported By (Individual): RD<br />Reported By (Organisation): R&amp;BM<br /><br />INDIVIDUALS<br /><br />Responsible, Responsive, NW, Client<br />To manage bookings and communicate transparently<br /><br />Observer, Responsive, NK, Guitar<br />Consulted for availability<br /><br />Involved, Passive, RG, Artist<br />Accepted alternate 29 June booking<br /><br />Impacted, Active, RD, Artist<br />To confirm availability and uphold professional standards<br /><br />ORGANISATIONS<br /><br />JS<br />Promoter responsible for booking live jazz.<br /><br />TSH<br />Venue hosting live jazz.</div>]]></content:encoded></item><item><title><![CDATA[Accidental cancellation and reinstatement]]></title><link><![CDATA[http://redandblackmusic.weebly.com/incidents/accidental-cancellation-and-reinstatement]]></link><comments><![CDATA[http://redandblackmusic.weebly.com/incidents/accidental-cancellation-and-reinstatement#comments]]></comments><pubDate>Mon, 20 Oct 2025 08:44:30 GMT</pubDate><category><![CDATA[Agreements]]></category><guid isPermaLink="false">http://redandblackmusic.weebly.com/incidents/accidental-cancellation-and-reinstatement</guid><description><![CDATA[    On Wed, 1 Oct 2025 at 11:17, RD wrote:Hi JMO,No problem at all, happy to reinstate! Let me know if you need to chat through anything regarding the contract, deposit, or if you need any further details added in there.Thanks,RD&#8203;On 1 Oct 2025, at 11:13, JMO wrote:I will send all final details over this evening Thankyou&nbsp;Begin forwarded message:From: "JMO"Subject: Re: Contract - RD - 18/10/2025Date: 1 October 2025 at 11:12:37 BSTTo: RDHi RD I&rsquo;m so sorry I didn&rsquo;t mean to can [...] ]]></description><content:encoded><![CDATA[<div>  <!--BLOG_SUMMARY_END--></div>  <blockquote>On Wed, 1 Oct 2025 at 11:17, RD wrote:<br />Hi JMO,<br />No problem at all, happy to reinstate! Let me know if you need to chat through anything regarding the contract, deposit, or if you need any further details added in there.<br />Thanks,<br />RD<br />&#8203;<br />On 1 Oct 2025, at 11:13, JMO wrote:<br />I will send all final details over this evening Thankyou&nbsp;<br /><br />Begin forwarded message:<br />From: "JMO"<br />Subject: Re: Contract - RD - 18/10/2025<br />Date: 1 October 2025 at 11:12:37 BST<br />To: RD<br />Hi RD I&rsquo;m so sorry I didn&rsquo;t mean to cancel this booking I mistook your email for a venue booking I previously booked, I definitely still want you to play at the baby shower on the 18th please&nbsp;<br /><br />On Wednesday, October 1, 2025, JMO &nbsp;wrote:<br />Hi I&rsquo;m sorry I&rsquo;d like to cancel this booking, sorry for the inconvenience&nbsp;<br /><br />On Monday, September 29, 2025, RD wrote:<br />Hi JMO,<br />I hope you enjoyed your weekend.<br />Please find attached and below contract for the event on 18/10/2025.<br />Please do take a look and let me know if any adjustments are needed. Once happy, you can either reply to the e-mail with written confirmation, or sign the attached PDF.<br />I have also attached an invoice for the deposit payment.<br />Anything else you need, please feel free to let me know!<br />Thanks,<br />RD</blockquote>  <div class="paragraph" style="text-align:left;">&#8203;Title<br />Accidental cancellation and reinstatement<br /><br />Description<br />On 29/09/2025, RD issued the performance contract and invoice for the event RD @ The Courts, Penarth, Cardiff &ndash; 18/10/2025, to client JMO &nbsp;O&rsquo;Sullivan. The booking included live saxophone performance for a baby shower, scheduled 18:00&ndash;21:00, with a total fee of &pound;350 and a 50% deposit payable to secure the engagement.<br />On 01/10/2025 at 11:09, JMO emailed to cancel the booking, writing, &ldquo;Hi I&rsquo;m sorry I&rsquo;d like to cancel this booking, sorry for the inconvenience.&rdquo; Later that morning, at 11:12, she followed up to explain the cancellation had been made in error, stating, &ldquo;Hi RD I&rsquo;m so sorry I didn&rsquo;t mean to cancel this booking, I mistook your email for a venue booking I previously booked, I definitely still want you to play at the baby shower on the 18th please.&rdquo;<br />RD promptly reinstated the booking, replying at 11:17, &ldquo;Hi JMO, No problem at all, happy to reinstate! Let me know if you need to chat through anything regarding the contract, deposit, or if you need any further details added in there.&rdquo; JMO responded later that day at 11:13 to confirm she would send over final details that evening.<br />On 03/10/2025 at 14:15, JMO confirmed the deposit had been paid, writing, &ldquo;Hi RD that all sounds perfect, I&rsquo;ve sent over the deposit just now, it would have come from an account jmo studio. Thanks, Jmosullivan.&rdquo; This payment officially reinstated and secured the booking.<br /><br />Action Taken<br />Upon receiving the accidental cancellation, RD maintained professionalism and responded immediately to clarify and reinstate the booking without penalty or issue. The artist ensured all contract and deposit terms were still valid, re-confirming the details in writing to maintain the paper trail and uphold the original agreement. The reinstatement was successfully processed within the same day.<br /><br />Resolutions<br />The matter was fully resolved, and the booking was reinstated without disruption. The client paid the deposit and the performance proceeded as planned on 18/10/2025. Both parties maintained positive communication thereafter.<br /><br />Notes Comments<br />Clients occasionally make administrative errors when managing multiple bookings. It is advisable to request written confirmation before acting upon any cancellation notice to avoid unnecessary confusion or lost work. Maintaining professionalism and immediate clarification helps preserve client relationships and ensures contractual consistency.<br /><br />Reported<br />Reported Date: 20/10/2025<br />Reported By (Individual): RD<br />Reported By (Organisation): R<br /><br />INDIVIDUALS<br /><br />Responsible, Active, JMO, Client<br />Event organisation, payment, communication of booking changes<br /><br />Impacted, Active, RD, Artist<br />Contract management, booking administration, client communication</div>]]></content:encoded></item><item><title><![CDATA[Last minute change of finish time]]></title><link><![CDATA[http://redandblackmusic.weebly.com/incidents/last-minute-change-of-finish-time]]></link><comments><![CDATA[http://redandblackmusic.weebly.com/incidents/last-minute-change-of-finish-time#comments]]></comments><pubDate>Mon, 20 Oct 2025 08:42:57 GMT</pubDate><category><![CDATA[Extended]]></category><guid isPermaLink="false">http://redandblackmusic.weebly.com/incidents/last-minute-change-of-finish-time</guid><description><![CDATA[    &#8203;Hi rory it&rsquo;s J, I booked you for the 18th October,&nbsp;I&rsquo;m so sorry I&rsquo;m rubbish at communicating over email, I did look over your set lists, I absolutely love set 3 but is it possible to take a few songs out of it? Also I booked a dj to start at 8:30 so I only need you to play till then if that&rsquo;s ok? x  TitleLast minute change of finish timeDescriptionRD arrived at The Courts, Penarth, Cardiff at 15:30 and completed set-up and sound check in preparation for a  [...] ]]></description><content:encoded><![CDATA[<div>  <!--BLOG_SUMMARY_END--></div>  <blockquote>&#8203;Hi rory it&rsquo;s J, I booked you for the 18th October,&nbsp;<br />I&rsquo;m so sorry I&rsquo;m rubbish at communicating over email, I did look over your set lists, I absolutely love set 3 but is it possible to take a few songs out of it? Also I booked a dj to start at 8:30 so I only need you to play till then if that&rsquo;s ok? x</blockquote>  <div class="paragraph" style="text-align:left;">Title<br />Last minute change of finish time<br /><br />Description<br />RD arrived at The Courts, Penarth, Cardiff at 15:30 and completed set-up and sound check in preparation for a confirmed performance start time of 18:00 and finish time of 21:00, as agreed in the show advance and contract email correspondence (29/09/2025, 04/10/2025, and 13/10/2025).<br />At 16:47, while waiting to begin, RD was approached by the client, J, who requested, &ldquo;Can you start now?&rdquo; The artist complied, beginning the performance at 16:47 despite the confirmed start time being two hours later. The client also verbally advised that the performance would now conclude at 18:30 instead of 21:00.<br />The original email correspondence had clearly stated and reconfirmed the start and finish times in writing. The client had not provided any written notice of changes before the day of the event. This last-minute adjustment also rendered previously booked accommodation unnecessary, resulting in additional cost.<br />J had earlier messaged via WhatsApp on 07/10/2025, stating, &ldquo;Hi RD it&rsquo;s J, I booked you for the 18th October, I&rsquo;m so sorry I&rsquo;m rubbish at communicating over email, I did look over your set lists, I absolutely love set 3 but is it possible to take a few songs out of it? Also I booked a DJ to start at 8:30 so I only need you to play till then if that&rsquo;s ok? x&rdquo;<br /><br />Action Taken<br />RD was early and therefore able to comply with the client&rsquo;s request to begin the performance immediately. The artist commenced at 16:47 and played continuously until 18:30, ensuring the event proceeded smoothly despite the unplanned change.<br /><br />Resolutions<br />The performance was completed successfully, and the client expressed positive verbal feedback on the day. No disruption occurred to the event itself, though the artist incurred avoidable costs due to the timing alteration.<br /><br />Notes Comments<br />Future show advance email templates should include stricter wording to emphasise that clients must confirm all performance times and event details in writing prior to the event. This will mitigate confusion and ensure accountability. Clients should also be made aware that last-minute changes cannot always be accommodated, and artists cannot be held responsible for issues arising from unconfirmed or ignored correspondence.<br /><br />Reported<br />Reported Date: 20/10/2025<br />Reported By (Individual): RD<br />Reported By (Organisation): R<br /><br />INDIVIDUALS<br /><br />Responsible, Responsive, JMO, Client<br />Communicating event timings and managing entertainment schedule<br /><br />Impacted, Active, RD, Artist<br />Adhering to confirmed booking terms, delivering performance</div>]]></content:encoded></item><item><title><![CDATA[Accommodation booked when one not needed]]></title><link><![CDATA[http://redandblackmusic.weebly.com/incidents/accommodation-booked-when-one-not-needed]]></link><comments><![CDATA[http://redandblackmusic.weebly.com/incidents/accommodation-booked-when-one-not-needed#comments]]></comments><pubDate>Mon, 20 Oct 2025 08:38:01 GMT</pubDate><category><![CDATA[Hotels]]></category><guid isPermaLink="false">http://redandblackmusic.weebly.com/incidents/accommodation-booked-when-one-not-needed</guid><description><![CDATA[    Hi rory it&rsquo;s J, I booked you for the 18th October,I&rsquo;m so sorry I&rsquo;m rubbish at communicating over email, I did look over your set lists, I absolutely love set 3 but is it possible to take a few songs out of it? Also I booked a dj to start at 8:30 so I only need you to play till then if that&rsquo;s ok? x  TitleAccommodation booked when one not needed.DescriptionArtist was originally booked for a performance from 18:00&ndash;21:00 in Cardiff on 18/10/2025. Under the original  [...] ]]></description><content:encoded><![CDATA[<div>  <!--BLOG_SUMMARY_END--></div>  <blockquote>Hi rory it&rsquo;s J, I booked you for the 18th October,<br /><span></span>I&rsquo;m so sorry I&rsquo;m rubbish at communicating over email, I did look over your set lists, I absolutely love set 3 but is it possible to take a few songs out of it? Also I booked a dj to start at 8:30 so I only need you to play till then if that&rsquo;s ok? x<br /><span></span></blockquote>  <div class="paragraph" style="text-align:left;">Title<br />Accommodation booked when one not needed.<br /><br />Description<br />Artist was originally booked for a performance from 18:00&ndash;21:00 in Cardiff on 18/10/2025. Under the original conditions, the last train back to Gloucester would have been missed. However, new train times appeared on the Trainline app closer to the gig date, which would have allowed same-day travel. The issue was exacerbated when the client, J, messaged via WhatsApp on 07/10/2025 saying, &ldquo;Hi RD, it&rsquo;s J, I booked you for the 18th October, I&rsquo;m so sorry I&rsquo;m rubbish at communicating over email, I did look over your set lists, I absolutely love set 3 but is it possible to take a few songs out of it? Also I booked a DJ to start at 8:30 so I only need you to play till then if that&rsquo;s ok? x&rdquo; The client had not been responding to show advance emails.<br />A flexible accommodation rate was booked for &pound;34, which enabled cancellation up to two days before. On the day of the event, the artist was verbally informed that the new performance start time was 16:30 and the finish time 18:30. This change had not been communicated in advance. The artist was already on site, set up and sound-checked, and therefore able to comply. The new timing made overnight accommodation unnecessary.<br />The artist attended the accommodation in person on the day to request cancellation. Reception made several phone calls to five different managers; eventually, one manager advised that the booking was non-refundable at that stage. The artist therefore incurred a &pound;34 loss for the accommodation, and an additional &pound;7 loss for having purchased an open return train ticket rather than a cheaper day return.<br /><br />Action Taken<br />The artist had originally chosen the flexible rate at &pound;2 more than the non-refundable rate to allow for possible schedule changes. Upon learning the revised gig timings, the artist approached reception to enquire about cancelling, aware from the terms and conditions that it was unlikely to be possible. Reception initially appeared to be arranging a refund authorisation but, following contact with a manager, confirmed that the booking could not be refunded. The artist therefore complied with the accommodation terms and initially decided to make use of the room.<br /><br />Resolutions<br />After confirming the earlier finish time of 18:30, the artist collected belongings and caught the 20:22 train home to Gloucester, accepting the incurred costs as a learning experience. For the next booking on 15/11/2025 in Kingston-upon-Thames (finishing 21:00, after the last train home), the artist has opted to stay up overnight and travel back on the 06:00 coach to offset previous losses.<br /><br />Notes Comments<br />Do not book accommodation until the day of the gig, and if possible, only after the performance has commenced. Clients can be unreliable or uncommunicative, and may alter event details at short notice without warning. If advance accommodation is essential (e.g., for remote locations or group travel), continue to use flexible rates and confirm logistics before any cancellation deadlines.<br /><br />Reported<br />Reported Date: 20/10/2025<br />Reported By (Individual): RD<br />Reported By (Organisation): R<br /><br />INDIVIDUALS<br /><br />Responsible, Passive, JMO, Client<br />Communicating event details and schedule<br /><br />Responsible, Responsive, RD, Artist<br />Booking, travel, accommodation, performance</div>]]></content:encoded></item><item><title><![CDATA[Saxophone Damage Due to Microphone Attachment Incident – Pre-Show Equipment Failure]]></title><link><![CDATA[http://redandblackmusic.weebly.com/incidents/saxophone-damage-due-to-microphone-attachment-incident-pre-show-equipment-failure]]></link><comments><![CDATA[http://redandblackmusic.weebly.com/incidents/saxophone-damage-due-to-microphone-attachment-incident-pre-show-equipment-failure#comments]]></comments><pubDate>Sun, 29 Jun 2025 23:00:00 GMT</pubDate><category><![CDATA[Accidents]]></category><guid isPermaLink="false">http://redandblackmusic.weebly.com/incidents/saxophone-damage-due-to-microphone-attachment-incident-pre-show-equipment-failure</guid><description><![CDATA[    &#8203;TitleSaxophone Damage Due to Microphone Attachment Incident &ndash; Pre-Show Equipment FailureDescriptionOn the evening of Saturday 28th June 2025, approximately 30 minutes before the scheduled performance time, I experienced a critical equipment failure due to an incident involving my saxophone and attached microphone system.The microphone was securely mounted on my saxophone bell and connected to a wireless receiver unit, which was placed in my trouser pocket. While setting up at th [...] ]]></description><content:encoded><![CDATA[<div>  <!--BLOG_SUMMARY_END--></div>  <div class="paragraph" style="text-align:left;">&#8203;Title<br />Saxophone Damage Due to Microphone Attachment Incident &ndash; Pre-Show Equipment Failure<br /><br />Description<br />On the evening of Saturday 28th June 2025, approximately 30 minutes before the scheduled performance time, I experienced a critical equipment failure due to an incident involving my saxophone and attached microphone system.<br />The microphone was securely mounted on my saxophone bell and connected to a wireless receiver unit, which was placed in my trouser pocket. While setting up at the DJ booth, I temporarily placed my saxophone down without realising the microphone cable was still tethered to the receiver. As I walked away from the booth, the tether tightened and pulled the saxophone off the surface, causing it to fall forcefully to the ground. The instrument landed directly on the key stack and sustained significant structural and mechanical damage.<br />The saxophone is a Yamaha Professional Series Alto Saxophone, purchased new in 2023 for approximately &pound;2,000. The impact rendered the instrument unplayable.<br /><br />Action Taken<br />Upon assessing the damage and confirming the saxophone was inoperable, I immediately contacted fellow musician Oli , who was able to travel from Harrow and provide a backup soprano saxophone. This allowed me to fulfil the performance, albeit with a one-hour delay to the scheduled start time. I notified the agent and venue of the delay and coordinated soundcheck adjustments with the on-site technician to accommodate the substitute instrument.<br /><br />Resolutions<br />The gig was completed successfully using the loaned soprano saxophone. The damaged Yamaha instrument has since been sent to a specialist repair technician based in Germany for full assessment and potential restoration. The instrument is currently considered near-total loss pending the outcome of the inspection and quotation from the technician. I am in the process of contacting Insure4Music to initiate a claim.<br /><br />Notes Comments<br />Wireless microphone receiver units should never be physically connected to the player&rsquo;s clothing or person without a quick-release or slack system in place.<br />Future setups should include either:<br />A stand-mounted microphone to eliminate any physical tethering risk, or<br />A harness or strap-mounted receiver with a secured cable loop to prevent the instrument from being dragged.<br />It is recommended that all band members conduct a pre-show gear safety check to ensure wireless connections are safely routed and instruments are secure when not in use.<br />Insurance documentation should be reviewed annually to ensure all high-value items are listed and current proof of ownership is retained.<br /><br />Reported<br />Reported Date: 30/06/2025<br />Reported By (Individual): RD<br />Reported By (Organisation): R<br /><br />INDIVIDUALS<br /><br />Involved, Responsive, JB, Agent<br />Provided encouragement and reassurance.<br /><br />Involved, Active, OS, Soprano Sax<br />Came at short notice with a loan instrument and saved the gig.<br /><br />Responsible, Active, RD, Alto Sax<br />Caused the accident and managed to source an alternative instrument.</div>  <blockquote>Hi. My microphone was on the sax. The receiver was in my pocket. I put the sax down on the Dj booth and walked away not realising they were still attached. The sax went down, right on the keypad. It&rsquo;s a new sax. This happened 30 min before showtime. &pound;2K practically a write off. Won&rsquo;t play.<br /><span></span></blockquote>]]></content:encoded></item><item><title><![CDATA[Difficulty Securing Percussionist for 11/05/2025 Gig]]></title><link><![CDATA[http://redandblackmusic.weebly.com/incidents/difficulty-securing-percussionist-for-11052025-gig]]></link><comments><![CDATA[http://redandblackmusic.weebly.com/incidents/difficulty-securing-percussionist-for-11052025-gig#comments]]></comments><pubDate>Sat, 10 May 2025 07:45:31 GMT</pubDate><category><![CDATA[Availability]]></category><guid isPermaLink="false">http://redandblackmusic.weebly.com/incidents/difficulty-securing-percussionist-for-11052025-gig</guid><description><![CDATA[    &#8203;Hi all!&#128075; do we know any cajon players who might be up for joining us on Sunday?Date: 11/05/2025Time: 13:00-16:30Venue: SH, GL5 3APRepertoire: Bossa NovaThanks, RD  TitleDifficulty Securing Percussionist for 11/05/2025 GigDescriptionEfforts to secure a suitable percussionist for the 11/05/2025 SH gig were unsuccessful until the final stages of preparation, due to short notice, stylistic requirements (Bossa Nova), venue constraints (small space &ndash; cajon preferred over drum  [...] ]]></description><content:encoded><![CDATA[<div>  <!--BLOG_SUMMARY_END--></div>  <blockquote>&#8203;Hi all!&#128075; do we know any cajon players who might be up for joining us on Sunday?<br />Date: 11/05/2025<br />Time: 13:00-16:30<br />Venue: SH, GL5 3AP<br />Repertoire: Bossa Nova<br />Thanks, RD</blockquote>  <div class="paragraph" style="text-align:left;">Title<br />Difficulty Securing Percussionist for 11/05/2025 Gig<br /><br />Description<br />Efforts to secure a suitable percussionist for the 11/05/2025 SH gig were unsuccessful until the final stages of preparation, due to short notice, stylistic requirements (Bossa Nova), venue constraints (small space &ndash; cajon preferred over drum kit), and low fees. Numerous contacts and networks were activated without success until a referral from DS resulted in a last-minute booking of SM.<br /><br />Action Taken<br />Contacted multiple percussionists and drummers, including PB, AY, MF , SRl, JB, Richard Brooke, and CC.<br />Sought local recommendations from JA (Stroud Forr&oacute; &ndash; no response), TS (S SMba &ndash; responsive), and JS&rsquo;s JS (provided contact info).<br />Engaged via the SVA Jazz JS Musicians WhatsApp group and Stroud Music Facebook group.<br />Reached out to several pianists (TC, DT, PB ) &ndash; all unavailable &ndash; leading RD to cover piano duties and switch between piano and flute.<br />NK (guitarist) provided SRl&rsquo;s details.<br />Public posting led to a lead from RG, who recommended Richard Brooke (ultimately unsuitable).<br />Final successful recommendation came via DS, who circulated the need among folk contacts, leading to SM being booked.<br /><br />Resolutions<br />SM was confirmed on cajon to support the Bossa Nova and Latin material, resolving the gap with a musically suitable solution.<br />RD covered piano duties due to unavailability of others, rotating between piano and flute as needed.<br /><br />Notes Comments<br />Fee of &pound;30 was a significant barrier in recruiting capable, committed musicians at short notice.<br />Lack of clarity from promoter NW created uncertainty around confirmation and financial accountability.<br />RD has begun compiling a local database of percussionists and pianists to streamline future bookings.<br />For future gigs: RD intends to ask for clear confirmation from NW in writing, and offer musicians a top-up fee from his business funds, bringing total pay to a fairer rate (target: &pound;50 minimum).<br />This incident revealed a weakness in short-notice contingency planning and the importance of cultivating reliable, style-appropriate local contacts.<br /><br />Reported<br />Reported Date: 10/05/2025<br />Reported By (Organisation): R&amp;BM<br /><br />INDIVIDUALS<br /><br />Involved, Responsive, AY, Percussion<br />Unavailable, doesn't play cajon.<br /><br />Involved, Responsive, CC, Percussion<br />Unavailable, noted for future reference.<br /><br />Involved, Active, DS, Referrer<br />Instrumental in resolving the situation via folk network.<br /><br />Involved, Responsive, DT, Piano<br />Unavailable for piano, led to the decision of booking cajon instead.<br /><br />Involved, Responsive, F, Referrer<br />Conducted independent enquiries off RD's WhatsApp group callout.<br /><br />Involved, Responsive, JS, Referrer<br />Provided contact for CC to RD via Facebook.<br /><br />Involved, Responsive, JB, Percussion<br />Unavailable, doesn't play cajon.<br /><br />Involved, Passive, JA, Referrer<br />Didn't respond to RD's message on Facebook.<br /><br />Involved, Responsive, MC, Percussion<br />Unavailable, noted for future reference.<br /><br />Observer, Passive, MF, Bass<br />Not involved in fixing process but another member of band.<br /><br />Observer, Passive, NW, Promoter<br />Responsible for venue and booking logistics, passive in resolving musician shortfall.<br /><br />Involved, Responsive, NK, Guitar<br />Contributor to personnel search (provided SR&rsquo;s contact).<br /><br />Involved, Responsive, PB, Percussion<br />Unavailable, doesn't play cajon but does play reduced kit setup. Also facilitated WhatsApp post.<br /><br />Involved, Responsive, PC, Piano<br />Initially didn't respond but later said unavailable for piano after percussionist was booked.<br /><br />Involved, Responsive, Percussion<br />Unsuitable, but expressed interest in joining for future.<br /><br />Involved, Responsive, RG, Referrer<br />Provided contact for Richard Brooke to RD via Facebook.<br /><br />Responsible, Active, RD, Bandleader<br />Responsible for assembling the band, managing communications and repertoire, active in solving the personnel issue.<br /><br />Involved, Active, SM,&nbsp;<br />Ultimately booked and responsible for live performance.<br /><br />Involved, Responsive, SR, Percussion<br />Unavailable, noted for future reference.<br /><br />Involved, Responsive, TS, Referrer<br />Engaged in Facebook messaging with RD regarding potential players.<br /><br />Involved, Responsive, TC, Piano<br />Unavailable for piano, led to the decision of booking cajon instead.<br /><br />ORGANISATIONS<br /><br />JJ<br />Contacted as a stakeholder for referrals.<br /><br />JS<br />Organising the 11/05/2025 gig.<br /><br />S<br />Contacted as a stakeholder for referrals.<br /><br />SFG<br />Contacted as a stakeholder for referrals.<br /><br />TSH<br />Hosting the 11/05/2025 gig.</div>]]></content:encoded></item><item><title><![CDATA[Double Booking at SH – Sunday 11/05/2025]]></title><link><![CDATA[http://redandblackmusic.weebly.com/incidents/double-booking-at-sh-sunday-11052025]]></link><comments><![CDATA[http://redandblackmusic.weebly.com/incidents/double-booking-at-sh-sunday-11052025#comments]]></comments><pubDate>Sat, 10 May 2025 07:21:54 GMT</pubDate><category><![CDATA[Communication]]></category><guid isPermaLink="false">http://redandblackmusic.weebly.com/incidents/double-booking-at-sh-sunday-11052025</guid><description><![CDATA[    &#8203;Hi NW,Just wanted to thank you for being so lovely and understanding about this Sunday, 11/05/2025. I&rsquo;m really sorry you and your musicians have been messed around&mdash;especially with some of them travelling from Ross-on-Wye. It&rsquo;s a frustrating situation for both of us.Had the roles been reversed, I would&rsquo;ve honoured my booking and paid my players regardless&mdash;so if any of your band members are out of pocket, please know I&rsquo;m on financial standby &#129312; [...] ]]></description><content:encoded><![CDATA[<div>  <!--BLOG_SUMMARY_END--></div>  <blockquote>&#8203;Hi NW,<br />Just wanted to thank you for being so lovely and understanding about this Sunday, 11/05/2025. I&rsquo;m really sorry you and your musicians have been messed around&mdash;especially with some of them travelling from Ross-on-Wye. It&rsquo;s a frustrating situation for both of us.<br />Had the roles been reversed, I would&rsquo;ve honoured my booking and paid my players regardless&mdash;so if any of your band members are out of pocket, please know I&rsquo;m on financial standby &#129312; (we both know the deal!). I&rsquo;d be more than happy to help&mdash;just send over your bank details if needed.<br />Really appreciate you handling this with such professionalism, grace, and kindness&mdash;as you did on Easter Day.<br />Rx</blockquote>  <div class="paragraph" style="text-align:left;">Title<br />Double Booking at SH &ndash; Sunday 11/05/2025<br /><br />Description<br />A scheduling conflict occurred for a performance slot at the <span>SH</span> on Sunday, 11 May 2025. Two bands&mdash;one led by RD and the other by NW&mdash;were both under the impression that they were booked for the same event. The conflict was only discovered days before the event, after RD spoke with NW directly. NW confirmed that she and her band, including musicians travelling from Ross-on-Wye, had also been expecting to play that date.<br />The confusion originated from a lack of formal confirmation or clear communication from NWSVA, the promoter and organiser for live music at the <span>SH</span>. Despite RD's previous preparations, rehearsals, communication and web listing for the gig, the booking was not properly confirmed by NWSVA to either party in writing. RD had been informed that the date was his; however, NW had also been verbally offered or led to believe the same.<br /><br />Action Taken<br />RD reached out to NW upon discovering the overlap.<br />NW proactively contacted NWSVA directly to clarify the situation and informed her group to stand down.<br />NW graciously deferred the performance to RD&rsquo;s group, given his prior understanding of the booking and preparation already undertaken.<br />RD offered financial compensation should any of NW&rsquo;s musicians be left out of pocket due to the cancellation.<br />NW confirmed with RD that she communicated the change to her group and agreed to perform on a future date (Sunday, 1 June 2025).<br />No direct communication was initiated with NWSVA by RD at this stage, to avoid potential escalation or tension.<br /><br />Resolutions<br />NW&rsquo;s band withdrew from the Sunday 11 May performance. RD&rsquo;s band will fulfil the engagement as originally understood. NW's band will take the following available date. RD offered to provide financial support for any out-of-pocket musicians in NW&rsquo;s band, though NW has not taken up the offer at this time.<br /><br />Notes Comments<br />The incident reflects a broader concern around unclear and inconsistent communication practices by the promoter.<br />The lack of a formal booking system or calendar appears to have contributed directly to the double booking.<br />This is not the first time issues of communication have occurred in this context, indicating a potential pattern.<br />RD expressed that, had the roles been reversed, he would have honoured the commitment to his musicians and covered their pay regardless.<br />The professionalism and tact shown by NW was instrumental in de-escalating the situation and should be acknowledged.<br />Clearer systems, written confirmations, and proper advance communication are necessary to avoid future incidents of this nature.<br /><br />Reported<br />Reported Date: 10/05/2025<br />Reported By (Individual): RD<br />Reported By (Organisation): R&amp;BM<br /><br />INDIVIDUALS<br /><br />Impacted, Responsive, JC, Tenor Sax<br />Saxophonist in NW&rsquo;s band, potentially impacted by the cancellation.<br /><br />Responsible, Passive, NWSVA, Promoter<br />Responsible for booking and coordinating live music events at the <span>SH</span>.<br /><br />Impacted, Responsive, NK, Guitar<br />Guitarist in RD&rsquo;s band, scheduled to perform on 11/05/2025.<br /><br />Impacted, Active, NW, Bandleader<br />Bandleader originally expecting to perform, responsible for managing her ensemble and resolving the scheduling conflict.<br /><br />Impacted, Active, RD, Bandleader<br />Bandleader responsible for assembling, preparing, and delivering the performance on 11/05/2025.<br /><br />&#8203;ORGANISATIONS<br /><br />JS<br />Organising the 11/05/2025 gig.<br /><br />TSH<br />Hosting the 11/05/2025 gig.</div>]]></content:encoded></item><item><title><![CDATA[Lack of Acknowledgement Resulting in On-the-Day Lineup Conflict – 20/04/2025 Gig]]></title><link><![CDATA[http://redandblackmusic.weebly.com/incidents/lack-of-acknowledgement-resulting-in-on-the-day-lineup-conflict-20042025-gig]]></link><comments><![CDATA[http://redandblackmusic.weebly.com/incidents/lack-of-acknowledgement-resulting-in-on-the-day-lineup-conflict-20042025-gig#comments]]></comments><pubDate>Tue, 06 May 2025 15:03:30 GMT</pubDate><category><![CDATA[Communication]]></category><guid isPermaLink="false">http://redandblackmusic.weebly.com/incidents/lack-of-acknowledgement-resulting-in-on-the-day-lineup-conflict-20042025-gig</guid><description><![CDATA[    Group chat:[13:49, 11/04/2025] NWSVA: MF can do Sunday with D on keys so could have L, D RD to join[13:57, 11/04/2025] +44: I cant play sunday unfortunately[13:57, 11/04/2025] DL: Neither[13:58, 11/04/2025] RD : Same time arrive 12:30, and then start 13:00?[17:11, 11/04/2025] +44: if this is the 17th and 20th, i can do?[08:27, 13/04/2025] RD : Bit confused. Is there a gig today?Or is it next Sunday?[10:00, 13/04/2025] NWSVA: It didn&rsquo;t work out with getting confirmation so will arrange  [...] ]]></description><content:encoded><![CDATA[<div>  <!--BLOG_SUMMARY_END--></div>  <blockquote>Group chat:<br />[13:49, 11/04/2025] NWSVA: MF can do Sunday with D on keys so could have L, D RD to join<br />[13:57, 11/04/2025] +44: I cant play sunday unfortunately<br />[13:57, 11/04/2025] DL: Neither<br />[13:58, 11/04/2025] RD : Same time arrive 12:30, and then start 13:00?<br />[17:11, 11/04/2025] +44: if this is the 17th and 20th, i can do?<br />[08:27, 13/04/2025] RD : Bit confused. Is there a gig today?<br />Or is it next Sunday?<br />[10:00, 13/04/2025] <span>NWSVA</span>: It didn&rsquo;t work out with getting confirmation so will arrange another Sunday. Managed to get someone else to fill the slot<br />&#8203;[14:31, 13/04/2025] RD : Am in London this week so can&rsquo;t do Thursday 17/04/2025, but some other Thursdays will be possible.<br />Can definitely do next Sunday 20/04/2025, I can bring+play sax+flute, and I could play piano. Time 12:30 arrive / 13:00 start.<br />[15:04, 13/04/2025] <span>NWSVA</span>: Ok I&rsquo;ll be in touch tomorrow and we can work on fixing dates in calendar<br />[15:12, 13/04/2025] RD : Ok thank you<br />[22:00, 17/04/2025] RD : Back from London now<br />see you on Sunday 20/04/2025 at 12:30 SH<br />[12:23, 20/04/2025] RD : I&rsquo;m here with NW<br />[12:29, 20/04/2025] <span>NWSVA</span>: Yes NW is booked in for today so I&rsquo;m a bit confused. Did she get in touch with you RD<br />[12:31, 20/04/2025] RD : She said come join anyway as I was under the impression I was booked &#128070;<br />&#8203;<br />NW chat:<br />[12:27, 20/04/2025] NW SVA: Are you playing with NW today. I&rsquo;m a bit confused<br />[12:32, 20/04/2025] RD : Yes she just said I could join her, as i&rsquo;d turned up</blockquote>  <div class="paragraph" style="text-align:left;">Title<br />Lack of Acknowledgement Resulting in On-the-Day Lineup Conflict &ndash; 20/04/2025 Gig<br /><br />Description<br />RD declared his availability for 20 April 2025 twice in the WhatsApp group but received no response from <span>NWSVA</span>. With no definitive confirmation or rejection, and recalling the prior week&rsquo;s issue, RD attended the SH gig to ensure he wasn&rsquo;t again left out of a gig he may have been expected at. Upon arrival, he found that NW&rsquo;s band had already been booked. NW, acknowledging the situation, kindly invited RD to join her group. He performed and was paid for the event.<br /><br />Action Taken<br />RD clarified his presence with NW, who accommodated him. RD&rsquo;s mother, who attended, proactively explained the confusion to NW before NW arrived, helping avoid tension.<br /><br />Resolutions<br />Although RD was not officially booked, NW&rsquo;s inclusive approach resolved the situation gracefully. <span>NWSVA</span> was confused by RD&rsquo;s attendance, underscoring the issue: lack of clear communication or confirmation. RD now understands that appearing unconfirmed risks confusion and must be avoided unless expressly booked by <span>NWSVA</span>.<br /><br />Notes Comments<br />The lack of any direct response to multiple confirmation attempts by RD was the root of this issue. Going forward, RD will only attend if explicitly confirmed by <span>NWSVA</span> or the appointed bandleader. NW&rsquo;s professional handling prevented escalation.<br /><br />Reported<br />Reported Date: 06/05/2025<br />Reported By (Individual): RD<br />Reported By (Organisation): R<br /><br />INDIVIDUALS<br /><br />Involved, Active, KD, Advisor<br />Explained the lack of communication to NW on arrival.<br /><br />Responsible, Passive, <span>NWSVA</span>, Promoter<br />Failed to acknowledge or negate RD's communications via WhatsApp group.<br /><br />Impacted, Active, NW, Bandleader<br />Didn't book RD for the event but understood the lack of communication and invited him to join regardless.<br /><br />Observer, Passive, PD, Advisor<br />Not there on the 20/04/2025 but supported assertion that an enquiry constituted a confirmation.<br /><br />Impacted, Active, RD, Alto Sax<br />Under the impression that he was booked and turned up at the event, honouring commitment.<br /><br />ORGANISATIONS<br /><br />JS<br />Promoter booking musicians for the events.<br /><br />TSH<br />Venue hosting the live music.</div>]]></content:encoded></item><item><title><![CDATA[Misinterpretation of Booking Format – Band-Based vs. Individual Engagements]]></title><link><![CDATA[http://redandblackmusic.weebly.com/incidents/misinterpretation-of-booking-format-band-based-vs-individual-engagements]]></link><comments><![CDATA[http://redandblackmusic.weebly.com/incidents/misinterpretation-of-booking-format-band-based-vs-individual-engagements#comments]]></comments><pubDate>Tue, 06 May 2025 15:02:31 GMT</pubDate><category><![CDATA[Communication]]></category><guid isPermaLink="false">http://redandblackmusic.weebly.com/incidents/misinterpretation-of-booking-format-band-based-vs-individual-engagements</guid><description><![CDATA[    [23:29, 10/04/2025] NWSVA: There are slots for live music at SH Thursdays and Sundays. I know it&rsquo;s short notice but there&rsquo;s a slot this Sunday? 1 till 4 two one hour sets with lunch in between plus &pound;[amount] each or Thursday &pound;[amount] each 7 til 10.30  TitleMisinterpretation of Booking Format &ndash; Band-Based vs. Individual EngagementsDescriptionOn 11 April 2025, RD responded to a WhatsApp message from promoter NWSVA offering a Sunday slot at SH. RD expressed availa [...] ]]></description><content:encoded><![CDATA[<div>  <!--BLOG_SUMMARY_END--></div>  <blockquote>[23:29, 10/04/2025] <span>NWSVA</span>: There are slots for live music at SH Thursdays and Sundays. I know it&rsquo;s short notice but there&rsquo;s a slot this Sunday? 1 till 4 two one hour sets with lunch in between plus &pound;[amount] each or Thursday &pound;<span>[amount]</span> each 7 til 10.30</blockquote>  <div class="paragraph" style="text-align:left;">Title<br />Misinterpretation of Booking Format &ndash; Band-Based vs. Individual Engagements<br /><br />Description<br />On 11 April 2025, RD responded to a WhatsApp message from promoter <span>NWSVA</span> offering a Sunday slot at SH. RD expressed availability and asked logistical questions, understanding&nbsp;<span>NWSVA</span> was assembling a lineup as he had during the first edition of the residency. <span>NWSVA</span> later indicated that MF and Dom were confirmed, suggesting RD and others could join. RD interpreted this as a confirmation of involvement. However, no further communication from <span>NWSVA</span> followed. On the day (13 April), RD checked in and was told someone else had been booked. RD&rsquo;s parents, assuming <span>NWSVA</span>&rsquo;s message was a confirmation, advised RD that he should have simply turned up &mdash; possibly missing a gig that MF&rsquo;s group may have expected him at.<br /><br />Action Taken<br />RD followed up in the chat with two messages of availability for 20 April 2025 but received no acknowledgement. Learning from the previous week, he turned up on the 20th to avoid missing a potential opportunity.<br /><br />Resolutions<br />It became clear that <span>NWSVA</span> is now booking pre-existing lineups rather than assembling bands on the fly. RD's parents had incorrectly interpreted <span>NWSVA</span>&rsquo;s earlier approach (from the scratch band in the first edition) as ongoing practice. The assumption that <span>NWSVA</span> was putting together a group, rather than confirming existing ensembles, led to the misunderstanding.<br /><br />Notes Comments<br />Going forward, RD now understands that <span>NWSVA</span> is booking full bands, and he must ensure he is part of a pre-confirmed lineup before assuming a booking. Passive or ambiguous messaging should not be treated as confirmation.<br /><br />Reported<br />Reported Date: 06/05/2025<br />Reported By (Individual): RD<br />Reported By (Organisation): R<br /><br />INDIVIDUALS<br /><br />Involved, Responsive, KD, Advisor<br />Incorrectly interpreted <span>NWSVA</span>'s message as <span>NWSVA</span> putting together a lineup rather than booking existing lineups. Misinterpretation was carried forward by RD when he turned up on 20/04/2025.<br /><br />Observer, Passive, MF, Bandleader<br />Had his own lineup for the 13/04/2025 event.<br /><br />Responsible, Passive, <span>NWSVA</span>, Promoter<br />Responsible for booking lineups/musicians for the SH residency.<br /><br />Involved, Responsive, PD, Advisor<br />Incorrectly interpreted <span>NWSVA</span>'s message as <span>NWSVA</span> putting together a lineup rather than booking existing lineups. Misinterpretation was carried forward by RD when he turned up on 20/04/2025.<br /><br />Impacted, Responsive, RD, Alto Sax<br />Confused about whether <span>NWSVA</span> was requesting RD as a solo musician, or as a lineup.<br /><br />ORGANISATIONS<br /><br />JS<br />Promoter booking musicians for the events.<br /><br />TSH<br />Venue hosting the live music.</div>]]></content:encoded></item><item><title><![CDATA[House System / Amplification Issue — 04/05/2025]]></title><link><![CDATA[http://redandblackmusic.weebly.com/incidents/house-system-amplification-issue-04052025]]></link><comments><![CDATA[http://redandblackmusic.weebly.com/incidents/house-system-amplification-issue-04052025#comments]]></comments><pubDate>Tue, 06 May 2025 11:53:37 GMT</pubDate><category><![CDATA[Sound]]></category><guid isPermaLink="false">http://redandblackmusic.weebly.com/incidents/house-system-amplification-issue-04052025</guid><description><![CDATA[    &#8203;[15:28, 04/05/2025] RD: Hey BH,Just a quick one &mdash; I&rsquo;ve arrived at the venue and they mentioned they&rsquo;d prefer me to go through the house system. That wasn&rsquo;t communicated to me, and as per our messages&#128070;, I brought my amp specifically for today and have been lugging it around for the last couple of days. &#128517;I explained this is my 4th time playing here &mdash; the 1st time back in August, the house system wasn&rsquo;t compatible with my setup, so I us [...] ]]></description><content:encoded><![CDATA[<div>  <!--BLOG_SUMMARY_END--></div>  <blockquote>&#8203;[15:28, 04/05/2025] RD: Hey BH,<br />Just a quick one &mdash; I&rsquo;ve arrived at the venue and they mentioned they&rsquo;d prefer me to go through the house system. That wasn&rsquo;t communicated to me, and as per our messages&#128070;, I brought my amp specifically for today and have been lugging it around for the last couple of days. &#128517;<br />I explained this is my 4th time playing here &mdash; the 1st time back in August, the house system wasn&rsquo;t compatible with my setup, so I used my amp. The 3rd time I did go through the house system, but it ended up way too quiet and I struggled to hear the backing tracks properly. So bringing the amp today was a conscious choice.<br />That said, all good from my end &mdash; the girl here seemed chilled and didn&rsquo;t say I couldn&rsquo;t use my own (wireless) gear. Just wanted to keep you in the loop i&hellip;<br />[15:31, 04/05/2025] RD: The convo: I (80% sure!) convinced her that it&rsquo;s fully projecting and I can move around depending on where the guests are. She said something a bit vague about checking, but didn&rsquo;t seem too fussed. I didn&rsquo;t show her our messages &mdash; just said you&rsquo;d asked me to bring it.</blockquote>  <div class="paragraph" style="text-align:left;">Title<br />House System / Amplification Issue &mdash; 04/05/2025<br /><br />Description<br />On 04/05/2025, at 22C(Bristol), RD was booked to perform a solo saxophone set with backing tracks via his own battery-powered amplifier, as had been agreed upon in correspondence with the booking agent (BH, HP). Upon arrival at 3:00pm, a venue staff member (barmaid, identity TBC) queried whether he would use the in-house sound system instead.<br />This request was not pre-communicated by the agent or client (E), and contradicted prior messages confirming the artist would bring his own amplification. The artist shared that he had deliberately brought his own amp based on prior performance experience at the venue, where the house system was either incompatible or underpowered.<br />Following a brief discussion with the barmaid, RD proceeded with his own equipment, which was deemed acceptable on the day.<br /><br />Action Taken<br />RD clarified his technical setup and previous experience with the venue's system.<br />He explained that he had brought and intended to use his own wireless, portable amplifier.<br />The waitress indicated she would &ldquo;check,&rdquo; but did not object, and later confirmed she was happy with the setup part-way through the event.<br />RD proceeded with the performance using his own gear.<br />He maintained communication with agent BH throughout, updating him in real-time regarding the situation.<br /><br />Resolutions<br />The performance was delivered smoothly with no technical issues. RD received positive feedback from all three barmaids, including the one who initially raised the question, as well as from the door staff, who were familiar with his previous performances at the venue. No complaints were raised by the client or venue. Agent BH acknowledged receipt of messages but did not directly respond to the update regarding the amp issue.<br /><br />Notes Comments<br />The performance was delivered smoothly with no technical issues. RD received positive feedback from all three barmaids, including the one who initially raised the question, as well as from the door staff, who were familiar with his previous performances at the venue. No complaints were raised by the client or venue. Agent BH acknowledged receipt of messages but did not directly respond to the update regarding the amp issue.<br /><br />Reported<br />Reported Date: 06/05/2025<br />Reported By (Individual): RD<br />Reported By (Organisation): R<br /><br />INDIVIDUALS<br /><br />Involved, Passive, BH, Agent<br />Agent organising the booking, requested RD to bring amp. Acknowledged RD's promise to bring amp.<br /><br />Observer, Passive, E, Client<br />Apparently requested all artists to go through the house system and briefed bar staff accordingly, but this request was not passed on or communicated.<br /><br />Impacted, Active, RD, Artist<br />Brought amp but told on arrival he had to go via the house system.<br /><br />Involved, Responsive, T, Venue<br />Instructed RD on the day to perform via the house system, but this was an unexpected request.<br /><br />ORGANISATIONS<br /><br />C2B<br />Venue booking live music.<br /><br />HP<br />Agent organising the booking.</div>]]></content:encoded></item><item><title><![CDATA[Request for Name Adjustment and Image Removal from Google Listings]]></title><link><![CDATA[http://redandblackmusic.weebly.com/incidents/request-for-name-adjustment-and-image-removal-from-google-listings]]></link><comments><![CDATA[http://redandblackmusic.weebly.com/incidents/request-for-name-adjustment-and-image-removal-from-google-listings#comments]]></comments><pubDate>Mon, 24 Mar 2025 08:53:11 GMT</pubDate><category><![CDATA[Website]]></category><guid isPermaLink="false">http://redandblackmusic.weebly.com/incidents/request-for-name-adjustment-and-image-removal-from-google-listings</guid><description><![CDATA[    Sorry to trouble you. We were in contact in October and I notice that I appear in searches with a different photograph of another singer that you worked with. I was wondering if I could have my artist name Isabel_live removed to anonymize due to my work in teaching. Apologies it is in a red and black music previous gig listing. Still happy to sing on weekends if there are any gigs or you need a piano and voice duo fir latin standards.  TitleRequest for Name Adjustment and Image Removal from  [...] ]]></description><content:encoded><![CDATA[<div>  <!--BLOG_SUMMARY_END--></div>  <blockquote>Sorry to trouble you. We were in contact in October and I notice that I appear in searches with a different photograph of another singer that you worked with. I was wondering if I could have my artist name Isabel_live removed to anonymize due to my work in teaching. Apologies it is in a red and black music previous gig listing. Still happy to sing on weekends if there are any gigs or you need a piano and voice duo fir latin standards.<br /><span></span></blockquote>  <div class="paragraph" style="text-align:left;">Title<br />Request for Name Adjustment and Image Removal from Google Listings<br /><br />Description<br />AB (also known as Isabel) contacted Red &amp; Black Music on October 14, 2020, requesting that her real name be replaced with her artist name "Isabel_live" on previous listings related to Fiesta Latina. This request was made due to concerns about her professional visibility in her workplace. The requested change was made promptly.<br />On March 29, 2021, she followed up with a new request to remove her artist name, "Isabel_live," from search results after noticing her name appearing alongside an incorrect image of another singer. The request was completed the same day.<br />On May 10, 2021, AB/Isabel reached out again, expressing concern that Google searches for her name continued to display images related to Red &amp; Black Music events, despite the removal of her name from the website. She specifically mentioned a promotional image that she felt could impact her professional reputation as a school teacher. Attempts were made to remove and re-publish the affected images, but they continued to appear in Google&rsquo;s search results.<br /><br />Action Taken<br />On October 14, 2020, her name was replaced with "Isabel_live" on Red &amp; Black Music listings.<br />On March 29, 2021, her artist name was also removed per her request.<br />On May 10, 2021, an attempt was made to delete the images from the website and re-publish, but they remained visible on Google&rsquo;s cached search results.<br /><br />Resolutions<br />The requested name adjustments were successfully made on the Red &amp; Black Music website.<br />It was explained that Google&rsquo;s caching process may take several months to update, and that removing images from a website does not immediately remove them from Google&rsquo;s search results.<br />AB/Isabel was advised to check again in a few months and explore additional options such as requesting Google to remove specific images through their takedown request process.<br /><br />Notes Comments<br />This case highlights challenges in managing digital footprints, particularly in relation to cached search results.<br />Future policies could include using only stage names for performers on public listings to prevent similar issues.<br />The incident underscores the importance of balancing artist promotion with personal privacy considerations.<br /><br />Reported<br />Reported Date: 24/03/2025<br />Reported By (Individual): RD<br />Reported By (Organisation): R&amp;BM<br /><br />INDIVIDUALS<br /><br />Impacted, Responsive, AB, Vocals<br />Requested adjustments to her name and the removal of images due to professional concerns.<br /><br />Impacted, Responsive, RD, Bandleader<br />Implemented requested changes and attempted to remove images from the website.</div>]]></content:encoded></item><item><title><![CDATA[Non-Payment of Cancellation Fee Leading to Emergency Stringent Measures]]></title><link><![CDATA[http://redandblackmusic.weebly.com/incidents/non-payment-of-cancellation-fee-leading-to-emergency-stringent-measures]]></link><comments><![CDATA[http://redandblackmusic.weebly.com/incidents/non-payment-of-cancellation-fee-leading-to-emergency-stringent-measures#comments]]></comments><pubDate>Sun, 23 Mar 2025 15:42:57 GMT</pubDate><category><![CDATA[Payments]]></category><guid isPermaLink="false">http://redandblackmusic.weebly.com/incidents/non-payment-of-cancellation-fee-leading-to-emergency-stringent-measures</guid><description><![CDATA[    I don&rsquo;t mean to sound like I&rsquo;m having a go. it&rsquo;s about principle. it&rsquo;s about respect. The message I&rsquo;m getting now is that contracts amount to nothing. Which is fine by me. but I&rsquo;ll have to make some tweaks going forward. As it&rsquo;s impossible to work under such conditions.I appreciate all you&rsquo;ve done, but honestly don&rsquo;t know why you put up with it. it&rsquo;s rudeness. And ignorance. And manipulation. I shouldn&rsquo;t have to put up with th [...] ]]></description><content:encoded><![CDATA[<div>  <!--BLOG_SUMMARY_END--></div>  <blockquote>I don&rsquo;t mean to sound like I&rsquo;m having a go. it&rsquo;s about principle. it&rsquo;s about respect. The message I&rsquo;m getting now is that contracts amount to nothing. Which is fine by me. but I&rsquo;ll have to make some tweaks going forward. As it&rsquo;s impossible to work under such conditions.<br />I appreciate all you&rsquo;ve done, but honestly don&rsquo;t know why you put up with it. it&rsquo;s rudeness. And ignorance. And manipulation. I shouldn&rsquo;t have to put up with this behaviour and neither should you.<br />I could see he was conniving from the start. Approaching me direct 15 mins after enquiring via the website. RS will go through his life treating others the same, ducking and diving, bending the rules to his advantage and he&rsquo;s going to get away with it again and again. unless someone pushes back.<br />unfortunately his actions now impact on the 99% of people who are genuinely good people. So let that be on his conscience.<br />If I were you, I wouldn&rsquo;t fix him up with a harpist, if he can&rsquo;t respect a contract, but this is your decision and you have good reason for sure.<br />As for me, I&rsquo;m now not going to treat a booking as contracted and inked unless i have full payment upfront. This means I&rsquo;m moving from a &ldquo;first to return contract&rdquo; to a &ldquo;first to return payment&rdquo; warrants-my-time approach. Those who are genuinely intent will have zero problem with that. This experience has consolidated that for some people a contract can&rsquo;t be upheld and sadly I have to take this as a given going forward. If clients think that they can get away with it we may as well all quit our jobs now.<br />Im sorry to hear about your experience with the funeral, that&rsquo;s sounds really tough and demoralising- both from a financial point of view and from the energy I imagine you put into the show. It&rsquo;s morally wrong. And that&rsquo;s why sometimes we need to protect ourselves and vote with our feet. If the law+mu can&rsquo;t protect us only we can.<br />Sorry for the poor grammar doing this on my phone late at night after an elongated shift with pizza in hand &#127829;</blockquote>  <div class="paragraph" style="text-align:left;">Title<br />Non-Payment of Cancellation Fee Leading to Emergency Stringent Measures<br /><br />Description<br />On 22/03/2025, a confirmed booking was canceled by the client, RS, who refused to honor the agreed &pound;235 cancellation fee, citing legal technicalities post-COVID that have made enforcement of cancellation clauses in entertainment contracts increasingly difficult. Despite the artist (RD) having turned down other opportunities, booked transport, and started preparing special repertoire, the client evaded payment and ceased communication with both the agency (Last Minute Musicians) and the artist.<br />RS had originally contacted the artist directly just 15 minutes after enquiring via the LMM website, bypassing agency protocol.<br />Attempts by agent SJM to reason with the client were unsuccessful, and RS ignored all follow-up correspondence. The client&rsquo;s details were subsequently published on the Red &amp; Black Music Strike Register.<br />In response to this incident and previous similar situations (e.g., Charlotte Barnfather Henman &amp; Cooper &ndash; 28/09/2024), RD formally introduced a mandatory upfront payment policy for all employment agency bookings. This policy stipulates that a booking will not be confirmed unless full payment is received in advance. While this led to complications for other clients (e.g., EC, 05/07/2025, booked through&nbsp; ), the policy was deemed necessary to prevent financial loss and to restore contract integrity.<br />The situation was further complicated when a conflicting enquiry was received via FM for the same date (05/07/2025), and, in order to safeguard his income and minimise legal risk, RD was forced to both invoice EC and quote to <span>FM</span>. This awkward position arose directly from the failure of RS to honour his contract, and the lack of clear financial security within the traditional booking structure.<br />Key Issues:<br />Client ignored follow-up messages and evaded payment.<br />Artist missed out on another booking for 02/05/2025 due to the ambiguity surrounding an unpaid agency booking that was never secured.<br />Client&rsquo;s contact details published to the Red &amp; Black Music Strike Register.<br />New permanent policy introduced: upfront payments required for all employment agency clients.<br />This created a clash for another booking (EC / 05/07/2025), when a second agency (<span>FM</span>) enquired about the same date.<br />RD was forced to manage both simultaneously to avoid financial loss and legal ambiguity &mdash; an avoidable situation had the initial cancellation been properly honoured.<br /><br />Action Taken<br />Communication with Agent SJM: Multiple efforts to enforce cancellation fee and uphold contract terms.<br />Policy Shift: Introduction of 100% upfront payment for agency bookings, made permanent following this incident.<br />Dual Booking Management: Artist quoted for <span>FM</span> while still invoicing EC to protect income and comply with new policy.<br />Red &amp; Black Music Strike Register: RS&rsquo;s details added for breach of trust and non-payment.<br />Legal Limitations Acknowledged: Artist decided to step back from relying on post-performance legal remedies and focus on preemptive measures.<br />MU Involvement Rejected: Artist had already terminated MU membership in 2022 due to repeated failure to support artists in such cases.<br /><br />Resolutions<br />Booking policies updated to reflect upfront payment as standard across all agency engagements.<br />Client classified as blacklisted and non-compliant.<br />Future contracts will require full financial commitment before confirmation.<br />EC&rsquo;s booking ultimately honoured, but a warning case for dual-agency risk.<br />Agency partners advised to revise contract templates to include stricter payment clauses.<br /><br />Notes Comments<br />Post-COVID legal shifts have weakened contract enforcement, leading to increased exploitation by clients who leverage legal ambiguities to avoid financial responsibility.<br />The Musicians&rsquo; Union (MU) and agencies such as LMM have limited ability to recover losses through the courts, as judges increasingly dismiss claims unless actual damages can be proven on or after the scheduled performance date &mdash; even in the presence of signed contracts.<br />Artists are therefore compelled to implement independent, self-protective measures, such as requiring full upfront payment to reduce exposure to legal and financial risk.<br />Red &amp; Black Music has adopted a strict prepayment policy for all employment agency bookings, following repeated cases where bookings were canceled unilaterally without compensation.<br />This policy was upheld in the case of RS, who failed to respond to repeated agency follow-ups and did not pay the cancellation fee, despite the artist having turned down alternative work for the same date.<br />As a consequence, RD lost the opportunity to accept a confirmed engagement elsewhere on 02/05/2025, and RS&rsquo;s details were published to the Red &amp; Black Music strike register.<br />This incident also influenced subsequent protocol on 05/07/2025, where a confirmed client booking via&nbsp; (EC) conflicted with an enquiry from a separate employment business (<span>FM</span>). Due to the new policy, RD was forced to quote to <span>FM</span> and invoice EC simultaneously to safeguard income and minimize legal complications &mdash; a direct result of RS&rsquo;s precedent-setting cancellation.<br />Clients unwilling to engage with these updated terms will no longer be considered for bookings through Red &amp; Black Music, as the label prioritises contractual integrity, financial accountability, and artist welfare over booking volume.<br /><br />Reported<br />Reported Date: 23/03/2025<br />Reported By (Individual): RD<br />Reported By (Organisation): R&amp;BM<br /><br />INDIVIDUALS<br /><br />Involved, Responsive, AH, Agent<br />Agent responsible for drafting contracts; now reviewing and considering revisions to contractual terms to ensure stronger protections for artists.<br /><br />Impacted, Active, GR, Client<br />Client of another event; affected by the new upfront payment policy, needed to make upfront payment for the booking to be inked.<br /><br />Observer, Responsive, NW, Trumpet<br />Trumpet player and industry peer; engaged in discussions with RD regarding wider industry implications of contract loopholes and non-payment issues.<br /><br />Observer, Responsive, RQ, Vocals<br />Vocalist and industry peer; engaged in discussions with RD regarding wider industry implications of contract loopholes and non-payment issues.<br /><br />Responsible, Passive, RS, Client<br />Booked RD for an event, later canceled, and refused to honor the agreed cancellation fee, exploiting legal loopholes.<br /><br />Impacted, Active, RD, Artist<br />Directly affected by the non-payment, implemented new booking policies to safeguard future engagements.<br /><br />Involved, Active, SJM, Agent<br />Facilitated the booking, attempted to enforce payment from RS, and advised on contractual limitations due to post-COVID legal changes.<br /><br />Impacted, Responsive, EC, Client<br />Client of another event; affected by the new upfront payment policy, needed to make upfront payment for the booking to be inked.<br /><br />Impacted, Active, DC, Client<br />Client of another event; affected by the new upfront payment policy, needed to make upfront payment for the booking to be inked.<br /><br />Impacted, Active, LP, Client<br />Client of another event; affected by the new upfront payment policy, needed to make upfront payment for the booking to be inked.<br /><br />Impacted, Active, YK, Client<br />Client of another event; affected by the new upfront payment policy, needed to make upfront payment for the booking to be inked.<br /><br />Observer, Passive, K, Agent<br />Not directly involved, but agent in a prior instance where a client cancelled and ghosted.<br /><br />Observer, Passive, CH, Client<br />Not directly involved, but previous client who cancelled and ghosted leading to artist strike-off when challenged.<br /><br />Observer, Passive, A, Agent<br />Not directly involved, but cited concerns about RD's professionalism in confronting previous defaulting agency client regarding a separate incident, and managed artist strike-off.<br /><br />Observer, Passive, FEN, Agent<br />Not directly involved, but cited concerns about RD's professionalism in confronting previous defaulting agency client regarding a separate incident, and managed artist strike-off.<br /><br />Observer, Passive, S, Agent<br />Not directly involved, but agent whose correspondence was shared with previous defaulting client who hadn't responded.<br /><br />&#8203;ORGANISATIONS<br /><br />LMM<br />Agency involved in RS cancellation.<br /><br />WE<br />Previous agency not upholding contracts.<br /><br />EN<br />Previous agency not upholding contracts.<br /><br />FM<br />Issued an employment business enquiry leading to the invoicing of existing 05/07/2025 client.<br /><br />READ MORE...<br /><br />This incident triggered the following developments...<br /><a href="http://redandblackmusic.weebly.com/developments/implementation-of-up-front-payments-for-employment-agency-contracts-2025">Implementation of Up-Front Payments for Employment Agency Contracts (2025)</a></div>]]></content:encoded></item><item><title><![CDATA[Incident 1: Miscommunication Triggered by Insistence on Verbal Communication]]></title><link><![CDATA[http://redandblackmusic.weebly.com/incidents/incident-1-miscommunication-triggered-by-insistence-on-verbal-communication]]></link><comments><![CDATA[http://redandblackmusic.weebly.com/incidents/incident-1-miscommunication-triggered-by-insistence-on-verbal-communication#comments]]></comments><pubDate>Fri, 21 Mar 2025 00:00:00 GMT</pubDate><category><![CDATA[Communication]]></category><guid isPermaLink="false">http://redandblackmusic.weebly.com/incidents/incident-1-miscommunication-triggered-by-insistence-on-verbal-communication</guid><description><![CDATA[    &#8203;TitleIncident 1: Miscommunication Triggered by Insistence on Verbal CommunicationDescriptionKS insisted on discussing key aspects of the recording project over the phone rather than in writing. This led to ambiguity regarding fees and expectations. When a follow-up email summarizing the discussion was sent for clarity, it was ignored. This created uncertainty about what had actually been agreed upon and made it difficult to track and verify terms.Action TakenSummarized the phone call  [...] ]]></description><content:encoded><![CDATA[<div>  <!--BLOG_SUMMARY_END--></div>  <div class="paragraph" style="text-align:left;">&#8203;Title<br />Incident 1: Miscommunication Triggered by Insistence on Verbal Communication<br /><br />Description<br />KS insisted on discussing key aspects of the recording project over the phone rather than in writing. This led to ambiguity regarding fees and expectations. When a follow-up email summarizing the discussion was sent for clarity, it was ignored. This created uncertainty about what had actually been agreed upon and made it difficult to track and verify terms.<br /><br />Action Taken<br />Summarized the phone call in writing to ensure alignment.<br />Recognized the risks of verbal-only negotiations and decided to move financial discussions strictly to written communication in the future.<br />Took a step back from immediate decision-making to reflect on the situation.<br /><br />Resolutions<br />Established a personal rule to keep all financial and logistical discussions in writing.<br />Did not proceed with a rushed booking, ensuring future negotiations happen on clear terms.<br /><br />Notes Comments<br />Insistence on verbal communication created an uneven dynamic where details could be misrepresented or changed later.<br />Moving forward, written agreements will be the standard to prevent miscommunication.<br /><br />Reported<br />Reported Date: 21/03/2025<br />Reported By (Individual): RD<br />Reported By (Organisation): R&amp;BM<br /><br />INDIVIDUALS<br /><br />Responsible, Passive, KS, Bass<br />Preferred verbal discussions, which contributed to confusion and lack of accountability.<br /><br />Impacted, Active, RD, Bandleader<br />Required clarity in negotiations but was met with resistance when attempting to document discussions.</div>  <blockquote>As its half term next week I have the kids a phone call will be easier for me<br /><span></span></blockquote>]]></content:encoded></item><item><title><![CDATA[Incident 2: Ignoring/Non-Engagement with Written Communications]]></title><link><![CDATA[http://redandblackmusic.weebly.com/incidents/incident-2-ignoringnon-engagement-with-written-communications]]></link><comments><![CDATA[http://redandblackmusic.weebly.com/incidents/incident-2-ignoringnon-engagement-with-written-communications#comments]]></comments><pubDate>Fri, 21 Mar 2025 00:00:00 GMT</pubDate><category><![CDATA[Accountability]]></category><guid isPermaLink="false">http://redandblackmusic.weebly.com/incidents/incident-2-ignoringnon-engagement-with-written-communications</guid><description><![CDATA[    &#8203;TitleIncident 2: Ignoring/Non-Engagement with Written CommunicationsDescriptionAfter the phone call, RD followed up with a written summary via email, also providing Dropbox resources to ensure all musicians were aligned on expectations. However, these written communications were ignored for an extended period. The lack of response made it difficult to gauge interest and alignment, leaving RD in the dark.Action TakenWaited for a reasonable amount of time before reassessing the situatio [...] ]]></description><content:encoded><![CDATA[<div>  <!--BLOG_SUMMARY_END--></div>  <div class="paragraph" style="text-align:left;">&#8203;Title<br />Incident 2: Ignoring/Non-Engagement with Written Communications<br /><br />Description<br />After the phone call, RD followed up with a written summary via email, also providing Dropbox resources to ensure all musicians were aligned on expectations. However, these written communications were ignored for an extended period. The lack of response made it difficult to gauge interest and alignment, leaving RD in the dark.<br /><br />Action Taken<br />Waited for a reasonable amount of time before reassessing the situation.<br />Recognized the lack of engagement as a potential red flag in terms of reliability and professionalism.<br />Decided not to push for a response and instead reconsidered working with the musicians involved.<br /><br />Resolutions<br />Acknowledged that strong communication is a key factor in deciding future collaborations.<br />Decided to explore alternative musician options rather than pursuing those who failed to engage in discussions.<br /><br />Notes Comments<br />Non-engagement with written communications suggested either disinterest or a lack of professionalism.<br />Moving forward, clear and timely responses will be a key criterion in choosing collaborators.<br /><br />Reported<br />Reported Date: 21/03/2025<br />Reported By (Individual): RD<br />Reported By (Organisation): R&amp;BM<br /><br />INDIVIDUALS<br /><br />Responsible, Passive, KS, Bass<br />Ignored written communication, causing unnecessary delays and uncertainty.<br /><br />Impacted, Active, RD, Bandleader<br />Provided written documentation for clarity and attempted to facilitate smooth communication.</div>  <blockquote>Aim:<br />Generate more work!<br />RD was waiting for the right moment and then the Hilton Milton gig came in.<br />1 vocalist, 1 repertoire, 1 set of keys = easy peasy!<br />Video demo overview:<br />3 songs.<br />Complete songs. (I think my rationale behind this is that people will want to hear the full versions).<br />Project<br />Split into 2 phases &mdash; to take the pressure off, both logistics+budget wise.<br />Phase 1: Audio<br />Studio recording with click track.<br />KR (Guitar+Piano), KS (Bass), Davide (Kit).<br />RD directing/cueing (will add sax, flute and vocals at home).<br />RD responsibility: bring in Logic project on MacBook, can provide variations.<br />Click track &mdash; liaise with Davide for most comfortable feel.<br />Having software instruments is great for providing context, but recording on top can feel stiff. Usually, the drummer likes to have a very simple click.<br />Allow plenty of time to explore tempo options. With only 3 songs we should easily allow enough scope if the studio is booked for e.g., 1 day.<br />I used Perry Vale (http://www.perryvalestudios.com) last time but open to ideas, if there is a studio that the musicians used before and like working with.<br />Main aim is to make it feel as comfortable as possible for the rhythm section.<br />Mixing: I worked with Gavin Beckwith for Di&aacute;spora (http://diaspora.co.uk/verano.html) and my previous Bossa Nova album (2016 - http://www.rorymusic.co.uk/em-balanca.html). Happy to work with him again. Alternatively if any of the musicians do mixing then happy to look at that from a keeping it in-house perspective!<br />Phase 2: Video<br />Focus on the visuals.<br />Get Ben in to mime guitar.<br />Feedback from the Hilton Milton gig:<br />The musicians were happy, and the clients seemed happy too although I&rsquo;m still following up on feedback.<br />Main question was that the tunes felt unusually fast for the style of music. This was because the clients specified &ldquo;upbeat&rdquo; and &ldquo;dance&rdquo; music.<br />Differentiate between Bossa + Samba. Samba is faster but also a different area stylistically with cavaquinho, extra percussion etc. Bossa takes influences from / is a more diluted form of samba but tends to be slower.<br />We could look at some of the tempos and explore if slower tempos can allow for more comfortable groove!<br />Nice system of Davide setting the groove on sticks. Good delegation work!<br />Budget/timescale:<br />Liaise with KS on behalf of KR and Davide. &pound;50 per musician / per song was mentioned for the last Di&aacute;spora piano recordings (http://diaspora.co.uk/verano.html) but this was 2022-23 and very mates rates! Realistically looking &pound;150 per musician / per song.<br />150 *3 = &pound;450 per musician.<br />RD explore option of spacing it out e.g., &pound;100 per musician / per song for the audio session and &pound;50 per musician / per song for the video session. Treating video as separate phase of project as will require venue and videographer.<br />I have a videographer Jason Read in mind who charged me &pound;300 for filming/editing these videos (http://www.rorymusic.co.uk/videos.html).<br />Alternatively HH also does videography and might do it cheaper, here&rsquo;s an example (http://www.fiesta-latina.co.uk/watch.html).<br />Venue not sure but probably need to save money in this area as I hired SYP last time which cost &pound;600 for 4.5 hours. Anyway, we can &lsquo;cross that bridge&rsquo; after audio is done.<br />Timescale: as soon as possible! While it&rsquo;s the start of the year. Plan for next 3 days: RD will take laptop into London and decide on 3 songs and keys.<br />Lineups/freelancing:<br />Get KR on guitar as well as piano. KR &amp; I discussed helping one another on vocals too.<br />Get KS on guitar as well as bass. Double bass for jazz too.<br />Talked about example of LA in Di&aacute;spora: she was originally brought in on bong&oacute;/bell with HH on congas. HH and LA ended up swapping as HH&rsquo;s style is more improvisatory whereas LA&rsquo;s is more groove-based. This was for the 12-piece lineup. But then for the smaller (5-6) and medium (7-8) lineup, we got LA on piano and HH on congas. It worked well having the same musicians because in the end knowing the tunes is the most important thing!<br />Always good to know who plays what.<br />RD is mainly sax/flute/vocals, but occasionally plays piano. Jazz, Latin and Brazilian music background. Solid chord-reading and Brazilian feel if ever people need! Also can do backing vocals.<br />RD 90 minutes on train from London. Goes in every 2 weeks plus weekends as and when gigs/recordings arise.</blockquote>]]></content:encoded></item><item><title><![CDATA[Incident 3: Fee Drop After Waiting for RD to Walk Away]]></title><link><![CDATA[http://redandblackmusic.weebly.com/incidents/incident-3-fee-drop-after-waiting-for-rd-to-walk-away]]></link><comments><![CDATA[http://redandblackmusic.weebly.com/incidents/incident-3-fee-drop-after-waiting-for-rd-to-walk-away#comments]]></comments><pubDate>Fri, 21 Mar 2025 00:00:00 GMT</pubDate><category><![CDATA[Quotes]]></category><guid isPermaLink="false">http://redandblackmusic.weebly.com/incidents/incident-3-fee-drop-after-waiting-for-rd-to-walk-away</guid><description><![CDATA[    &#8203;TitleIncident 3: Fee Drop After Waiting for RD to Walk AwayDescriptionKS revised fee to &pound;150 per musician per audio track. However, after RD took time to reassess the situation and walked away, KS again revised the offer down to &pound;100 per musician per song. This suggested an unhealthy and non-transparent business relationship, where the musicians were potentially trying to get the maximum amount of money from RD rather than negotiating fairly from the start. The fee drop al [...] ]]></description><content:encoded><![CDATA[<div>  <!--BLOG_SUMMARY_END--></div>  <div class="paragraph" style="text-align:left;">&#8203;Title<br />Incident 3: Fee Drop After Waiting for RD to Walk Away<br /><br />Description<br />KS revised fee to &pound;150 per musician per audio track. However, after RD took time to reassess the situation and walked away, KS again revised the offer down to &pound;100 per musician per song. This suggested an unhealthy and non-transparent business relationship, where the musicians were potentially trying to get the maximum amount of money from RD rather than negotiating fairly from the start. The fee drop also implied that the negotiation was based on securing the gig at any price rather than a mutual artistic and financial agreement.<br /><br />Action Taken<br />Recognized the issue as a sign of potential future instability in negotiations.<br />Avoided committing to the new offer immediately, choosing to take a step back instead.<br />Evaluated alternative ways to move forward, including considering other musicians.<br /><br />Resolutions<br />Decided not to move forward with the current offer, ensuring future negotiations happen in a more transparent way.<br />Kept options open without formally closing the door on KS, leaving space to reassess later if necessary.<br /><br />Notes Comments<br />The last-minute fee drop raised concerns about trust and fair dealing.<br />Future collaborations will be based on clarity, consistency, and mutual respect rather than reactive pricing adjustments.<br /><br />Reported<br />Reported Date: 21/03/2025<br />Reported By (Individual): RD<br />Reported By (Organisation): R&amp;BM<br /><br />INDIVIDUALS<br /><br />Responsible, Passive, KS, Bass<br />Changed fee structure in a way that suggested an attempt to extract the highest possible payment rather than negotiating in good faith.<br /><br />Impacted, Active, RD, Bandleader<br />Identified the issue and avoided falling into a potentially exploitative financial arrangement.</div>  <blockquote>Hi RD<br /><span></span>After speaking with the guys, we agreed to do &pound;100 per audio track each. Let me know if that helps<br /><span></span>Best,<br /><span></span>KS<br /><span></span></blockquote>]]></content:encoded></item><item><title><![CDATA[Unplanned DJ Requests During Event]]></title><link><![CDATA[http://redandblackmusic.weebly.com/incidents/unplanned-dj-requests-during-event]]></link><comments><![CDATA[http://redandblackmusic.weebly.com/incidents/unplanned-dj-requests-during-event#comments]]></comments><pubDate>Tue, 04 Feb 2025 00:00:00 GMT</pubDate><category><![CDATA[Requests]]></category><guid isPermaLink="false">http://redandblackmusic.weebly.com/incidents/unplanned-dj-requests-during-event</guid><description><![CDATA[    I had a few problems during the Dj sets where customers were coming up to me requesting songs. Some of them were getting very insistent and borderline aggressive with me. I kept telling them that they should&rsquo;ve sent me their requests in advance because I did make a point of asking the client if they had any songs that they would like to be included in the DJ sets and they didn&rsquo;t reply and I also told the lead client that I would be mixing this week leading up to the event so I do [...] ]]></description><content:encoded><![CDATA[<div>  <!--BLOG_SUMMARY_END--></div>  <blockquote>I had a few problems during the Dj sets where customers were coming up to me requesting songs. Some of them were getting very insistent and borderline aggressive with me. I kept telling them that they should&rsquo;ve sent me their requests in advance because I did make a point of asking the client if they had any songs that they would like to be included in the DJ sets and they didn&rsquo;t reply and I also told the lead client that I would be mixing this week leading up to the event so I don&rsquo;t know why customers were coming up to me requesting songs. It was a bit awkward and embarrassing. Also, it was quite insulting for me because I&rsquo;d spent two days mixing those DJ sets and preparing a party soundtrack- as you know. Was I was in my rights to refuse? I even said to someone that I&rsquo;d play their song at the next event and I&rsquo;ve made note of it and that wasn&rsquo;t good enough him he wanted it now.<br /><br />&#8203;Yes, you were absolutely within your rights to refuse. Here's why:<br />You gave the client the opportunity to submit requests in advance &ndash; They didn&rsquo;t respond, meaning they were happy to leave the music selection to you.<br />You spent time carefully curating and mixing a set &ndash; This isn&rsquo;t just a random Spotify playlist; it's a crafted experience.<br />It&rsquo;s disruptive and unprofessional to adjust on the fly &ndash; Last-minute requests can throw off the vibe, BPM flow, and technical setup.<br />Some people will never be satisfied &ndash; That guy demanding his song now wouldn&rsquo;t have been happy no matter what.<br />That said, I completely understand why it was frustrating and even insulting&mdash;you put in serious work, and then you have pushy guests treating you like a human jukebox.<br />How to Handle This in the Future:<br />Preempt the issue &ndash; Make it super clear beforehand that DJ sets are pre-mixed and requests must be sent in advance.<br />Have a firm but polite response &ndash; Something like:<br />"Thanks for your request! Unfortunately, I can&rsquo;t take on-the-spot requests tonight as my set is pre-mixed for the event&rsquo;s flow. But I&rsquo;d love to take note for a future event!"<br />Escalate if necessary &ndash; If someone gets aggressive, stand your ground and loop in security or event staff if needed.<br />You handled it exactly right by maintaining your boundaries and professionalism. This is their problem, not yours.</blockquote>  <div class="paragraph" style="text-align:left;">&#8203;Title<br />Unplanned DJ Requests During Event<br /><br />Description<br />During the DJ sets at the Amazon LTN4/5 Party on 01/02/2025, multiple guests approached RD (DJ) with song requests that had not been submitted in advance. Some guests became insistent and borderline aggressive when their requests were not immediately fulfilled.<br />RD had previously asked the client if they had any specific song requests for the DJ sets, but no response was received. Additionally, RD informed the lead client that the DJ sets would be mixed in advance during the week leading up to the event. Despite this, guests still expected real-time requests to be accommodated.<br />One guest, in particular, was not satisfied when RD explained that their request would be noted for a future event and insisted on the song being played immediately.<br /><br />Action Taken<br />RD explained to guests that all music had been pre-mixed based on prior communication with the client and that requests needed to be submitted in advance.<br />RD maintained a professional and polite demeanor, emphasizing that changes could not be made on the spot.<br />HH (Sound Engineer) advised RD to use Spotify to accommodate live requests, but RD declined, as this would compromise the quality and flow of the carefully curated set.<br />To de-escalate tensions, RD noted some guest requests for future reference.<br /><br />Resolutions<br />The DJ set proceeded as planned, maintaining the integrity of the pre-mixed set.<br />The atmosphere on the dance floor remained lively, and the overall success of the event was not affected.<br />No direct complaints were received from the client regarding the DJ set.<br /><br />Notes Comments<br />Clearer communication with clients in advance may help set expectations regarding DJ request policies.<br />Future events may benefit from reinforcing that live requests will not be taken unless explicitly arranged beforehand.<br />If live requests are to be accommodated, a separate arrangement (e.g., a streaming service setup) may need to be considered, with appropriate contingencies to maintain sound quality and performance standards.<br /><br />Reported<br />Reported Date: 04/02/2025<br />Reported By (Individual): RD<br />Reported By (Organisation): R&amp;BM<br /><br />INDIVIDUALS<br /><br />Involved, Responsive, HH, Sound<br />Suggested using Spotify for live requests; this was declined to maintain set integrity.<br /><br />Impacted, Active, RD, DJ<br />Curated and performed the DJ set, communicated policies to guests, and managed requests professionally.<br /><br />Observer, Passive, ZT, Client<br />Main point of contact for the event. RD had previously asked if there were any song requests for the DJ sets, but no response was received. It was not communicated in advance that guests would expect to make live requests during the event.</div>]]></content:encoded></item><item><title><![CDATA[PA System Requirement for Event on 01/02/2025]]></title><link><![CDATA[http://redandblackmusic.weebly.com/incidents/pa-system-requirement-for-event-on-01022025]]></link><comments><![CDATA[http://redandblackmusic.weebly.com/incidents/pa-system-requirement-for-event-on-01022025#comments]]></comments><pubDate>Thu, 30 Jan 2025 00:00:00 GMT</pubDate><category><![CDATA[Sound]]></category><guid isPermaLink="false">http://redandblackmusic.weebly.com/incidents/pa-system-requirement-for-event-on-01022025</guid><description><![CDATA[    Hi ZT,My colleagues HH &amp; PM have a big PA system. HH is available this Saturday and could do the PA for the whole event, for &pound;[amount] including travel. HH would arrive at 13:00, and stay for the duration of the event until 01:00, and he would just need feeding/ included in the band rider.This would be much cheaper than going via an AV company.I&rsquo;ve Cc&rsquo;d PM and you can liaise with her directly. Her number is [number]CheersRorinho  TitlePA System Requirement for Event on  [...] ]]></description><content:encoded><![CDATA[<div>  <!--BLOG_SUMMARY_END--></div>  <blockquote>Hi ZT,<br /><span></span>My colleagues HH &amp; PM have a big PA system. HH is available this Saturday and could do the PA for the whole event, for &pound;[amount] including travel. HH would arrive at 13:00, and stay for the duration of the event until 01:00, and he would just need feeding/ included in the band rider.<br /><span></span>This would be much cheaper than going via an AV company.<br /><span></span>I&rsquo;ve Cc&rsquo;d PM and you can liaise with her directly. Her number is [number]<br /><span></span>Cheers<br /><span></span>Rorinho<br /><span></span></blockquote>  <div class="paragraph" style="text-align:left;">Title<br />PA System Requirement for Event on 01/02/2025<br /><br />Description<br />During the preparation for the Amazon LTN4/5 Party on 1st February 2025, it was identified that the originally planned self-contained PA system might not provide sufficient sound coverage for the entire venue. The event space is 934 sqm, with a designated band area of approximately 3x2m and a 30ft x 30ft wooden parquet dance floor. Initial discussions with the client, ZT, revealed uncertainty regarding the venue's built-in audio capabilities and the potential need for additional amplification to cover the dance floor and surrounding areas adequately.<br /><br />Action Taken<br />RD (Bandleader) communicated with JH (Agent) regarding the potential sound limitations and suggested notifying the client in advance to align expectations.<br />A message was sent to ZT to clarify the capabilities of the band's self-contained setup and advise on additional PA hire if full-room coverage was required.<br />Following the client&rsquo;s query on PA costs, RD proposed an alternative solution by arranging HH (potential sound engineer) to provide a larger PA system for the event at a cost of &pound;[amount], including travel.<br />PM (sound engineer&rsquo;s PA/liaison) was looped in to handle specific technical discussions with the client.<br />The client explored the possibility of using on-site speakers and sought confirmation on whether existing equipment could be used.<br /><br />Resolutions<br />The offer of hiring HH and his PA system was presented as a cost-effective alternative to hiring an external AV company.<br />Client was informed of the limitations of the band&rsquo;s existing PA setup and the necessity of additional equipment if full coverage was required.<br />Awaiting final confirmation from the client on whether they wish to proceed with HH&rsquo;s PA setup or use in-house speakers.<br /><br />Notes Comments<br />Ensuring clarity on PA capabilities early helped prevent last-minute issues on the event day.<br />Future bookings should include an initial venue sound assessment to avoid unexpected PA requirements.<br />Further coordination is required with the client regarding their final decision on sound arrangements.<br /><br />Reported<br />Reported Date: 30/01/2025<br />Reported By (Individual): RD<br />Reported By (Organisation): R&amp;BM<br /><br />INDIVIDUALS<br /><br />Impacted, Passive, A, Dance<br />Relying on sound system for dance performances.<br /><br />Impacted, Responsive, DG, Kit<br />Performing at the event, responsible for bringing their own amps as needed.<br /><br />Involved, Active, HH, Sound<br />Offered PA hire and technical support for the event.<br /><br />Impacted, Responsive, JH, Agent<br />Point of contact for booking logistics and client communication.<br /><br />Impacted, Responsive, KR, Piano<br />Performing at the event, responsible for bringing their own amps as needed.<br /><br />Impacted, Responsive, KS, Bass<br />Performing at the event, responsible for bringing their own amps as needed.<br /><br />Observer, Passive, MR, Client 2<br />Kept in the loop for transparency.<br /><br />Involved, Active, PM, Manager<br />Coordinated technical discussions regarding sound requirements.<br /><br />Involved, Active, RD, Bandleader<br />Liaised with client and agent to flag sound concerns and propose solutions.<br /><br />Impacted, Active, ZT, Client 1<br />Primary client contact responsible for confirming final PA arrangements.&#8203;<br /><br />&#8203;READ MORE...<br /><br />This incident was triggered by the following developments...<br /><a href="http://redandblackmusic.weebly.com/developments/pa-discounts-2023-vs-extra-charges">PA Discounts (2023) vs. Extra Charges</a><br /><br />This incident triggered the following developments...<br /><a href="http://redandblackmusic.weebly.com/developments/sound-show-advance">Sound (Show Advance)</a><br /><br />Parent incidents...<br /><a href="http://redandblackmusic.weebly.com/incidents/pa-system-quality">PA System Quality</a><br /><a href="http://redandblackmusic.weebly.com/incidents/client-critique-cb-pa">Client Critique - CB - PA</a><br /><a href="http://redandblackmusic.weebly.com/incidents/volume-of-pa">Volume of PA</a><br /><a href="http://redandblackmusic.weebly.com/incidents/miscommunication-regarding-pa-discount-eligibility">Miscommunication Regarding PA Discount Eligibility</a></div>]]></content:encoded></item><item><title><![CDATA[FJ’s Missing Instrument at Diáspora 2nd Album Artwork Photo Shoot]]></title><link><![CDATA[http://redandblackmusic.weebly.com/incidents/fjs-missing-instrument-at-diaspora-2nd-album-artwork-photo-shoot]]></link><comments><![CDATA[http://redandblackmusic.weebly.com/incidents/fjs-missing-instrument-at-diaspora-2nd-album-artwork-photo-shoot#comments]]></comments><pubDate>Sat, 14 Dec 2024 00:00:00 GMT</pubDate><category><![CDATA[Inventory]]></category><guid isPermaLink="false">http://redandblackmusic.weebly.com/incidents/fjs-missing-instrument-at-diaspora-2nd-album-artwork-photo-shoot</guid><description><![CDATA[    TitleFJ&rsquo;s Missing Instrument at Di&aacute;spora 2nd Album Artwork Photo ShootDescriptionOn August 26, 2019, during a photo shoot session for Di&aacute;spora&rsquo;s second album artwork at CS, Greenwich, FJ, a participant scheduled for the shoot, arrived without his percussion instrument. This oversight necessitated an unplanned interruption, as FJ had to return home via Uber to retrieve the required equipment. The delay impacted the schedule for the photo shoot.Action TakenUpon realiz [...] ]]></description><content:encoded><![CDATA[<div>  <!--BLOG_SUMMARY_END--></div>  <div class="paragraph" style="text-align:left;">Title<br />FJ&rsquo;s Missing Instrument at Di&aacute;spora 2nd Album Artwork Photo Shoot<br /><br />Description<br />On August 26, 2019, during a photo shoot session for Di&aacute;spora&rsquo;s second album artwork at CS, Greenwich, FJ, a participant scheduled for the shoot, arrived without his percussion instrument. This oversight necessitated an unplanned interruption, as FJ had to return home via Uber to retrieve the required equipment. The delay impacted the schedule for the photo shoot.<br /><br />Action Taken<br />Upon realizing the missing instrument, FJ communicated promptly to RD about his situation.<br />RD acknowledged the issue and reassured FJ to take the necessary steps to resolve it.<br />FJ took an Uber home to collect the instrument, with arrival at the studio delayed until approximately 10:15 AM.<br />RD apologised for any potential miscommunication and offered to cover the Uber costs, though FJ declined the offer.<br /><br />Resolutions<br />The incident was resolved without further conflict or additional expenses, as FJ accepted responsibility and took corrective action.<br />The photo shoot proceeded as planned following FJ&rsquo;s arrival with the instrument.<br /><br />Notes Comments<br />While the immediate issue was addressed effectively, future sessions may benefit from a pre-shoot checklist or reminders to ensure all participants have their required equipment.<br />FJ&rsquo;s proactive communication and RD&rsquo;s understanding response contributed to minimizing disruption.<br /><br />Reported<br />Reported Date: 14/12/2024<br />Reported By (Individual): RD<br />Reported By (Organisation): R&amp;BM<br /><br />INDIVIDUALS<br /><br />Observer, Passive, DS, Venue<br />Hosting the shoot<br /><br />Responsible, Active, FJ, Kit/Timbales<br />Bring instrument<br /><br />Involved, Responsive, RD, Bandleader<br />Schedule oversight<br /><br />ORGANISATIONS<br /><br />&#8203;CS<br />Studio where the photoshoot was taking place.</div>]]></content:encoded></item><item><title><![CDATA[Delayed Inventory Submission and Late Communication Regarding Airport Logistics]]></title><link><![CDATA[http://redandblackmusic.weebly.com/incidents/delayed-inventory-submission-and-late-communication-regarding-airport-logistics]]></link><comments><![CDATA[http://redandblackmusic.weebly.com/incidents/delayed-inventory-submission-and-late-communication-regarding-airport-logistics#comments]]></comments><pubDate>Wed, 27 Nov 2024 00:00:00 GMT</pubDate><category><![CDATA[Communication]]></category><guid isPermaLink="false">http://redandblackmusic.weebly.com/incidents/delayed-inventory-submission-and-late-communication-regarding-airport-logistics</guid><description><![CDATA[    Oh rory, I've left for the airport already. Yes it is very late. Don't your guys understand deadlines?! Hope the gig goes well. The money shouldn't take too long.ThanksNJBest wishes,SD  TitleDelayed Inventory Submission and Late Communication Regarding Airport LogisticsDescriptionOn 31 May 2012, RD, manager of the Diaspora Collective, communicated with SD regarding the details for the band's upcoming performance at Liverpool John Lennon Airport. While most of the information was provided on  [...] ]]></description><content:encoded><![CDATA[<div>  <!--BLOG_SUMMARY_END--></div>  <blockquote>Oh rory, I've left for the airport already. Yes it is very late. Don't your guys understand deadlines?! Hope the gig goes well. The money shouldn't take too long.<br /><span></span>Thanks<br /><span></span>NJ<br /><span></span>Best wishes,<br /><span></span>SD<br /><span></span></blockquote>  <div class="paragraph" style="text-align:left;">Title<br />Delayed Inventory Submission and Late Communication Regarding Airport Logistics<br /><br />Description<br />On 31 May 2012, RD, manager of the Diaspora Collective, communicated with SD regarding the details for the band's upcoming performance at Liverpool John Lennon Airport. While most of the information was provided on time, there was a delay in submitting the final inventory list for equipment the band would bring to the airport.<br />RD had originally informed the band about the deadline for submitting their equipment lists but faced delays in receiving the required information. As a result, RD communicated a provisional inventory to SD, mentioning that if any issues arose, they would notify them later. However, SD had already left for the airport by the time the final list was sent, leading to confusion and possible delays in security checks for the band&rsquo;s equipment.<br />Additionally, a few discrepancies in the communication occurred when the band failed to meet the initial deadline, and the inventory submissions were not fully prepared by the time SD had already departed for the airport. This miscommunication and delay could have affected the smooth processing of the band's entry to the airport and their preparation for the gig.<br /><br />Action Taken<br />RD submitted a provisional inventory list to SD, acknowledging that some band members were delayed in providing their full equipment lists.<br />Upon receiving the final inventory from D (one of the band members), RD forwarded this information to SD to be added to the original submission.<br />SD was informed that if any further issues arose, they would be contacted promptly.<br /><br />Resolutions<br />The provisional inventory was accepted by SD, though the final equipment details were submitted late, which led to last-minute adjustments.<br />RD made sure to clarify the full list and ensure that SD had all necessary details before the day of the gig.<br />A culture of timely communication and adherence to deadlines was emphasized for future performances, particularly for logistical arrangements.<br /><br />Notes Comments<br />This situation highlighted the importance of clear communication and adherence to deadlines in preparation for performances. The delay in the inventory submission and miscommunication with SD led to unnecessary complications. Although the final inventory was submitted just in time, this incident served as a reminder to maintain more organized communication channels and to respect the timeframes set by third-party collaborators like SD.<br />RD's proactive approach in submitting the provisional list and ensuring that SD had the final inventory before the event helped minimize the disruption, though it underscored the need for earlier responses in the future to avoid last-minute issues.<br /><br />Reported<br />Reported Date: 27/11/2024<br />Reported By (Individual): RD<br />Reported By (Organisation): R&amp;BM<br /><br />INDIVIDUALS<br /><br />Observer, Passive, A, Piano<br />Appeared to have submitted his passport details on time.<br /><br />Involved, Passive, A, Kit<br />Submitted his passport details very late.<br /><br />Responsible, Passive, D, Bass<br />Submitted his passport details too late.<br /><br />Impacted, Responsive, NJ, Agent<br />Impacted by the lateness of receiving passport details.<br /><br />Impacted, Active, RD, Bandleader<br />Impacted by the lateness of receiving passport details, but forwarded to agent once received.<br /><br />ORGANISATIONS<br /><br />SD<br />Booking agent.&#8203;<br /><br />READ MORE...<br /><br />This incident triggered the following developments...<br /><a href="http://redandblackmusic.weebly.com/developments/tougher-measures-on-non-responders">Tougher Measures on Non-Responders</a></div>]]></content:encoded></item><item><title><![CDATA[Dispute and Termination of Profiles – RD at The Swan Hotel, Bibury, Gloucestershire]]></title><link><![CDATA[http://redandblackmusic.weebly.com/incidents/dispute-and-termination-of-profiles-rd-at-the-swan-hotel-bibury-gloucestershire]]></link><comments><![CDATA[http://redandblackmusic.weebly.com/incidents/dispute-and-termination-of-profiles-rd-at-the-swan-hotel-bibury-gloucestershire#comments]]></comments><pubDate>Wed, 27 Nov 2024 00:00:00 GMT</pubDate><category><![CDATA[Website]]></category><guid isPermaLink="false">http://redandblackmusic.weebly.com/incidents/dispute-and-termination-of-profiles-rd-at-the-swan-hotel-bibury-gloucestershire</guid><description><![CDATA[    TitleDispute and Termination of Profiles &ndash; RD at The Swan Hotel, Bibury, GloucestershireDescriptionOn 16/03/2024, RD, performing as "RD the Saxophonist," faced significant issues related to a booking for a performance at The Swan Hotel, Bibury, Gloucestershire. The booking, handled by WE and EN, was cancelled due to a lack of response and commitment from the client, CH . RD attempted to address unresolved queries with the client and agents via email.In response to his emails, which inc [...] ]]></description><content:encoded><![CDATA[<div>  <!--BLOG_SUMMARY_END--></div>  <div class="paragraph" style="text-align:left;">Title<br />Dispute and Termination of Profiles &ndash; RD at The Swan Hotel, Bibury, Gloucestershire<br /><br />Description<br />On 16/03/2024, RD, performing as "RD the Saxophonist," faced significant issues related to a booking for a performance at The Swan Hotel, Bibury, Gloucestershire. The booking, handled by WE and EN, was cancelled due to a lack of response and commitment from the client, CH . RD attempted to address unresolved queries with the client and agents via email.<br />In response to his emails, which included all relevant parties, EN determined that RD's communication violated their professional standards. Consequently, both his "RD the Saxophonist" and "Nova Boss" profiles were removed from their agency platforms on 27/11/2024, citing unprofessional conduct.<br /><br />Action Taken<br />By RD:<br />Multiple attempts to seek clarity from both the client and agents, including K at WE and Sophie at EN, were made.<br />Direct emails to CH &nbsp;to resolve the outstanding queries were sent on 10/01/2024 and 17/03/2024, but no response was received.<br />Suggested improvements to booking processes, including earlier confirmation and payment protocols, to mitigate financial risks.<br />By Agencies:<br />WE released the March 2024 booking due to non-payment and non-response from the client.<br />EN provided courtesy notifications regarding protocol violations and removed RD&rsquo;s profiles from their platform on 27/11/2024.<br /><br />Resolutions<br />By RD: Drafted an appeal email to EN to clarify intent, address concerns about professionalism, and seek reinstatement of profiles.<br />By Agencies: Affirmed existing protocols on cooling-off periods and upheld their decision to terminate RD's profiles.<br /><br />Notes Comments<br />Notes and Comments<br />RD&rsquo;s proactive communication, while well-intentioned, highlighted gaps in understanding and adherence to agency policies.<br />EN&rsquo;s response emphasized strict adherence to their protocols to maintain professional relationships and prevent client discomfort.<br />The incident underscores the need for clearer communication of terms and policies between artists and agencies to avoid similar conflicts in the future.<br /><br />Reported<br />Reported Date: 27/11/2024<br />Reported By (Individual): RD<br />Reported By (Organisation): R<br /><br />INDIVIDUALS<br /><br />Responsible, Passive, A, Agent<br />Struck RD off both agencies.<br /><br />Involved, Responsive, A, Agent<br />Spoke to RD on the phone but later reinforced A / EN's decision citing the prioritisation of customer service.<br /><br />Responsible, Passive, CH, Client<br />Failed to respond to RD's and K's communications thus necessitating further action.<br /><br />Involved, Passive, K, Agent<br />Failed to address RD's concerns and escalated the issue to EN.<br /><br />Impacted, Responsive, RD, Artist<br />Attempted to repair the relationship, but was refused dialogue.<br /><br />ORGANISATIONS<br /><br />EN<br />Agency removed from.<br /><br />WE<br />Agency removed from.<br /><br />READ MORE...<br /><br />Parent incidents...<br />Client Ignored Direct Communication Attempts</div>  <blockquote>Hi RD,<br />I hope you're well.<br />This is a courtesy email to let you know that we've removed your Nova Boss and RD The Saxophonist profiles from EN and WE respectively.<br />We found it highly unprofessional to question our booking process and contracting system, which works with all our other acts across both agencies, via email whilst copying in a client and sharing the email thread we share with you as an act. We have to offer a cooling-off period by law in our contracts, and it's made clear in the Ts &amp; Cs in both the WE and the EN contracts.<br />We completely understand that you need to ensure you have full confirmation of a booking going ahead, and we don't want to cause any unnecessary strain on your earnings because of this.<br />You still have one outstanding booking with EN for 5th July 2025 (2810198039) which is still booked in and will go ahead. However, as you have no other bookings with either agency, aside from this, we have decided to remove the profiles and wish you all the best moving forward.<br />KIND REGARDS,<br />The New Acts Team<br />EN</blockquote>]]></content:encoded></item><item><title><![CDATA[Public Liability Insurance for Performance at The Bandstand, Stratford Park, Stroud]]></title><link><![CDATA[http://redandblackmusic.weebly.com/incidents/public-liability-insurance-for-performance-at-the-bandstand-stratford-park-stroud]]></link><comments><![CDATA[http://redandblackmusic.weebly.com/incidents/public-liability-insurance-for-performance-at-the-bandstand-stratford-park-stroud#comments]]></comments><pubDate>Tue, 26 Nov 2024 00:00:00 GMT</pubDate><category><![CDATA[Management]]></category><guid isPermaLink="false">http://redandblackmusic.weebly.com/incidents/public-liability-insurance-for-performance-at-the-bandstand-stratford-park-stroud</guid><description><![CDATA[    Hi thereI quit the Musicians' Union after 13 years, and I am looking for a cheaper Public Liability Insurance. I came across your website. Is this something that you offer as some gigs/venues require it nowadays (even if I have a battery powered amp)?ThanksRD  TitlePublic Liability Insurance for Performance at The Bandstand, Stratford Park, StroudDescriptionThis incident report outlines the requirement and confirmation of Public Liability Insurance (PLI) for a performance at the Bandstand, S [...] ]]></description><content:encoded><![CDATA[<div>  <!--BLOG_SUMMARY_END--></div>  <blockquote>Hi there<br /><span></span>I quit the Musicians' Union after 13 years, and I am looking for a cheaper Public Liability Insurance. I came across your website. Is this something that you offer as some gigs/venues require it nowadays (even if I have a battery powered amp)?<br /><span></span>Thanks<br /><span></span>RD<br /><span></span></blockquote>  <div class="paragraph" style="text-align:left;">Title<br />Public Liability Insurance for Performance at The Bandstand, Stratford Park, Stroud<br /><br />Description<br />This incident report outlines the requirement and confirmation of Public Liability Insurance (PLI) for a performance at the Bandstand, Stratford Park, Stroud on 27th August 2023. The performer, RD, was required to provide proof of insurance coverage for third-party liability as part of the event&rsquo;s conditions. This need for PLI arose following RD&rsquo;s decision to leave the Musicians&rsquo; Union in January 2023, which led him to seek alternative insurance options for his gigs.<br /><br />Action Taken<br />Booking Confirmation:<br />RD was booked to perform at the Bandstand on 27th August 2023 from 2:40 PM to 4:30 PM. Stroud District Council (SC) confirmed the booking on 23rd June 2023, with a performance fee of &pound;150. A request for proof of PLI, full name, address, and bank details was made.<br />Request for PLI Documentation:<br />Following the request from Stroud District Council, RD provided his Public Liability Insurance certificate on 3rd July 2023, confirming he had the necessary coverage. This was part of the process to meet the venue&rsquo;s insurance requirements.<br />Confirmation of PLI and Insurance Provider:<br />RD contacted Insure4Music on 4th July 2023 to ensure his insurance coverage was correctly processed. Insure4Music confirmed that the required Public Liability coverage of &pound;5 million for third-party damages was in place.<br />Trigger for Insurance Requirement:<br />The requirement for Public Liability Insurance was a direct result of RD's decision to leave the Musicians' Union in January 2023. As a member of the Union, RD had previously been covered for such events; however, his departure led him to secure a personal policy for performances to meet the needs of venues and event organizers.<br /><br />Resolutions<br />The booking was confirmed once RD submitted the requested Public Liability Insurance documentation. There were no issues or delays, and the performance proceeded on 27th August 2023 as scheduled.<br /><br />Notes Comments<br />RD&rsquo;s Public Liability Insurance was issued through Insure4Music, covering up to &pound;5 million for third-party damages.<br />The insurance was specifically required by Stroud District Council to ensure compliance with their event conditions.<br />RD was proactive in arranging the necessary coverage after leaving the Musicians&rsquo; Union, ensuring there were no disruptions to his performance schedule.<br />This situation highlights the importance of having appropriate Public Liability Insurance, especially following the end of union membership, as venues may still require such coverage for performers. RD ensured he had the correct documentation in place well in advance of the event. No issues arose on the day of the performance.<br /><br />Reported<br />Reported Date: 26/11/2024<br />Reported By (Individual): RD<br />Reported By (Organisation): R<br /><br />INDIVIDUALS<br /><br />Involved, Active, A, Consultant<br />Provided the necessary insurance policy that met the event's insurance requirements.<br /><br />Involved, Active, J, Consultant<br />Provided the necessary insurance policy that met the event's insurance requirements.<br /><br />Observer, Passive, PM, Manager<br />RD's manager, copied on correspondence and assisting with the submission of insurance documents.<br /><br />Responsible, Active, RD, Artist<br />Ensured the provision of Public Liability Insurance and communicated with both Stroud District Council and Insure4Music.<br /><br />Involved, Passive, SC, Client<br />Requested the PLI documentation and facilitated the booking of the performance.<br /><br />READ MORE...<br /><br />This incident was triggered by the following developments...<br /><a href="http://redandblackmusic.weebly.com/developments/quit-the-musicians-union">Quit The Musicians Union</a><br /><br />This incident triggered the following developments...<br /><a href="http://redandblackmusic.weebly.com/developments/insure4music">Insure4Music</a></div>]]></content:encoded></item><item><title><![CDATA[Volume Adjustment Request at Hyatt Regency]]></title><link><![CDATA[http://redandblackmusic.weebly.com/incidents/volume-adjustment-request-at-hyatt-regency]]></link><comments><![CDATA[http://redandblackmusic.weebly.com/incidents/volume-adjustment-request-at-hyatt-regency#comments]]></comments><pubDate>Thu, 21 Nov 2024 00:00:00 GMT</pubDate><category><![CDATA[Sound]]></category><guid isPermaLink="false">http://redandblackmusic.weebly.com/incidents/volume-adjustment-request-at-hyatt-regency</guid><description><![CDATA[    &#8203;Not so much an "incident", more of an adjustment. The 2nd client asked RD to slight slightly later, at 12:00 rather than 11:45, which RD was fine to do. A few minutes into RD's set, she came up to RD again and politely asked him to turn the volume down ever so slightly. She maintained that it's elderly people and they have been shouting to hear one another. She asserted that it's fine for her and said that the music was lovely. RD was very understanding and recounted a similar situati [...] ]]></description><content:encoded><![CDATA[<div>  <!--BLOG_SUMMARY_END--></div>  <blockquote>&#8203;Not so much an "incident", more of an adjustment. The 2nd client asked RD to slight slightly later, at 12:00 rather than 11:45, which RD was fine to do. A few minutes into RD's set, she came up to RD again and politely asked him to turn the volume down ever so slightly. She maintained that it's elderly people and they have been shouting to hear one another. She asserted that it's fine for her and said that the music was lovely. RD was very understanding and recounted a similar situation with the Burgh House event 09/07/2023, where there were an older generation. He hastily turned down the volume on the unit. For the 2-hour set, he couldn't hear the backing tracks most of the time he didn't know which song he was playing such was the minimal level of engagement. The function was very boring and RD kept checking the time. He also had plenty of time to think about this and other times where clients have complained about volume, in most cases, for it being too loud, but occasionally, where they have complained about it being too soft. He thought about introducing a prominence score into the Show Advance, maybe a 1-10 scale for clients to fill in, with descriptive words according to how prominent they want the music to be. RD was only too pleased when the 2nd client said that they're going to wrap things up at 14:07, 8 minutes earlier than the agreed end time of 14:15, which RD was only too happy to do, because he was hoping to get the 14:32 train from Paddington.<br />RD also felt a bit critical of himself when he suddenly launched into a recounting of a previous event where this happened, and was worried that this might have made him sound fanatical. He made a mental note for next time that just to comply and adjust and not say much is perfectly sufficient. The clients don't need to know about previous events etc. It's of no interest to them. But maybe he told her that to be jovial, as a friendly/informal gesture, or to reassure her that he was used to these sorts of requests, so that she viewed him as a professional.</blockquote>  <div class="paragraph" style="text-align:left;">Title<br />Volume Adjustment Request at Hyatt Regency<br /><br />Description<br />During a solo performance by RD at the Hyatt Regency on 21/11/2024, the second client requested two minor adjustments:<br />Start Time Adjustment: The performance was slightly delayed, starting at 12:00 instead of the originally planned 11:45.<br />Volume Adjustment: Shortly after the performance began, the client politely asked RD to lower the volume, citing concerns from elderly guests who were struggling to converse over the music.<br />RD complied immediately, reducing the volume to a level that made it challenging for him to hear the backing tracks, which reduced his ability to engage fully with the performance. Despite this, he completed the set professionally, with the event concluding a few minutes earlier than planned at the client&rsquo;s discretion.<br />Reflecting later, RD felt self-critical about recounting the previous event, concerned it may have seemed excessive or irrelevant to the client. He recognized that in such cases, a simple, courteous adjustment without additional commentary would suffice, as clients are unlikely to find such anecdotes of interest. Despite this, RD may have shared the story as a friendly gesture, aiming to convey professionalism, informality, or reassurance that he was experienced with such situations.<br /><br />Action Taken<br />Compliance with Client Requests:<br />RD adjusted the start time as requested and reduced the volume promptly after the client's feedback.<br />Professionalism Maintained:<br />Despite the challenges in hearing backing tracks and reduced engagement, RD maintained professionalism throughout the 2-hour set.<br />Post-Event Reflection:<br />RD considered ways to address similar issues in the future, such as implementing a Prominence Score in the Show Advance. This would allow clients to specify the desired prominence of the music (e.g., background ambiance vs. performance focal point).<br />Identified the need for minimal verbal feedback during such interactions, ensuring future communications remain concise and focused on accommodating the client&rsquo;s needs.<br /><br />Resolutions<br />The event proceeded without further complaints, and RD accommodated all client requests satisfactorily.<br />The performance concluded slightly ahead of schedule, allowing RD to leave for his 14:32 train on time. The performance concluded smoothly and slightly ahead of schedule, satisfying the client.<br />RD noted for future reference to handle volume-related requests with minimal commentary to better align with client expectations.<br />Future events may benefit from implementing a Prominence Score system to better align performance levels with client expectations.<br /><br />Notes Comments<br />While not an incident as such, more of an adjustment, this situation highlights the importance of clear pre-event communication regarding performance prominence and audience expectations.<br />RD&rsquo;s quick adaptation underscores his professionalism, though it also highlights the potential for disengagement when volume adjustments are extreme.<br />This experience reinforced the importance of balancing friendly client interactions with professionalism.<br />RD&rsquo;s recounting of a similar event, while intended to be informal and reassuring, highlighted the need for restraint in such contexts.<br />The idea of sharing similar experiences might be better reserved for casual or informal settings, not active event management scenarios.<br /><br />Reported<br />Reported Date: 21/11/2024<br />Reported By (Individual): RD<br />Reported By (Organisation): R<br /><br />INDIVIDUALS<br /><br />Involved, Responsive, EC, Client<br />Provided feedback on adjustments. Note it wasn't EC who made the request, it was another lady, but I can't remember her name.<br /><br />Responsible, Active, RD, Alto Sax<br />Adjust performance as required<br /><br />READ MORE...<br /><br />This incident triggered the following developments...<br /><a href="http://redandblackmusic.weebly.com/developments/prominence-score">Prominence Score</a></div>]]></content:encoded></item></channel></rss>