Handoffs

A Shared Drive That Survives Project Handoffs

Put project files under team ownership and test a handover before a departing account loses access.

Store the final proposal in the team's drive if colleagues will need it when its original author leaves. Start moving working material there once several people have responsibility for the project. An index link in the shared space should lead to the deliverable itself, or name the arrangement for material that another organization controls.

In Google Workspace shared drives, the organization owns the files, and files stay in the drive after a member leaves. The help page also distinguishes membership of the drive from separately shared files or folders. Check your Workspace edition and organization settings before changing membership or moving content.

Assign rights for the work people do

Start with a sample project folder and decide who needs to manage membership, who should reorganize folders and who simply needs to contribute files or review them. Map those jobs to the roles actually available in your drive. Give the project an owner for administrative questions and at least one other team member who can act if that person is away.

When Check in the sample folder
Create A contributor can add a draft, and a reviewer can read it
Transfer The next owner can find the file, make the needed edit and invite a permitted collaborator
Archive A reader with expected access can find the final version through the index

Avoid using a broad drive role to solve access to one file. If policy permits, share a specific item with a reviewer who does not need the full drive. Verify limited-access folder behavior with the intended members because folder access does not always match drive membership.

Rehearse a departure

Copy a harmless document into the sample folder. Open it from a second authorized account using the same link a colleague will receive. Confirm where the file lives in Drive and who can edit it. Then have the test contributor leave or adjust the test membership with the appropriate manager and verify that the link still works for the remaining owner. Use an expendable project and accounts you are allowed to manage.

Before moving a real project, inventory documents that live in My Drive, files owned by another organization and items that other tools reference. Check whether each can be moved and what happens to its permissions. Record links that require repairs.

Define who can help after the change

List the file actions that must still happen when a colleague leaves. A designer might need to add working attachments, a coordinator might need to move finished files to an archive, and a customer might need to comment on one document. The customer's ability to open the link says nothing about the coordinator's ability to organise the drive. Test each action using the account that will need it.

Suppose a campaign team stores all briefs in a drive used by three departments. One outgoing producer grants access through individual file links and remembers which draft the client approves. Give an authorised teammate enough access to handle the next production day, then try the smallest set of permissions that supports the work. Have the teammate open the current brief from the project index and attach a harmless file to the test project. Ask an approved reviewer to open the review copy and attempt a comment. This exercise gives you separate evidence for contribution, editing and outside review.

Write down the person who can repair each failed action. If that person is the outgoing producer, address the dependency first. For example, assign an available drive manager the task of handling membership, while a project coordinator keeps the index current. A backup manager is useful only if they know which drive and request they are expected to cover and their organisation has granted them the authority.

Separate folder access from file ownership

Check where the files live before moving them. In Google's shared drive instructions, membership and sharing with non-members are two ways of granting access. Some organisations restrict what guests can see and how files can be moved. Verify the shared-drive access rules for the role and edition you use. An organisation-owned document can remain in the drive while your link to it still fails for a reviewer whose direct permission was removed.

For a file outside the project drive, ask who owns it and whether relocation is allowed. An agency may control a licence or a client can require their original to stay in their own account. Record those boundaries in the index. Use the supplier's approved access process or keep an authorised copy of the permitted material in the team drive. When a linked spreadsheet supplies numbers to the final proposal, open its link while signed in as the new owner and check the particular tab the team needs.

Use an access inventory. For each high-priority link, record its home, the role the new owner needs, and the person who can change that permission. Move and repair one harmless item first if you expect the transfer to affect permissions on related files. Keep the old URL in your notes until you know which links, bookmarks or automations actually need an update.

Make the archive usable when nobody remembers the project

Choose a date and accepted filename for the final deliverable. A reviewer following the index should land on that copy. Make an archive reader try the path without relying on a previously opened tab. Check that the accepted wording and any supporting evidence needed later are in locations the reader can still reach.

A simple handoff record can describe the difference between the deliverable, source materials, and files another organisation controls. Include one contact for permissions and a second route to use if that person leaves. For a live job, the one-hour project handoff drill gives the incoming owner a chance to use the drive before they have to answer for it in a meeting. Review what the recipient could open and update any link that pointed to an outgoing member's personal folder.

If a handoff includes an external reviewer, write the expected end date for their access alongside the review task. Have the drive manager confirm whether the reviewer is a member, an invited guest on the file, or a recipient of another organisation's copy. After the review, that information tells the manager which permission to revisit. A change to your drive has no effect on a file the recipient already downloaded.

Sources