Planning is an agentic workflow pattern that decomposes a complex query before retrieval, retrieves for each sub-query, and synthesizes the results. section 15.2.1
Use planning when a single retrieval pass cannot assemble the required evidence.
- Treat planning as a runtime decision: determine how to decompose the question and how many sub-queries it requires. section 15.2.1
- Retrieve independently for each sub-query, then combine the results into one answer. section 15.2.1
- Prefer planning over fixed query expansion when the question's information needs vary at runtime. section 15.2.1
- Balance quality against latency because additional model calls increase response time. section 15.9
Comparing claims processing with industry benchmarks
A planning agent separates the question into internal claims-process documentation and external auto-insurance industry data, retrieves each independently, and synthesizes the comparison. section 15.2.1










