BEATHOVEN · Canada · international
Small canadian label preparing a first radio campaign. The contact list includes mismatched talk and music formats. Check the current schedule and music submission rules before outreach.
Audiencesmall Canadian label preparing a first radio campaign
Deliverableclean files, metadata, pronunciation guide and release information
Signalhuman replies and independently verified spins
Define the situation
A release plan starts with what the team can actually support.
This guide is for small Canadian label preparing a first radio campaign. Its starting constraint is specific: the contact list includes mismatched talk and music formats. Before buying distribution or outreach, define what a meaningful editorial response would look like and who can approve the artist's presentation.
Name the constraint
A larger audience is not always a more relevant audience.
The tempting shortcut is assuming an automated submission confirms airplay. Instead, check the current schedule and music submission rules before outreach; write that reasoning into the campaign brief so the next team member can check why each channel was chosen.
Prepare a usable asset
The receiving editor should not have to reconstruct the project.
Prepare clean files, metadata, pronunciation guide and release information. Give every file an owner, revision date and working link; if a recipient has to guess which mix or photograph is current, the handoff is not ready.
Choose the right contact
A list becomes a network only when there is real editorial fit.
The relevant route is campus and community radio programmers. Test format and recent editorial history, then remove channels where there is no plausible musical fit. A short list with context is more useful than a directory copied without review.
Write the pitch
Specific reasons matter more than promotional adjectives.
Build the opening line from the actual context—the contact list includes mismatched talk and music formats—rather than an unsourced superlative. The recipient should understand what the track sounds like, why it belongs in this programme or publication, and how to hear it.
Sequence the launch
A realistic calendar respects the lead times of each recipient.
Sequence asset approval, first approach, follow-up and review. In this situation, build a contact log that captures programme, language and consent. Allow each contact to follow its own submission instructions instead of applying one deadline to every outlet.
Interpret the signal
Sending a link is not the same as securing attention.
Measure human replies and independently verified spins. Record the source and date for each observation. A view, an editor's reply and a verified broadcast are different events and should remain distinct in reporting.
Know when to stop
A small result can prevent a large waste of budget.
Set the stop condition before spending: assuming an automated submission confirms airplay. If early contact suggests poor fit, revise the story or target group before increasing reach; a failed test is useful if it prevents repeated mistakes.
Protect the relationship
Trust and permission matter as much as reporting.
For campus and community radio programmers, verify the rights, clean/explicit labels and contributor credits attached to clean files, metadata, pronunciation guide and release information. The risk of assuming an automated submission confirms airplay makes a signed approval trail more valuable than an unverified claim of industry support.
Make the next decision
Documented learning is an outcome even without coverage.
The next step is to build a contact log that captures programme, language and consent. Conclude with a short decision memo: what was sent, what was learned, what remains unverified and what should change for the next release.
Build a contact log that captures programme, language and consent.
Editorial decisions remain independent; placement and audience outcomes cannot be guaranteed.
