Guided walkthrough: meeting notes into a summary and actions

Walkthrough · 12 minLast checked against the live product: 13 July 2026

30-second recall from earlier lessons

You ask Claude for 'total revenue by region' from a sales spreadsheet. It replies instantly with confident figures. Before you quote them, what should you be sure of?Nothing; Claude read the file, so the totals must be right.That Claude actually computed the figures with the analysis tool rather than eyeballing them, and that you told it how to handle blanks and errors in the data.That the answer came back quickly, which means it's simple enough to trust.That you asked politely, so Claude took extra care.

Claude's Research mode returns a well-structured report on a market question, full of citations. You're about to put its headline claim in a board paper. What's the wise next step?Use it as-is; a cited, structured report has clearly done the checking for you.Open the links behind the load-bearing claims and confirm the sources actually support them, weighing how authoritative each source is.Ask Claude to add more citations so it looks more thorough.Trust the claims with the most footnotes and ignore the rest.

By the end, you'll be able to…

Take one real task through the Gemini app from paste to finished output
Check a Gemini summary against the source and correct it in the chat
Turn messy notes into a clean summary and an actions table with owners

Why it matters

Reading about Gemini is one thing; watching a whole job go from start to finish makes it click. This walkthrough takes one everyday task, turning a page of rough meeting notes into a summary and a clear list of actions, through the standalone app, so anyone with a Google account can follow along and know exactly what to expect before trying it themselves.

What we're doing

Every team has the same problem: someone scribbles notes in a meeting, and days later nobody's sure what was decided or who's doing what. We'll fix that with Gemini. We'll take Fernway's weekly ops-sync notes, really messy, with half-finished actions and a couple of unassigned jobs, and turn them into (a) a short summary a manager could read at a glance and (b) a table of actions with owners and due dates.

We'll do the whole thing in the standalone app at gemini.google.com, so everyone can join in regardless of plan, with no in-app side panel needed. Open Gemini in another tab and follow along as you read. If you don't have notes of your own to hand, download the Fernway meeting notes and use those.

Step 1: Open Gemini and start a fresh chat

Go to gemini.google.com and sign in. Start a new chat so this task isn't tangled up with anything else in your history. Have your notes ready to paste. For this walkthrough, the Fernway meeting notes.

Step 2: Ask for the summary and the table together

Type a single, specific prompt, then paste the notes underneath it. Give Gemini the reader, the two things you want, the exact table shape, and a guardrail against invention.

The main promptGemini

Below are rough notes from our weekly operations meeting. Give me two things.

A three-sentence summary a manager could read at a glance.
A table of every action, with columns: Action, Owner, Due date. If an action has no owner, put UNASSIGNED in the Owner column. If there's no date, leave Due date blank.
Only use what's in the notes. Don't invent owners, dates or actions. Here are the notes:

[paste the Fernway meeting notes]

Why this works: It names the reader, asks for both outputs in one go, fixes the table columns, tells Gemini how to handle gaps (mark UNASSIGNED), and forbids invention, so you get usable output first time instead of a vague paragraph.

Gemini reads the notes and returns a short summary followed by a table. On the Fernway notes you should see the office-move decision, the expenses-form switch, and a row of actions for Tom, Dan, Maya and Priya, plus a couple marked UNASSIGNED (the August holiday-cover rota and the summer-social venue).

Step 3: Check it against the notes

This is the step people skip, and it's the one that matters most. Skim the real notes against Gemini's output. You're looking for three things:

Did it miss an action? The notes are messy, and a job buried mid-paragraph is easy to drop.
Did it invent an owner or a date? Check that every owner and due date in the table actually appears in the notes. If Gemini has quietly assigned the holiday-cover rota to someone, that's a hallucination. The notes say nobody picked it up.
Did it get a detail wrong? For instance, the lease auto-renews if no notice is given by 31 August. A summary that flips that around is worse than useless.

If something's off, don't start over. Fix it in the chat.

Correcting a mistakeGemini

Two corrections. The holiday-cover rota has no owner in the notes. Mark it UNASSIGNED, don't assign it to anyone. And check the office-move row: the lease auto-renews unless we give notice by 31 August, so the action is to get a cost comparison before then. Fix those and show me the table again.

Why this works: Pointing at the specific error and the source of truth (the notes) fixes it precisely, without throwing away the rest of the good output.

Step 4: Shape the output for how you'll use it

Now make it fit the job. Maybe you want the unassigned actions flagged at the top so they don't get forgotten, or a one-line note on decisions still needing sign-off.

Shaping the final versionGemini

Now sort the table so any UNASSIGNED actions are at the top. Underneath the table, add one short line listing the actions that still have no owner, so I can chase them.

Why this works: Reordering and flagging turn a correct table into a useful one. The unassigned jobs, the ones most likely to slip, are now impossible to miss.

Step 5: Read it yourself, then use it

You've got a clean summary and a checked, well-ordered table. Before you send it round or paste it into your notes, read the whole thing once yourself. Confirm the owners and dates match reality, the tone suits the audience, and nothing's crept in that shouldn't be there. Gemini did the tidying; you're the one signing it off.

That final human check is the whole discipline of using these tools well: Gemini drafts, you decide. It's what keeps you, not the tool, accountable for what goes out.

Worked result, in words

For the Fernway notes, a good final output reads something like: a three-sentence summary noting Q2 numbers are mostly in with the South soft, a decision to get a full office-move cost comparison before the 31 August lease deadline, and a team-wide move to the new expenses form by end of July. Then a table: Tom to investigate the soft South numbers and to bring Harlow renewal figures; Dan to pull the cost comparison and circulate the expenses form; Maya on desks, IT chasing and the contact-form check; Priya to write the feedback-process brief; and two rows marked UNASSIGNED (the holiday-cover rota and the summer-social venue) pulled to the top so they get owned.

Common mistakes

Sending without reading. Gemini can get a detail wrong or strike the wrong tone. Always read the final version yourself first.
Trusting the summary blindly. Skim the real notes too. A missed decision or a flipped deadline in a summary can cause real trouble.
Letting it invent owners. If the notes don't name who owns a job, the honest output is UNASSIGNED, not a plausible-looking guess. Check every owner against the source.
Starting a new chat to fix a small error. A near-right output is one follow-up away from right. Correct it in place and keep everything that was working.

Keeping current

The task and the discipline here are durable: messy notes into checked, owned actions will always be useful. The exact screen may shift; if it looks different, check Google's Gemini Apps updates and Gemini Apps Help. Accurate as of 13 July 2026.