
Check whether another editor holds the project's editing lock. Adobe describes a shared-storage workflow in which colleagues can access a project and copy content while its editing owner works. Read access is therefore different from permission to change that project.
Key Takeaways
- Being able to open or read a project does not establish editing ownership.
- Coordinate the handoff rather than bypassing an active collaborator.
- Verify the received state before making the next revision.
Identify the collaboration context
Confirm whether the work is part of a shared Production and which editor is responsible for the active revision. A project that is intentionally locked for editing should not be treated like a corrupt file.
Ask which state should become your starting point: the current in-progress work, the last approved cut or a separate alternate. These are editorial decisions that the lock itself cannot make.
Respect the editing handoff
Adobe's project-locking guide says opening a project for editing locks it so another editor does not overwrite the work. Colleagues can still access it and copy content, while changes require the editing owner to finish the relevant handoff.
Coordinate with that person through your team's normal process. Do not delete lock-related files or force a competing edit merely because the material is visible.
If you need an independent alternative, establish a separate project workflow and identify its relationship to the original. Avoid creating an unannounced competing “final” on shared storage.
Verify what you receive
When the handoff is ready, inspect the project identity and recent changes before continuing. Check the scene you are expected to revise and any dependency that was recently added.
In an illustrative two-editor workflow, one person may finish the narration structure while another prepares color work. The ability to inspect the first person's timeline can help planning, but it does not mean both should independently overwrite its editorial state.
Record unresolved questions so the next action is clear.
Accept the next revision
After your work, identify the state that is ready for the next collaborator. Keep the associated reference movie and notes aligned with that project version.
Use the approved-version handoff to make editorial authority explicit. Include shared project files and needed dependencies in the approval scope record when the work leaves the shared environment.
Source: Adobe's project-locking guide.
Related tasks
- How Do I Keep the Approved AI Image or Video from Getting Lost Among Revisions?
- What Does Approved Mean for an AI Project: Concept, Story or Final Master?
Sources and scope
- Adobe: Project locking with multiple open projects: Shared local Production project locks while editing; colleagues retain access/copy ability without editing until handoff.
Prepared by Imagild Editorial, the company editorial team responsible for these guides. AI assisted research and drafting. This is documentation-based guidance, not a claim of hands-on testing or independent review. Report a correction.
Cover: Pignatta / Pixabay, Content License. The city photograph is an illustrative source asset; it does not show this application or a test result.