Sending a proxy project another editor can open
Build a small remote editing handoff, test the relink and return to the camera originals for finishing.
A cinematographer has two cards of 4K footage and the editor has a laptop on a slow connection. Sending the smallest possible movie of the whole shoot might let the editor watch the material tonight. It will also merge clip boundaries, camera names and perhaps several audio channels into one file. The next editor needs the identity of each shot as much as the picture inside it. A proxy handoff keeps a lightweight counterpart for each original and preserves the relationship between the two.
Set up one honest test
Before processing a whole card, pick a shot with a clear sync event, some fine detail and a recognisable ending. A slate closing at the head and a person crossing at the tail make good checks. Add one representative clip from every other recording setup. A phone in portrait, a camera at a higher frame rate and a clip with four audio channels each give the test a different job.
Record the source filename, card identity, duration, frame rate and audio channel layout for those clips. If two cameras both produce a file called C0001, keep their original card folders and assign each card its own folder above them. A stable path such as “Day 01 / B camera / Card 02” gives a human something to compare when a relink dialog suggests several plausible matches. Keep the camera originals and a verified backup under the owner's control.
Create proxies from the media you actually imported
Build the project from the full-resolution clips. Create the proxy for a test clip through the editing application, or attach an existing camera proxy to its corresponding project item. In Premiere, Attach Proxies is available for supported video media in the Project panel. A separately recorded WAV or a still photograph belongs in the project with its own media file. Those assets also have to reach the remote editor.
Choose proxy settings the receiving machine can decode smoothly. Resolution affects file size and detail, and codec choice affects the work required for playback. Use a short representative export to compare them. Record the file size and ask the editor to scrub in both directions and play the number of simultaneous angles the job requires. A tiny file that plays one stream beautifully may be a poor choice for a four-angle interview.
Check orientation, aspect ratio and audio channel mapping on every test. A stereo proxy of a file containing separate microphone channels can change what the editor hears or prevent the intended attachment. Keep source timing intact. Applying a speed change while making the proxy would make the source and the lightweight copy describe different moments at the same timeline position.
Build a folder that travels together
Give the project a shared parent folder containing the project file, proxies, separate audio, graphics and any temporary music the editor has permission to use. Keep fonts and plug-ins on a dependency list. Check their licences before sharing installers or font files. A rendered reference for a complex title can show the expected result while the receiving editor arranges access to the original tools.
Create a tiny reference sequence showing each camera, a title and all the audio sources likely to matter. Export a small viewing copy and place it next to the project. Name the sequence and reference file with the same revision. That reference gives the second editor a way to distinguish “the room was dark” from “the receiving computer applied a second conversion.” It also helps them notice a missing external sound recording before editing all afternoon.
Test from the receiving side
Open a copy of the handoff from a different parent path, ideally on the receiving computer with the original storage disconnected. Keep the sender's working project safely closed during this test. Confirm the proxy files are available, scrub to the marked action in the first clip and listen to the sound channels. Compare the beginning and the end of the longest test clip with the reference sequence. A timing difference can accumulate while the first few seconds appear correct.
Ask the receiving editor to make two unmistakable test edits. Put a marker on the frame where the slate closes and cut just as the person leaves the shot. Have them send back the project revision and a reference export. On the finishing machine, reconnect to the originals and compare those exact frames. This tests the return trip, which the first successful playback on a laptop cannot prove.
Spot a mistaken attachment before finishing
Look at a shot from each pair of identically named camera files. Compare a face, a slate number or a visible movement against the full-resolution source, then check an edit near the end. If the wrong take appears, inspect the match criteria in the relink dialog and reconnect the affected group using its original card folder. A file name by itself tells you little when both cards began their numbering at one.
For the final output, confirm all required originals are online. Premiere ordinarily exports from available full-resolution media. Its export settings also offer a Use Proxies option for an intentional proxy export. Check that choice and any preview-render options before the finishing pass. Export a short length containing a detailed surface, fine lettering and an important sync point. Reopen the file outside the project and compare it to the source-backed timeline.
Keep the tested project revision, a list of media the finisher must have and the small reference next to the delivery. When the next episode arrives, reuse the folder structure and the checks. Repeat the sample whenever the camera, recording format or remote computer changes. The goal is a cut that survives the trip home.