Use Gemini in Google Docs to Draft a Client Handover Runbook

What This Does

Turns a bullet list of a client's systems, key contacts, and access notes into a structured handover document a new office manager, incoming employee, or replacement IT provider can actually follow, instead of one assembled from memory the day the handover is due.

Before You Start

• Access to Google Docs, either a personal Google account or the client's or your firm's Google Workspace tenant
• Gemini's writing features enabled. On Google Workspace this ships with the Business Standard plan and higher ($14/user/month); on a personal account it needs a Google AI Pro or Ultra subscription. If you don't see a spark icon near the bottom of a document, ask your admin or check your Google One or Workspace settings
• A bullet list of the systems, vendors, and contacts you're handing over, with any credentials replaced by a pointer to where they're actually stored

Steps

1. Draft the bullet list first, outside the AI

Before opening Gemini, write your own rough list: systems in use, vendor contacts, license locations, and where passwords live, your firm's or the client's password manager, not the document itself. This becomes the raw input, not something Gemini invents.

2. Open Gemini in the document

Open a new or existing Google Doc. Look for the spark icon near the bottom of the page, or open the side panel and click Ask Gemini. Choose Help Me Create for a first full draft, or paste your bullet list and ask Gemini to structure it.

3. Ask for the structure you actually need

Tell Gemini what the finished document is for and who reads it. For example, ask it to organize the bullets under headings like Systems Overview, Key Contacts, Access and Credentials Locations, and Open Items, in that order.

4. Refine with Match Writing Style or Refine

If the draft reads too generic, select a section, click Refine, and choose Rephrase or Elaborate, or type a custom instruction such as "add a one-line description of what each vendor does for this client."

5. Check it against reality before handing it off

Read the finished document against the live client environment. Confirm every system named still exists, every contact is still current, and no step assumes access that changed since your bullet list was written.

Real Example

Scenario: A retainer client is bringing an office manager on board to handle vendor calls, and you need a handover document ready before your next visit.

What you type: "Turn this bullet list into a handover runbook for an incoming office manager: systems are a cloud-hosted file server, Microsoft 365 email and Teams, a managed firewall, and a backup service. Vendor contacts are the ISP and the backup vendor. Credentials are stored in [password manager name]. Structure it with headings for Systems Overview, Key Contacts, Access Locations, and Open Items."

What you get: A formatted document with each system described in plain language, a contacts table, a note pointing to the password manager instead of any actual password, and a short open-items list you fill in with anything still pending.

Tips

• Never type an actual password, API key, or admin token into the prompt or the document, even as an example. Reference the password manager entry by name instead.
• Use generic role titles like "office manager" or "billing contact" rather than a full employee roster pulled from the client's directory.
• Save the finished structure as a Google Docs template once it works well, so the next handover starts from a shell instead of a blank page.

Tool interfaces change. If a button has moved, look for similar AI/magic/smart options in the same menu area.