State the reader, decision, comparison criteria, and risk that could change the outcome.
AI Source Comparison Tool for Evidence-led Research Decisions
Build a comparison packet from pasted notes before you trust a recommendation: frame the decision, separate evidence from assumptions, flag unsupported claims, and hand off primary-source checks.
Choose a comparison workflow
Start with a decision pattern, then replace the pasted notes and verification rules with your own material.
Evidence packet and prompt
Vendor Decision Matrix / Evidence table
Source comparison packet: Vendor Decision Matrix Target output: Evidence table Decision reader: Product lead and security reviewer 1. Decision frame Question to answer: Compare two AI meeting assistants for a privacy-sensitive product team. Comparison criteria: - Privacy boundary, citation quality, price recency, setup time, failure modes 2. Supplied material Source A - Vendor page notes: SSO mentioned; retention policy link not pasted; exports action items. Source B - Security note excerpt: supports regional storage; pricing note is from last quarter. Team note - Must avoid sending client recordings to unclear subprocessors. 3. Evidence-constrained AI prompt Act as a careful source comparison assistant. Work only from the pasted source notes above. 1. Do not invent citations, dates, prices, metrics, URL contents, or facts not present in the supplied material. 2. Mark every conclusion as "supplied evidence", "verify next", or "assumption". 3. If sources conflict, explain the mismatch before stating what the current material supports. 4. Put recency, privacy, cost, failure states, and fit conditions into risk notes when they matter. 5. If the notes cannot support a recommendation, name the missing evidence instead of filling it in. 4. Evidence comparison table | Criterion | Source A | Source B | Evidence state | Risk / verify next | | --- | --- | --- | --- | --- | | [Criterion] | [Supplied finding] | [Supplied finding] | Supplied / Verify / Assumption | [Gap or conflict] | 5. Red flags and claims not ready - Flag claims without an original source, date, sample note, or operating condition. - Separate "plausible" from "supported by the supplied notes". - Require primary-source confirmation before relying on price, compliance, performance, or security claims. 6. Primary-source verification checklist - Return to original pages, papers, contract language, product docs, or experiment logs for key facts. - Record verification date, source owner, version changes, and items that remain unclear. - Assign each evidence gap to a reviewer and the decision it could change. 7. Output request Return a Evidence table. Finish with: - Safest current conclusion - Claims still unsupported - Three checks required before a decision - Handoff summary for the next reviewer
Keep supplied evidence, missing proof, conflicts, and assumptions visible in one packet.
Hand off exact primary-source checks before a recommendation becomes publishable or operational.
Source comparison template library
Vendor Decision Matrix
Compare tools with privacy, cost, setup, evidence quality, and operating risk made explicit.
Evidence Review Packet
Separate supplied findings, assumptions, conflicts, and primary-source checks before writing a brief.
Claim Fact-check Queue
Turn marketing or research claims into a verification queue with unsupported claims flagged.
Procurement Handoff Brief
Prepare the missing checks another reviewer needs before cost or compliance approval.
How to keep AI research comparisons trustworthy
Use stable labels, pasted excerpts, dates when known, and notes about what was not captured.
A feature claim matters less than the evidence, limit, recency, and condition behind it.
A good packet tells the next reviewer where to confirm the fact that could change the decision.
Source comparison FAQ
Does this tool open URLs or uploaded files?
No. This dedicated page works from text you paste into the form. It prepares a safer comparison packet and verification queue for a future cited-source workflow.
Will it create citations for me?
It should not invent citations. Use the packet to preserve source labels and to identify which claims still need a primary-source check.
When should I use a comparison packet instead of a summary?
Use it when one answer could change a decision, approval, purchase, publish step, or research recommendation and evidence gaps need to stay visible.