Running a Research Mode Query Step by Step
Research mode is only as good as the question you give it and the read you give its report afterward.
This page walks through a full run, start to finish - framing the question, starting the research, and reading what comes back - so the process feels concrete rather than abstract.
Summary
Research mode works in three phases from your side of the conversation: framing the question, letting the investigation run, and reviewing the report it returns.
Each phase has its own habits that separate a useful research report from a shallow one.
Framing matters most, because a vague question gives Research mode little to actually decompose and investigate.
Once started, the process runs on its own - your job shifts from directing it to waiting and, later, reading critically.
The review step is not optional: a cited report is only trustworthy once someone has actually checked a sample of those citations.
Recipe
Quick-reference shape for a Research mode run.
1. Frame a specific question with real constraints (who/what/when/scope).
2. Start the research task from a normal Claude.ai conversation.
3. Let it run - it works through sub-questions and sources on its own.
4. Read the returned report, starting with the summary, then the citations.
5. Spot-check 2-3 citations that matter most to your decision.
6. Follow up with a narrower question if the first report was too broad.When to reach for this:
- You have a question that needs comparing multiple sources, not just one answer.
- You need a written, checkable summary you can share with someone else.
- The information you need might be time-sensitive or something Claude shouldn't guess at from memory.
- You're willing to wait longer than a normal reply in exchange for a more thorough answer.
- You want a repeatable process your team can use consistently for recurring research needs.
Working Example
Here's a complete run from framing through review, using a realistic business question.
Step 1 - Frame the question:
Weak framing: "Tell me about project management tools."
Strong framing: "Compare three current project management tools -
Asana, Linear, and Monday.com - on pricing tiers, seat limits, and
whether each offers a free tier as of today. Cite each vendor's own
pricing page."
Step 2 - Start the research task:
Send the strong framing above as your message and start Research mode.
Step 3 - Let it run:
Research mode plans sub-questions (one per tool), searches for
current pricing information on each, and reads what it finds.
This step takes noticeably longer than a normal reply - that's expected.
Step 4 - Read the returned report:
"Report: Project Management Tool Pricing Comparison (as of [date])
- Asana: Free tier available (up to 10 users); paid tiers from
$X/user/month. [Source: asana.com/pricing]
- Linear: No unlimited free tier; paid tiers from $Y/user/month.
[Source: linear.app/pricing]
- Monday.com: Free tier available (up to 2 seats); paid tiers from
$Z/user/month. [Source: monday.com/pricing]
Note: pricing pages for all three list monthly and annual options;
this report cites monthly list pricing unless noted."
Step 5 - Spot-check citations:
Open at least the two vendor pricing pages most relevant to your
decision and confirm the figures still match what the report says.
Step 6 - Follow up if needed:
"Now break down Asana's paid tiers in more detail - what's included
at each level?"What this demonstrates:
- A constrained question (three named tools, specific attributes, "as of today") gives Research mode concrete sub-questions to investigate.
- The returned report is structured per sub-question, with a citation attached to each claim.
- The report proactively notes a caveat (monthly vs. annual pricing) rather than hiding the ambiguity.
- The review step (spot-checking citations) is a deliberate action, not something the report does for you.
- A follow-up question can drill into one part of the report without restarting the whole investigation.
Deep Dive
How It Works
- Framing sets the scope: specific entities, attributes, and time constraints become the sub-questions Research mode investigates.
- Once started, Research mode plans, searches across multiple sources per sub-question, reads what it finds, and synthesizes a single report - this runs autonomously, without you steering each step.
- The report format groups findings by sub-question and attaches a citation to each claim, so the structure of your question tends to show up in the structure of the report.
- Caveats and disagreements between sources are meant to surface in the report itself, not get silently smoothed over.
- A follow-up question after the first report reuses the same conversation's context, so you don't need to re-explain the original scope.
Framing a Question Well
| Weak framing | Why it's weak | Stronger version |
|---|---|---|
| "Tell me about X" | No comparison, no scope, no constraint | "Compare named options A, B, C on specific attributes" |
| "What's the latest on Y" | No time window, no source expectation | "What changed about Y in the last quarter, citing primary sources" |
| "Is Z a good idea" | Opinion question, nothing to research | "What are the documented trade-offs of Z, based on independent sources" |
Reading the Report
A useful reading order is: read the summary first for the overall shape of the answer, then work through each cited claim that actually matters to your decision, then check whether the report flagged any disagreement between sources.
Claims that don't matter to your decision don't need the same scrutiny as the ones that do - reading a research report critically doesn't mean opening every single citation.
Gotchas
- Starting with a vague question and blaming the report. A report built from a vague question will be broad and shallow because there was little to decompose. Fix: rewrite the question with named entities, specific attributes, and a time window before starting.
- Treating the summary as the whole report. The summary is a compressed version of the findings; skipping the cited detail means missing caveats the report deliberately included. Fix: read past the summary for anything the report will be used to decide.
- Never opening a single citation. A report can look thorough while resting on sources that don't actually say what the summary implies. Fix: spot-check at least the citations behind the claims that matter most.
- Assuming a follow-up needs to restate everything. Research mode's follow-up questions build on the same conversation, so re-explaining the whole original scope is usually unnecessary. Fix: ask the narrower follow-up directly, referencing "the report above."
- Sharing a report onward without a review pass. Forwarding a cited report to a decision-maker implies it's been checked, even if it hasn't. Fix: do a short review - citation quality, source diversity, dated claims - before sharing it further.
Alternatives
| Alternative | Use When | Don't Use When |
|---|---|---|
| Regular conversation | The question is well-known, opinion-based, or doesn't need comparing sources | You need a defensible, checkable answer for a real decision |
| Research mode with connectors | The question needs internal company knowledge alongside public sources | No connectors are set up yet for the sources you'd need |
| Manual research | You need to personally verify every step for a high-stakes decision | Time is limited and a first-pass synthesized report would still help |
FAQs
How specific does my question actually need to be?
Specific enough that Research mode can turn it into concrete sub-questions - naming entities, attributes, and a time window is usually enough.
Vague, open-ended questions tend to produce broad, shallow reports.
Can I interrupt or redirect a Research mode task once it's started?
Research mode runs the investigation on its own once started rather than pausing for step-by-step direction; if the framing was off, the more effective move is usually to let it finish and then follow up with a narrower question.
What should I read first in a returned report?
Start with the summary for the overall shape of the answer, then read the cited detail behind any claim that actually matters to your decision.
Do I have to check every citation?
No.
- Prioritize citations behind claims that matter to a real decision.
- Spot-check rather than exhaustively verify every line.
- Treat a claim you're not going to act on with less scrutiny than one you are.
What if the report only found weak or repetitive sources?
That's useful information itself - it tells you the topic may not have strong, independent public coverage, and you should weigh the report's confidence accordingly rather than treating it as settled.
Can I ask a follow-up question about the same report?
Yes - a follow-up in the same conversation can drill into one part of the report without you needing to restate the original scope.
Why did my report come back broader than I expected?
This usually traces back to framing - a question without named entities, specific attributes, or a time window gives Research mode more ground to cover and less to narrow in on.
Is it normal for Research mode to take a while?
Yes.
Planning sub-questions, searching multiple sources, reading them, and synthesizing a cited answer is genuinely more work than a single-pass reply, so a longer wait than usual is expected.
Should I trust a report more if it has more citations?
Not automatically.
Citation count matters less than citation diversity - several citations that trace back to the same original source don't add independent confirmation, even though the report looks well-sourced.
What's the fastest way to fix a disappointing first report?
Rewrite the original question to be more specific - name the exact entities, attributes, and time window you care about - rather than assuming the feature simply underperformed.
Can I reuse the same question format for recurring research needs?
Yes, and it's worth doing - a consistent question template for a recurring research task (like a monthly competitor check) makes reports easier to compare over time, and can be packaged into an Agent Skill if the team runs it often.
Should I share a Research mode report exactly as returned?
Only after a short review pass - checking citation quality, noting any dated claims, and confirming nothing in the report surprised you enough to double-check first.
Related
- How Research Mode Works Inside Claude - the mechanics behind the process this page walks through
- Evaluating Research Mode Output: Sources and Confidence - a deeper framework for the review step
- When to Use Research Mode vs a Regular Conversation - deciding whether a question needs this process at all
- Connected Tools Checklist Before You Start a Task - what to confirm before a run that needs internal sources
- Research Mode, Skills & Tools Best Practices - habits that build on this walkthrough
Stack versions: Written against the Claude model lineup current as of ~June 2026 - Claude Fable 5, Claude Opus 4.8, Claude Sonnet 5 (the default), and Claude Haiku 4.5. Model names, pricing, and product features move quickly - verify current specifics at platform.claude.com/docs before relying on them.