--- title: "Research with Claude without losing the source trail" description: "Turn a small document collection into a checked research memo with claim-level references, disagreements and visible gaps." author: Power of AI date: 2026-09-06 url: https://powerofai.ca/claude/research-with-documents --- # Research with Claude without losing the source trail Turn a small document collection into a checked research memo with claim-level references, disagreements and visible gaps. The answer should lead you back to the evidence. Reading several documents together is a promising use of AI because the hard part is often connecting information spread across them. It is also easy for a fluent summary to erase disagreements. Structure the work so you can move from the conclusion to the source passage and back again. That makes the result easier to trust and much easier to revise. ## Start with an inventory and a question Choose a specific question that the supplied documents might answer. For example: “Which requirements changed between these two public program guides?” is more useful than “Summarize everything.” List the files, their dates and their roles. Tell Claude whether later documents supersede earlier ones or whether that relationship still needs investigation. Ask which files were readable and what material appears missing. A scanned page, a truncated table or an absent appendix can change the result. Keep unreadable material in the memo’s limitations rather than treating it as reviewed. If the question needs current external evidence, identify that as a separate research step. ## Extract claims before writing the story Request a table with one substantive claim per row. Add the document name, a page or section locator, a short supporting passage and an uncertainty note. Keep extraction separate from interpretation. “The deadline is September 30” and “This gives applicants more time” are different claims and may require different evidence. Open a sample of the references immediately, including the most consequential claim and one disputed claim. Check that the cited passage actually supports the wording. If a locator is wrong, repair the source trail before asking for a polished report. Otherwise the final memo can hide a weak extraction behind a coherent narrative. ### A request you can adapt Compare these approved documents against my question. First inventory readable inputs. Then create a claim table with source, locator, supporting passage, interpretation and uncertainty. Preserve disagreements. Use “not established by these documents” where appropriate. Draft the memo only after I review the table. ## Let conflicting sources remain visible Two documents can disagree because they describe different dates, populations or definitions. Ask for those possible explanations, but require evidence before choosing one. A useful memo may conclude that the discrepancy is unresolved and name the additional document needed to resolve it. Keep a distinction between no evidence and evidence of absence. A guide that does not mention a requirement does not necessarily cancel it. A missing record does not prove that an event never happened. These are reasoning checks you can apply yourself, regardless of which model produced the draft. ## Deliver a memo someone else can check Lead with the answer the evidence supports, then give the most relevant references and unresolved questions. Include the scope and dates of the source collection. If you used a project knowledge base, identify the specific documents involved; the project name alone is not a citation. Export the claim table with the memo so another reader can inspect the chain. Before sending, verify that copied links and locators survived the export. If the source collection changes, rerun the affected claims rather than assuming the whole memo remains current. This creates a research artifact that can improve as new evidence arrives. ## Take this into your next task A good research memo is a useful answer with a short, inspectable path back to its sources. [Build a project brief](/showcase#brief-builder). ## Sources and editorial notes Reviewed September 6, 2026. Product capabilities depend on the app, plan, region and workspace settings. Workflows and prompts are authored teaching material, not recorded model results or measured time-saving claims. - [Anthropic: projects and project knowledge](https://support.claude.com/en/articles/9517075-what-are-projects) ## Keep going - [Use Claude Projects as a working editorial desk](/claude/projects-and-writing) - [Gemini Deep Research: from a broad question to a checked brief](/gemini/deep-research) - [Turn Research into a Searchable Website with AI](/workflows/research-to-website)