Establish what is happening
Capture the ranked sample
Record query, filters, sort, result positions, matched fields, freshness, boosts, pins, and useful destination. Include one result whose position is clear and one disputed row. Keep rule or index references alongside the sample.
Separate evidence from inference
Write which visible or recorded signal supports the order and which explanation is only suspected. Compare textual match, business rule, freshness, and selected sort. A missing explanation is not proof the ranking mechanism is wrong.
Set an explanation boundary
State which ranking factors can be shown, which need an internal trace, and what a reviewer must know to make a safe change. Preserve the disputed query. Stop when another person can reproduce the question without repeating the entire debate.
What to carry forward
The triage output is an explanation boundary with ranked sample, visible signals, hidden inputs, and task context. Stop when surprise and evidence absence are distinct. If the order is intentional but opaque, route explainability work separately from relevance correction.
Technical background: Elastic documentation.
Keep the decision with the work.
Use a Work Item in Aglet to record the problem, the evidence you have, and the next decision. Add an owner and priority, then keep updates in the discussion so the next person can follow the reasoning.
Create an account See the product workflow