# Client review / revision protocol

The number of revision rounds is decided in the brief, not after the
first cut. Hold the line.

## In the brief (before you shoot anything)

```text
Delivery includes:
- 1 master cut up to [N] minutes
- 2 rounds of revisions per cut milestone (rough cut, fine cut)
- Cuts after picture-lock are billed at $X/hr
```

If they push back, the answer is *"happy to do unlimited rounds at $Y/hr,
or we keep the round budget and any further changes are billed separately."*

## When you send a cut

**Send a Frame.io / Wipster / Vimeo Review link**, never a download. You
need timecoded comments, not voice memos saying "the bit near the start".

In the email body:

> Hi [client],
>
> Here's the [rough/fine] cut: [link]
>
> Please leave **timecoded comments** in Frame.io rather than email or
> WhatsApp — that way I can address every note precisely.
>
> One ask: please collect feedback from all decision-makers (you, [partner],
> [parent if relevant]) and consolidate into one comment thread. Conflicting
> notes from multiple people are the #1 cause of revision-round overruns.
>
> This is round [N] of [N_total] for this milestone. After this round we
> move to [next milestone].

## When their feedback arrives

Sort it into three buckets before touching the timeline:

| Bucket | Example | How to handle |
|---|---|---|
| **Factual** | "Wrong name on lower-third", "Crooked horizon" | Fix everything in one pass |
| **Subjective + small** | "Can we try a different song for this beat?" | Pick the strongest 1-2 to try, batch the rest |
| **Subjective + big** | "Can we restructure the first half?" | Push back politely. Restructure = new milestone, not a revision |

Reply within 24 hours with: *"Bucket A I'll handle. Bucket B I'll try X
and Y. Bucket C is a structural change outside this revision round — happy
to discuss timeline/budget if you want to go that direction."*

## When they bypass the protocol

A WhatsApp message saying "could you also tweak…" arrives at 11pm.

Reply: *"Drop it as a Frame.io comment on the current cut and I'll batch
it into the next revision round. Helps me keep everything in one place."*

Don't ever do a one-off "small change". One small change is a precedent
for ten more.

## Picture lock protocol

When the cut is approved, send:

> Per our agreement, [date]'s cut is picture-locked. Music, grade, and
> mix are happening this week. Any change after this point is billed at
> $X/hr.
>
> Confirming you're happy to lock here? (Reply with "locked").

Save the email. That's your insurance.

## Final delivery checklist

- [ ] Master ProRes 422 HQ exported
- [ ] Web H.264 1080p exported
- [ ] Social cuts rendered (9:16 + 1:1 + 16:9 if asked)
- [ ] Subtitle SRT exported alongside web master
- [ ] Music licence PDFs in `07_EXPORTS/final/licenses/`
- [ ] Folder zipped + delivery link sent
- [ ] Email asks for: testimonial, referral to one other couple/planner,
      tag on social

The referral ask is the single most under-used revenue lever in
wedding/doc work. It only works if you ask the same day you deliver.

## Archive in 90 days

After delivery + 90 days:

- [ ] Move project to `08_ARCHIVE/` on the project SSD
- [ ] Drop a final flat ProRes copy + the picture-lock DRP
- [ ] Delete proxies + render caches (huge space saving)
- [ ] Confirm the mirror SSD still has the source footage
- [ ] Note the archive date in `00_ADMIN/`

If the client asks for a re-edit in 6 months, you can revive the project
from the archived DRP without rehunting media.