A Brazilian livestream can put the same songs on two reporting clocks. Ecad uses setlists or recordings for independent internet shows and distributes monthly, while platform streams depend on usage reports and quarterly processing. The practical release decision is to identify the route before the show, then assign someone to secure the record that route needs.
Choose the route before the show
Start with how the audience will receive the performance. For an independent internet show, Ecad can work from a setlist or a recording. That gives the operator a task it can plan around the event: preserve an accurate account of what was performed. A campaign calendar that records only the stream date leaves that task without an owner.
A platform stream creates a different dependency. Its royalty processing relies on a usage report and runs quarterly. A setlist may still help the team understand the performance, but it does not replace the platform usage report in that route. Before committing to a release window, identify who will obtain the report and who will check it when the quarter is processed. The person running the event and the person reviewing royalties need the same route written into the plan.
The distinction changes what “done” means on show day. For the independent show, the team can finish its performance record as the event happens or from its recording afterward. For the platform stream, the team must also track the later report. Treating both as a single livestream line in a release spreadsheet conceals the difference between an event record the operator can preserve and a usage record that arrives through the platform route.
Keep the song and recording records separate
The reporting route is only one part of the handoff. Indonesia’s WAMI process distinguishes a distributor upload from songwriter royalties and calls for a mandate and accurate composition records. Argentina’s CAPIF process asks recording owners to check their representation mandate and declare each master for radio and public play. Those are separate national processes, but they expose a useful release-planning rule: delivering a recording does not, by itself, complete every rights record connected to it.
For the livestream, make a working file that lets the label identify the performed songs and the recordings in its catalogue. The setlist or event recording belongs with the performance record for the independent-show route. Keep the catalogue’s composition information and recording ownership information available to the people handling their respective rights. This is an internal handoff, not a claim that one Brazilian form covers every right.
That separation also makes a missing payment easier to investigate. A distributor statement addresses recording income from the activity it reports; it cannot serve as a universal receipt for the song side. A distributor’s master statement cannot establish whether the song side of a German stream was paid. Apply the same accounting discipline here: decide which royalty route a check concerns before comparing it with a statement.
Put the evidence on the calendar
The release plan needs two dates for each Brazilian livestream route: the performance date and the review point after its processing cycle. Independent internet shows use monthly distribution, while platform streams go through quarterly processing. Record the expected cycle beside the event so the team does not treat an absence of money immediately after broadcast as a completed audit.
A compact handoff can carry the work:
- Before the event: mark whether the show follows the independent internet route or the platform route, and name the person responsible for its reporting record.
- At the event: preserve the setlist or recording for an independent internet show, using the method available for that performance. Both can provide Ecad with the performance information for that route.
- After the event: obtain the platform usage report when the platform route applies, then compare the relevant royalty result with the report after quarterly processing. That route depends on platform usage data.
- At the royalty review: log the event, route, supporting record and result together so a missing item can be traced to the right handoff.
This sequence gives the team a specific question at each stage. Before broadcast, ask whether the performance record will exist. After broadcast, ask whether the required report has reached the person reviewing royalties. At the processing point, ask whether the result corresponds to the performance or usage record. Those checks are more useful than treating a livestream as complete once its promotional window closes.
Use the route to set the workload
An independent show calls for immediate attention to its setlist or recording and a monthly review. A platform stream calls for an owner of the usage report and a quarterly review. Those are the two Brazilian reporting paths and processing cycles. Put the route, record owner and review cycle in the release brief before scheduling the performance. That turns the royalty follow-up into an assigned job while the people and records are still close to the event.
