Establish what is happening
Collect paired queries
Place the literal and corrected forms beside language, product family, result count, and first useful action. Include a typo that should correct, a valid uncommon term, and a brand name. Keep the submitted text visible in the comparison.
Test meaning preservation
Compare result overlap and requested outcome, not only edit distance. A hyphen or case change may preserve meaning while a short typo may create another product. Record when a correction should be suggested rather than applied silently.
Set a correction boundary
State supported language, confidence, opt-out, and fallback rules. Preserve examples that must remain literal. Stop when the team can explain which variants are equivalent in the selected context and which need a separate vocabulary review.
What to carry forward
The triage output is a correction boundary with paired terms, expected overlap, context, and confidence. Stop when literal and corrected intent are distinguishable. If one edit could name a different product, keep the original query primary and route the ambiguity for investigation.
Technical background: GOV.UK developer 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