A client sign-off sheet for AI ad clips: one row per clip

Columns for a sign-off sheet on AI-generated ad clips, which Sume fields fill each, and what the client is actually approving. For agencies sending batches.

4 min readSume
All posts

Send the client one row per clip, and make the approval cover the label decision as well as the picture. A client who signs off only on how the ad looks has not decided who adds the AI label, and that is the question platforms ask later.

What columns does the sheet need?

Keep it to what a client can answer in a minute. The last two columns are the ones agencies forget.

Sign-off sheet
ColumnFilled bySource
Clip name and thumbnailYouA still from video inspect
Job idYouSubmit response, readable at GET /v1/jobs/:id
Contains AI face, voice or photoreal sceneYouYour brief and the clip
Contains a paid placementClientContract
Who sets the platform labelClient and youAgreed in writing
Approved, changes, rejectedClientReply

How do you get thumbnails for the sheet?

Video inspect returns stills as durable media.sume.com images. Ask for explicit timestamps so every row shows the same moment, for example the first second. Probe and stills are unbilled.

curl -X POST https://api.sume.com/v1/video-inspect \
  -H "Authorization: Bearer $SUME_API_KEY" \
  -H "Content-Type: application/json" \
  -H "Idempotency-Key: thumb-row-014" \
  -d '{"video_url": "https://media.sume.com/artifacts/example/clip14.mp4",
       "frames": {"at": [1.0]}}'

What does the client approve?

The clip as rendered, at that job id. A later edit is a new job and a new row. That keeps a change request from silently replacing the version that was approved. Whether labeling is needed under a given platform's rules is not decided by the sheet; it records who decides, and this is not legal advice.

Sources

Related posts

More in Use cases

All Use cases posts

Written by Sume