For one Veo shot, the useful handoff is a small bundle: the chosen clip, its prompt, the inputs supplied to Flow and the decision that made this take final. A watermark check answers a different question from that bundle. Start with the shot the client will receive, then work back to the exact generation you kept.
Flow settings change. Record what was selected and what the exported file actually contains on the generation date, rather than reconstructing those details from a subscription name later. The official sources below were rechecked on 6 September 2026.
A filled Veo handoff: generation and delivery are different files
Fictional example, not a real generation, verification or client approval. The unresolved permission is deliberately visible so the receiver knows what to do next.
- Flow record and prompt
- CITY-001 / SH010. Frames-to-video, generated 5 September 2026. Model: Veo; exact variant not recorded. Prompt: ‘Slow dolly towards the empty glass pavilion at sunrise; preserve the supplied facade and keep the camera level.’ Start frame: REF-01-pavilion.png; no end frame.
- Chosen take → delivery file
- SH010-take03.mp4 → CITY-SH010-delivery-v02.mp4. Take 03 kept for its steady facade; v02 adds a trim and grade. The delivery hash is not yet recorded. Neither the filename nor a dated note proves file integrity.
- Visible marking
- Generation setting recorded as off on 5 September; no visible label observed in delivery v02. This does not describe its invisible SynthID signal.
- Verification of the delivery copy
- Illustrative Gemini result: inconclusive. File checked: CITY-SH010-delivery-v02.mp4; check recorded 6 September 2026, 10:30 UTC. Retain the reported result with the file; do not translate it into ‘not AI’.
- Decision and next owner
- Producer selected v02 for review; client approval is pending. REF-01 commercial-use permission is unresolved. Next: the producer checks that permission before asking the client to approve this exact delivery version.
Download the Veo handoff record (.md) Use the blank fields for your clip; the example is a guide to the record, not a BTW import format.
What Google Veo stores on its side
- Google says Flow outputs made with Veo include invisible SynthID watermarks. Visible watermarking now has a profile-menu toggle and applies automatically in India, South Korea and Vietnam. Source
- Flow supports text-to-video, frames-to-video and ingredients-to-video workflows; the selected method determines which inputs you should archive. Source
- Gemini supports SynthID verification, but some results can be inconclusive. Google documents upload and rolling usage limits, so check the current help page before scheduling a large batch. Source
- Google says SynthID usually survives changes such as resizing and compression; a verification result does not identify the project, prompt or approval behind a shot. Source
What gets lost without your own record
- A client opening a delivered clip cannot reconstruct your selected prompt, input rights, rejected takes or approval decision from a watermark result.
- A separate edit or export can become the delivered version. Keep that relationship explicit instead of assuming the generation download and the final master are the same file.
- A clean-looking frame does not tell you which visible watermark setting was active. Preserve the generation setting and inspect the delivery copy.
The documentation checklist for Google Veo
- Record the Flow project, shot identifier, generation date and selected model; keep a screenshot or settings note where useful.
- Save the exact prompt and the input files used by your chosen generation method, including start and end frames or ingredient images.
- Keep source and permission notes for each supplied image, voice or other reference.
- Record the visible watermark setting and inspect the export; do not infer the setting from a former tier rule.
- When verification is relevant to the delivery, save the result, check date and exact file checked. Preserve an inconclusive result as inconclusive.
- Connect the client decision to the final delivered version, including any edit made after generation.
Behind The Workflow gives this Google Veo record a practical home: keep an asset with the prompt, model, references, versions and decisions your team adds. Upload or explicitly capture the available details, fill the gaps, and review the record before handoff. BTW does not automatically reconstruct an external generation history or verify reference rights.
For a practical test, ask a teammate to identify the approved take and the input image used for it without opening your Flow account. If they need your memory to answer, add the missing link to the record. Keep a hash of the delivery copy if you need to compare files later; a dated note alone is not a trusted timestamp.
Provider marking and a publisher's disclosure are separate tasks. Where Article 50 applies, assess the publication context and record the disclosure decision. Neither an internal shot log nor a successful SynthID check automatically satisfies every disclosure obligation.
Frequently asked questions
My Flow download has no visible watermark. Is it unmarked?
No. Check the exported file and the Flow watermark settings. An absent visible label does not tell you whether an invisible SynthID signal is present; these are separate forms of marking.
Can my client check a Veo clip themselves?
Gemini offers verification for supported files. Send the exact delivery copy, and keep the result with its check date. This check supplements the production record rather than explaining how the shot was made.
Which Flow inputs should I archive per shot?
Save the actual inputs you used: the prompt, the start and end frames where supplied, and ingredient images where supplied. Add the selected model, chosen take and subsequent edits so another person can follow the handoff.
Does a negative or inconclusive SynthID check prove footage is not AI?
No. Record the result as reported. It does not rule out other AI systems, and an inconclusive check is not evidence that Google AI was absent.