Client Delivery via Drive

When a workflow is finished and ready to hand off, you usually share it via Google Drive. This page covers what to share, what permissions to set, and how to package it.

What goes in the delivery folder

For each delivered workflow:

{workflow-code}-{version}-delivery/
  exports/
    Account-A/
      scene-01.mp4
      scene-02.mp4
      ...
      broll-01.mp4
      broll-02.mp4
    Account-B/
      ...
  script.md                  the approved script
  storyboard.md              the approved storyboard
  README.md                  delivery notes (how to assemble, AI Label Trick, etc.)

The folder structure mirrors what's in Assets/{workflow}/exports/ — you're essentially copying the per-account export folder + key reference documents.

Step 1: Verify everything's exported

Before sharing, run through the final delivery checklist:

• Every scene has a picked candidate exported as MP4
• All B-roll clips are exported
• Files use the standard scene-numbered naming
• Storyboard and script are accessible
• The compliance audit has been completed and documented

If any of these is missing, fix before sharing. Don't ship incomplete folders.

Step 2: Upload to Drive

Use the gdrive skill:

You: upload Assets/XYZG3/exports/ to a new Drive folder called
     'XYZG3-V1 Final Delivery'. Share with viewer access — anyone
     with the link can view.

Claude:
  Creating Drive folder 'XYZG3-V1 Final Delivery' in My Drive...
  Uploading 40 files (8 scenes × 5 accounts) + storyboard.md +
  script.md... ~280 MB total.
  Setting permissions: viewer access, anyone with the link.

  Share link: https://drive.google.com/drive/folders/[id]

  Folder is live. Total upload time: 2 min.

Step 3: Add the README

The client doesn't necessarily know our pipeline's conventions. Add a README.md to the Drive folder that covers:

# XYZG3-V1 — Final Delivery

## What's in this folder

- **exports/{Account}/** — Final MP4 clips for each account, one folder per
  account. Scene-numbered (scene-01.mp4 = first scene, etc.).
- **script.md** — Approved script with hook / body / CTA segments.
- **storyboard.md** — Scene-by-scene visual breakdown.

## How to assemble each account's video

For each account:

1. In your video editor, lay scenes in numeric order (scene-01, scene-02, etc.)
2. Insert B-roll clips at the timestamps indicated in storyboard.md
3. Add on-screen captions matching the script
4. Apply AI Label Trick on the timeline:
   - 0.01-second flash of dark screen at the very end of the video
   - Required for TikTok Shop content (avoids AI-content flag)
   - NOT required for Amazon or Meta Shop content
5. Export at 1080×1920 (9:16 vertical)

## Posting

- Platform per account: see storyboard.md
- Sales channel mechanics per account: see storyboard.md
- For Amazon-keyword accounts: confirm ManyChat automation is live before posting

## Issues / questions

Reply to the share email or contact [team contact info].

This is the client's onboarding into the deliverables. Don't skip it.

Step 4: Set the right permissions

Viewer (anyone with link)

Default for client deliveries. Client can view and download. Cannot edit or share with others (well, they can share the link, but they can't change the contents).

Viewer (specific people)

Higher security. Only emails you've granted access can view. Use when content is sensitive or under embargo.

Editor

Only when the client genuinely needs to edit. Almost never — the deliverables are deliverables, not living documents.

Never share with "Anyone on the internet" unless the content is explicitly public-safe (rare for actual production deliverables).

Step 5: Send the link

How you send the link depends on the client relationship:

• Email with a brief note about what's inside
• Slack DM with the link and a one-line summary
• Project management tool (Asana, Notion, etc.) as a comment on the relevant ticket

The link goes with context. Don't drop a bare URL with no explanation. Even a one-sentence note ("here's the final delivery for XYZG3-V1 — let me know if you have questions") makes the handoff feel intentional.

Variations by client type

Agency client

Probably wants the raw exports + reference docs. The agency does the assembly themselves. Standard delivery folder above is fine.

Direct-to-brand client

May not have a video editor in-house. Consider also providing: - A pre-assembled "rough cut" of one account's video as a reference for how it should look - A short video walkthrough of how to assemble (Loom or similar) - More detailed README

In-house post-production team

Probably already knows the conventions. Lean delivery is fine — just the exports + storyboard.

What NOT to share

Some things you probably don't share with the client even if they're in Assets/{workflow}/:

Content	Why not share
The raw .nbflow file	Proprietary to our pipeline; doesn't add value to the client
The contact sheets (if video copy)	Internal reference; not needed for assembly
Prompt files (image / Veo)	Proprietary methodology
Compliance audit details	Internal QA artifact
Failed candidate images / clips	Quality concerns; only deliver the picked candidates
Version registry entries	Internal tracking

When in doubt, share less. The client can ask if they need more.

Tracking what was delivered

After delivery, log it:

• In the version registry: add a note that V1 was delivered to the client on a specific date
• In your project tracker: mark the workflow as "delivered"
• In your communication channel: have a record of the delivery message

This audit trail matters when the client comes back in 3 months asking about that specific delivery.

Common delivery mistakes

Forgetting the README

The client doesn't know your conventions. Without instructions, they assemble wrong.

Sharing incomplete folders

Missing scenes or missing B-roll. Always verify the file count matches expected (scenes + B-roll + reference docs).

Wrong permissions

Setting "Editor" by accident, or restricting to specific emails when the client wanted to forward. Verify permissions before sending the link.

Not bumping the version

If you made any edits to the workflow after the generation pass (surgical fixes, captions adjustments), bump the version BEFORE delivering. The delivered version should match the registry.

Promising and forgetting

You said "I'll send the delivery by Friday" and didn't. Build the delivery step into the workflow checklist so it doesn't get dropped.

When you're ready

You've finished Chapter 11. You can now take a fresh product brief and produce ready-to-post, client-deliverable content across multiple accounts. This is the full pipeline applied end-to-end.

→ Next: Chapter 12 — Workflow Optimization. Now that you know every task, learn to do them efficiently — cost awareness, automation with the Generation Runner, parallel workflows.