Creating A Radio Station Format

A radio format is the repeatable programming promise a station makes to its listeners. It determines which music and other content belong on the station, how the sound changes through the day, how often important material returns, and where news, commercials, imaging and programs fit.

Software can apply that format consistently, but it cannot decide what the station should be. Make the editorial decisions first. Then translate them into metadata, selection rules, Clock Formats and Day Formats in Power Studio.

Define The Station Promise

Start with a short format brief that programmers, presenters and management can understand. It should answer:

• Who is the primary listener?
• Why should that listener choose this station?
• Which music styles, eras and languages belong, and which do not?
• How familiar, current, energetic or adventurous should the station sound?
• How should mornings, daytime, evenings, nights and weekends differ?
• How much speech, news, imaging, promotion and commercial content is expected?
• Which moments must occur at a fixed time?

Use concrete choices. "A varied mix for everyone" is difficult to schedule because it does not say which track should follow another. A useful brief defines the core sound, the acceptable edges and the role of every daypart.

Also decide who owns the format. The music director or program director should approve editorial changes. Technical administrators can configure Power Studio, but they should not have to guess the intended music balance or station sound.

Define The Target Audience

A useful target audience is more than an age range. Describe the listener's situation, expectations and reason for choosing the station. A commuter looking for familiar energy in the morning may want a different balance from a listener using the same station as a calm background during the workday.

Define:

• the primary listener and any secondary audience the station deliberately serves;
• the listening occasions that matter, such as commuting, work, evenings or weekends;
• the expected balance between familiarity and discovery;
• acceptable boundaries for style, era, language, tempo and speech;
• how much repetition the listener will notice or accept;
• the role of each daypart in the complete station sound.

Turn these choices into observable programming decisions. For example, a weekday daytime clock may favor familiar core music and a stable tempo, while an evening clock can allow more discovery or specialist material. Do not create a separate clock for every imagined listener. Create one only when the promised sound or operational structure really changes.

Power Studio has an Audience classification that can be used in Clock Formats, separation rules and Max per Playlist settings. Use it when the same library genuinely serves distinct audience groups. Do not label every track with broad values such as Everyone; that adds maintenance without helping the scheduler make a decision.

Turn The Promise Into A Content Model

The scheduler can only use distinctions that are stored consistently. Before building clocks, decide how the library will describe the station's content.

A practical model usually includes:

• Content type for music, jingles, promos, commercials and other operational behavior.
• Criteria for the main programming groups, such as current, recurrent, gold or a defined music style.
• Rotation for the relative importance or desired exposure of music groups.
• Special for station-specific, seasonal or program-specific uses.
• Audience, Decade and Language when those properties genuinely influence scheduling.
• Rating, year, tempo, mood and BPM where the library is complete enough to support those filters.

Keep the model small enough to maintain. Two labels that mean almost the same thing will eventually be applied differently, making clocks harder to understand and candidate pools less predictable. Document the meaning of each value and who may change it.

See Track Categories and Asset Management before classifying a large library.

Criteria Versus Special

Use Criteria for the main scheduling families that define the station's normal rotation. A Criteria value should answer: "What primary role does this track have in the format?" Typical music examples are:

• A Current, B Current or another clearly defined current-music structure;
• Recurrent;
• Gold or separate gold eras when they are scheduled differently;
• a core genre or format group when that is the station's main organizing principle.

Use Special for a second dimension: specialization, detail or a temporary use that cuts across the main Criteria groups. Examples include:

• Acoustic, Dance, Rock or another substyle;
• Local or Regional;
• Christmas, Summer or another seasonal property;
• a named show, feature or campaign;
• a production detail that is genuinely used by Clock Formats or separation rules.

The right division depends on how the station schedules. If Rock is one occasional flavor inside current, recurrent and gold music, it fits Special. If rock categories are the station's main clock structure, they may belong in Criteria instead. Store a property where it answers one consistent scheduling question; do not duplicate the same distinction in both groups.

One track may have values in both groups. On a Clock Format line, multiple selected Criteria values work as OR, and multiple selected Special values also work as OR. The groups are combined with AND.

For example:

Criteria is A Current or B Current
AND Special is Acoustic or Local

This selects a track that has at least one of the selected current Criteria values and at least one of the selected Special values. It does not require all four values. Every extra group narrows the candidate pool, so confirm that the combination exists on enough active tracks before using it in a clock.

Decide Which System Owns Each Decision

A complete station format often crosses several systems. Give each decision one clear owner:

• Power Studio library metadata describes what an item is and when it may be selected.
• Power Studio Clock Formats define the order and selection rules for the hour.
• Power Traffic or another traffic workflow determines which commercials and campaigns belong in a scheduled block.
• News, program and import providers supply dynamic content at positions reserved by macros.
• Power Studio playout executes the resulting playlist and gives operators controlled ways to handle exceptions.

Do not manually reproduce the detailed output of another planning system in every Clock Format. Reserve the correct position and let the responsible integration supply the current block or program. This keeps commercial, editorial and operational changes in the systems where they are maintained.

See Power Traffic Integration and Dynamic Content And Macros for Power Studio examples.

Check Whether The Library Can Support The Plan

Every clock position creates demand for eligible content. Estimate that demand before adding strict rules.

For example, if a clock contains four positions from one current-music group and the clock is used for many hours each day, that group must supply enough usable tracks for the intended title and artist separation. The exact result also depends on other clocks, dayparts, previously scheduled items and the rules applied by the scheduler.

For every important group, check:

1. How many positions use it in an hour and across the broadcast day.
2. How many active tracks have complete and correct metadata.
3. Whether those tracks are allowed in the required dayparts.
4. Whether title, artist, category and other separation rules leave enough alternatives.
5. Whether new music, expired promotions and unavailable audio are maintained on time.

Do not design a rotation around the total number of files in a folder. The useful pool is the content that is active, correctly classified, available at that date and time, and eligible under all relevant rules.

When the pool is too small, choose deliberately: add suitable content, use the group less often, broaden its definition or relax a separation rule. Adding more filters normally reduces the pool further.

Set Track And Artist Repeat Values

Power Studio uses Repeat Values to create variety over time. A Repeat Value is stored in minutes for both tracks and artists, with each value controlling a different part of the rotation:

• The track Repeat Value determines how long that track rests before it is normally available again.
• The artist Repeat Value determines how long that artist rests before another music track by the artist is normally available.

For music, both values work together. The track value controls title exposure, while the artist value spreads different songs by the same artist. This lets a high-rotation title return at the intended pace without allowing one artist to dominate the station's sound.

For a jingle, Power Studio only evaluates the track Repeat Value. The artist Repeat Value is not applied when scheduling jingles. Assigning the correct Content Type therefore gives music and imaging their intended repeat behavior automatically.

Choose Practical Repeat Values

Avoid using values of several days or weeks as a general way to create variety. This is especially important for the artist Repeat Value because it affects every music track linked to that artist. When many artists remain unavailable for a long time, the normal candidate pool becomes unnecessarily small.

Power Studio protects playlist generation by progressively relaxing breakable scheduling rules when the requested combination leaves too few candidates. This is an intentional continuity safeguard. It can, however, produce a broader selection than the format owner expected, or give the remaining eligible tracks more exposure than intended. Practical Repeat Values allow the normal rules to guide most selections.

Use these values as starting points for testing, not as fixed requirements:

For example, Madonna or Michael Jackson can have enough different suitable tracks for another title to be considered after one or two hours. The Repeat Value of the individual title can still keep that particular song resting for longer.

There is no single correct value for every station. Start with the intended audience experience, then test the values against the actual categories, library and clocks.

Extend Repeat Control With Exclusions

Power Studio extends Repeat Values to related track and artist records through Exclude Tracks and Exclude Artists:

• Use Exclude Tracks to connect versions that should share repeat protection, such as an original, radio edit, remix or duplicate record that listeners will perceive as the same song.
• Use Exclude Artists to connect artist identities that should be kept apart, such as aliases, group and solo names, or collaboration records.

When one of these tracks or artists is planned, Power Studio also updates the planning state of the connected records. Exclusions are therefore part of the Repeat Value design, not a workaround for it. They let the format owner decide which musical relationships listeners are likely to recognize.

Keep artist names and exclusions consistent, and connect only the relationships that matter to the station's sound. A collaboration can be linked to each relevant artist, while an occasional contribution can remain independent when no additional separation is wanted.

Match Repeat Values To Category Turnover

Repeat Values should be in line with how often the track's categories are requested by the format and how many eligible tracks are available in those categories.

As a rough estimate:

average category turnover = eligible tracks / calls per hour

A group of 20 eligible tracks called twice per hour has an average turnover of about 10 hours before artist spacing, dayparts, exclusions and other format choices are considered. Use a track Repeat Value below that theoretical turnover so the scheduler has several valid alternatives. When a category contains fewer tracks, use it less often, add suitable tracks or choose a shorter Repeat Value.

Calculate this from the tracks that are active and eligible at the intended date and time, not from the total number of audio files. A track can also belong to several categories, so review the combined demand from every Clock Format position that can select it.

Repeat Value Means Available, Not Guaranteed

A Repeat Value defines the earliest time at which a track or artist can normally be considered again. It does not mean the item will be scheduled as soon as that period has passed.

The next selection still depends on the Clock Format line, Criteria and Special values, dayparts, category separation, Max per Playlist, Rating and the other eligible tracks. Repeat Value controls rest; it does not create a fixed rotation promise.

Use Rating For Relative Exposure

Use Rating to tell the playlist scheduler which tracks may receive more opportunities and which library gems should appear only occasionally. A higher-rated track normally has more opportunities to qualify during regular selection, while a lower-rated track remains available but is selected less often.

This is more effective than assigning a Repeat Value of several days or weeks. Repeat Value sets the minimum rest period; Rating shapes the relative exposure after a track is available. If a Clock Format line requires a specific Rating range, that explicit range remains the selection boundary for that position.

Fine-Tune The Result

Generate consecutive hours and days to hear how track repeats, artist repeats and exclusions work together. One isolated hour shows the sequence, while a longer test shows the rotation.

If the result needs more or less variety, adjust the relevant Repeat Value or Rating, the exclusions, the size of the music pool or the number of calls in the clock. Change one layer at a time, generate the test again and listen to the resulting rotation.

Design The Hour Before Building It

Sketch representative hours on paper or in a spreadsheet first. Place the least flexible elements before filling the remaining positions.

Start with:

• news, traffic, commercial breaks and network joins;
• mandatory station IDs, sponsor messages and program elements;
• live sources, downloaded programs and other time-dependent content;
• presenter links, features and voice-track positions;
• music groups and station imaging.

Then review the sequence as a listener would hear it. Look for long runs of similar material, abrupt tempo or mood changes, repeated artist types, too many interruptions, and imaging that competes with speech. The order of categories matters as much as the number of positions.

Create separate clocks only when the listener experience or operational workflow is meaningfully different. Morning drive, daytime, evening, overnight, weekend and specialist programs may need different clocks. Small variations can often share one clear clock instead of creating many near-duplicates.

Build The Format In Power Studio

Use the Format Planner to turn the design into two layers:

• A Clock Format contains the ordered lines for one hour.
• A Day Format assigns Clock Formats to times during a broadcast day.

Build one representative Clock Format first. Give it a name that describes its purpose, such as Weekday Daytime or Sunday Evening, and add the fixed and dynamic elements before the music lines.

Use the appropriate line type:

• Normal selection criteria for music and other items selected from a pool.
• Static Item for a named, reusable fixed item.
• Macro Item for dynamic content such as traffic, news or downloads.
• Live source item for an external input or stream.
• Link to previous item when an item must remain attached to the preceding item.
• Fill Out when an item must still occur before a fixed transition.
• Rotate Tracks when a smaller, deliberately managed pool should use rotation behavior.

Within one criteria column, selected values work as OR. Across different columns, criteria work as AND. A line with Current or Recurrent in one column can enlarge the pool; adding English language in another column limits that combined pool to matching English tracks.

Start with the minimum criteria needed to express the programming decision. Add tempo, mood, year, rating or other limits only when they improve generated playlists and the matching metadata is reliable.

Choose Between Explicit And Flexible Clock Lines

Power Studio supports two useful ways to build normal music positions.

With an explicit clock, each line calls for one narrowly defined Criteria value or combination. This gives precise category placement and makes the hour easy to explain. Use it for important rotation positions, specialist segments and listener promises that must be recognizable in every generated hour.

The drawback is rigidity. Repeating the same category sequence every hour can make the station predictable, and a line with one small required pool has few alternatives when repeat, artist or daypart rules block its tracks.

With a flexible clock, a line allows several values from one group. Power Studio can then choose from the remaining values while Category Separation and Max per Playlist control the result. Flexible does not need to mean unrestricted: a controlled OR pool such as Recurrent or Gold is safer than a music line with no Criteria at all.

The available controls apply to Criteria, Special, Rotation, Audience, Decade and Language:

• Max consecutive determines how many tracks with a value may occur in succession.
• Separation determines how many other tracks must occur before that value may return after its maximum consecutive use.
• Max per playlist caps how often a value may occur in one generated playlist.

These settings shape a pool; they do not define a minimum or guarantee a target percentage. If an hour must contain exactly three currents, use explicit current positions. If it may contain a varying blend with no more than three currents, a broader pool with Max per Playlist can be appropriate.

Do not set separation or maximum rules that contradict the clock. For example, a clock that explicitly calls the same Criteria value four times cannot also expect a Max per Playlist of two to be satisfied normally. When only one value is selected on a line, review the Ignore when only one value is selected for a clock format line option for that classification. It can keep separation from fighting an intentional fixed position, but it does not turn an impossible pool into a healthy one.

A completely unrestricted music line can select from every active music track that passes its other rules. Use that only when the library is deliberately homogeneous or another classification provides the intended boundary. For most stations, freer programming should still start from a documented group of acceptable Criteria values.

Recommended Hybrid Approach

Combine both styles:

1. Use explicit lines for the core rotation and fixed editorial promises.
2. Use controlled multi-value lines where variety is welcome.
3. Use Criteria for the main pool and add Special only where a real secondary condition is needed.
4. Use separation to prevent clusters and Max per Playlist to prevent one value from dominating the hour.
5. Generate consecutive test hours and inspect the actual distribution before adding more rules.

This keeps the station identity visible in the clock while giving Power Studio enough choice to solve normal repeat and artist conflicts.

Think of the format as four layers:

Keep each decision in the correct layer. Do not add a narrow Special condition to solve an artist-repeat problem, and do not raise a Repeat Value to correct a category balance that belongs in the clock or separation settings.

Choose Timing Behavior Deliberately

A good music sequence can still fail operationally when its timing model is wrong.

In a Day Format, Floating allows tracks to play in full and lets the next playlist start close to its planned time. This often suits music-led or presenter-led hours. A non-floating transition keeps a stricter boundary and may fade preceding music so news, commercials or a network join starts on time.

Use fixed behavior only where the station has a real fixed commitment. Check Clock Format Duration, Extra time, Fill Out lines and linked items together. The goal is not merely to make the planned duration add up, but to produce a playable hour with safe transitions and enough reserve content.

Use Candidate Counts As A Warning Signal

The Tracks column in a Power Studio Clock Format shows an estimated number of tracks available for a line. Use it to find unexpectedly small pools while designing the clock.

The number is a guideline, not a library total or scheduling guarantee. Actual scheduling also depends on the selected date and time, previously planned items and the rules applied during that run. A value of zero does not necessarily mean that the scheduler cannot find an item, but it is a reason to inspect the criteria and library.

Generate, Listen And Review

Do not approve a format from the clock editor alone. Generate test playlists for several representative dates and hours, including:

• the busiest weekday daypart;
• an evening or overnight period;
• a weekend;
• the same daypart on consecutive days;
• a fixed news, traffic or commercial transition;
• an hour with a small or specialist music pool;
• unattended automation and, where applicable, a presenter-led hour.

Review both the playlist and the sound. Check:

• category and rotation balance;
• title and artist repetition across adjacent hours;
• songs that repeatedly land in a similar clock position or time of day;
• tempo, mood, era and language flow;
• imaging and speech placement;
• total duration and reserve content;
• fixed-time transitions and Fill Out behavior;
• missing, unavailable or incorrectly classified items;
• selections that are technically valid but editorially wrong.

Use Playlist Insight and planning analysis to see which Clock Format line selected an item, how many candidates were available and where the scheduler had difficulty. Then correct the cause in the right place.

If one track is classified incorrectly, fix its metadata. If a whole pool is too small, review the category and separation model. If the same manual playlist correction is needed repeatedly, change the Clock Format. Avoid solving a structural problem with daily manual edits.

See Scheduling Review and Playlists for the operational review workflow.

Introduce Changes Safely

Treat a format change as an editorial release, not as a quick setting change.

1. Copy or document the current working format.
2. State the intended listener-facing change.
3. Update metadata and content pools before clocks that depend on them.
4. Test the new Clock Formats on future dates.
5. Compare the distribution and sound with the current format.
6. Have the format owner approve the result.
7. Assign the new clocks in the correct Day Formats and weekday defaults.
8. Review the first generated broadcast days after activation.

Keep temporary holiday, event and campaign formats clearly named. Remove or archive them when they are no longer used so they are not selected accidentally later.

Format Checklist

Before using a format on air, confirm:

• The station promise and daypart goals are written down.
• Category names have one agreed meaning.
• The active library can support the planned exposure and separation.
• Clock Formats are readable and contain only necessary rules.
• Day Formats assign the correct clocks at every changeover.
• Floating, fixed timing, Fill Out and dynamic content have been tested.
• Several generated hours have been reviewed and listened to.
• The first live or automated days have a named reviewer and fallback plan.

Continue with Build A Clock And Day Format Step By Step for a complete worked example.

Once the format is stable, configure automatic generation on one clearly assigned machine with Scheduler. Continue reviewing results: library changes, new music, seasonal material and programming changes can all alter how the same clocks perform over time.