Open a project.
Scripts sit next to the storyboards in the project you already have open. Start blank, or drop in a two-column AV structure and begin.
Two-column AV with live runtime, client comments anchored to the line with no login, and one click from approved script to editable storyboard frames.
The script lives in Google Docs. The board lives in Boords. Every trip between the two is a chance for the pair to drift apart.
Script and storyboard in the same project, on the same version.
Feedback arrives as a reply-all thread, tracked changes on Final_v3_REAL.docx, and one comment sent by text at 11pm.
One review link. Every comment anchored to the line it is about.
New round, new file. Last round’s feedback stays in last round’s document, which nobody opens again.
New version, comments carried across, both versions still readable.
Someone asks which draft the client actually approved and the honest answer is that you would have to go and look.
Who approved what, when, on which version. One click.
Scripts sit next to the storyboards in the project you already have open. Start blank, or drop in a two-column AV structure and begin.
Free-form for a treatment, two-column AV for a spot. Paste from Docs and the formatting comes with it. Your team can write alongside you in real time.
One review link, no login. The client comments on the line, approves, and the trail is recorded. Then turn the script into a storyboard.
PDF, Word, Markdown, or plain text. The PDF is a typeset document, not a screenshot: searchable text, working links, AV columns intact.
AV blocks count the audio words and give you the runtime at anything from 50 to 300 words per minute. Find the overrun before the record session.
Pull a colleague into a thread and they hear about it in their inbox, their email, or Slack. A follow bell per script sets who gets what.
Draft, In Progress, Needs Review, Changes Required, Approved. The same pills as your storyboards, so one glance covers the whole project.
Live cursors, edits that sync as you type, and a script that keeps working through a dropped connection and syncs when it returns.
Lock a review link with a passphrase, decide whether guests can download, and turn comments on or off per script.
Hand it the brief and get a first pass to react to. Reacting to a draft is faster than staring at a blank page.
Ask for the 45 to become a 30 without losing the argument, and see the change land in the document rather than in a chat window.
Eleven comment threads across two versions, turned into the list of things you still have to decide.
Ask for the board and it runs the same script-to-storyboard conversion, then tells you what it made.
Scripts live in the same project as your storyboards, so there is no new tool to roll out and no account for your client to create.
Sarah changed the status of Explainer Script v3 to Approved
8 JulDev commented on Explainer Script v3
8 JulTom shared Explainer Script v3 with sarah@beacon.co, dev@beacon.co
7 JulTom created Explainer Script v3, a new version of Explainer Script v2
7 JulSarah changed the status of Explainer Video v2 to Approved
6 JulTom created Explainer Video v2 from Explainer Script v2
6 JulAmara marked a comment on Explainer Script v2 as complete
5 JulSarah changed the status of Explainer Script v3 to Approved
8 JulDev commented on Explainer Script v3
8 JulTom shared Explainer Script v3 with sarah@beacon.co, dev@beacon.co
7 JulTom created Explainer Script v3, a new version of Explainer Script v2
7 JulSarah changed the status of Explainer Video v2 to Approved
6 JulTom created Explainer Video v2 from Explainer Script v2
6 JulAmara marked a comment on Explainer Script v2 as complete
5 Jul