Split documented facts from AI interpretation and speculation

Separates verifiable source facts from analytical assumptions and extrapolations. Use it to keep executive memos, reports, and summaries strictly accountable.

You getVerifiable Facts and inferred Commentary

Prompt

Prompt
Act as an analytical editor. Audit the provided text against my source notes to cleanly separate verified source facts from inferred commentary or AI-generated assumptions.

- Sort statements into strict source-backed facts versus interpretations or deductions.
- Flag any claim that extrapolates beyond the literal boundaries of the source material.
- Do not delete useful insights; categorize them transparently.

Output format:
- Verifiable Facts: bullet points supported directly by the text, citing the line or passage.
- Inferred Commentary: bullet points showing extrapolations, labeled by risk level (Low, Medium, Speculative).
- Missing Connectors: short notes on what evidence is missing to turn the inferences into confirmed facts.

Here is the material:

Example output

Example for: an executive summary of quarterly churn analysis

Verifiable Facts
  • User churn increased by 14% in the enterprise segment during Q3 (Source: Table 2, Revenue Metrics).
  • The billing migration took place on July 14th (Source: Engineering Changelog).
  • Exactly 42 enterprise accounts submitted exit surveys citing payment portal errors (Source: Support Log Summary).
Inferred Commentary
  • "The migration directly triggered the entire churn spike" — Risk: Medium. While the timing matches, the source notes do not rule out concurrent competitor discounting mentioned in sales calls.
  • "Enterprise customers are unwilling to adopt the new payment gateway" — Risk: Speculative. The survey noted technical processing errors, not active customer rejection of the platform brand.
  • "Customer support response delays amplified customer frustration" — Risk: Low. Logically sound based on high ticket volume, but response times were not measured in the source data.
Missing Connectors
  • Need time-stamped ticket resolution averages for July through September to validate the support delay claim.
  • Need churn exit interview logs from non-reporting accounts to confirm billing was the primary driver across all lost accounts.
Written by AI from this prompt. Your results will vary.

Paste both your original source notes and the AI draft into Gemini, Claude, or ChatGPT. If you want a clean version, follow up by asking for a rewrite containing only verifiable facts.

Make it repeatable

Keep using this prompt without pasting it in every time.

Keep exploring

More in AI Tools & Prompt Engineering
AI Tools & Prompt Engineering

Stop AI from inventing numbers and quotes

Constrain the model to rely strictly on your provided source material, flagging gaps explicitly instead of fabricating facts, metrics, or citations.

AI Tools & Prompt Engineering

Combine the strongest parts of two drafts

Merge two competing drafts into a unified, polished piece. Use it when two AI variants each contain strong paragraphs worth keeping.