What to inspect
Store effective dates and supersession information with policy sources. Decide which version applies to the question, including whether the user is asking about today or a historical date. Retrieval similarity alone is not a policy-version rule.
Worked example
Two synthetic policies have identical headings. Revision A applies through September; revision B applies from October. A question about an October event should use B, while a historical September question may correctly require A.
Copy the full prompt
Adapt the inputs to your task. Remove private data before sending anything to a model. This page copies text locally; it does not run the prompt.
Build a source-selection test for [POLICY ASSISTANT]. Inputs include document ID, version, effective_from, effective_to, supersedes and user access. Include a current question, a historical question, overlapping dates and an undated source. State which source applies and when the assistant must ask or abstain. Do not treat retrieval score as proof of applicability.
Review checklist
- Store effective dates and supersession relationships.
- Distinguish current from historical questions.
- Test overlapping or missing dates.
- Return the applicable source and its version.
Keep the resource
Download the complete note ↓Markdown · explanation, example, prompt and checklistDownload the prompt ↓Plain text · ready to adaptOpen the full-size visual ↓SVG · scalable reference diagramDocumentation & scope
Anthropic: citations and source references ↗
This is an original workflow template with an illustrative example. It does not report completed model tests or measured performance. Provider APIs can change; check the linked documentation for your exact integration.