The task
Several people work on a video. Its idea, source clips, script and feedback can end up in separate conversations. The team needs a shared screen with a clear state for each material.
The pilot fits into the existing work system. Editors and managers use their own roles and record publications after they happen.
The workflow
- A card holds the audience, topic, product, idea source, assignee and deadline.
- Materials come from a library or supplied links, with start and end timestamps for each excerpt.
- The script, edit file and ready-video versions belong to the same card.
- A manager approves the latest ready version or returns it with comments.
- Placement links and the actual publication date are stored separately; one video is counted once.
Edits and access
Editors work on assigned cards. Managers control assignment, acceptance and publication records. The server enforces the role permissions.
When two people edit concurrently, the page retains a draft and offers a comparison. Updating an approved material requires returning it for revision.
Verification and result
The source contains tests for video-project rules, viewer access, drafts and PostgreSQL behaviour. The pilot has a separate change with a verifiable file set.
The result is a manual approval workflow with ideas, materials, versions and acceptance on one screen. This pilot does not start collection, generation or social publishing. Audience-growth outcomes were not measured separately.