The editor and storyboards

An episode is made from code, so it can be changed after it is made without starting again: the editor turns your request into a revision — rendered again and checked like any episode — while the version you have stays until the new one passes. And storyboards let you approve each episode's plan — its hook, its scenes and the facts they rely on — before any GPU time is spent.

The editor#

What you can change#

Every cut falls in a clean pause, clear of words and captions, so nothing is ever cut mid-word.

Make a revision#

1. Open a ready, held or published episode of the channel's own and find Edit this episode.
2. Fill in what you want:
   • In your own words — type a change; Another change adds a second and a third (each 3 to 280 characters);
   • Narration lines and captions — open the list, click a line, and edit what the narrator says (the field counts the words against the most that fit) or its caption (up to twelve lines at a time); in the Highlight style, one word between stars, *like this*, is the highlighted one;
   • Scenes — untick a scene to drop it, or move it with the arrows;
   • Caption style for this episode — where your workspace has caption styles.
3. Read What changes: each line before and after, the scenes dropped or moved, the style, and the new length. Any problem — a line too long for its place, a caption over 30 characters a line — is listed in words, and the request cannot be sent until it is fixed.
4. Press Make this revision — N credits. The price on the button is what is reserved.

The revision is rendered again and goes through every check, the critic included — usually 15 to 40 minutes. A notice on the episode says "Revision N is being made", with a link to follow it.

Versions#

Under the form, Versions lists every version of the episode: Version 1 · as it was made and each revision, with what was asked, who asked, when, its length, its critic score and what it cost — and What changed, line by line.

• A revision that passes every check becomes the current version: the posts not made yet use it, and it says "Current — the posts not made yet use it".
• A revision that does not pass is not charged, and the current version stays exactly as it was. Its reason is shown.
• Watch version N plays any finished version; Make current (a two-press button) switches back to it — posts made from then on use it.

An episode keeps up to 30 versions.

What a revision changes, and what it never changes#

• A post already made never changes. Each post records the version it went out with.
• Posts not made yet use the current version — on the schedule and when you press Post now.
• A channel that asks for approval asks again for a revised episode.
• A carousel not posted anywhere yet is made again from the new version.
• A held episode stays held after a revision passes: "Revised: this version passed every check — release it to post when you are ready." Its release price does not change.
• A translation made after the revision is made from the current version.

Storyboards#

What it does#

With storyboard approval on, each episode the channel's schedule or its autopilot would make is planned first, in one quick step on our servers: a storyboard with

• the hook — what is said over the title in the first seconds;
• five to nine scenes — for each, what is on screen, what is said, and the facts it relies on, each with its source from the topic's own research;
• the payoff and the call to action.

The storyboard waits in Approvals for an answer before any GPU time is spent. Once approved, the episode is made from it, and its checks hold it to the plan.

Turn it on#

1. Open the channel and find Storyboards in the right column.
2. Tick Approve each episode's storyboard before it is made.
3. Set Waits for an answer — 1 to 168 hours (24 by default) — and When nobody answers in time:
   • Skip that day's episode (with a notice) — the day goes without, and the next topic is planned;
   • Approve it by itself — the plan goes ahead as written.
4. Optionally, under Also ask (optional), list up to five email addresses of people outside the workspace — a client, a sponsor. Each gets a private link to read the storyboard and approve it or ask for changes, with no account needed.
5. Press Save.

Editors, admins and owners change these settings. Turning it off withdraws a waiting storyboard, puts its topic back, and the channel makes its episodes as before.

Answer a storyboard#

Waiting storyboards are in Approvals (the sidebar shows how many), under Storyboards. Each card shows the channel, the title, how long it waits and what happens then, and every beat with its facts and sources.

• Approve — its episode starts within a minute, at the episode's usual price, which is shown under the button.
• Edit the beats — change the Title (3 to 70 characters), What is said (3 to 600 characters) and What is on screen (up to 400) of each beat, and tick Required — said as written, or the episode comes back from its checks on the beats that must be said. Then Save (it still waits) or Save and approve.
• Reject — say Why not? in a sentence and press Reject it. The topic goes back to the backlog with your reason; it is planned again only after the channel's other topics, at least a week later, with your words in mind — and the channel's next topic is planned at once.

Editors, admins and owners answer storyboards. People you listed by email answer through their own link, once: they approve, or ask for changes, which counts as a rejection with their words.

You are told when a storyboard is waiting: owners, admins and editors in the app, and owners and admins by email — at most one email every six hours.

What happens to the episode#

The approved storyboard goes with the episode to the GPU box: the episode agent builds that plan, and the quality checks compare the narration with the beats. A beat that strays is a note; a required beat that is not said sends the episode back for a fix round.

Never a silent stall#

• A waiting storyboard is the channel's one episode in the making: the channel waits for it, and other channels never do.
• When its hours are up, it is approved by itself or its day is skipped — a notice to the owners and admins, and a skipped line on the Publishing page.
• If three storyboards could not be written in one day, the channel tries again the next day.

Settings#

Credits and plans#

• A revision's price is built from what you ask: a base for every revision (it is rendered again and fully checked), more when an agent makes changes in your own words, a little more for each further change in words, and a small amount for each narration line said again. The button shows what it reserves before you press it; you are charged what the revision really used at your plan's rate — the rest comes back — and nothing when it does not pass. The typical figure is in the pricing page's "What things cost" table, as "A revision".
• A storyboard is one small model job, priced before it starts and shown on the channel's Storyboards card; the episode it leads to is priced as usual when it is made. See "A storyboard" in the same table.
• If the price changes while the editor is open, the request is refused with "The price changed since the editor showed it" — look at the new price and send it again.
• The editor and storyboards are on every plan, the Trial included.

Limits and good to know#

• Only a channel's own shorts are edited: a translation, a clip or a compilation is made from them.
• Episodes made before their source was kept, or before narration, cannot be edited; every episode made since can.
• The channel's kit is needed to render a revision again.
• No AI wording: a request or a storyboard edit that would label the episode as AI-made is refused.
• The editor and storyboards through the API: on plans with the API (Pro and above), a revision and a storyboard's approval can be requested through the REST API and the MCP server, with the same checks and prices.

Troubleshooting#

• "An episode can be edited once it is ready." Wait for it to be made; a held episode can be edited too.
• "N words do not fit — at most M." A rewritten line must fit its place before the next one: shorten it, or ask for the change in your own words instead.
• "This episode has 30 versions, the most it keeps." Make an earlier version current, or edit a newer episode.
• "Change N reads like an instruction to the software…" Say what should change in the episode itself — "end on the bridge at night" — not instructions, links or commands.
• "Say why, in a sentence…" A rejection needs a reason of at least a few characters: it goes back with the topic.

Related#

• Episodes — what a revision changes
• Approvals on your phone — where storyboards wait
• Review links for clients — the links outside approvers get
• The quality gates and the critic — every check a revision passes