The Workflow Edit | Practical AI Tool Tutorial
How to Use Google Workspace Gemini Without Generic AI Instructions
Stop copy-pasting from five different files. Use Gemini in Google Docs to pull your project details together into one clean status summary you can actually send.
Dear Suzannah
Dear Suzannah, I need to write a project status update but the details are scattered across a Doc, a Sheet, and three email threads. I keep copy-pasting bits into a blank document and losing track of what I already included. Is there a faster way to pull it all together without manually hunting through every file?
Let Gemini draft the summary from your existing files.
Open a Google Doc, use the Help me write feature, and reference the files you need. Gemini pulls the context together so you start with a structured draft instead of a blank page.
The real use case
You have a project status update due and the details live in a Google Doc with notes, a Sheet with progress numbers, and several Gmail threads with decisions. Instead of manually copy-pasting from each file, you use Gemini’s Help me write in Google Docs to draft the summary. The tool reads your file context and produces a structured update with progress, blockers, and next steps. You review it, fix anything inaccurate, and send it.
The tool-specific prompt to use
This prompt is written for Gemini’s Help me write feature in Google Docs. Paste it, then replace the bracketed items with your real project details. Use @ to reference specific files when available.
Draft a project status summary for [project name] using context from these files: [list Doc names, Sheet names, or email threads]. Audience for this update: [manager, stakeholder, client]. Purpose: [weekly update, milestone review, go/no-go decision]. Include these sections: [current progress, blockers, next steps, risks]. Tone: [concise, factual, no filler]. Start with a one-sentence headline status labeled green, yellow, or red. Then list completed work, in-progress items, and blockers as bullet points. Pull specific dates, numbers, and owner names from the referenced files and do not invent them. If a detail is missing from the files, write TBD rather than guessing. Keep the full summary under 250 words. Flag anything that needs a decision this week. End with a Next steps section listing three to five action items, each with an owner name and due date. Do not add enthusiasm, marketing language, or generic project-management advice. Match the tone of the source documents. If the project is behind schedule, state it plainly. Make the summary easy to paste into an email without reformatting. Remove any sentence that does not help the reader make a decision or understand progress.
Prompt length: 187 words.
Make the result less generic
- Reference the actual file names with @ so Gemini pulls real data instead of guessing.
- Name the specific stakeholders who need this update so the tone matches what they expect.
- List the exact blockers from your Sheet or email threads so nothing gets glossed over.
- Require specific owner names and due dates in the Next steps section, not vague assignments.
- Delete any sentence that reads like a template and replace it with the real status from your files.
Quick human check
- Does the summary match the actual progress shown in your Sheet and email threads?
- Are all dates, numbers, and owner names real, not invented by Gemini?
- Is the headline status (green, yellow, or red) accurate for where the project stands?
- Can you paste this into an email or Doc and send it without major rewrites?
- Are the next steps specific enough that someone could act on them today?
