Live Music Reporting in an Event App: A Planned Set Is Not the Performance Record

If your business arranges live music, a running order tells the team what is expected. It does not establish which musical works were actually performed or that a collecting society has received a report. Before commissioning an event administration app, decide how the actual repertoire becomes a checked, event-specific reporting package and who completes the external submission.

A booking calendar and a performer contact list may be enough for planning. Reporting needs a different record. This guide uses PRS for Music's published live-performance reporting terms as a specific example, not as worldwide licensing advice or a promise that your business can submit claims on every musician's behalf.

Collect the performance, not just the programme

Imagine a fictional venue with two bands on the same evening. One changes its final song; the other plays a cover instead of its planned encore. Copying the advance set lists produces a tidy report of the wrong repertoire.

Specify an event record with its actual date, venue and address, performing act and the works performed. Ask the responsible performer or event contact to confirm changes after the show. Preserve the planned list if it helps operations, but label it as planned rather than silently treating it as confirmed performance evidence.

The PRS reporting terms require where, when, who and what, including all works performed, not just those written by one particular member. Your collection form should not invite someone to omit covers simply because the form belongs to a songwriter.

Keep different acts recognizable. An event-wide music list with no performer association leaves the reporting person reconstructing which set a work belongs to. Decide whether the business records each act's confirmation or assigns one knowledgeable person to review the complete event.

Identify the work separately from the performer

A band name is not the identity of every composition it performs. Ask what information the reporting person needs to distinguish a work, and how an uncertain match is handled. Do not let a convenient song-title suggestion silently become a verified work association.

PRS states that works on a submitted set list must be registered on its database to be considered for distribution purposes. It also sets repertoire and membership conditions. A locally saved song record therefore does not establish that a work is registered, eligible or controlled by PRS at the relevant time.

Commission an unresolved-work queue if that problem occurs in your business. Preserve the supplied title and clarification request alongside a reviewed match. These are proposed application controls, not a claim that PRS exposes an automatic matching API or that the developer can determine rights ownership.

Assign the reporting authority explicitly

PRS permits reporting by members and submissions by their representatives, while online reporting uses a membership or secondary user account. Do not assume a venue employee's access to the internal event app grants authority to use an artist's external account.

Define the handoff: who checks the repertoire, who is entitled to submit it, and what the business retains as evidence. A useful first version may export a reviewed package for an authorized person to enter through the existing service. Automated submission is a separate integration to investigate, not a feature implied by having a set-list form.

Do not ask staff to share personal passwords. Keep internal editing rights, performer confirmation and external submission authority distinct. The source's conditions apply to the PRS process; a German or Arabic interface does not transfer those conditions to another collecting society.

A saved package is not a submitted claim

Use explicit internal labels such as awaiting performer confirmation, ready for reporting and externally submitted. PRS says online claims will only be considered after the reporting member receives a claim reference number. If none is received after submission, its terms direct the member to contact PRS.

For your implementation, retain the actual reference and the package it relates to. Do not create a reference locally and present it as a PRS acknowledgement. If the submission outcome is uncertain, show an unresolved follow-up rather than instructing staff to submit again without checking.

Even a genuine reference is not a royalty award or licensing clearance. PRS describes online claim information as provisional and reserves modification and withholding rights. Its terms also allow verification of performance information. Preserve supporting event evidence without displaying a guaranteed-payment badge.

Demonstrate the exceptions before accepting the app

Use fictional acts and works for the acceptance criteria. Replace a planned song, include a cover, leave one work unresolved and give two acts different actual lists. Confirm that the reporting package contains the reviewed performance rather than the advance programme.

Then simulate a completed handoff with no external reference, a genuine reference recorded later and a corrected repertoire after submission. The app should identify which package was reported and leave the correction requiring follow-up, not silently rewrite the evidence of the earlier submission.

Bring that sequence to a web-app scoping discussion. The useful deliverable is a dependable repertoire handoff with visible external reporting evidence, not simply a nicer concert timetable.