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 as a Slack DM. 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 are full documents inside Boords, alongside your storyboards. Write free-form or in two-column AV format, collaborate with your team in real time, take frame-accurate feedback from clients through a review link, keep every version, and turn the finished script into a storyboard in one click.
No, and deliberately so. Boords is built for video teams writing commercials, brand films, explainers, and social cuts, not for feature screenplays. There is no Final Draft or Fountain export. If you write screenplays for film and television, a dedicated screenwriting tool will serve you better.
Yes. Share the review link and anyone you send it to can read the script and leave comments anchored to specific lines. No account, no login, no seat. You can set a passphrase on the link, and you decide whether guests can download the script.
Yes. The AV block is a first-class part of the editor, not a table you format by hand. It gives you Scene, Audio / Voiceover, and Visual columns, and it counts the audio words to work out voiceover runtime at your chosen reading speed. The default is 130 words per minute and you can set anything between 50 and 300.
Yes. Press Storyboard and Boords reads the script, identifies the scenes, and builds a storyboard of editable frames with your fields already in place. You confirm the field names, the number of scenes, and the frame size before it runs. This is the part no standalone script tool can do, because the board has to live in the same product as the script.
PDF, Word (.docx), Markdown, and plain text. The PDF export is a real typeset document rather than a screenshot: searchable text, working links, tables and AV columns preserved, and an optional statistics page with word count, reading time, and total voiceover runtime.
Paste it straight into the editor and the formatting comes with it, or attach the file to the Script Agent and ask it to lay the script out for you. There is no separate file-import step when you create a script: a new script starts blank and you paste or draft into it.
Yes. Our guide to how to write a video script covers the method in eight steps, from the brief and the beat list through the two-column AV format, timing, client sign-off, and turning the approved script into a storyboard, with a complete worked example. The free video script template is the same AV format as a standalone editor.
Yes. Scripts are collaborative in real time, with live cursors so you can see who is working where. Edits sync as you type, and if your connection drops your work syncs automatically when it comes back.
They come with you. Creating a version copies the comment threads across by default, still anchored to the right lines, so a new round does not throw away the last one. Each version keeps its own status, and the activity trail records who did what and when across all of them.
The Script Agent works in the editor sidebar. It can draft from a brief, tighten a script you have written, summarise open feedback, and send the script to a storyboard. It is available where your team has AI features switched on, and team admins control that in team settings.
No. Your scripts, storyboards, and images are not used to train AI models.
Scripts are included on every Boords plan. See pricing for the details of what each plan covers.
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.