The approval is buried in a Slack thread from three Tuesdays ago.
Sign-off is recorded against the version, with a name and a timestamp.
Final_v3_REAL.pdf and its five siblings in the email chain.
A share link for every version, and every round on record.
The 11pm text: did the client actually sign this off?
Read receipts and first-view logging. You know who opened it, and when.
Notes arrive by email, WhatsApp, and a call, never on the frame.
Clients comment on the frame itself. No login, no account.
A second Slack thread, so the client does not see the internal debate.
Team-only comments, right next to the client feedback, hidden from guests.

“I can't picture our video process without Boords. It makes sharing and collaborating on storyboards feel simple and polished for both first-time clients and experienced team members.”
“Because multiple team members can work in Boords at once, and because clients can add their comments directly into the storyboards, we save a lot of time and reduce the chances of errors.”
Avatars show who is in the project and on the board right now, so nobody edits blind.
Every image change saves as a revision. Lock the one the client signed off.
Clients review the timed cut on the same share link, so pacing gets signed off before the edit.
Give a teammate or a freelancer access to specific projects only. Guests can comment, never edit.
Filter the record by person, including guests, by action, and by time range.
Bring teammates in with a link. Clients and guest reviewers never need an account.
Most video teams run client review through tools that were never built to hold an approval. Feedback arrives by email, in a Slack thread, over a call, and in a marked-up PDF called Final_v3_REAL. Each round produces another file, another thread, another chance for a note to go missing. Then, weeks later, someone asks which version the client actually approved, and the answer is an archaeology project. The cost lands at the worst possible moment: after the shoot, after the edit, when a missed note means redoing finished work.
Boords keeps the whole preproduction record in one place. Clients review scripts, storyboards, and animatics through one link, with no account. Comments sit on the frame they are about, statuses are set per version, and every action lands in the Activity Log with a name and a timestamp. Studios like Mobula Design have closed every review round this way for years. When a client signs off, you can prove it.
No. You send one link. Clients open it, comment on the exact frame, set a status, and approve the version, all without creating an account or remembering a password. No login is the point: the fewer hoops a reviewer jumps through, the faster the sign-off comes back. More in the sharing links guide.
Every storyboard version carries a status: Draft, In Progress, Review Needed, Changes Required, or Approved. Signed-in teammates and no-login guests can both set it, and every change is logged with a name and a timestamp. When someone asks who approved what, on which version, the answer is one click, not a search through email. More in the activity guide.
Yes. Send the board by email straight from the share panel and every recipient gets their own link. Boords records when each person first opened it and what they did next, comments included, so you know whether to chase or to wait. More in the sharing links guide.
A team admin installs the Boords Slack app once, then each teammate connects their own account. Mentions, replies, comment completions, and comments on storyboards you follow arrive as direct messages with a link straight back to the storyboard. Nothing posts to channels, and the approval record stays in Boords, where you can still find it in March. More in the notifications guide.
You create a new version. The approved version stays on record, untouched, so the sign-off you collected still stands, and the next round starts from a clean board. Individual frames work the same way: every image change is saved as a revision, and you can lock the one the client approved. More in the frame revisions guide.
Yes. The same share link plays the timed animatic, so pacing and timing get signed off before anyone opens an editor, on the same record as the board itself. More in the animatics guide.
Yes. Roles and project-level permissions let you give a teammate or a freelancer access to specific projects only. Guests on share links can comment and set statuses, but they can never edit the work. More in the team users guide.
Free to start. Send one link, and stop chasing approvals through Slack.