Storyboard guide

Client storyboard review: a snapshot and feedback workflow

Updated

Run a clear review round with stable shot codes, a frozen PDF and an external feedback log. Understand what Creator’s read-only links do and do not establish.

Start a free six-cell board
Colleagues discuss a paper storyboard. AI editorial illustration, not a client testimonial or approval record.
Colleagues discuss a paper storyboard. AI editorial illustration, not a client testimonial or approval record.

Image note: AI editorial illustrations made with Google Vertex AI gemini-nano-banana-2.1. People and stories are fictional. These are not customer photographs, Creator screenshots, exact exports or proof of product testing.

Two fictional colleagues notice, water and reposition a sunflower in a continuous four-panel story.
Two fictional colleagues notice, water and reposition a sunflower in a continuous four-panel story.

A review closes when the responsible person makes an explicit decision about an identified version. Sending a link or exporting a PDF does not establish approval. Use the smallest process that lets a reviewer name the shot, explain the change and confirm what happens next.

Prepare a reviewable snapshot

Start with a fictional four-beat scene: a drooping sunflower is noticed, dry soil is identified, it is watered, and it stands by the window. Expand it to six cells with an establishing view and a reaction. Give the cells stable codes A–F, then put the audience, intended message and unanswered questions in a short brief.

Name the board “Sunflower — R1 — 2026-10-29”. Save editable JSON and a visual PDF with readable headings and captions. That PDF is the snapshot reviewers can refer to even if the working board changes. The illustration is an editorial story concept, not evidence of a real client project.

Use an external feedback log

Ask for one actionable issue per entry. “Make it warmer” needs clarification: color, lighting, performance or tone? Keep the observation separate from the proposed solution so the team can solve the actual problem.

FieldExample entry
Revision and shotR1 / D
ObservationThe watering action is hard to read
Requested changeShow the spout above the soil
Responsible personName the assigned collaborator
DecisionAccept, clarify or decline with reason
StatusOpen until the revised frame is checked

Share within the real product boundary

Creator has a read-only sharing flow, and creating a link requires authentication. The viewer is intended for anyone holding the URL; treat that URL as access to the board. Confirm the relevant account and plan conditions in the current interface before promising access to others.

This guide does not claim Creator provides pinned comments, approval signatures, Slack or Teams notifications, MP4 review export or an immutable revision history. Use a separate document or issue tracker for the feedback log. A live read-only link is not, by itself, a frozen approval record. Check it in a separate signed-out window before using it in a real review.

Resolve and freeze the next revision

Collect feedback against R1, decide each item, then create R2. For the watering note, adjust D and inspect C–E so the change preserves the plant, pot and action direction. Record the decision, export R2 and ask the assigned approver to accept or reject that named revision explicitly.

Separate creative review from brand or other specialist checks when their questions differ. Do not imply that exporting a board performs those checks. Keep personal or confidential production material out of an unrestricted link unless your own sharing policy permits it.

Reproduce a small review locally

Use two windows and the same six shot codes. Compare the snapshot with the current board, verify that each logged issue points to a real code, and inspect the phone rendering. Saving, opening and reading a board tests usability; it does not prove an external person approved it. No customer feedback, paid-account sharing result or notification delivery is asserted here.

Sources and verification

First-party product verification record. Open Storyboard Creator. Technical reference: immutable file data.

These sources support terminology and the inspected implementation. They do not endorse CineoBoard. The examples and suggested review process are original fictional exercises, not measured production outcomes.