Browse
Productivity

Pull the facts out of this document

Turn a long report, contract or transcript into a structured list of facts, numbers and dates, each with a pointer back to where it came from.

No votes yet this week
Output
Text
Written with
Claude Fable 5.1
Added

The prompt

Extract the facts from this document. I'll use them for [WHAT YOU'RE DOING WITH THEM, e.g. a comparison of three suppliers].

What I care about most: [TOPICS, e.g. prices, delivery times, cancellation terms]

<document>
[PASTE THE DOCUMENT]
</document>

Rules:
- Only facts that are actually in the document. No inferences, no "probably".
- Every fact gets a pointer to where you found it: a section name, a heading, or a short quote.
- Keep numbers exactly as written, with their units and currencies.
- If the document contradicts itself, list both versions and mark the contradiction.
- If something I care about isn't covered at all, say so explicitly. A gap is a finding.

Format: one table per topic I listed, with the columns Fact, Detail, Source. Then a short section called "Not covered" and one called "Unclear".
  • extraction
  • research
  • summaries

What it generates

Example

NoteThis is an example. Results change between runs and model versions. Claude Prompts is a fan project and is not affiliated with Anthropic.

Getting the most from this prompt

Where it saves time

Supplier quotes, lease agreements, insurance documents, long meeting transcripts, research reports. Anything you'd otherwise read twice with a highlighter. It's also a decent way to compare several documents: run it on each with the same topics, and you get tables that line up.

Getting reliable tables

List your topics in the order you want the tables. Be concrete, because "costs" gets you everything with a number in it, while "unit price, setup fees, price increases" gets you what you actually need. Very long documents are better in two or three chunks, with the same topic list each time.

Trust, but check

The source column exists so that you can verify anything that matters before you act on it. Spot-check a few rows against the original, especially numbers. Read "Not covered" as carefully as the tables: a contract that says nothing about payment terms is telling you something.

How to use this prompt

  1. [01] Copy

    Copy the prompt

    Use the copy button above. The full text is included, nothing is cut off.

  2. [02] Fill in

    Replace the yellow parts

    Everything highlighted in yellow is a placeholder. Swap it for your own topic, audience or data.

  3. [03] Vote

    Run it in Claude and vote

    If the result helped, press the heart. Votes decide which prompts make the weekly top 10.

More like this

All productivity prompts
Text output

Summary. The launch moves from 2 October to 9 October so the checkout bug can be fixed properly. Marketing keeps the original date for the teaser email. Decisions Launch day is now 9 October. The teaser email still goes out on...

Meeting notes to decisions and owners

Turn messy notes or a transcript into decisions, a task table with owners and dates, the open questions, and a message for the team channel.

Text output

Everything fits except the conference talk outline, which I've pushed to the following week (see the note at the end). Monday Morning (your best hours) 8:30 to 10:00 write the Q4 proposal draft. 10:15 to 11:00 keep going, or...

Plan my week around energy, not just time

Give Claude your tasks, your fixed appointments and when you actually have energy, and get a week plan that puts hard work where you can do it.

Learn the technique

All articles
2 min read

How to use XML tags in Claude prompts

Wrapping parts of your prompt in simple tags is one of the easiest ways to get more reliable answers from Claude. A practical guide with examples.