Your marketing lead approves the film. Accounts payable is still processing the balance. The media team assumes the launch files are ready, while the production company is waiting for permission to release them. Everyone may be doing their own job correctly, yet the launch is still stuck.
For international brands commissioning work from China, a single “complete” label is too coarse for this handover. Approval, payment conditions, access to files and receipt of the right package need separate records. Automation can connect them; it cannot decide what the parties meant by each one.
A new software signal, not a proven collection result
Cutvey's official press kit, updated November 3, 2026, lists a November 1 launch. Its delivery page describes downloads that can wait for cut approval and a paid invoice, with early release available when a studio records a reason. These public descriptions were checked November 4. They are vendor statements, not an ONCE product test or evidence of faster customer payment.
The structural point is that review, billing and file release can become executable conditions in one workflow. ONCE's inference is that more automation makes the definitions of those conditions more consequential. This article does not recommend buying the software or assume a particular Chinese supplier can use its payment services.
The ONCE four-state handover card
This is a proposed project-management method. Attach four independent records to one identified delivery package. They may progress together, but none should silently stand in for the others.
| State | What it records | What it does not establish |
|---|---|---|
| Version approved | A named person approved a specified version and scope | Every language, cutdown and technical output has been checked |
| Payment condition met | Authorized finance staff confirmed the agreed condition for the relevant invoice | The files meet the production specification |
| Package released | The intended recipients can access the agreed package | They downloaded, decoded and checked it |
| Receipt checked | The receiving team checked the specified files | New scope or every remaining obligation has also been completed |
Keep the package ID, manifest, approver, finance contact, release time, receiving checker and outstanding items together. A controlled spreadsheet can do this. The point is to connect the records, rather than have three departments each write “handled” in a different place.
Make the approval specific before connecting a trigger
“Cut V6 approved” might mean picture and pacing, with final audio, captions or clean versions still outstanding. Record that scope explicitly. A picture approval should not become a blanket release of everything in the project folder.
If the approved timeline is subsequently exported into a delivery package, identify that relationship and check the outputs. A new creative approval may or may not be necessary, depending on the change. Technical output checks still have a job to do even when nobody intended to change the content.
Finance should define and confirm the agreed payment condition. A screenshot, a buyer's statement that payment has been arranged and a processor's status may represent different stages. Use the actual channel's meaning and the project's agreed terms. Editors should not have to infer financial completion from a message thread.
The content team generally needs a release decision, any unresolved difference and a responsible contact. It does not need complete account details in an ordinary review group. Equally, a supplier should not surprise the buyer with a new payment gate just before launch.
Test three exceptions before trusting the happy path
Approved, but payment not yet confirmed. Can the buyer still review a sufficiently clear copy to check content and captions? Who updates finance status? Define preview and download access in advance, so the process does not become “no acceptance without files, no files without payment.”
Payment condition met, but access remains closed. Check whether the package is ready, the invoice is connected to the right project and the recipient is correct. Investigate the existing record instead of taking another payment or creating a replacement project to hide the mismatch.
Released, but receipt checks fail. An expired permission, damaged archive, missing version and wrong codec require different fixes. Preserve the original package and issue a new identified package with a change list where necessary. A download count cannot certify the contents.
These are fictional process drills, not allegations about Cutvey. Use non-sensitive sample files to demonstrate them. There is no need to make real payments or upload unreleased client material simply to test a proposed handover.
Plan legitimate early release instead of hiding it
A brand may already have agreed credit terms or an internal payment process that finishes after launch. Design a release arrangement consistent with that agreement from the beginning. The existence of a software lock does not make full prepayment the right rule for every project.
If the parties agree an exception, record the approver, exact package, outstanding matters, owner and next check date. File access and invoice status should remain independently legible. This is coordination advice, not a determination of contractual rights or legal enforceability.
For an invented three-language launch, the English advertising package might be released first while two other languages continue through checks. Report that partial handover precisely. Do not label all languages delivered, or open unchecked stems and project files merely because the main film was approved. The established scope still determines what is included.
Buy handover support as actual work
Ask a production partner who handles manifests, version checks, recipient support, failed transfers and the agreed retention period. Sending one link and maintaining multi-market delivery are different workloads. The quote should make that distinction understandable.
For ONCE's recurring content-service model, useful operational records include what waited for whom, how long it waited and why a package reopened. Observe approval-to-payment-condition, condition-to-release and release-to-receipt intervals separately. Explain the reasons before treating any interval as a performance problem. No margin improvement can be inferred without real labor and cost records.
At kickoff, have marketing, finance and the receiving media team rehearse one complete handover with a sample package. If someone is unavailable, the next responsible person should still be findable. More planning topics are available in ONCE's video production articles.
Sources and scope
Checked November 4, 2026: Cutvey's Press kit (updated November 3; launch listed as November 1), Deliver and get paid and Review and approve (product pages show no publication date). Vendor descriptions establish stated functionality only. ONCE did not log in, execute payments or verify collection outcomes. The handover card and examples are original analysis; the cover is a fictional business illustration.
