Day 11: Read a 60-page research doc or board pack in five minutes.
The boring document on your desk doesn't need 45 minutes. It needs a sharper prompt and a colleague who reads fast.
Welcome to Day 11 of the challenge.
There’s a document on your desk. Maybe a board pack. Maybe a contract. Maybe a 47-slide pitch deck from a vendor. Maybe a long report you’ve been told to read.
You haven’t opened it. It’s been sitting there since last Wednesday.
Today we close that loop. Not by you finally sitting down with it. By Claude reading it for you and telling you only what you actually need.
Five minutes. Decision made. Move on.
A word before we start
Most AI “summarise this” prompts produce a summary. A summary is not what you want.
A summary tells you what’s IN the document. It doesn’t tell you what to DO. Half the time it doesn’t even tell you what matters.
You’re not a librarian. You’re a decision-maker reading the document because you need to act, push back, sign, decline, approve, escalate, walk into a meeting prepped. The brief has to ask Claude for that. Sharply.
Today’s prompt is the most powerful one in the challenge so far. Memorise the shape of it. Use it on every long document for the rest of your working life.
Step by step
Step 1. Pick a real document you’ve been avoiding. Not a hypothetical one. The actual one on your desk or in your downloads folder. Board pack, contract, deck, report. Anything ten or more pages you’d rather not read.
Step 2. Open Cowork in your desktop app. Opus for this one. (The thinking is heavier today.)
Step 3. Drag the file into a new chat. Or use the + button to attach. PDF, Word, deck, plain text, all work. If it’s a Google Doc, export to PDF first.
Step 4. Paste this brief:
I need to know what’s in this document but I don’t have 45 minutes. Tell me, in this order:
1. The one thing if I only read one sentence. 2. The three things if I read for two minutes. 3. What to question or push back on. Anything that doesn’t add up, contradicts itself, or feels weak. 4. Anything in here that contradicts something earlier in the doc. 5. The questions I should ask before I respond / approve / sign / decide.
Be ruthless. If a section is filler, say so. If a claim is unsupported, say so.
Context for you: [in 2-3 sentences, tell Claude WHY you’re reading this. Who’s asked for your response. What decision you’re being pulled into. What you suspect already.]
Before you start, ask me three clarifying questions about the context.
Step 5. Answer Claude’s three questions. (This step matters. The questions force Claude to pin down what you’re really looking for. Without them, you get a generic read.)
Step 6. Read the output.
You’ll notice the structure pulls you forward. The one-sentence read first. The three-minute read second. The pushback third. By the time you’ve finished reading Claude’s brief, you’ve already formed an opinion.
Step 7. For each item flagged as “question or push back on,” ask Claude:
Quote me the exact line from the document where this happens. Give me the page number or section if there is one.
That’s the receipt you’ll use in the meeting, the reply, the escalation.
Step 8. Save the brief.
Save this as 2026-XX-XX-doc-[short name].md in my Cowork folder.
When the meeting happens or the email gets sent, you’ve got the read. When someone challenges you, you’ve got the receipts.
A safety note
If the document is genuinely confidential (legal, M&A, board-sensitive, employee data), think before you drop it into a chat. Two checks:
Is it covered by your company’s AI policy? Most enterprise Claude accounts are now approved for confidential material. Personal Claude Pro is treated as your own device. If you’re not sure, ask IT or check the policy doc.
Would you read it on a train with someone sitting next to you? If yes, drop it in. If no, redact the sensitive sections before you attach.
When you’re done, delete the chat. The document goes with it.
What you’ll notice
The summary is shorter than you’d write. By a lot.
A 60-page board pack collapses to four or five lines that matter. The rest is genuinely filler, repetition or framing. Once you see this happen once, you trust it. Twice, you stop reading long docs the slow way.
The pushback is the unlock. The “things that don’t add up” list will surface contradictions you’d have missed because you’d have read in a straight line. Claude reads non-linearly. It cross-checks. It catches the buried number that doesn’t match the earlier slide.
You walk into the meeting having read for five minutes and you’re sharper than the person who read for forty.
Why this works
The friction with long documents was never the reading. It was the reading PLUS the formulating-an-opinion PLUS the remembering-what-mattered PLUS the cross-checking. Four jobs disguised as one.
Claude does the assembly. You make the call. The call is faster because the assembly is done. Same pattern as Day 5 (statement reading), Day 7 (inbox cross-check), Day 8 (inbox triage), Day 10 (planning). You’ll see it everywhere from here on.
Side note: when NotebookLM beats Claude for this
If the document is something you need to LEARN (a complex regulation, an academic paper, a deeply technical brief from a discipline you don’t know), Google’s NotebookLM is genuinely better than Claude for the learning task. It builds a chat interface trained on the document so you can keep asking questions, and produces study-guide-style summaries and audio overviews.
For DECISION-PREP, which is what today is, Claude is sharper.
Different jobs, different tools. Knowing which to reach for is the next layer of fluency.
Key takeaway
The “what to DO” prompt, not the “summarise” prompt. Five minutes. The doc you’ve been avoiding, read, with pushback and questions ready.
Use this prompt structure on every long document for the rest of your working life.
Where this is heading
You’ve made AI do the reading. Tomorrow we make it do the deciding. Or rather, we use it to make the decision you’ve been weighing for a week, the right way.
Tomorrow on Switched On
Day 12: Decide the thing you’ve been weighing.
Five questions. Five minutes. The A-or-B decision sitting on your plate, off your plate, today.
Nishma x
P.S. How did today land? Three buttons, thirty seconds → Tap one
I read every response. The data shapes the rest of the challenge.
Catching up? Days 0 to 10 are on the Switched On Substack archive HERE.
Got a friend or a colleague who this might be useful for? Send her to nishma.co/30daychallenge
SwitchedOn #SwitchedOnAIChallenge
