How Boords Helps with Storyboard Approvals and Version Tracking
Boords handles storyboard approvals and version tracking by keeping the approval record and the revision history in the same place as the storyboard itself: you share a board with a client, they leave feedback on it, you revise, and the platform records who approved what, when, and on which version. That matters most for agencies and brands running client-facing video pre-production, where the cost of a change depends entirely on how late it arrives.
What the approval and version problem actually looks like
Storyboard sign-off usually breaks in one of two ways. Either feedback arrives scattered across email threads, PDF markups, and call notes, so nobody can say which comments were addressed; or a board gets approved verbally, then quietly changes, and the version that reaches the shoot is not the version the client thought they signed off on.
Boords frames the second problem directly with the line "Who approved what, when, on which version" — the platform is built to answer that question rather than leave it to memory or a folder of dated files.
How the workflow runs
The pieces Boords describes on its site map to a straightforward sequence:
- Plan the script and storyboard. Scripts, storyboards, and animatics are created in the same workspace, so the board is not a separate artifact exported from somewhere else.
- Share with the client. Work is shared directly rather than sent as an attachment, which keeps the client looking at the current board instead of a downloaded copy.
- Collect feedback. Comments come back on the board itself, so notes stay attached to the frame they refer to.
- Track versions and revisions. As the board changes, versions are tracked, which is what makes the approval record meaningful — an approval is tied to a specific version, not to "the storyboard" in general.
- Get sign-off. Approval is captured in the platform, closing the loop.
The practical benefit is that steps 3 and 4 happen in the same place as step 5. When feedback and approval live in one system, you do not have to reconstruct which comments were resolved before sign-off.
Why version tracking is the part that saves money
Boords makes the economic argument explicitly: "Revisions are cheap on a board, expensive on a shoot." That is the reason version tracking is not just administrative hygiene.
A change caught at the storyboard stage costs a redraw. The same change caught on set costs crew time, talent time, location time, and possibly a reshoot day. Version tracking is what makes the early, cheap revision actually happen — because a client can see the current board, comment on it, and approve a specific version, rather than discovering the discrepancy when the camera is already rolling.
For agencies, this also protects the paper trail. If a client later disputes a creative decision, the approval record shows which version they saw and when they signed off.
Where it fits in a production stack
Boords positions itself as pre-production rather than a hosting or distribution tool — the site describes connecting "preproduction to the rest of your stack," meaning the board is meant to feed downstream tools rather than be the final destination for the video. If you are evaluating it against a hosting-and-sharing platform, they are solving different problems: Boords is about getting the board right and approved before anything is shot.
What the evidence supports, and what to check yourself
The site's own customer quote, from Erin Oliver, Head of Production at ENTHRAL, describes the shift in these terms: the team previously spent so much time creating storyboards that they were happy to put in front of clients, and now anyone in the business can create visually pleasing storyboards. That is a claim about production speed and accessibility, not about approval mechanics specifically — worth weighing as a signal of overall workflow fit rather than proof of the version-tracking behavior.
Two things to verify on your own before committing:
- Pricing and plan limits. Boords has a pricing page, but the plan tiers, seat counts, and any limits on client reviewers are not specified in the material here. Check the pricing page for current terms rather than assuming a free tier or unlimited client access.
- How client reviewers interact. Whether clients need an account, can comment without logging in, or can only view is a detail that determines how frictionless sign-off actually is for your specific clients. Test it with one real project before rolling it out across a team.
If your bottleneck is scattered feedback and ambiguous sign-off on client video work, the approval-and-version model is aimed squarely at that. If your bottleneck is hosting, streaming, or post-production review of finished cuts, this is upstream of your problem.