1. Radio Station Management
  2. Features
  3. Programming Schedule
Feature · Programming Schedule

Programming Schedule

Plan presenter led programs with visible air windows and broadcast status.

OverviewSlots Awaiting Approval
Radio Station Management · Programming Schedule

Slots Awaiting Approval

Approval waits for the station manager

New
Program titleStarts atEnds atStatusPresenter
Planned bs-31320 Oct23 OctPlanned
Planned bs-31309 Oct18 OctPlanned
Planned bs-79420 Oct26 OctPlanned
Planned bs-78806 Oct12 OctPlanned
Planned bs-60120 Oct27 OctPlanned
6 of 6 records
Planned bs-313Broadcast slots · BS-31122
Planned
Starts at20 Oct
Ends at23 Oct
Example screen with sample data

What you can do

Plan the air window

A broadcast slot holds the program title, presenter, start, end and status. The programming coordinator uses these records to build the running schedule, while the station manager reviews which programs are ready to air. A presenter is selected from People, so the schedule identifies a person rather than leaving a name in free text. A planned slot and an approved slot mean different things to the team; the status tells the reader whether the window has been accepted.

The calendar view makes the start and end visible together. A coordinator can compare neighboring programs before saving a change, then review the approved slots with the manager. Once a slot has aired, its status reflects that result. Cancelled slots stay recognizable in the record. The program title is the slot’s label; content production is tracked separately through projects and content items.

How the work is organized

The coordinator maintains the air windows, and the station manager owns the approval decision.

  • Keep each slot attributed. Select the presenter from the station’s people records.
  • Separate plan from approval. Use the status to show when a proposed window has been accepted.
  • Preserve the air window. Review the beginning and end together when moving a program.

What to agree during setup

Set the station’s planning horizon and decide who can approve a slot. Agree when an aired result is entered, who records a cancellation and how a changed presenter is communicated. Confirm the time zone used for the schedule before loading a week’s programs. Bring a sample day with an early program, a handoff between presenters and a cancelled window; these examples will expose ambiguous ownership quickly.

Check the handoff on an actual case

A coordinator creates a morning program for a presenter between 07:00 and 09:00. The slot is Planned while the station manager checks that presenter and window. After approval it appears among the Approved slots. The coordinator can see the next program’s start on the same calendar and resolve a gap before telling the presenters. After the broadcast, the coordinator records the slot as Aired. If the program is cancelled, the status makes that visible without erasing the planned window.

The example is about schedule control. An ad play log has its own scheduled and played times, tied to a content item; it should be reviewed in the evidence area rather than inferred from a program’s Aired status.

What your team sees

  • Programming Schedule — Read program windows and presenters on a calendar.
  • Slots Awaiting Approval — Check planned slots before the manager’s decision.
  • Approved Broadcast Slots — Prepare the accepted running schedule.

Follow the work through

Review the data model when importing existing program windows.

What it keeps track of

Data model
Broadcast slots
Scheduled programming slots with presenter, air window and broadcast status.
People
Station staff and contributors referenced by content, production and broadcast work.

Who uses it

Permissions
Programming Coordinator
, Station Manager and Admin.
The coordinator plans the slots; the manager approves the program window.

Set up Radio Station Management your way.

Start free, then use Proto to change fields, steps and approvals before your team goes live.

How to get started