Summarize a document folder with Claude: sources, conflicts and a useful report

Prepare an inventory before uploading

List each file, its date, purpose and status. Keep approved documents distinct from drafts. Rename ambiguous copies without overwriting the originals. If two documents cover the same topic, note which one updates the other and whether that update was actually approved.

Check your organization’s rules before sharing real files. A fictional test folder can reveal formatting problems without disclosing client records. The file-upload documentation explains supported inputs and current constraints; inspect the actual extraction when tables or scans are important.

Build an evidence matrix

Ask for a table containing the claim, source file, relevant passage or page, date and certainty. Require “not found” when evidence is absent. A filename alone is insufficient if a reviewer cannot locate the supporting passage.

Suppose an initial plan lists 12 participants, a draft amendment proposes 15 and a signed record confirms 16. Do not average these figures. They describe different versions and statuses. The report should explain that the signed record is the confirmed source, while retaining the earlier figures as history if useful.

Separate facts, analysis and recommendations

Use distinct sections so readers can tell what the documents say from what the assistant infers. A recommendation should identify the facts behind it and the assumptions it needs. “The project may need another facilitator” is a suggestion, not a decision recorded in the files.

For a short executive report, request the decision question, confirmed facts, unresolved conflicts and next actions. Put the detailed evidence matrix in an appendix. This keeps the main report useful while allowing the underlying claims to be checked.

Review the difficult parts directly

Open the original source for every important date, amount and commitment. Verify calculations independently. Tables, scanned documents and footnotes can be misread or omitted. Ask the assistant to identify extraction uncertainty instead of claiming that an incomplete reading is comprehensive.

If the folder is large, process a coherent subset first and maintain a shared evidence table. A Claude Project can organize reference material and instructions; it does not remove the need to manage versions or verify the final report.

Answer the decision question using only the supplied documents. Create an evidence matrix with claim, filename, passage or page, date and status. Separate confirmed facts, contradictions, analysis and recommendations. Mark missing evidence and extraction uncertainty. Do not average conflicting figures or invent an approval.

Deliver and maintain the report

Date the report and list the document versions used. Keep the report alongside its source inventory. When a new document arrives, identify which claims change rather than silently regenerating everything. The recipient should understand what was checked and what remains unresolved.

Download the report template. For numeric material, use our Excel verification workflow. For recurring meeting records, try a small Claude Skill.

Frequently asked questions

Can I ask for a one-page summary? Yes, but retain the evidence matrix. A short output still needs traceability.

Should the assistant choose between contradictory files? Only when an explicit rule or source status justifies that choice. Otherwise the contradiction should remain open.

Sources

• →Anthropic: upload files to Claude.
• →Anthropic: create and manage Projects.
• →Anthropic: use Cowork safely.