01
Where this one gets misread
This step decides what is actually searched for, and it is almost never shown. A rewritten query can quietly change the question you asked, and the answer will be a good answer to a question you did not ask.
Glossary
What is query understanding?
Query understanding is the step before retrieval that works out what the user meant, then turns it into the terms and filters the system searches with.
Updated 21 Aug 2026
02
Questions to ask
Ask for a worked example on your own material, and the evidence needed to reproduce it.
- Can you see the query that was actually run?
- What rewriting or expansion happens?
- How are filters inferred from the wording?
- What happens with a genuinely ambiguous question?
03
How Marella uses the term
We use “Query understanding” only where a product mechanism or an evaluation method backs it up, and we say when the behaviour depends on how a deployment is configured.
- Backed by a product mechanism or an evaluation method
- Deployment differences flagged
What this page does not prove
- B1A definition is not a claim about how the product performs.
- B2Vendor implementations vary.
- B3Test the term against a representative workflow.
Related pages
Test the claim on your documents
Pick a real piece of work, agree what a good answer looks like, then go through the results together.