Use Gemini in Google Docs to Turn Meeting Notes into a Reviewable Action Plan

A meeting note can look tidy and still leave the next person guessing. The useful output is a short action plan that shows what was actually agreed, what still needs an owner, and which details are missing.

This is a documentation-based guide with an illustrative example. The notes and output below are fictional. No Gemini execution is claimed.

What you will make

You will turn a fictional meeting note into a reviewable action plan with these columns:

• Action
• Evidence from the note
• Named owner, if one exists
• Date, if one exists
• Dependency or open question

Gemini in Google Docs can draft and refine text, use selected files as sources, and show suggestions for review. Google says the feature requires an eligible Google Workspace or Google AI plan. The exact controls can vary by account.

Fictional input

Create a new Google Doc and paste this complete note:

Project: Northstar client onboarding
Meeting date: 21 October 2026

Maya said the welcome guide still needs the current support hours. Leo will ask Support for the approved wording, but nobody set a date for that request.

The team agreed that the first client walkthrough should use the revised dashboard screenshots. Priya has the revised screenshots. The note does not say whether the screenshots have final approval.

Sam suggested moving the walkthrough to Thursday. Maya said Thursday could work if the support-hours wording is ready. No final date was agreed.

Open questions:
- Who approves the screenshots?
- When should the client receive the welcome guide?
- Does the walkthrough need a technical specialist?

Steps

1. Open the note in Google Docs on a computer. The official instructions describe Gemini in Docs on the web version of Google Docs.
2. Open Gemini from the document. If the control is missing, check whether your account has an eligible plan and whether your administrator has enabled the feature.
3. Add the following prompt. Keep the note in the document so you can compare the draft with the source.
4. Read the suggestions before accepting any change. Apply individual suggestions only after checking them against the note.
5. Copy the resulting action plan into a separate section below the original note. Keep the original text unchanged.

Copyable prompt

Turn the meeting note above into a reviewable action plan.

Use only facts stated in the note. Do not invent an owner, deadline, approval, dependency, or decision.

Return a table with these columns:
1. Action
2. Evidence from the note
3. Owner
4. Date
5. Dependency or open question

If the note does not state a value, write "Not stated". Keep suggestions and agreed actions separate. Add a final section called "Needs confirmation" with one question for each missing owner, date, approval, or dependency. Do not rewrite the original note.

If the prompt targets a specific section, name that section in the prompt. Google documents a way to target a section or refine selected text, and it also lets you add Drive files as sources. This guide keeps the task inside one fictional document so the source boundary is easy to inspect.

Illustrative output

This is an editor-written example, not a Gemini result. The first table contains stated commitments or agreed choices. The second preserves the recorded suggestion. The third contains inferred follow-ups for a person to accept or reject, not tasks the meeting agreed. All three use the requested five columns.

The meeting date, 21 October 2026, is source metadata. It is not an action deadline. “Not stated” means the note supplies no confirmed value.

Explicit actions and agreed choices

| Action | Evidence from the note | Owner | Date | Dependency or open question |
| --- | --- | --- | --- | --- |
| Ask Support for approved support-hours wording | "Leo will ask Support for the approved wording, but nobody set a date for that request." | Leo | Not stated | Approved wording and whether it is ready: Not stated. |
| Use revised dashboard screenshots in the first client walkthrough | "The team agreed that the first client walkthrough should use the revised dashboard screenshots." "Priya has the revised screenshots. The note does not say whether the screenshots have final approval." | Not stated | Not stated | Screenshot approver and final approval: Not stated. Technical-specialist requirement: Not stated. |

Suggestion recorded in the note

| Action | Evidence from the note | Owner | Date | Dependency or open question |
| --- | --- | --- | --- | --- |
| Consider moving the walkthrough to Thursday; suggestion only | "Sam suggested moving the walkthrough to Thursday." "Maya said Thursday could work if the support-hours wording is ready. No final date was agreed." | Not stated | Not stated | Ready support-hours wording is a stated condition; readiness and acceptance of Thursday: Not stated. Sam is the speaker, not an assigned action owner. |

Inferred follow-ups for human review, not agreed tasks

| Action | Evidence from the note | Owner | Date | Dependency or open question |
| --- | --- | --- | --- | --- |
| If a person accepts this follow-up, consider updating the welcome guide with approved support hours | "Maya said the welcome guide still needs the current support hours." | Not stated | Not stated | Approved wording/readiness and acceptance of this proposed follow-up: Not stated. |
| If a person accepts this follow-up, consider confirming the walkthrough date before scheduling anything | "No final date was agreed." | Not stated | Not stated | Maya's support-hours condition applies to Thursday, not a confirmed date. Wording readiness, the chosen date and acceptance of this proposed follow-up: Not stated. |

Needs confirmation

• Support request date: When will Leo ask Support for the approved wording? Date: Not stated.
• Approved wording and readiness: What wording has Support approved, and is it ready for the welcome guide? Wording/readiness: Not stated. This also checks the condition on Maya’s Thursday suggestion.
• Screenshot-use owner: Who is responsible for using the revised screenshots in the walkthrough? Owner: Not stated. Having the files does not assign that action to Priya.
• Shared walkthrough date: What is the confirmed walkthrough date? Date: Not stated. Thursday was suggested, and no final date was agreed.
• Screenshot approver: Who approves the screenshots? Approver: Not stated.
• Screenshot approval: Have the revised screenshots received final approval? Approval: Not stated.
• Thursday-suggestion owner: If the suggestion is accepted, who would own moving the walkthrough? Owner: Not stated; Sam and Maya are not assigned that action.
• Thursday decision: Has the Thursday suggestion been agreed, and who can confirm that decision? Decision/approval: Not stated. Ready support-hours wording is a condition, not proof of agreement.
• Guide follow-up acceptance: Should the inferred guide-update follow-up be accepted at all? Approval of this proposed task: Not stated.
• Guide follow-up owner: If accepted, who would own the update? Owner: Not stated; do not assign it to Leo from his separate Support request.
• Guide follow-up date: If accepted, when should the update be completed? Date: Not stated.
• Date-confirmation follow-up acceptance: Should the inferred date-confirmation follow-up be accepted? Approval of this proposed task: Not stated.
• Date-confirmation follow-up owner: If accepted, who would own confirming the date? Owner: Not stated.
• Date-confirmation follow-up deadline: If accepted, by when should that confirmation be done? Date: Not stated. This is separate from the walkthrough date itself.
• Client delivery: When should the client receive the welcome guide? Delivery date: Not stated.
• Technical requirement: Does the walkthrough need a technical specialist? Requirement: Not stated.

Status: DRAFT, awaiting human review. None of the suggestions or inferred follow-ups is an approved task, and no message, scheduling or document-change approval is granted here.

Acceptance checks

Before you share the action plan, check that:

1. Every action points to a sentence in the fictional note.
2. Leo is the only named owner in the source, and he is attached only to asking Support for wording.
3. Thursday remains a suggestion rather than a confirmed meeting date.
4. The screenshot approval question remains open.
5. The original note is still present and unchanged.
6. Every missing owner, date, approval, or dependency appears in Needs confirmation.
7. Explicit actions/agreed choices, the recorded Thursday suggestion and inferred follow-ups are visibly separate.
8. The three original open questions appear verbatim in Needs confirmation.
9. Every Not stated table gap has a matching confirmation question, including acceptance, owners and deadlines for inferred follow-ups.
10. The meeting date is not reused as a deadline, and an inferred follow-up is not presented as an agreed task.

If the result goes wrong

• Gemini invents dates or owners: add the sentence “Not stated is required when the note is silent,” then compare each row with the source again.
• The action plan omits a question: ask Gemini to list every sentence containing “not stated,” “suggested,” or “open question,” then review the list manually.
• Gemini cannot see the document: check that you opened the document in Google Docs on a computer and that Gemini is available for your account. Do not paste sensitive notes into an unapproved account as a workaround.

Limits and privacy

Treat the output as a first draft. Google notes that AI suggestions can be inaccurate, and you should review them before applying changes. Use fictional or approved notes while learning the workflow. Do not add confidential meeting material to a personal account unless your organisation allows it.

CTA

For more practical AI workflows for real work, join the updates at cihanuygur.com.

Sources

• Google Docs Editors Help, Write and edit with Gemini in Docs
• Google Docs Editors Help, Collaborate with Gemini in Google Docs