The new owner has one hour and a meeting the next morning. Put tomorrow's action at the top of the handoff. Add its due time, a link to the current deliverable and the person who can answer a question.
The handoff can be one shared note. GitLab's communication handbook discusses writing decisions and context down so people can use them asynchronously. Use the note to point to the recorded work. Preserve the file owners and permissions of the underlying folder, especially if some assets belong to a client or another team.
Write an entry another person can act on
A real handoff could start with a sentence like “At 10 a.m. Friday, show Mara the export named Approved preview in the delivery folder and ask whether the sign-off includes captions.” Add the approved file and date, the last decision that affects it, and the choice that is open. Link to the people responsible for the next step and identify any date or time zone that could cause a missed handoff.
| Time | What the new owner should try |
|---|---|
| First 15 minutes | Open the latest deliverable from the handoff link in their own account |
| Next 20 minutes | Locate two decisions and the pending approval with its owner |
| Final 25 minutes | Draft the next message or perform a harmless rehearsal of the next step |
Make sure the current file is easy to distinguish from the working draft. In a Google document you can name a version that editors can retrieve when no separate approved PDF exists. Give people who need only a readable copy a link they can actually open.
Resolve access gaps with the recipient
If the recipient sees a request-access screen, identify who controls that file and route the access request before the outgoing owner leaves. In eligible Google shared drives, team-owned files remain when a member leaves. Direct links and special folders can still have different permissions. Check linked files that were created outside the drive individually.
Try the handoff without the outgoing owner
In the first 15 minutes, have the new owner open the index link from the account they will actually use. Ask them to locate the accepted preview and the short description of what the client will see. If two files have the same name, check which one the person opened and why. The file they used may have been downloaded last week. Update the link to the current copy and put the approved date in the handoff record before going on.
Keep the outgoing owner's help available during the session, but let the recipient try each step alone first. A real task can show a dependency that a screen-sharing walkthrough hides. For example, a current preview opens from the index, while the caption log beneath it requires approval from a separate team. Ask that team to grant the appropriate access to the intended account if policy permits. A handoff can record an unresolved permission explicitly and identify who will help, which tells the incoming owner what to do if they encounter it tomorrow.
Reconstruct the decisions that affect the next step
For the next 20 minutes, choose a decision that changed what will be delivered and one that changed who approves it. Ask the recipient to find both and explain how they affect the morning meeting. The captions case needs a clear answer about whether the sign-off covers picture only or also the caption file. If the only record is a comment on a working document, add one sentence in the handoff note with the decision and its supporting link. The Google Docs decision trail shows how to keep the rationale with a named version.
Write down the decision that remains open in the same terms the recipient will hear in the meeting. “Check captions” may leave the owner unsure whether to confirm a deadline or approve the text. “Ask Mara whether approval includes captions, then record the answer by noon” gives both a question and an action. Identify who owns the work if the answer is no. Make one place in the note where the recipient will record that outcome.
Spend the final minutes on tomorrow's action
During the final 25 minutes, let the recipient draft the next message or run through a harmless version of the action. If they need to send a delivery link, draft the recipients and attachments without sending it. If a handoff includes a recurring task, open the settings and ask who can change the owner without starting a second copy of the work. Check that the person has the right access for that specific action. A staged rehearsal can stop before a live send or permission change.
| If you observe this | Use the remaining time to |
|---|---|
| The link opens but the final and draft look identical | Mark the accepted version and verify the link again. |
| The approval owner is still unknown | Name the teammate who will find out before the meeting. |
| The recipient cannot use the destination account | Arrange access with its owner and record a fallback approved by the team. |
| The next action depends on a missing answer | Name the exact question and set a time for asking it. |
At the end, leave one stable link to the living handoff record. Mark the date when further updates should be made and who is responsible. Confirm the client-facing time with the owner of the calendar entry. If tomorrow's meeting is the first test of the handoff, keep an authorised alternate contact available with the same record until it has taken place.
If a recipient starts before the outgoing owner can attend, send the stable note in advance and leave a way to report the first failed action. The first ten minutes can be used for access checks over chat, followed by a call for the one decision that needs discussion. Keep the order of the rehearsal even when you split the hour. A link that opens only after somebody manually re-shares it may work for the call and fail again the following day under the expected account. Reopen it once after the meeting to catch that problem.



