Common Idea Catalog workflows
Set up practical saved views for planning, production, review, publishing, and cleanup.
Once your Channel has real Ideas, the Idea Catalog becomes much more useful when you create a small set of saved views for the work your team repeats.
The goal is not to create dozens of views. The goal is to make the next action obvious.
Recommended starter views
Start with five saved views:
You can add more later, but these cover most early workflows.
Workflow: All Active Ideas
Use this as the team's everyday catalog.
Suggested setup:
- Layout: Table
- Sort: Updated: Newest
- Filter: Status is not in Archived
- Group By: Status or Assignee if your team wants sections
- Columns: Title, Status, Priority, Categories, Assigned To, Release Platforms, Filming Dates, Release Date
Save it as All Active Ideas. If this is the view you want to see first, set it as your primary view.
Workflow: Owner Queue
Use this when each teammate needs a focused list of their own work. This workflow works best with a custom Single Team Member field such as Owner, Editor, Producer, or Designer.
Suggested setup:
- Layout: Table
- Sort: Priority: Highest or Release Date: Earliest
- Filter: custom Owner field equals [teammate]
- Optional filter: Status is not in Published, Archived
- Group By: Status when each teammate needs to see what stage their Ideas are in
- Columns: Title, Status, Priority, Assigned To, Owner, Release Date, custom handoff fields
If several people need the same pattern, create one saved view per role or person, such as Producer Queue, Editor Queue, or Design Queue.
Workflow: Production Board
Use this for the day-to-day movement of Ideas through production.
Suggested setup:
- Layout: Kanban
- Sort: Priority: Highest or Updated: Newest
- Filter: Status is not in Published, Archived
- Board stacked by: Idea Status
- Visible columns: Idea, Planned, Scripted, Ready to Film, Filming, Editing, Review, Scheduled
Drag Ideas between columns as their status changes. Hide statuses that are not useful for your current production process.
If your team tracks a separate single-select field like Thumbnail Status or Sponsor Approval, you can create a different kanban saved view with Board stacked by set to that field.
Workflow: Upcoming Releases
Use this to keep publishing dates visible.
Suggested setup:
- Layout: Table
- Sort: Release Date: Earliest
- Filter: Release Date is not empty
- Optional filter: Status is not in Published, Archived
- Group By: Release Platform when the same Channel publishes to multiple platforms
- Columns: Title, Status, Assigned To, Release Platforms, Release Date, linked calendar event details if visible
This view pairs well with the content calendar. Use the catalog to inspect the Idea details, then use the calendar to see the schedule visually.
Workflow: Thumbnail Review
Use this when the team is judging visual direction.
Suggested setup:
- Layout: Grid
- Sort: Updated: Newest
- Filter: Status is in Review, Scheduled or a custom thumbnail status field
- Columns: not applicable for grid, but keep the underlying fields clean
If your Channel tracks thumbnail workflow with custom fields, add fields like:
- Thumbnail Status
- Designer
- Needs Revision
- Reference Link
Then use those fields in filters and table views when you need more detail.
Workflow: Sponsor Pipeline
Use this if the Channel handles sponsored content.
Suggested setup:
- Layout: Table
- Sort: Release Date: Earliest
- Filter: custom Sponsor field is not empty
- Optional filter: custom Sponsor Approval field is not Approved
- Columns: Title, Status, Sponsor, Sponsor Approval, Integration Type, Assigned To, Release Date
This workflow works best after you create sponsor-focused custom fields in the Channel.
Workflow: Cleanup Queue
Use this when the catalog starts getting noisy.
Suggested setup:
- Layout: Table
- Sort: Updated: Oldest
- Filter: Status is in Idea, Planned
- Optional filter: Priority is empty or a custom owner field is empty
- Columns: Title, Status, Priority, Assigned To, Updated At
Review the list, then archive or delete stale Ideas in bulk when appropriate.
Keep the view list curated
A useful saved view list is short and obvious.
Good saved views usually have:
- A clear audience.
- A repeat workflow.
- A meaningful layout choice.
- Filters that remove noise.
- Group By or Board stacked by settings that match how the team discusses the work.
- Columns that match the job.
Delete or rename views that no longer describe how the team works.
Common mistakes
Creating one saved view for every tiny variation
Use saved views for repeat workflows. Use temporary filters for one-off questions.
Skipping custom fields
Some workflows need fields that do not exist by default. Add custom fields first, then build saved views around them.
Not assigning a primary view
Set your most useful saved view as primary so the catalog opens in a productive state by default.
Next step
Create All Active Ideas and Production Board first. Once those feel useful, add workflow-specific saved views for your team.