Workflow5 min read

A Google Drive handoff an editor can open on the first try

Arrange camera originals, audio, references, and approvals into a usable handoff, then test access from the recipient's side.

Imagine opening a folder called “Footage” on the morning a cut is due. It contains seventy phone clips, two files called “final,” a music track, and a link to another folder that asks for access. The footage has arrived. The editor still has to reconstruct the shoot before making the first cut. A useful handoff answers three questions up front. What belongs in this edit? Where are the originals? Who can make a decision if the material disagrees with the brief?

Begin with a short inventory

Take a two-camera interview as a working example. A camera operator recorded two cards, the guest wore a lavalier microphone, and the producer captured a few street scenes on a phone. On a sheet of paper, list those four sources. Count the expected files in each group and record any known gaps. If the second camera stopped halfway through the last answer, say so. Otherwise someone may spend an hour trying to recover footage that was never recorded.

Create a project folder with a name a recipient will recognise in their own Drive. Inside it, make folders for camera originals, external audio, approved brand elements, and references. Put one short handoff document at the top. A folder named “Approved for this film” is clearer than a mixed archive of logos, old moodboards, and brand decks. If you include alternates, give them their own home and explain what would trigger their use.

Preserve the camera cards

Camera filenames often repeat from one card to the next. A shot named C0001 can appear on both cameras. Give each card a distinct parent folder, such as “Camera A card 01” and “Camera B card 01,” and preserve the internal layout when copying the card. Some camera formats carry additional information alongside the obvious video files. Put scene descriptions in the inventory. That gives an editor human-readable context while preserving the paths needed when reconnecting media later.

The same principle helps with sound. If the sound recordist has named tracks by microphone or speaker, keep those names. In the handoff, identify who wore each microphone and mention where a camera scratch track can help with sync. A note that says “the guest and host swap seats after lunch but keep their microphones” can save more time than carefully colour-coding every folder.

Describe what belongs in the first cut

Open the handoff document with the job in two sentences. For the sample interview, you might request a four-minute profile of a bicycle mechanic for a community newsletter. The primary audience knows the shop but has never seen a wheel being built. The cut should end when a customer takes the repaired bike out into the lane. This gives the editor a way to choose between two equally attractive pieces of footage.

Below that, list the deadline with its time zone, the intended frame shape, language and subtitle needs, the contact for technical questions, and the person who can approve the story. Mark footage that must stay out of the public cut. A bystander who asked to remain off camera can be identified by card and clip. Keep private contact details and release documents in a separate location accessible to the people who need them.

Grant access for the job at hand

Google Drive lets owners invite named recipients and assign Viewer, Commenter, or Editor access. General access also controls who can open a link. For private client footage, begin with a restricted project and invite the editor using the address they actually use for work. An invitation to a personal account does little for someone reviewing under a studio account. Confirm whether their role and your download settings let them obtain the originals. Google Drive sharing guidance

Give reviewers a link to the cut they are reviewing. If they need to leave notes on a shared document, grant the appropriate commenting access there. An account with a role inherited from a parent folder may retain that access on material beneath it. Put internal notes and client deliverables into distinct folders with deliberate sharing settings. A workspace administrator may also limit external sharing. Resolve that with the owner before sending a public link to a restricted project.

Conduct a recipient-side rehearsal

Wait for the upload to finish, then compare the online file counts with the shoot inventory. Check the duration and size of the longest interview take and one external audio file. Ask the editor or a colleague invited with the same role to open the exact link you plan to send. Have them download one clip and play it locally. A preview that plays in your own account proves little about what someone else can access or download.

Try the same link in a signed-out window. For a restricted handoff, the expected result is an access prompt. For a public resource you intend to distribute to followers, the expected result is a readable or downloadable file. These checks answer different questions. If a shortcut points outside the shared folder, test its target separately. A shortcut is a pointer to another item and can introduce a second permission boundary. Google Drive file organisation

Keep the delivery stable after sending

Send one message containing the project link, the name of the handoff document, and the decision you need first. If a missing microphone take arrives tomorrow, add it to the existing structure, append a dated entry to the handoff, and identify the exact new file in your message. Avoid silently swapping the content under an old filename while an editor is downloading or syncing media.

At delivery, create a clean client-facing folder containing the agreed exports, captions, and any accompanying notes. Keep the review cut with visible timecode out of that folder. Agree who will retain originals and when access will be reviewed. The recipient should be able to find the approved square cut six months later by searching the project name and deliverable, even if everyone involved has long since forgotten which round of feedback produced it.

Sources