How long should a studio keep a project after delivery?
A workable default: keep the full project online for about three months, archive a reduced set for an agreed number of years, and write the policy into the quote.
Clear, practical guides for production teams and studios on review, approvals, delivery and running a project. An initiative by Not Important Studio.
Review & feedbackApprovals & sign-offDelivery & file transferProduction managementTools & comparisons
A workable default: keep the full project online for about three months, archive a reduced set for an agreed number of years, and write the policy into the quote.
Give every client review a date, a closing time, a named reviewer and an agreed number of rounds, then plan the making around those windows.
Approve the master once, then let a native reviewer per market check only what changed, track every version in one register, and recheck when the master moves.
Agree a review window with a closing time before you send, make 'no notes' an answer, remind once, and never read silence as approval of the final cut.
Give each reviewer their own link, add a passphrase sent separately, set an expiry, leave downloads off and withdraw links after the round. Watermarks come on top.
Lock picture on one numbered version, confirmed in writing by the named decision maker, with a short list of what may still change. Treat anything else as new work.
Keep three counters apart: a shot code that never changes, a version per shot that only goes up, and a review round agreed with the client. Name files from them.
WeTransfer suits one-off sends. Video teams outgrow it on file size, link lifetime and delivery records. What to compare, with vendor facts as of October 2026.
On an agency job the agency producer consolidates: gather every note on one version, settle conflicts with the decision maker, and send the maker one list.
Name one final approver before the treatment is signed, agree who sees each cut, and lock picture before grade and sound, working back from the release date.
Give freelancers access per project, keep their work in the job's own structure, ask for a hand-over note when they leave, and close access the day they finish.
Give every reviewer a remit: legal checks claims and required lines, brand checks identity and tone, product checks accuracy, and one named owner decides.
Send a short, curated shortlist through a link that needs no account, set it to expire at the decision date, keep downloads off, and close it once the role is cast.
Map who can change the outcome before round 1, invite them all to it with a deadline, and give watchers and deciders different links and different jobs.
A commercial's deliverables list names every master, cutdown, format, caption file, audio mix and still, with specs, where each runs and who signs it off.
Most Frame.io alternatives only replace review. For a small studio the bigger cost is the tools around it. Our pick, a cost example and honest options.
A studio outgrows its spreadsheet when the sheet stops being where the truth lives: versions, feedback and status drift elsewhere and someone has to reconcile them.
Useful video feedback names the timecode, says what you see and what should change, fits the current stage, and arrives as one consolidated list per round.
A revision round is one consolidated set of feedback on one version, from agreed reviewers, in a set window. Guides often cite two or three per deliverable.