FILE OPERATIONS · 6 MIN READ
How to organize branded and unbranded property media
Two outputs can come from the same source and still serve different delivery requirements. The operational risk is not creating the variants; it is losing which one was requested, reviewed and sent.
QUICK ANSWER
Treat branded and unbranded media as separate deliverable variants inside the same property job. Record which variants were ordered, use a stable naming or folder pattern, review each required output, mark the approved version explicitly, and build the delivery package from the job record. Never infer the correct variant from a vague “final” folder.
Model the variants as ordered outputs
Record branded and unbranded requirements at the service or deliverable level. Include the output type, current state and intended recipient or channel if the studio needs that distinction.
Do not duplicate the whole property job. One job should preserve the shared source, instructions and approval history while showing each required variant separately.
| Field | Example value | Why it matters |
|---|---|---|
| Deliverable | Property video | Keeps the media type explicit |
| Variant | Branded or unbranded | Prevents ambiguous “version two” labels |
| State | Review or approved | Separates upload from acceptance |
| Package | Named client handoff | Controls what is released |
Use names that expose the variant
Put the stable job identifier, deliverable and variant in the working name. Add a controlled version identifier when revisions occur. Keep “final” as a state in the job record, not a word that can appear in several filenames.
If the media type requires several files, place them in a variant-specific set and keep its manifest or expected count visible.
Review both outputs intentionally
Approval of the branded version does not automatically approve an unbranded export. Check that the required visual or audio identity is present or absent according to the brief, then verify format, property identity and completeness.
In a fictional photo-and-video order, the reviewer can approve both photo variants while returning only the unbranded video for correction. The job remains partially approved rather than collapsing into one status.
Assemble delivery from approved records
Choose files from the approved variant set and open the resulting client view. Confirm the package label does not expose internal shorthand and that no superseded or unintended variant is accessible.
The team’s service agreement and relevant platform requirements should govern which versions are supplied. This workflow guide does not prescribe a universal branding policy.