7 Claude Prompts for Summarizing Meetings and Long Documents

The best Claude prompts for summarizing tell Claude exactly what to pull out: decisions, owners, deadlines and open questions, in a fixed format. Paste a transcript or upload a PDF, give Claude a clear output template, and ask it to flag anything it cannot confirm. You get notes your team can act on, not a vague recap.

A plain "summarize this" request tends to return a tidy paragraph that nobody acts on. The seven prompts below fix that by forcing structure, so the output reads like minutes from a sharp project coordinator. They work on Claude's free plan, and most transfer to other assistants with small tweaks. For prompts beyond summaries, see our 50 copy-paste prompts for work.

Which summarizing prompt fits your task?

Use this table to jump to the right prompt. Each one is copy-ready: paste it into Claude, then paste your transcript or attach your file underneath.

1. The decisions, owners and dates prompt

This is the workhorse AI meeting summary prompt. Instead of asking for a summary, it asks for the four things people actually check after a meeting. It suits anyone who runs or attends recurring meetings, from team leads to freelancers on client calls.

You are a careful project coordinator. Summarize the meeting transcript below. Return only these sections:
1. Decisions made: one line each, with who made the call.
2. Action items: task, owner, due date. If no owner or date was stated, write "No owner" or "No date". Never guess.
3. Open questions: anything raised but not resolved.
4. Next meeting: date and agenda, if mentioned.
Keep the summary under 200 words. Include nothing that is not in the transcript.

Transcript:

The "never guess" line matters most. Without it, AI tools tend to fill gaps with plausible owners and dates, which is worse than leaving them blank. A blank tells you to follow up. A wrong name sends work to the wrong person.

2. The action-item table prompt

When a meeting produces a long to-do list, a table beats bullet points. This prompt adds a source quote to every task, so anyone can check where it came from. It suits project managers, operations staff and anyone who tracks tasks in a spreadsheet or project tool.

Turn the meeting notes below into a table with these columns: Task, Owner, Due date, Priority (High, Medium or Low), Source quote.
Rules:
- Use the speaker's own words for the source quote, under 15 words.
- Sort by due date, earliest first. Put tasks with no date at the bottom.
- Flag any task where two people seem to share ownership.
- If priority was not discussed, write "Not stated".

Notes:

Copy the table straight into Excel or Google Sheets. If you want the sheet to highlight overdue tasks, our guide to prompts for spreadsheet formulas shows how to get the right formula.

3. The executive brief prompt for long documents

Use this prompt when you need to summarize a PDF with AI before a meeting where you are expected to have read it. It suits managers, consultants, students and anyone handed a 60-page report with a day's notice.

I've attached a PDF. Read the whole document before answering. Then write a one-page brief for a busy executive:
- Bottom line: two sentences.
- The five most important points, each with its page number.
- Every number, deadline or obligation that requires action.
- What the document does not cover that a reader might assume it does.
Use plain English. No introduction, no closing remarks.

Claude handles long documents well, but layout still matters. Anthropic's long context prompting tips recommend placing the document near the top and your question at the end, which tends to improve answers. Uploading a file and then typing the prompt does exactly that.

If you are new to file uploads, start with our walkthrough on how to use Claude's free plan for work.

4. The quote-first prompt for contracts and policies

Summaries of legal or policy documents carry a real risk: a smooth paraphrase can quietly change the meaning. This prompt makes Claude pull the exact passages first, then summarize only from them. The same Anthropic guide suggests this quote-extraction step for long documents. It suits freelancers reviewing client contracts, HR teams reading policy updates and anyone answering a request for proposal (RFP).

First, find every passage in the attached document about payment terms, renewal, termination and liability. Copy each one in quotation marks with its section or page number.
Then, using only those quotes, explain in plain English:
- What I must do, and by when.
- What the other party must do.
- Anything unusual compared with a standard agreement of this type.
If the document says nothing about a topic, write "Not covered". Do not fill gaps from general knowledge.

Treat the output as a reading aid, not legal advice. For anything you are about to sign, the quotes make a lawyer's review faster, but they do not replace it.

5. The risks and open questions prompt

Most summaries tell you what a document says. This one tells you what it leaves out. It suits project leads, reviewers and decision makers who need to push back before approving a proposal, budget or plan.

Act as a skeptical senior reviewer. Read the attached proposal and list:
1. The three biggest risks, with the passage that raises each one.
2. Assumptions the author makes without evidence.
3. Questions I should ask before approving, ranked by importance.
4. Who in the document seems responsible for each risk, if anyone.
Be direct. Skip praise and general comments.

Run this after prompt 3 in the same chat. Claude already has the document in context, so you get a sharper second pass without uploading the file again.

6. The follow-up email prompt

A summary only helps if it reaches the people who need it. This prompt turns your AI notes summary into a recap email in one step. It suits meeting organizers, account managers and freelancers who need a written record of what a client agreed to.

Using the meeting summary above, draft a follow-up email to all attendees:
- One line of thanks.
- Decisions as bullet points.
- Action items as bullet points, each with owner and due date.
- Ask for corrections by end of day Friday.
Keep it under 150 words. Friendly, direct, no filler.

Change "Friday" to your own deadline before sending, and check the owners and dates against your memory of the meeting. For other situations, such as chasing a late reply, see these professional email prompt examples.

7. The multi-document tracker prompt

Single summaries miss trends. When you have a series of weekly reports or meeting notes, this prompt shows what changed between them, which is where Claude for long documents really pays off. It suits operations managers, agency leads and anyone reporting progress upward.

I've uploaded several weekly status reports, oldest first. Build a table with these columns: Project, Status in the first report, Status in the latest report, What changed, Dates that slipped.
Below the table, list:
- Projects that have not changed in two or more reports.
- Any commitment made in an earlier report that later reports never mention.

The second list is where this prompt earns its keep, because dropped commitments are easy to miss when you read reports one at a time. Large batches of files can hit usage limits faster on the free plan. If you plan to run this every week, compare the $20 AI plans before you upgrade.

If your reports already live in Google Workspace, Gemini in Google Docs can summarize them without any downloading or uploading.

How do you summarize confidential files safely?

Before you paste a client contract or an internal meeting transcript into any AI tool, check what happens to that data. With Claude, the answer depends on your plan.

On consumer plans (Free, Pro and Max), Anthropic may use your chats to train future models if the "Help improve Claude" setting is on. You can switch it off under Settings, then Privacy. Anthropic's announcement of its updated consumer terms explains this choice and the longer data retention that applies when training is allowed. Commercial plans, such as Team, Enterprise and the API, fall under separate terms and are not used for training by default.

Use this checklist before you upload anything sensitive:

• Check your employer's AI policy. Many companies allow only approved tools or work accounts.
• Remove what Claude doesn't need. Replace client names, account numbers and personal details with labels such as "Client A".
• Skip regulated data. Health records, financial account details and customer personal data usually belong in a company-approved tool only.
• Get consent for recordings. Consent rules for recording calls vary between US states, and in the UK, data protection law (UK GDPR) covers recordings that capture personal data. Tell attendees when a meeting is transcribed.
• Review your training setting. Check it once now, and again whenever Anthropic updates its terms.