# 12. Prepare a Video for Handoff and the Next Test

A finished master is not the whole project result. A week later, you or another person should be able to tell—without a spoken tour—which file was accepted, where the materials came from, whether the video may be released, and what to test next.

This lesson helps you assemble a small, clear handoff package. It does not replace technical review of the master: for the practice, you need a video that opens and plays in full, makes sense without explanation, and has no accidental cutoffs, unreadable titles, or broken joins.

```learner-callout
{"stable_id":"aiv-c130-one-master","role":"key-point","title":"One master, several versions","body":"A video has one final: the accepted master. Vertical, horizontal, shorter, localized, and other versions are delivery formats made from that master."}
```

## 12.1. Master and Derivative Versions

Keep one master: the best accepted version, without accidental recompression or cropping. It can produce a vertical or horizontal version, a short teaser, a subtitled version, a version without embedded text, a localized version, a cover, or a preview. Those files serve different jobs, but they are not different final videos.

Here is the familiar trap: someone crops the video to 9:16, downloads it from a messenger, then uses that file to make the horizontal version. Quality starts walking down the stairs. Create derivatives from the master, not from an already compressed derivative.

## 12.2. Minimum Handoff Package

The recipient does not need the project’s entire digital attic: draft frames, every attempt, and every working reference can stay in the archive. They need a package that makes the current status and next action clear.

```text
1. Accepted master.
2. Required derivative versions.
3. Record: goal, audience, accepted viewer promise, and call to action (CTA).
4. Sources, rights, and required attribution.
5. Log: what worked and what to test next.
```

```learner-callout
{"stable_id":"aiv-c130-handoff-package","role":"technique","title":"The package must explain its status","body":"When someone opens the folder and can tell without a call which file to use, what it should do for the viewer, and what happens next, the package is doing its job."}
```

## 12.3. Rights, Attribution, and Currency

A technically sound file and permission to release it are different checks. After reviewing the master, record separately who owns the source files, music, likenesses, brands, and third-party footage; which permission or license exists; the platforms and territories it covers; required attribution; and what must not be released.

If the video or caption contains a date, price, ticket, discount, release, plan, or link, recheck the market, date, and final destination. An old trailer can be technically perfect while the line “in theaters June 12” still sends the viewer into the past.

```learner-callout
{"stable_id":"aiv-c130-rights-boundary","role":"caution","title":"Do not fill a gap with a guess","body":"If permission is not confirmed, use the exact status: “publication is not permitted until rights are confirmed.” A beautiful export does not issue a license automatically."}
```

## 12.4. CTA and the Next Test

The package inherits the viewer promise already accepted in the concept. This is not the moment to invent the idea again: check that the final video delivers that promise and that the call to action leads to the intended step.

One video does not have to exhaust a strong idea. The next version can test one different hook, ending, duration, format, or level of explanation. Change one hypothesis rather than producing nearly identical copies; otherwise you cannot tell what made the difference.

After release, read the result through the video’s goal:

- for attention — retention and completed views;
- for trust — saves and substantive responses;
- for action — clicks, inquiries, or another expected step;
- for portfolio — whether the viewer understands what you can do.

```learner-callout
{"stable_id":"aiv-c130-metric-meaning","role":"observation","title":"A metric without a conclusion is only noise","body":"A large number does not always mean a useful result. Record not only the metric, but also what it proves and what it does not prove for the video’s goal."}
```

---

## 12.5. Practice and Check: Assemble a Real Package

Create a clearly named folder or archive. Put the master, the required versions, and the record below inside it. This is not paperwork for the folder’s sake: the record lets you transfer the result without losing its meaning.

Copy the form and fill in only what is already known. If something is absent, name the limitation rather than imitating completion.

```template
Project title:
Accepted master:
Derivative versions and purposes:
Goal, audience, and accepted promise:
CTA:
Sources and attribution:
Rights and restrictions:
What was technically verified:
What was verified for release:
What remains unproven:
Post-release result, if available:
Next hypothesis:
```

```learner-callout
{"stable_id":"aiv-c130-build-package","role":"practice","title":"Build a package for a real recipient","body":"Give the folder a clear name, place the master and required versions inside it, then complete the record so the next person can see the status, limitations, and next test."}
```

Open the package as a recipient, preferably from another folder or device. Check that files open, names make sense, links lead to the intended destinations, and the status does not need a spoken explanation.

```learner-callout
{"stable_id":"aiv-c130-recipient-check","role":"checkpoint","title":"Handoff check","body":"Another person should be able to identify the master, the purpose of each version, the viewer promise, the release conditions, the result to measure, and the next hypothesis. If any point is unclear, rename the file, add the exact limitation, or complete the missing line, then check the package again."}
```

**Takeaway:** the package is ready not when the folder looks final, but when someone can open and use it without a spoken decoding session. If the master or rights confirmation is still missing, state the exact next action or the honest limitation.