A China-based production partner has sent the final review link. Your regional team approves the edit and downloads a copy. Later, a new agency asks for the approved master. Is the file in the shared drive actually that master—or simply the convenient download offered by the review page?
For an international marketing team, approval and delivery answer different questions. Approval establishes which content was accepted. Delivery establishes which agreed file reached the intended recipient. ONCE recommends closing a video project against the latter, not against the continued availability of a player.
What an “original” download can—and cannot—establish
Checked on October 26, 2026, the Frame.io V4 guide How can I download files? offers an original-file download and a smaller proxy. Its V4 Media Links documentation describes the original as the file preserved as uploaded.
The production implication is narrow but important: “original” identifies a relationship to an upload. If a supplier uploads a review export, downloading that upload does not establish that it is the agreed final export. Nor does it automatically transfer camera footage, an editable project or separate audio assets.
A different provider makes the distinction explicit in its own service description. PlayPause’s Offline Review & Download for Review describes a web-optimized review proxy and a separate permission-controlled original download. That is evidence of one provider’s workflow, not a claim about every review platform.
These are current documentation checks, not reports of a newly launched feature or results from ONCE account testing. Neither provider defines your production contract for you.
ONCE’s received-file check
Connect four objects: the agreed export, the uploaded object, the recipient’s downloaded file and its intended use. This is ONCE’s proposed acceptance method, not a reported client experiment.
Start with the export specification. Identify the approved version, language, aspect ratio, subtitle treatment and technical requirements appropriate to its destination. A filename containing “final” does not resolve these choices.
Next, have the producer identify the actual upload corresponding to that export. A matching thumbnail is not enough. Then have the real recipient use the permissions they will actually receive—not the producer’s privileged account—to download the file.
Record the resulting filename, size, duration and relevant media properties. Open the local copy and inspect its beginning, ending, sound, subtitles and important frames. Where necessary, ask the receiving system’s operator to confirm compatibility. Successful browser playback is a different check.
An optional checksum comparison can help establish transfer identity: the producer calculates a checksum for the agreed export, and the recipient independently calculates one for the downloaded file. Matching results check byte consistency. They do not approve the edit, certify quality or establish usage rights.
Do not turn this into a blanket demand for the largest possible file. A web distribution export and a future reversioning master can have different requirements. “4K” or a MOV extension, by itself, is not an acceptance specification.
Keep review convenience without confusing the deliverables
A lightweight proxy can be entirely appropriate for feedback or offline review. A deliberately specified and approved small distribution file can also be a valid deliverable. The failure occurs when a convenient review download silently substitutes for a different promised output.
Consider a hypothetical overseas brand sourcing production in China. Its e-commerce team needs a captioned publishing file, while an exhibition partner needs a different framing or audio arrangement. This is an illustrative scenario, not an ONCE case study. Two successful downloads do not establish that both teams received their respective agreed versions.
If another agency will need to change copy or language later, discuss editable assets separately. An approved finished master does not automatically include the project, source media, fonts, plug-in dependencies or audio components. Specify the required scope and conditions before handover.
Buy an accountable handover
A production estimate should identify who prepares the output list, grants access, completes recipient-side downloading and retains the acceptance record. It should also state the storage period, how files can be supplied again and when a new format or fresh export becomes additional work. No standard price or saving is assumed here.
For ONCE, the strategic opportunity is to make production assets easier to hand over and reuse, rather than treating a sent link as the end of service. That is a service-design inference, not evidence of higher margins or an industry-wide transition.
Before closing the next job, request a short output list and ask the actual file recipient to verify one real download. The useful closing question is: “Which agreed file has reached which person?”
