Cut Recurring Meeting Times in Half With Claude + Granola

Start by getting the recurring meeting into Granola.

You can use Granola for free. It does not join the call, and if the meeting is already on your calendar, Granola can detect it and start a new note when the meeting begins. If the meeting is impromptu, start a quick note manually.

The important part is consistency. You want Granola to become the memory bank for this meeting over time. One note is useful. Five notes from the same recurring meeting are much more useful because Claude can start seeing patterns.

If you use spaces in Granola, create one for the recurring meeting you want to improve. For example:

Weekly content slate meetings
Client check-ins
Leadership syncs
Project standups

That extra organization makes the audit cleaner because the meeting history is easier to isolate.

Pro tip: Use one Granola space for each recurring meeting you want to audit. Claude will have a much easier time finding the right notes later.

Open Claude and go to:

Customize > Connectors > Browse connectors

Search for Granola, connect your account, and approve the connection.

Once connected, Claude can search your notes, list meetings, and pull meeting transcripts. That is what makes this different from copying one meeting summary into a chat. Claude can look across the recurring meeting history and find the work that keeps repeating.

Before running the full audit, confirm Claude can find the right meeting:

Use my connected Granola notes to find the most recent meetings for [RECURRING_MEETING_NAME].

Return:
- the meeting dates you found
- a one-line summary of each meeting
- whether there is enough context to audit this recurring meeting
- anything you cannot access or are unsure about

Do not recommend changes yet.

If Claude finds the wrong meetings, tighten the meeting name, date range, attendee names, or Granola space.

Now ask Claude to audit the recurring meeting.

The goal is not to summarize the meetings. The goal is to find what should move out of the live call.

Use this prompt:

Look at my five most recent [RECURRING_MEETING_NAME] meetings in Granola.

Audit them so we can make this recurring meeting more efficient and shorter.

Look for:
- repeated status updates
- delayed decisions
- unresolved topics
- repetitive questions
- work that keeps happening during the meeting
- friction points that slow the meeting down
- tasks AI could automate or prepare before the meeting

Give me a report on:
1. What we can improve
2. What should happen before the meeting
3. What still needs live discussion
4. What AI could help automate or do faster before the meeting
5. Any missing context or assumptions I should verify

Use evidence from the Granola notes. Do not invent owners, dates, or decisions.

Review the output before asking Claude to create anything.

In the recording, the audit was useful because it found work that was happening live but should have happened before the meeting. It also separated status updates from decision-making. That is the shift you are looking for: less live catch-up, more live decisions.

Once the audit looks right, ask Claude to turn it into concrete meeting assets.

Use this prompt:

Based on the recurring-meeting audit, create three outputs.

Output 1: A one-page pre-read document for attendees.
It should include:
- meeting purpose
- what changed since the last meeting
- required attendee inputs
- open threads from previous meetings
- decisions we need to make live
- a proposed shorter agenda
- a "come prepared with" checklist

Output 2: AI tasks or automations we can run before the meeting.
For each one, include:
- what the task does
- what source it uses
- where the output should go
- whether it needs human review

Output 3: A simple weekly workflow.
Show how the pre-read could be created and shared in [GOOGLE_CALENDAR / NOTION / SLACK / EMAIL] before each meeting.

Keep the pre-read short enough for attendees to complete in five minutes.
Do not include sensitive notes that attendees should not see.
Phrase uncertain owners, dates, or decisions as confirmation questions.

The best output should give you two things at once: a memo you can send before the next meeting and a list of work that no longer needs to happen live.

Do not accept the first draft blindly. Remove anything too vague, too sensitive, or too time-consuming for attendees. A good pre-read should make the meeting lighter, not create a second meeting before the meeting.

The final step is to improve the notes you will create in future meetings.

Ask Claude to create a Granola template for this recurring meeting:

Create a Granola note template for [RECURRING_MEETING_NAME].

The template should make future notes easier to audit and reuse.

Include sections for:
- final decisions
- action items
- unresolved topics
- repeated questions
- prep work that should happen before next time
- things to improve about the meeting

Keep the section titles simple enough to use inside Granola.

Then open Granola and create a custom template for that recurring meeting. Add the sections Claude recommends and apply it to future notes.

This is the part that makes the system improve over time. Better notes make the next Claude audit more useful, and the next audit makes the next meeting easier to prepare.