Creator and Editor Feedback Rounds: Review Cuts Without Chaos

Key Takeaways

• Storyflow is our pick for running a creator and editor's review rounds across a month: each video's wall holds the edit brief, the review link and one notes table per round, on a board the editor joins free when a paid member invites them.
• Our editorial rule: review story first, then pacing, graphics, captions and sound, and the thumbnail last. Round 1 checks layer 1, round 2 checks layers 2 to 4, and a final check covers layer 5 and errors. Each layer is cheaper to change than the one before it.
• A note asks for a change inside the current round's layer and the agreed scope. A change request reopens an earlier layer or adds new work, so it gets a cost in days and a yes or no before the editor starts it.
• In Storyflow, give each notes round 2 working days on the review calendar, and stagger four videos one week apart so each week has one rough cut, one fine cut and one final.
• A usable note has four parts: timecode, what you see, why it matters to the viewer, and what to try. "It drags" is not a note; "04:10 to 05:30 repeats the clamping from 02:40, cut to the reveal" is.
• A cut is final when the final check passes and the creator writes one sign-off line on the video's wall. Picture lock is the point after which sound, colour and captions stop moving.
• Storyflow does not pin a comment to a frame or a timecode. Timecoded review happens in the editor's review tool or the editing app, and the link and the decisions live on the board.

How to Review a Month of Cuts With Your Editor: 8 Steps

Review rounds tend to go wrong in three places: notes arrive in four apps, the creator mixes story notes with typo fixes, and nobody can say when a cut is done. These eight steps close all three. Storyflow is our product, so weigh the tool choice with that in mind; the method works anywhere that holds a table beside the work.

1. Set up one Storyflow board for the month, with a wall per video. Each wall holds the script, the edit brief, the review link and the round tables. The editor never asks where something lives.
2. Build the review calendar as a table on the Storyflow board. One row per video, rows kept in date order, with columns for rough cut, round 1 notes, fine cut, round 2 notes, final cut, final check and publish. Count every date back from the publish day.
3. Agree the five layers and what each round may touch before the first cut lands. Write them at the top of the board: round 1 is story, round 2 is pacing, graphics, captions and sound, and the final check is the thumbnail and errors.
4. Watch round 1 once without stopping, as a viewer, then write notes on story only. Put them in the Round 1 table on the video's wall within 2 working days.
5. Sort every note before you send it: note or change request. A change request goes into its own table on the Storyflow wall with the days it adds and a decision column.
6. Write round 2 notes against the timecodes in the editor's review tool, then copy the list to the Storyflow wall. One list, once, in one place. The board is the record; the review tool is where you point at a frame.
7. Run the final check as a yes or no list, not a notes round. Captions read against the locked cut, the thumbnail against the first 30 seconds, chapters, end screen and the sponsor disclosure.
8. Write the sign-off line on the Storyflow wall and stop. "LOCKED, 1 March, final check passed, signed off by Dani." After that line, only errors reopen the cut.

If the plan and handoff side of the month is the part you are missing, the monthly handoff checklist for a creator and editor covers the planning session and the brief, and this guide picks up when the first cut arrives. The YouTube content pipeline page shows the board around both.

A kanban of fictional client projects. Swap clients for this month's videos and the Waiting column becomes "waiting on notes", which shows at a glance who holds each cut.

The Storyflow 5-Layer Review Sequence

Most review chaos is not about taste. It is about order. A creator who notes the font on a lower third in the same message as "the whole middle section should go" has asked the editor to polish something that is about to be deleted. The fix is a fixed order of attention, written on the board where both people can see it.

The rule, defined

The Storyflow 5-Layer Review Sequence: on a Storyflow board, every cut is reviewed in five layers in a fixed order (story, pacing, graphics, captions and sound, thumbnail), with round 1 on the rough cut checking layer 1, round 2 on the fine cut checking layers 2 to 4, and a final check on the locked cut covering layer 5 and errors; any note that reopens an earlier layer is logged as a change request. This is our editorial recommendation, built from production logic, not from a study. Change the round boundaries if your channel needs to, and keep the order.

Why five layers, in this order

Each layer depends on the one before it, and each is cheaper to change than the one before it.

The fifth layer is last for a reason YouTube's own analytics make plain. YouTube's audience retention help defines the intro figure as the share of viewers still watching after the first 30 seconds, and says a high figure can mean the first 30 seconds matched what the thumbnail and title led viewers to expect. You can only check that match against a cut that has stopped changing.

Why two rounds and a final check, not three rounds

There are two kinds of notes, structural and finishing, so there are two rounds. The final check is not a third round: it asks yes or no questions about errors and packaging, and a "no" names the error. A third notes round almost always means the edit brief left a story decision open, so fix the brief for next month instead of adding rounds this month. The two-round count matches the 4-2-1 Rule in the monthly handoff checklist, so the two guides work together.

What the rule leaves out

It does not tell you how to cut, what to pay or which ideas to make. It does not replace a review tool for pointing at a frame. It is a shape for attention, and it works only if the creator holds to it in round 1, which is the round where the temptation to mention everything is strongest.

How to put the rule on the board

In Storyflow, write the five layers as a note at the top of the month board, and give every round table on every wall a Layer column. A note in the wrong layer is then visible before it is sent, and the editor can see which round a row belongs to without asking.

A weekly planner board. The review rhythm in this guide fits in the same shape: cuts on Monday, notes on Wednesday, finals on Friday.

Note vs Change Request: The Line Between Feedback and New Work

A note asks the editor to change something inside the current round's layer and the scope the brief already agreed; a change request reopens an earlier layer or adds work the brief did not include. In Storyflow, notes go in the round table on the video's wall and change requests go in a separate Change Requests table with a cost and a decision.

A note spends the editor's time inside the deal. A change request spends time outside it, so it needs a price and a yes before anyone starts. Calling a change request a note is a quick way to sour a freelance relationship: the creator thinks they asked for a tweak, the editor loses a day, and neither says so until the invoice.

The three-question sort

Before you send a round, read every line against three questions:

• Does it touch a layer earlier than this round's? A story note in round 2 is a change request.
• Does it add something the brief did not include? A new graphic, a new section or a pick-up shot is a change request.
• Does it need footage or audio that does not exist yet? That is a change request, and often a reshoot.

Three "no" answers mean it is a note. One "yes" moves the line into the Change Requests table.

Price it in days, not in feelings

Write the cost as days added to the final cut, agreed with the editor, plus any fee your agreement sets. "Plus 1 day, no fee" and "plus 2 days, half-day rate" are both fine answers. In Storyflow, the Change Requests table has four columns that settle this: Request, Layer reopened, Days added, Decision. A request with an empty Decision cell is not approved, whatever the chat thread says.

When the answer is "next video"

Some change requests are good ideas that arrive too late. The best home for them is the next video's wall, not this cut. A creator who realises in round 2 that the whole video should open on the failure, not the success, has learned something about the format. Put it in next month's brief and lock this one.

When a note turns into a change request mid-round

Sometimes the editor finds that a small note is big: "tighten the intro" turns out to need a re-ordered first minute. The editor flags it on the row, moves it to the Change Requests table, and waits for a decision. That one habit keeps the editor from silently absorbing a day and keeps the creator from being surprised by a late cut.

What Each Round Checks

Every round has a cut type, a set of layers and a question it answers. Write this table at the top of the month board and point at it when a note drifts.

Round 1: rough cut, story only

Watch once without stopping, at normal speed, with the edit brief closed. Your first viewing is the only one where you see what a viewer sees. Then write notes on five things only: whether the hook makes the promise, whether each section earns its place, whether the order builds, what is missing, and what to cut. A rough cut with temp music, missing b-roll and no graphics is supposed to look rough. Noting that is noise. If round 1 finds a hook problem on every video, the fix sits upstream, in planning the video from idea to script.

In Storyflow, the Round 1 table on the video's wall has one row per note, and every row's Layer cell reads "Story". If you catch yourself writing a different layer, park the note in a Round 2 Parking column so it is not lost and not sent.

Round 2: fine cut, pacing, graphics, captions and sound

Now the finish. Watch once with sound and once muted. Muted viewing tests captions and on-screen text the way a commuter sees them, and it catches graphics that only make sense with narration. Note trims, pauses that run long, b-roll that repeats, music under speech, levels, caption errors and graphic timing. Nothing in round 2 should change the story; if a story idea appears, it goes through the three-question sort.

Final check: locked cut, packaging and errors

The final check runs as a list of yes or no questions, covered in the section on when a cut is final below. It has one rule: a "no" must name an error, not a preference. "Caption at 11:02 misspells mortise" is a valid no. "I think the outro could be warmer" is not.

Sponsor review: when a third party watches

When a brand has paid for an integration, its review is a separate pass against its own brief, not a third creative round. Agree in the deal which cut they see, how long they have and which points they may change, and write those terms on the sponsored video's wall before the shoot. YouTube asks creators to tick the paid promotion setting in the video details, which adds a disclosure label at the start of the video. The US Federal Trade Commission's guidance for influencers says a disclosure belongs in the video itself rather than only in the description, and that viewers are more likely to notice one made in both audio and video. Your editor checks both in the final check; your agreement and local law decide what else applies.

A fictional brand's advertising brief laid out on a board. A sponsor's agreed points belong on the sponsored video's wall in the same way, beside the cut they apply to.

How to Write a Note an Editor Can Act On

An editor reads a note looking for one thing: what to do. A note that describes the creator's feeling leaves the editor guessing, and a guess costs a round. The format below adds a few seconds per note and removes most of the back and forth.

The four parts of a usable note

1. Timecode. Where it starts and, for a stretch, where it ends. Use the timecode in the review copy, not the raw footage, unless you are pointing at an unused take. Editing apps count in hours, minutes, seconds and frames, the SMPTE timecode format, but minutes and seconds are enough for most YouTube notes.
2. What you see or hear. The fact, not the feeling: "the clamping shot from 02:40 appears again".
3. Why it matters to the viewer. "We already know this, so the middle stalls before the reveal."
4. What to try, or "your call". "Cut to the reveal at 05:20", or "Your call: something shorter here". A note with no suggestion is allowed, but say so, so the editor knows their judgment is invited.

Then give it a weight: Blocker (the cut cannot publish with this), Fix (do it unless you have a reason not to, and say the reason) or Your call (the editor decides). Weights tell the editor where the creator's taste ends and their own begins.

Ten vague notes rewritten

Ask questions as questions

"Why did you cut the second test?" is a question, and it deserves an answer before a decision. Put questions in their own rows with the weight "Question", and let the editor reply in the same row. Half the time the answer is "the audio clipped on that take", and the note disappears. A question written as an order ("put the second test back") skips the information the editor already has.

One voice per round

When a co-host, a manager and a creator all watch, their notes merge into one list before the editor sees them, and one person settles contradictions. Two people's notes on the same timecode that disagree hand the editor a decision they cannot make. In Storyflow, give the round table an Owner column, and let the person named at the top of the wall own the merged list.

Write the list once

A stream of messages ("oh and one more thing") is the fastest way to lose a note. Write the full list, read it once against the three-question sort, and send it as one table. If you remember something an hour later, add a row and tell the editor that one row was added, with its timecode. The guide to managing video projects with a team has more on version discipline when several people review.

A document open on a board, here holding a written analysis. Long round notes, such as a structural rethink of a video, read better as a document on the video's wall than as forty table rows.

Review Deadlines for a Month of Videos

A review calendar counts back from each publish date and staggers videos one week apart, so the editor never has two rough cuts due in the same week. Write it as a table on the Storyflow board, one row per video, rows kept in date order.

The turnaround table

These starting turnarounds assume one freelance editor, long-form videos of 10 to 20 minutes and a weekly upload. Replace them with your own after a month.

In Storyflow, those nine steps become columns of the review calendar table, and the empty date cells show a hint until you fill them, so a missing deadline stands out.

Stagger four videos one week apart

Hand off one video a week and every week has the same shape: a rough cut and a fine cut land on Monday, notes go out on Wednesday, a final cut lands on Friday, and one video locks the following Monday. The editor works on three videos at once, each at a different stage, which is a steadier week than four rough cuts arriving together after a batch shoot. If you batch the shoot, batch the handoff too, but release the footage to the editor one video a week. The batching and editorial calendar guide covers the shoot side of that rhythm.

What happens when the creator is late

Late notes move the publish date or squeeze the editor, and the second is how good editors leave. Agree the rule up front: notes that arrive after the deadline move the final cut by the same number of days, and if that misses the upload, the video moves a week and the next one in the queue takes its slot. In Storyflow, change the row's dates in the review calendar the same day, so the editor sees the new plan instead of hearing about it.

What happens when the editor is late

The same rule runs the other way: a late cut moves the creator's notes deadline by the same number of days. The point of the rule is not blame. It is that nobody absorbs someone else's delay by working the weekend, because that is a cost that never appears on the board.

Reminders

Storyflow has no due-date reminders, so put the Wednesday notes block and the Monday final check in your own calendar as appointments. A to-do on the video's wall with an assignee and a due date gives the editor an in-app notification when it is assigned, which is useful for change requests that need a reply. If you also keep a publish calendar for the audience side, the content calendar for creators page shows it as a table beside the plan.

When Is a Cut Final?

A cut is final when the final check passes on the locked cut and the creator writes a sign-off line on the video's wall. Film and television call the equivalent moment picture lock: the point when changes to the cut are done and approved, after which sound, music and colour can be finished because the timing will no longer shift. A YouTube edit compresses those stages into days, but the logic holds. Every change after the lock costs re-timing somewhere else.

The final check list

Run it on the final cut, once with sound and once muted. Each line is yes or no.

Sources for those rules, as of November 2026: YouTube's help pages on chapters, end screens, custom thumbnails and adding subtitles, and the BBC subtitle guidelines, which recommend 160 to 180 words per minute and, for online landscape video, a line no wider than 68% of the frame. If you want a written loudness standard to point at, broadcasters in Europe work to EBU R 128, which sets an average of -23 LUFS; for YouTube, agree your own target with the editor and put it in the brief.

Write the sign-off in one line

"LOCKED, 1 March, final check passed, signed off by Dani." One line, at the top of the video's wall, by the person named as the approver. In Storyflow, write it in a note, not a comment, because resolving a comment thread deletes it, and a deleted approval is no approval. The line tells the editor to export and stop, and it tells next month's creator what was decided.

What may still change after the lock

Three things can change after the lock without reopening the cut. The thumbnail can still be tested: YouTube's title and thumbnail testing lets eligible long-form videos compare up to three options, picks a winner by watch time share and usually finishes within two weeks, and it runs in YouTube Studio on a computer. Captions can be corrected in YouTube Studio after publishing. The description and its links can be edited at any time. Anything else, including "one tiny trim", reopens the cut and goes through the Change Requests table.

Captions: who checks them

The editor produces captions; the creator checks names, terms and anything spoken off-mic. Captions are text for people who cannot hear the audio, which is why the W3C's captions guidance treats them as including non-speech information needed to follow the video, not only the words. Automatic captions are a draft. Brand names, technical terms and accents are where they fail, and a creator knows those better than anyone.

A six-stage workflow from brief to delivery with a comment beside one stage. The same left-to-right layout works for one video's path from handoff to lock.

Who Gives Notes, and Who Says Yes

Most channels with an editor have more than two people in the review: a co-host, a manager, a sponsor, a friend whose taste the creator trusts. Every extra voice is useful in round 1 and dangerous in the final check. Decide who does what before the month starts.

The roles on a review

Name one approver per video

One name, at the top of the wall. Approval by committee gives every reviewer a veto and none of them the job. If a manager approves sponsored videos and the creator approves the rest, write that on each wall, not in a group chat.

Give the editor a channel role, not a password

When the editor uploads and schedules, give them a channel permission. YouTube's channel permissions help describes an Editor role that can upload and publish but cannot delete published content or manage permissions, and an Editor (Limited) role with the same rights minus revenue data, as of November 2026. Editor (Limited) is usually the right choice for a freelancer.

The Round Notes Template to Copy

Copy this table onto each video's wall as the round notes table, one per round. The filled rows are a fictional round 2 for the fictional channel Hollow Oak Woodworking, video 3, "I Restored a 1950s Hand Plane".

Two rows are change requests. Row 5 adds new work and was approved with a day added; row 8 reopens story in round 2 and went to the next video's wall. Everything else is a note the editor could act on without a reply. In Storyflow, the Weight and Done columns are plain text or status cells, and the blank ones show a hint until someone fills them.

A six-phase launch board with a status tracker beside the columns. A month of four videos reads the same way: one column per video, the review calendar as the tracker.

Worked Example: Hollow Oak Woodworking's March

The channel is fictional and so are the people; the dates and the method are the ones this guide recommends. Dani makes a weekly woodworking video and works with Tomas, a freelance editor, who also delivers captions and the final thumbnail from Dani's concept. March 2027 has four publish Thursdays: 4, 11, 18 and 25 March. Video 2 carries a sponsored segment for Kestrel Clamps, a fictional tool brand.

The board

Dani's March board has a note at the top with the five layers and the round rules, a review calendar table, and four walls, one per video. Each wall holds the script as a document, the edit brief, a link card to the review copy in Tomas's review tool, a Round 1 table, a Round 2 table, a Change Requests table and the sign-off note. Video 2's wall also holds the sponsor's agreed points. Each wall started from the same layout as the YouTube video planner. Tomas was invited to the board and joined free; he works on it by hand and has no in-app AI, which he does not need for this.

The review calendar

Read down any Monday: on 1 March, Tomas delivers V3's rough cut and V2's fine cut, and Dani locks V1. Read down any Wednesday: on 3 March, Dani sends V3's round 1 notes and V2's round 2 notes. The rhythm repeats.

Round 1 on V1: a story problem found early

Dani watched V1's rough cut once, straight through, and wrote six notes, all story. The important one: the finished bench appeared at 00:22, after a minute of explaining why plywood is underrated. The note read "00:00 to 00:30: show the finished bench in the first 5 seconds, then explain", weighted Blocker. A second note asked a question: why was the sheet-cutting diagram missing? Tomas answered in the row: the diagram existed only in Dani's notebook. Dani photographed it and uploaded it to the board; it became a note, not a change request, because the brief had listed it.

Round 2 on V3: a change request caught

Round 2 on V3 produced the eleven rows in the template above. Two were change requests. The exploded diagram of the plane's parts was new work, so Tomas priced it at one extra day, Dani approved it in the Decision cell, and the final cut moved from Friday to Monday morning, still in time for the lock. The idea of moving the sharpening section earlier reopened story in round 2, so it went to April's board as a note for the next restoration video.

The sponsored video

Kestrel Clamps' agreement let its marketing contact see V2's fine cut and gave them two working days, landing inside Dani's round 2 window. Their notes went into a Sponsor table on V2's wall, separate from Dani's, and Dani merged the one that mattered (show the quick release in close-up) into her own round 2 list. In the final check Tomas confirmed the spoken disclosure at the start of the read and the on-screen text, and Dani ticked the paid promotion box when the video was scheduled.

The lock and the look-back

Each video's wall ends with a sign-off note. On 29 March, Dani spent fifteen minutes reading the four Round 1 tables side by side. Three of the four videos had a hook note. The fix went into April's edit brief: "Open on the finished piece, explain after". April's round 1 notes should be about something else. Two round notes that were really new video ideas went to the channel's idea bank instead of April's board.

A pre-production board for the next video, with script notes and dated next steps in walls. The look-back's lesson, open on the finished piece, goes into the next brief here before anything is filmed.

Do This in ChatGPT or Claude

You can set up the review calendar, the round tables and the change log from a chat, and they land on the Storyflow board your editor opens. ChatGPT calls these plugins and Claude calls them connectors; both use the same Storyflow account.

Storyflow works inside ChatGPT and Claude; the board stays in your Storyflow account either way.

Install it in ChatGPT

Open the Storyflow listing in ChatGPT's plugin directory, select Install plugin, sign in to Storyflow and choose which projects ChatGPT may use, and whether it may also make changes. Availability depends on your ChatGPT plan, workspace and region, as OpenAI's plugin help explains, and its permissions article covers when ChatGPT asks before acting. In a chat, type @ and pick Storyflow, or choose it from the + menu. The ChatGPT YouTube video plan page shows the board side, and the ChatGPT video script page covers the script that round 1 is judged against.

Connect it in Claude

Add a custom connector with the address https://mcp.storyflow.so/mcp, following Anthropic's custom connector guide. Setup for every assistant is on the Storyflow MCP page, and the Claude YouTube video plan page shows the same job from Claude.

Prompts to copy

1. "On my March board, add a table called Review Calendar with one row per video and columns Video, Handoff, Rough cut, Round 1 notes, Fine cut, Round 2 notes, Final cut, Lock, Publish. Publish dates are Thursdays 4, 11, 18 and 25 March 2027. Count back: lock the Monday before, final cut the Friday before that, round 2 notes 2 working days before the final cut, fine cut 2 working days before that, round 1 notes 3 working days before the fine cut, rough cut 2 working days before that, handoff 5 working days before the rough cut. Keep the rows in date order."
2. "On V3's wall, create a Round 2 table with columns #, Timecode, Layer, What I see, Why it matters, What to try, Weight, Note or change request, Done. Here are my notes: [paste]. Put each note in its own row, set Layer to Pacing, Graphics, Captions or Sound, and mark any note about story or new work as Change request."
3. "Read the Round 2 table on V3's wall and copy every row marked Change request into a new table called Change Requests with columns Request, Layer reopened, Days added, Decision. Leave Days added and Decision empty."
4. "Add a note at the top of each video's wall listing the five review layers and which round checks which."
5. "What changed on the March board in the last week, and who changed it?"
6. "Compare the Round 1 tables on all four walls and list the kinds of note that repeat, so I can add them to April's edit brief."
7. "Add a note at the top of V1's wall: LOCKED, 1 March, final check passed, signed off by Dani."

What lands on the board

Tables with the rows and columns you named, notes, documents, headings, links and walls. The assistant reads the board's tables and notes, reports what changed and who changed it, and lists who is on the board. Plugin actions run on your ChatGPT plan and use no Storyflow AI credits.

What to check by hand

• Timecodes and what you saw: the assistant cannot watch your cut through Storyflow. It sorts and copies what you wrote.
• Layer calls: read every row it marked as a note against the three-question sort. A story note in round 2 is easy to misfile.
• Dates: check the review calendar against a real calendar, especially around weekends and month ends.
• Comments: the plugin cannot read board comments, so keep anything you want it to read in tables and notes.
• Owners: it cannot assign a to-do or ticket. It can fill an Owner column with people already on the board.
• Photos: a picture attached in the ChatGPT chat does not reach Storyflow; the plugin gives you an upload link for the board.
• Allowance: an editor you invite joins free with 25 plugin or connector actions a week; Plus, Pro and Max have no weekly limit.

The in-app AI is separate

Inside Storyflow, on paid plans, the built-in AI has its own menu workflows, such as Review what's on this board, What's missing here? and Turn my notes into a table. It reads the current board plus up to five documents and three other boards you attach, and it uses Storyflow AI credits. Those workflows do not run through the plugin or the connector, and an invited editor on a free account has no in-app AI.

Where to Run Review Rounds: Storyflow vs Other Kinds of Tool

Storyflow is listed first on one stated basis: the job in this guide is the review record across a month (calendar, notes, change requests and sign-off) beside each video's plan, and Storyflow holds all of it on one board. Pointing at a frame is a different job, and another kind of tool does it better.

A video review tool

A proofing or review tool lets the creator click on a frame and type, so the note lands at the exact timecode, and many show versions side by side and record an approve button. That is the best way to point at things in round 2. Its limit is scope: it holds a cut, not the month, so the round calendar, the brief and the change log live elsewhere. Choose a review tool for the round 2 pass on any video where a frame matters, and link the review copy from the video's Storyflow wall. The creative review page shows how the board side of that pairing is laid out.

A shared doc

A doc is the most familiar place to write notes and the easiest to share. It is good for one long structural note, a page of thinking about why a video does not work. Its limit is that a channel ends up with eight docs a month, none of which show the dates or which notes were done. Choose a doc when one video needs a written rethink, and put it on the video's wall as a document so it sits beside the cut.

A spreadsheet

A spreadsheet is strong on dates and rows across many videos, and agencies running several channels often live in one. Its limit is context: a row cannot show the script, the thumbnail concept or the reference frames, so a note about "the shot from the brief" sends someone to another app. Choose a spreadsheet when the job is delivery tracking at volume and the creative review happens somewhere else.

A project management app

Project management apps bring reminders and dependencies, which Storyflow does not have. Notes typed as tasks lose the shape of a round, and the creator ends up with thirty task cards instead of one list. Choose one when the whole team already runs its work there and the review happens in a review tool; keep the round list in one task, not one task per note. For status across many videos on a board instead, see the video production tracker.

Team chat and voice notes

Chat is the fastest way to ask "which take?" and the worst place to keep a decision. Voice notes are worse, because nobody can search them. Use chat for questions, and copy the answer into the row it belongs to.

The editing app's own markers

Editors often turn notes into markers on the timeline, which is the right place for their working list. It is invisible to the creator and to next month's look-back. Let the editor keep markers, and keep the agreed list on the board.

A monthly planner with five areas side by side. One board per month, with one area per video, is the shape this guide's review record takes.

Mistakes and Fixes

Noting everything in round 1

Fonts, music and typos in a rough cut bury the two notes that matter. Fix: in round 1, write story notes only, and park everything else in a Round 2 Parking column on the Storyflow table.

Sending notes as a stream

Six messages over an evening means at least one note is missed. Fix: one list, once per round, in the round table. Added rows get flagged with their timecode.

Calling a change request a note

The editor absorbs a day of unpriced work and the next cut is late. Fix: run the three-question sort on every line, and move anything that reopens a layer or adds work into the Change Requests table with days and a decision.

Reviewing on a phone, muted, on the move

A phone viewing hides levels, small text and colour problems, and a muted viewing alone hides sound. Fix: watch round 1 on a laptop or TV with sound, and do the muted pass in round 2 on purpose.

Letting three people send notes directly

Contradictory notes on the same timecode leave the editor to choose between people. Fix: one approver per video merges the list before it goes out, and the merged list is the only one.

Approving in a comment

Resolving a comment thread on a Storyflow board deletes it, and the approval goes with it. Fix: sign off in a note at the top of the video's wall, one line, with the date and the name.

Treating the final check as round 3

"While we are here" notes in the final check move the upload. Fix: the final check accepts errors only. A preference goes to next month's brief.

Changing the thumbnail promise after the lock

A new thumbnail idea that the cut does not deliver hurts the first 30 seconds. Fix: if the thumbnail changes after the lock, check it against the opening of the cut before you upload, and use YouTube's title and thumbnail test to compare it with the original.

Skipping the look-back

The same hook note appears every month. Fix: fifteen minutes at month end reading all round 1 tables side by side, and one line added to next month's edit brief.

Storyflow's Honest Limits for Review Rounds

Storyflow earns its place in this workflow as the record: the month's calendar, each video's brief and the round tables on one board. It does not do the following, and the workflow above is built around that.

• No timecoded comments on video. You cannot click a frame in Storyflow and leave a note on it. Use a review tool or the editing app for that, and link it from the wall.
• No frame-level approval or version compare. Storyflow does not show two cuts side by side or record an approve button per version. The sign-off note is your record.
• No publishing. Storyflow does not upload, schedule or publish to YouTube and has no connection to YouTube Studio.
• No calendar view or reminders. Dates live in table date cells and to-dos; tables cannot be sorted, so keep rows in date order. Put deadlines in your own calendar.
• Comments need sign-in, and resolving deletes the thread. A view-only link opens with no account; to comment or draw, the visitor signs in. Keep decisions in notes.
• Assistants cannot read comments. The ChatGPT plugin and the Claude connector read tables, notes and documents, not comments.
• No native desktop or mobile app. Storyflow runs in the browser and is best built on a laptop.
• Paid-only during early access. Plus is $7.99 a month billed annually ($9.99 monthly) and includes the in-app AI; pricing has the plans. Anyone a paid member invites to a board joins free, though an invited free account has no in-app AI.

For the video editor's view of the same board, see the page for video editors; for the creator's, the page for YouTubers; and for a full video team, the video team collaboration page and the video production workflow.

The Bottom Line

Review rounds stop being chaotic when they have an order, a format and an end. Put the month on one Storyflow board, review story before pacing and the thumbnail last, write notes with a timecode and a reason, price change requests before anyone starts them, and sign off in one line. Start with next week's rough cut: set up the Round 1 table on its wall before the cut arrives, and see how many of your notes survive the story-only rule. To build the board from a chat, use the ChatGPT YouTube video plan workflow; for the edit brief that feeds round 1, the video editing brief page has the structure.

This article was published in November 2026, with YouTube and FTC guidance read in November 2026.