How to research and fact-check with AI: deep research mode

In short: deep research mode is when AI doesn't answer instantly but runs dozens of searches on its own, opens pages and assembles a sourced report in 5–30 minutes. It saves hours — but it doesn't remove verification: the model can still misread a source or cite a page that doesn't exist. One rule: open the links yourself.

How it differs from ordinary chat with search

Ordinary chat with web search fires one or two queries and answers in seconds. Research mode works differently: it splits your question into sub-questions, searches each, reads what it finds, notices contradictions, searches for the gaps — and only then writes a structured report with footnotes. It's a "search → read → refine" loop, spun many times without you.

Hence the difference in feel: a normal answer is the opinion of a well-read companion; a deep research report is a draft analyst's memo. With a bibliography you can check. Or fail to check — and step on a rake.

Where you'll find it

• ChatGPT — Deep Research mode, typically on paid plans, with a monthly run limit.
• Gemini — Deep Research, built into the interface, shows its research plan before starting.
• Claude — Research mode with web search and multi-source work.
• Perplexity — search-first by design, with a dedicated research mode.

Names and limits change almost monthly, so memorise the principle rather than the brand: if a tool shows a source list and spends minutes rather than seconds, that's the mode. How the models differ overall is covered in ChatGPT vs Claude vs Gemini.

How to brief it so the report is useful

The classic mistake is throwing in a one-line topic ("the EV market in Europe") and expecting magic. The mode will run and hand you fluff. Constrain the task on four axes: the question, the boundaries (period, region, source types), the format and what to do with uncertainty.

Task: build an overview of [TOPIC] for [PURPOSE / AUDIENCE].

Boundaries:
- period: material from [year/period] only
- region: [countries/market]
- sources: prioritise primary ones (reports, statistics,
  documentation, papers); blogs and press releases only as
  illustration, and flag them as such

Questions to answer:
1. ...
2. ...
3. ...

Format:
- a 5-bullet summary up front
- then a section per question
- every claim with a number gets a source link
- a table: source | date | what was taken from it

A separate closing section:
- where sources contradict each other
- what you could not find
- which claims are weakly supported

That last block is the most valuable and almost nobody asks for it. It turns the report from "confident text" into a map of what's known, showing where the ground is solid and where it's swamp. To go deeper on request design, see what a prompt is and how to write one and our prompt examples.

The main trap: sources that don't exist

Language models invent sources. Not occasionally, and not only "bad models" — it's systemic: the model generates a plausible continuation of text, and a plausible URL with a plausible paper title is just as easy to produce as a real one. The mechanics are unpacked in AI hallucinations: why models make things up.

Research mode lowers the risk because it genuinely visits pages. It does not remove it. Three ways fabrication leaks into a finished report:

• A dead link. The source either moved or never existed — in the report both look equally respectable.
• The link works, the claim isn't in it. The most common and most treacherous case: the page opens, looks relevant, but the number from the report simply isn't there — the model filled in the emphasis.
• A chain of retellings. The report cites a blog, the blog cites a news piece, the news cites "a study" nobody has seen. Formally there's a footnote. Factually there's no primary source.

The uncomfortable but honest conclusion: a footnote isn't verification, it's a promise of verification. The verifying is on you.

Verify a report in 5 minutes

1. List the claims something depends on. Usually 3–7 per report, not forty. The rest is context, where an error costs nothing.
2. Open the link for each one. Does it load? Then Ctrl+F for the number or keyword. Not there? The claim is unsupported. Full stop.
3. Walk back to the primary source. If the footnote leads to news about a report, find the report. Numbers mutate on the way.
4. Check the date. A "fresh" report is easily assembled from five-year-old articles if you didn't bound the period.
5. Ask for the opposite. Run a second pass: "find arguments against conclusion X and data that contradicts it." If nothing turns up at all, the search was probably shallow.

Five minutes of this ritual is the difference between "AI saved me a day" and "AI embarrassed me in a meeting".

Telling a good report from a pretty one

Deep research reports almost always look convincing: headings, bullets, footnotes, an even analytical tone. Beauty of form says nothing about quality of substance, so look at other signals.

• How many distinct sources back the key claims. If the whole report rests on two pages, it isn't research — it's a retelling of two pages.
• Whether source types vary. A report built only from blogs and media is weak. One with primary material (statistics, documentation, filings, papers) is strong.
• Whether dates are stated. An undated claim in a fast-moving topic is close to useless.
• Whether uncertainty is admitted. A good report says somewhere "the data diverges" or "no confirmation found". A report where everything is unambiguous is suspicious: reality doesn't look like that.
• Whether facts are separated from conclusions. "Sales grew X%" and "the market is heading for a boom" are different classes of statement and must not be blurred.

When research mode is the wrong tool

• You need one fact. A rate, a date, a definition — plain search is faster.
• The topic is under a day old. Indexing and access to fresh pages are uneven; read breaking news with your own eyes.
• The data is behind a wall. Paid databases, internal documents, paywalled papers — the model can't get in and, worse, will build an overview from abstract retellings.
• The stakes are medical or legal. A report is fine as terrain map and source list, not as the basis for a decision.

How to fit it into your workflow

The working pattern: deep research maps the field (who says what, and where) → you spend 5 minutes verifying the key claims → you ask the model to rewrite the report keeping only what's confirmed and to list separately what was dropped. The output is a short text you can stand behind line by line. Far faster than manual research, and still honest.

Keep basic hygiene in mind too: don't feed sensitive or other people's data into research mode — privacy when working with AI applies exactly as it does in ordinary chat. And if you're still getting comfortable with chat itself, start with the beginner's guide to ChatGPT.