How Process Driven manages YouTube content production in ClickUp

Executive overview

Producing one video per week — scripted, edited, published, promoted, and repurposed — generates a large operational load. ClickUp handles the entire pipeline: from idea capture through scripting, editing, and scheduling.

The system uses a form for idea intake, a sorting list for triage, a templated production task for each video, and a publication calendar linked via dependencies.

Build the pipeline around dependencies and templates, not memory — your routine tasks drive the schedule, not your attention.

Idea capture and triage

• A public ClickUp form captures video ideas from the team, course members, and YouTube comments
• Form includes fields for the idea, source link, member email, and optional screenshot
• All submitted ideas land in a sorting list — a shared backlog evaluated as a group
• A recurring routine task ("plan next X months of content") triggers the manual move of ideas into active production
• Ideas stay in the backlog until selected; no idea is lost or tracked in memory

Production task structure

• Each video becomes a task in the all video production list, created when an idea is approved
• A template is applied to the task on selection, adding: description scaffold, subtasks, due dates, and dependencies
• A prefix (episode number) is added to each subtask name so tasks are identifiable in Home without opening the parent
• The description holds general info (thumbnail notes, resources, upload instructions) rather than scattered custom fields — keeps context visible regardless of which subtask someone is in

Scripting and editorial workflow

• The script template inside the task has sections: hook, proof, information, what you learned, call to action, exit message
• Editor notes column captures in-edit requests (e.g. "add graphic here")
• Upload notes column captures YouTube-specific instructions (info cards, end screens, timestamps)
• Promotion messaging and timestamp drafts are written in the task before publication
• Review feedback is timestamped inline; checklists mark action items, bullets mark notes only

Editing review and dependencies

• Draft review tasks are chained with dependencies — each draft unblocks the next
• When a draft is approved, the editor receives an automatic notification their task is unblocked
• The final approval task is triggered automatically once the last revision is complete
• Dependency chains remove the need to chase anyone or track status manually

Publication scheduling and the calendar view

• A separate publication task exists for each week's video and newsletter
• The video production task is linked to the publication task via a dependency relationship (not a custom field) — this enables automations
• A rollup field on the publication task shows the video's current status and due date at a glance
• Scheduling a video means linking it to the next open publication slot by pasting a task relationship — no duplication, no copy-paste of metadata
• The gap between video-done date and publish date is a tracked metric; increasing that lead time is an explicit goal
• If a video is delayed, the status mismatch is visible in the calendar immediately

How the system evolved

• Started as one list with three subtasks: create, publish, repurpose
• Grew to the current structure after ~230 videos and the addition of team members
• Complexity scales with team size and production frequency — a solo creator doesn't need this level of detail
• The principle that stayed constant: no step lives in anyone's memory