Understanding the review workflow
Every review in Magpiie follows the same loop, whatever the format: upload, collect pinned feedback, work through it, upload the next version, and approve. Learn it once and it works for a YouTube video, a podcast episode, a thumbnail, or a script.
The review loop, step by step
- Upload a draft. Upload a video, short, thumbnail, script, or audio draft to a project to start the review.
- Bring in reviewers. Invite the people whose notes you need as project members, and share a public link with anyone who only needs to watch.
- Collect pinned feedback. Reviewers pin comments to the exact frame, script line, audio second, or spot on a thumbnail, tagged by category and priority.
- Work through the comments. The team moves each comment through Open, In progress, Needs info, Resolved, or Won't fix.
- Upload the next version. The new version stacks on top, and unresolved notes carry forward so reviewers can check each fix in one pass.
- Approve. Reviewers approve the version, and the sign-off is timestamped against it.
Who does what
| Role in the loop | What they do |
|---|---|
| Uploader (editor, writer, designer, audio engineer) | Uploads drafts and new versions, works through assigned comments, and marks them resolved. |
| Reviewer (producer, creator, client) | Leaves pinned comments, answers questions, checks fixes on the next version, and approves. |
| Owner or production manager | Sets up projects, invites members, assigns feedback, and gives the final sign-off. |
Why a structured loop is faster
- Nobody rebuilds a to-do list from chat threads. The open comments are the to-do list.
- Editors jump straight to the frame, line, or second a note is about.
- Unresolved notes follow the draft to the next version, so nothing gets lost between rounds.
- Everyone always reviews the latest version, not a cut you replaced two days ago.
- The approval is on record, so "did we sign off on v3?" takes one look to answer.