Identification
Reference the exact storyboard filename/version, page or scene numbers, and any asset IDs so the accepted document is unambiguous.
A Storyboard Acceptance Agreement creates an auditable record of client or stakeholder sign-off, limiting scope creep and clarifying who is responsible for next steps. It supports billing and dispute resolution by tying approvals to contract terms and delivery milestones.
Including these roles in the acceptance process reduces misunderstandings and speeds project handoffs.
An authorized decision-maker from the client organization (e.g., Creative Director, Brand Manager, Procurement Officer) who has legal authority to approve creative deliverables and accept associated costs on behalf of the client.
A representative of the production or creative firm (e.g., Producer, Account Manager, COO) permitted by internal delegation to confirm deliverable fulfillment and trigger production or billing actions.
Reference the exact storyboard filename/version, page or scene numbers, and any asset IDs so the accepted document is unambiguous.
List the criteria (e.g., visual fidelity, timing, narration notes) the storyboard must meet for acceptance and who verifies them.
State the acceptance date using MM/DD/YYYY to indicate when rights and obligations take effect.
Note what is excluded from acceptance and what changes require a formal change order or additional fees.
Provide signature blocks for each party with printed name, title, date, and any witness or notary lines required by jurisdiction.
Clarify next steps (production start, invoice issuance, asset handover) and any milestone triggers tied to acceptance.
| Field | Configuration |
|---|---|
| Signing Order | Sequential or parallel depending on approval structure |
| Authentication | Email link standard; use SMS or KBA for higher assurance |
| Audit Trail | Enable IP, timestamp, and device logging |
| Retention | Store signed PDF and audit record for required retention period |
Ensure retention and export options meet legal and internal recordkeeping policies before completing the signature workflow.
Specify how long the approval is valid (e.g., 14 days from delivery).
Agree on the expected time for requested changes (e.g., 5 business days).
State whether acceptance triggers immediate invoicing or a separate milestone.
Define when production may begin following acceptance (e.g., next business day).
Retention begins on the acceptance effective date.
Sender delivers storyboard draft and supporting notes for review.
Stakeholders review and compile consolidated comments.
Agency updates storyboard and prepares the acceptance agreement.
Client signs acceptance and production may commence.
| Criteria | Storyboard Acceptance | Change Order |
|---|---|---|
| Formal Scope Record | ||
| Triggers Billing | often | usually |
| Requires Signature | ||
| Includes Change Control | primary document |
| signNow | DocuSign | Adobe Sign | PandaDoc | HelloSign | |
|---|---|---|---|---|---|
| Starting Price | $8/user/mo | $15/user/mo | $14/user/mo | $19/user/mo | $15/user/mo |
| Free Trial | 7-day free trial, no card | Varies by plan | Varies by plan | Varies by plan | Varies by plan |
| Bulk Send | Yes | Yes | Yes | Yes | Varies |
| Audit Trail | Yes | Yes | Yes | Yes | Yes |
| HIPAA Compliant | Yes | Yes | Yes | No | No |
| Envelope Cap | No cap | 100 envelopes/user/year | Varies by plan | Varies by plan | Varies by plan |
A venture production firm used a storyboard acceptance to lock scope before animation
A real estate marketing team required client approval for property video storyboards