Mastery Module 12 · The Prompting Playbook

Ground the Answer

Last reviewed

Advanced

What you'll learn

~16 min
  • Cut hallucination by making the model extract supporting quotes before answering
  • Give the model explicit permission to say 'not found' instead of inventing
  • Structure long-document prompts so the model actually uses the source

This is the technique that matters most for research, legal, compliance, analysis, and any work where a confident-but-wrong answer is worse than no answer. It directly targets hallucination — the model’s habit of producing plausible, fluent claims that aren’t actually supported by the source.

The move:

Answer the question using only the document below.
First, in <quotes>, copy the exact sentences from the document that
support your answer. If the document does not contain the answer, write
"NOT FOUND" in <quotes> and stop.
Then, in <answer>, answer the question using only those quotes.
<document>
{the source}
</document>
Question: {the question}

You’ve forced a sequence: find the evidence, then answer from the evidence. The model can’t fluently invent a conclusion when it has to point at the exact sentences that back it up first.

Why quoting first works

Left to its own devices, the model generates the most plausible-sounding answer and may fill gaps with invention — it’s optimizing for a fluent response, not a sourced one. Requiring quotes before the answer changes the order of operations:

  1. It anchors the response in the actual text instead of the model’s general impression of it.
  2. It makes gaps visible — if there are no supporting quotes, that’s now obvious to both of you, instead of being papered over with a confident paragraph.
  3. It gives you something to verify. You can scan the quotes against the source in seconds, instead of re-reading the whole document to check the answer.

This is the same instinct as the reason-before-answering technique from the thinking lesson, pointed at a different failure: there, you wanted logical steps before a conclusion; here, you want textual evidence before a claim.

Give it permission to come up empty

Half of grounding is the quoting. The other half is explicitly allowing “I don’t know.” Models hallucinate partly because nothing in the prompt told them that “not found” is an acceptable answer — so they assume they must produce something.

If the answer is not in the document, say "The document does not
address this." Do not use outside knowledge. Do not guess.

Those three sentences prevent a large share of confident fabrications. “Do not use outside knowledge” is important too: without it, the model may quietly blend the document with its training data, and you lose the guarantee that the answer came from your source.

💡Quotes are your audit trail

When the model quotes first, you get a built-in fact-check. Skim the quotes, confirm they exist in the source and actually support the claim, and you’ve verified the answer faster than you could have read the document yourself. If a quote isn’t in the source — that’s the rare case where the model fabricated a quote, and now you’ve caught it. Spot-check quotes against the original on anything that matters.

Long documents: where to put what

Grounding gets more important as the source gets longer, because there’s more room for the model to drift. Anthropic’s long-context guidance gives a concrete structure:

  • Put the long document near the top, above your question and instructions. In Anthropic’s testing, placing the query at the end — after the document — improved response quality by up to 30% on long inputs.
  • Wrap the document in tags (the structure technique from the last lesson) so its boundaries are unambiguous.
  • Ask for quotes first when grounding matters, so the model re-reads the relevant parts before answering instead of relying on a fuzzy impression of a 50-page input.

Putting it together for a long source:

<document>
{the long document — placed first}
</document>
Using only the document above:
1. In <quotes>, copy the exact passages relevant to the question.
If none exist, write "NOT FOUND".
2. In <answer>, answer using only those quotes. Do not use outside
knowledge.
Question: {the question — placed last}
🧬In Your Field: Biotechclick to expand

No invented results, ever. When summarizing a methods section or a results table, “quote the exact sentences reporting each value before you summarize, and write NOT REPORTED for anything the paper doesn’t state” prevents the model from inventing a sample size or p-value that sounds right. In science, a fabricated number is the worst possible failure — grounding is non-negotiable.

🏛️In Your Field: Government / State Devclick to expand

Cite the regulation, don’t paraphrase it from memory. For policy and compliance questions, “answer only from the provided statute text, quoting the exact subsection before each conclusion, and say ‘not addressed’ if it’s silent” keeps the model from confidently misstating a rule it half-remembers from training. The quote is the citation your reviewer needs.

🏢In Your Field: Property Managementclick to expand

Ground answers in the actual lease. “Answer the resident’s question using only the lease text in <lease>, quoting the relevant clause first; if the lease is silent, say so” stops the model from inventing a policy that isn’t in the document — which is exactly the kind of error that turns into a dispute.

📦In Your Field: Procurementclick to expand

Quote the spec before you assert a requirement. When checking a vendor submittal against the project spec, “before approving each line, quote the exact spec section it must satisfy and flag any requirement the submittal doesn’t address” turns a rubber-stamp review into a defensible one — and the quotes are your paper trail when a vendor pushes back.

KNOWLEDGE CHECK

You're asking the model questions about a 40-page contract and occasionally getting confident answers that turn out to be wrong. What's the most effective fix?

Key takeaways

  • Quote first, answer second. Forcing the model to extract supporting passages before it concludes is the strongest single defense against hallucination.
  • Permit “not found.” Explicitly allow “the source doesn’t address this” and forbid outside knowledge — much of fabrication comes from the model assuming it must answer.
  • Quotes are your audit trail. Verify the claim by checking the quotes against the source — far faster than re-reading everything.
  • For long sources: document first, query last, wrapped in tags. Query-at-the-end placement alone can lift quality by up to 30%.
  • This is the technique to reach for on anything where wrong-but-confident is the costly failure — research, legal, compliance, analysis.

Next: Chain Your Prompts

Search lessons