The first shot plays. That is often the least useful thing an editor can say about a project that has just arrived from another workstation. An interview opening might play because its proxy is attached. A camera original from the same shoot might be inaccessible. A graphic might live in a downloads folder nobody copied. The machine that needs to finish the film can appear to have received everything until it reaches the one shot nobody selected during the initial check. A handoff succeeds when the recipient can establish which file supplies each picture and sound, and can deliberately return to the originals when the project calls for them.
A proxy is another representation of a source clip, normally made easier to edit by reducing its resolution or using a lighter encoding. The edit refers to the clip and its timing. The application can display a proxy during cutting while keeping the link to the source recording. That relationship is more valuable than the proxy itself. If the recipient receives two folders full of movie files but loses the correspondence between them, it takes time to establish which reduced file stands in for which original. If the recipient receives a project and a trustworthy map, they can work out what is missing before doing anything to the timeline.
Start with the collision that looks harmless
Imagine a short documentary with one interview and a day of street footage. Both cameras generate a clip called C0001. On the sender’s machine they sit inside separate card directories. The proxy job gives them the same stem and places each next to its source. Everything works there. During preparation for the transfer, somebody drags just the proxy files into a new flat folder and accepts the operating system’s offer to append a number to the second file. The second clip now has a name that reflects when it was copied, which tells the receiving editor almost nothing about its camera, card or contents.
Even when a program rejects incompatible clips, two files from similar cameras can share a format, frame rate, audio layout and length. It is possible to mistake one take for another if all you check is that the picture comes back. Two clips made while an interviewee was settling into a chair might look practically identical at the beginning. A mismatch might become obvious only when the interviewee starts speaking, or when the dialogue editor finds that a phrase expected at one timecode is somewhere else. A card name, camera identifier or untouched relative path gives you evidence that survives this kind of ambiguity.
There is no need to change the names created by a camera if their directory context is doing the job. Retain the source structure, including companion files and directories that your ingest process depends on. If proxies must live in a parallel directory, mirror the meaningful distinction between the cards. A colleague should be able to see that the source under Camera B, card 04 has a proxy under Camera B, card 04. Where an older production already uses a different naming convention, a small mapping table is cheaper than renaming hundreds of sources at delivery and forcing everyone else to relink. Make a project copy before adopting any new convention on an active cut.
Write down which work the package is supposed to support
A remote editor may only need to assemble a first pass. An online editor may need the originals, the current edit and enough context to reproduce the approved look. Those are two different deliveries even when they begin with the same project file. In a proxy-only handoff, list the original media as intentionally absent and say who can provide it. List the other required files separately. A music cue, an external recorder’s WAV, a title graphic and a subtitle file may have no proxy equivalent at all. A PDF with a reference frame is helpful for checking a grade, but a copy of the actual transform or a clear description of its place in the color pipeline is what allows the recipient to investigate a difference.
For a finishing handoff, inventory the original sources at the level the recipient can actually check. A note that reads “drive two is camera” leaves open whether that includes both cameras, the pickup shots and the material recorded after an interrupted take. A compact table can identify card folders, original and proxy roots, their relationship, and exceptions such as “external audio lives under Sound, day 2.” Keep file checksums for delivery copies where the team uses them. Matching checksums establish byte-for-byte identity with a known copy, which is useful when debugging a transfer. They cannot establish that a mislabeled file belongs to a particular clip or that the export used the expected color settings.
Include an approved reference movie from the precise timeline being handed over, with its version visible in the filename and, when useful, a timecode burn-in. It gives the receiving editor a way to see a missing overlay or a shifted line of dialogue before recreating all the sender’s plug-ins. Specify which timeline is current. Projects often accumulate multiple sequences with plausible names and similar runtimes. A recipient can have flawless links and still finish the wrong version. Note the expected first and last frames, and call out any opening black, tail silence or alternate credit card that might otherwise be mistaken for an error.
Attach the intended kind of media
Adobe’s Premiere documentation describes attaching proxies to full-resolution items as a specific operation. Its instructions also cover selecting matching properties and reconnecting other items automatically after identifying a candidate file. Keep the original clips as the organizing layer of a project whose finishing workflow depends on originals, and use the application’s proxy attachment command for the reduced files. Importing reduced movies as independent master clips in a fresh sequence creates a different project relationship. Depending on the project, recovering the original link from there may be much more involved than attaching existing proxies to the items already in the cut. Adobe Premiere, attaching proxies to full-resolution media
Final Cut Pro has distinct relink commands for original and proxy media. Apple’s guide specifies that a candidate must cover the media referred to by the clip, match the type and frame rate and have a similar audio channel configuration. It also explains how matching patterns can locate related files and says that relinking cannot be undone. That makes a duplicate project or library an especially sensible place to investigate a doubtful delivery. A matching filename on a replacement drive is the beginning of that investigation. It is worth comparing time range and content at both ends of the referenced section before accepting a group of files at once. Apple, relinking media in Final Cut Pro
A practical first pass is one clip per camera, one from each recording device and a few exceptions. Pick a clip that starts near a card boundary, a second clip with the same basename and a shot known to have a separate sound recording. Switch representations if both are present. Watch a few seconds from the middle as well as the first frame and compare recognizable actions or words with the reference. If the camera’s scratch track is normally muted, turn it on briefly in a duplicate and check that it belongs to the expected take. If you use any broad relink option after that, do it one well-identified group at a time so that any unexpected match can be traced to the last change.
Design the test around failure
The sender can make a perfectly valid copy and still run a misleading test. Opening the transfer package on the same workstation may silently find the original storage. A familiar path or managed media location can supply clips outside the delivery folder. If there is a second machine, opening from the transfer drive there is a direct test. Otherwise use a copy and disconnect the source drives that are safe to disconnect, recording exactly which are attached. Avoid moving or unmounting storage used by other active projects merely to make the test. Open the package as a colleague would, from the instructions you intend to include, and record anything that comes back without a clear explanation.
A sensible test includes the timeline’s most expensive ambiguities. In a montage, a two-second cutaway may be the only use of a card. Find it directly rather than watching the film through and relying on memory. If a clip has been retimed, check whether the same action occurs at the cut point against the reference. For a sequence with captions, find a caption near a cut and check its timing. Try an early and a late section of every long external audio recording that matters to the cut. This is also a useful moment to identify what needs a separate review. Finding the correct media tells you little about whether a custom effect, font or color transform resolves on another installation.
The report can stay short. “Three cards relinked, one missing, source and proxy compared at these three timecodes” gives a producer a clear decision. “Project opens fine” gives them none. If the handoff is proxy-only, try the expected editorial mode and note the unresolved originals so their absence is understood from the outset. For finishing, switch to the representation expected for output and inspect the export options. The timeline viewer and the export dialog are different parts of the workflow, and each application handles them differently. Adobe documents separate Premiere export controls for using proxies and for preview files. Inspect the options for the actual sequence and preset rather than relying on the appearance of the viewer. Adobe Premiere, export settings reference
Send back evidence along with the cut
A returned project should explain what changed after the original handoff. Suppose a remote editor adds two screen recordings and replaces a temporary music file. The finishing editor needs those new sources and permission to use them as appropriate, plus any matching proxies. Sending the whole original package again adds transfer time and can create competing copies of files everybody already has. Returning only a project file creates the opposite problem. A project copy, a dated list of new or replaced files, and a reference export from the revised sequence together let the finisher identify the actual differences.
There is value in agreeing in advance on what happens when a source link cannot be proven. In the hypothetical documentary, the wrong street shot may still make sense in the story. That does not make it an approved substitution. Put the unresolved clip and the timeline position in the handoff notes. Keep the receiver’s exploratory version separate from the approved edit while the sender locates the card. When an alternate shot is authorized, record it as an editorial decision, with a new reference. The more similar the candidates look, the more useful that distinction becomes later.
Before a full-length master, export a representative short section with motion, dialogue, a title and any demanding transform. Inspect the file in a separate player with the reference nearby, and listen as well as look. If the received edit is a temporary proxy cut, identify that version clearly in the filename and handoff note so it cannot get confused with the master. If it is the finishing package, confirm the source links and the intended audio channel layout before the long export. The point of the small export is to answer concrete questions early, while changing one option or restoring one source still takes minutes.
By the end, the useful artifact is a chain of evidence a second editor can follow. The version note identifies the cut. The relative path or mapping table establishes which camera file each reduced movie stands for. The reference shows what the edit looked and sounded like on the sender’s system. A few targeted playback checks show that the connection survived the move. That chain lets the person who inherits the film devote their attention to the work they were asked to do instead of discovering, two minutes into an export, which version of C0001 they received.