How to use a Righthand with Google Drive

Build a handoff index from a named folder

Use Righthand with Google Drive to prepare a document index for a specific project handoff. The deliverable is a source-linked inventory with missing or ambiguous items, not an automatic reshuffle of every file. Start with one approved folder and a checklist of expected documents.

Google's file reference includes identifiers, names, MIME types, parent references, and modification information. Duplicate filenames can represent different files. Preserve file IDs or direct links when deciding which document belongs in the handoff.

Confirm access and sharing separately

Select Google Drive in integrations, then inspect the connection's available listing and content-read actions. Reading a folder does not imply permission to move, rename, delete, or share its contents.

When direct retrieval is unavailable, an owner can supply an approved file list and selected documents. Label the inventory's snapshot time. Do not describe it as a complete search of Drive or assume an absent file does not exist elsewhere.

An illustrative client handoff

A project lead needs a final brief, approved assets, and an operating checklist for the incoming account owner. The assistant matches the expected-document list with files in the named project folder.

Two documents have “Final brief” in their names. One was modified recently, but recency alone does not prove approval. The assistant links both and asks the project lead which is authoritative. The approval record, if supplied, settles the choice.

A complete request

At 3 PM America/Los_Angeles on the handoff date, review the approved Drive folder and attached expected-document checklist. Produce a private index with file link or ID, name, type, modified time, checklist match, and approval evidence where supplied. Flag duplicate candidates, missing items, and inaccessible content. Send to me for project-lead review. Do not move, rename, delete, or broaden sharing. Check each selected link and reconcile the inventory with the folder scope before delivery.

This is an illustrative brief. The destination is a private report; publishing the index to a client requires a separate sharing decision.

What a useful result shows

An example entry could read: “Operating checklist found; source link included; modified this week; approval evidence not supplied.” Avoid replacing the missing approval with an assumption based on a filename or editor identity.

Include a coverage section: which folder was inspected, whether nested folders were included, what file types were readable, and which documents were inaccessible. A count without that scope can be misleading.

Reconcile content and permissions

Open a small sample of links and confirm that each points to the intended file. If the future recipient differs from the reviewing owner, their access needs separate verification. Do not promise that a recipient can view a document merely because the assistant can.

Handle shortcuts and duplicate copies explicitly. A shortcut may point outside the project folder, and two copies may diverge after the inventory is prepared. Retain the chosen source and its review date.

If the project changes, prepare an updated index rather than silently treating last week's inventory as current. Follow connection setup and review pricing before turning the handoff check into an ongoing responsibility.