GLOSSARY
Model router
A model router chooses a suitable model for a request. Selection criteria can include the task, expected quality, response time, cost and permitted data processing. These criteria can conflict: a quick answer may suit simple classification but be inadequate for a disputed contract issue.
Allocate effort to the decision
A meeting note, account research and the assessment of several negotiating options create different demands. A router could allocate processing effort accordingly. It must identify those demands reliably enough and direct uncertain cases to more suitable handling.
Incorrect routing has its own cost. A cheap model call saves little if its output requires repeated correction. Conversely, unnecessarily expensive processing can delay or inflate the cost of routine work. Selection should therefore connect to verifiable requirements and define a route for exceptions.
Compare with a simpler configuration
A useful evaluation compares routing with one carefully chosen fixed model configuration. Measure accepted outputs, rework and total operating costs, including the routing step itself. Model changes may require renewed assessment. Results should be separated by task type so that easy cases do not conceal failures on consequential ones. A token budget complements routing but cannot replace substantive quality checks.