These cookies are required for the website to function properly. They ensure security, enable basic features like page navigation, and store user session data. You cannot disable these cookies.
- Radio Station Management
- Features
- Production Work
Production Work
Assign project tasks and keep due dates and completion visible.
OverviewTasks in Review×
Radio Station Management · Production Work
New
Tasks in Review
Completion waits for the editor
| Task | Status | Project | Assigned to | Due date | |
|---|---|---|---|---|---|
| TSK-265 | Review | PRJ-5931 | 10 Oct | ||
| TSK-272 | Review | PRJ-8949 | 20 Oct | ||
| TSK-576 | Review | PRJ-2510 | 26 Oct | ||
| TSK-805 | Review | PRJ-6702 | 05 Oct | ||
| TSK-713 | Review | PRJ-9481 | 07 Oct |
6 of 6 records
TSK-265Production tasks · PT-75399
ReviewProjectPRJ-5931
Due date10 Oct
What you can do
Make the next piece of work clear
Production tasks record a task description, project, assigned person, due date, completion time and status. A producer can turn a project plan into specific work while the assignee sees what needs attention. Open, in progress, Review and Completed are the task’s available states. They describe the production work rather than the status of the parent project or content item.
A task is connected to Projects and People. That matters when several contributors work on the same program: the project gives context, and the assignee gives accountability. The People record also shows an assigned task count, useful for spotting a workload that needs discussion before another due date is promised.
How the work is organized
The content producer creates and assigns work, while the editor checks items that have reached review.
- Assign the person. Every production task points to a People record.
- Use the due date. Keep upcoming work visible before its project is due.
- Close the task deliberately. Record completion after its output has been checked.
What to agree during setup
Agree what deserves a separate task and who can change an assignment. A script draft, a recording edit and a final listening check may be separate tasks if different people own them. Decide what Review means for the team and who can mark a task Completed. Bring a sample project whose content is ready but one production task still needs review; that case tests whether the team can distinguish content approval from task closure.
Check the handoff on an actual case
For a planned interview series, the producer creates an editing task and assigns it to a colleague. The due date falls ahead of the broadcast window. The assignee begins work and moves the task to in progress. Once the edit is ready, the task enters Review. The editor checks the related content version and sends any corrections to the assignee. When the work is accepted, the task is marked Completed and the completion time records when that happened.
The project owner can see the task alongside other project work. The editor can use the review list to find outstanding checks. If the content item has not yet reached Approved, closing a task should not be treated as content publication; those are separate records with separate decisions.
What your team sees
- Production Tasks by Due Date — Find open and reviewing tasks with assignee, project and due date.
- Tasks in Review — Check work presented for editorial review.
- Projects in Production — See how open tasks fit the project schedule.
Follow the work through
- Content production: Move from project plan to completed work.
- Version and rights review: Check the version created by production.
Review the data model when importing outstanding tasks.
What it keeps track of
Data model- Production tasks
- Assigned production work items belonging to a project.
- Projects
- Content and programming projects with owner, schedule, budget and lifecycle status.
- People
- Station staff and contributors referenced by content, production and broadcast work.
- Content items
- Individual pieces of content produced under a project, from draft through publication.
- Content files
- Versioned file assets attached to a content item, with approval attribution.
Who uses it
Permissions- Content Producer
- , Editor, Station Manager and Admin.
- The producer assigns work; the editor reviews the result.
Set up Radio Station Management your way.
Start free, then use Proto to change fields, steps and approvals before your team goes live.