
Seeing project footage on two computers does not necessarily mean the organisation has two independently recoverable copies. The folders may be views of the same synchronised collection, where changes made in one place affect the others. Before relying on that arrangement for future films, ask the technical owner to explain the actual relationship between the copies.
The question is practical rather than brand-specific. A builder may have a project-video folder on a marketing laptop, a shared office computer and a cloud service. The number of places where the folder appears says little about what would remain available after an accidental change or an account problem.
Describe the change you want to withstand
Start with a realistic scenario. If someone removes a source clip from the working collection, what retained version can the organisation recover? If an approved film is overwritten with a later draft, how would the earlier approved version be located? Ask for an explanation tied to the actual setup.
Microsoft's OneDrive guidance explains that deleting a shared item deletes it for everyone and describes deletion across its cloud and computer workflows. That is a concrete example of why a synchronised view should not automatically be counted as an independent retained copy. Other systems have their own behaviour and recovery arrangements, which need checking in context.
This does not make synchronisation undesirable. It can be useful for current collaboration. The point is to understand what purpose it serves and what separate arrangements, if any, support recovery.
Involve the owner of the storage arrangement
Do not ask a production supplier to certify an internal storage system they do not manage. Bring the relevant organisational IT or information owner into the handover discussion. The supplier can explain the production files and intended future uses; the technical owner can explain the storage and recovery controls.
A simple diagram or written description may be enough to clarify which locations are synchronised, which versions are retained and who can restore them. Keep sensitive system details within the appropriate internal records rather than publishing them in a film brief or general asset catalogue.
In a hypothetical quarterly project series, the marketing team might use a shared working folder for current edits while a separate approved-deliverable collection is managed under the organisation's retention arrangements. The useful distinction is the different purpose and control, not the visual appearance of two folders.
Verify a recovery route without risking the originals
Ask the responsible team to demonstrate the relevant recovery behaviour using a safe test agreed with them. Do not experiment by deleting production footage to see what happens. The exercise should establish how a nominated retained version can be found and supplied to an authorised recipient.
Record any limitations that affect future production: who can request recovery, what information they need, which material is covered and whether recovery depends on a particular account or service arrangement. Avoid copying generic product retention periods into the brief unless the technical owner has confirmed that they apply to this organisation.
The production handover can then state where the working files go and which separate arrangement the organisation relies on for retention. This prevents the producer, marketing team and IT staff from each assuming that someone else's visible folder is the backup.
A clear explanation is more valuable than an unsupported assurance that the footage is in the cloud. It gives the next commission a realistic starting point and assigns custody to the people able to maintain it.
Source context
Microsoft guidance on deletion in OneDrive supports the narrow technical distinction discussed here. The commissioning example and suggested acceptance questions are original editorial guidance, not a description of a Live Images client or storage service.
Discuss the footage requirement
If retained project footage needs to support a future film, discuss the intended use with Live Images. Agree the material available and the production work required; specialist storage or recovery services should never be assumed.
Prepared with AI assistance for Live Images. Planning guidance is general; suitability and production scope must be agreed for your project.