Best practice L2 · Context engineering informational

Ask for Quotes and Locations, Not Just Claims

What it is

A grounding habit: ask the summary to attach the exact supporting quote and its location to each key claim, so you can verify the point without re-reading the whole source.

Claims onlyunverifiable· 'The report says X'· No way to check fast· Paraphrase can driftClaims + quotesverifiable→ Exact supporting quote→ Section or page ref→ Drift is visible
A claim with its quote is checkable; a bare claim is a leap of faith.

Why it works

A paraphrased summary can subtly overstate or invert what the source said, and you'd never know. Requiring a quote and a location for each claim anchors the summary to the text — drift becomes visible, and checking a point takes seconds. It also discourages the model from asserting things the document doesn't actually support.

When to use it

Summaries you'll act on or repeat: legal or policy documents, contracts, research papers, anything where a misread claim has consequences.

When not to use it

Casual gists for your own orientation, where quote-hunting is overhead and rough accuracy is fine.

Prompt

Summarise <document>. For each key claim, include the exact quote that supports it and where it appears (section/page). If a point isn't directly stated in the text, say so rather than inferring it.

Example

A contract summary claims 'termination requires 30 days' notice' and pins it to the quoted clause — you confirm it in seconds instead of re-reading twelve pages.

Common mistakes

  • Trusting a paraphrase that quietly overstates the source.
  • Not asking for locations, so verifying means re-reading everything.
  • Letting the model infer claims the document never actually makes.

Related