Model routing decision table for product teams

A model routing decision table turns scattered preferences into a reviewable product decision. It helps a team decide when to use a fast inexpensive model, when to use a stronger model, and when a human review step is still required.

## Start with task risk
Low-risk classification, formatting, and extraction can often use cheaper models. Tasks that affect user trust, billing, public content, or safety need stronger checks and usually a stronger model.

## Track cost and latency together
A slow model can be unacceptable even if it is accurate. A cheap model can be expensive if it causes retries or manual correction. The table should include both direct cost and review cost.

## Add fallback behavior
Each route should say what happens when the model fails, times out, or returns an invalid structure. A missing fallback is where routing complexity usually becomes a product bug.

## Keep examples attached
Store two or three real examples for each route. Without examples, the table becomes opinion. With examples, the team can rerun comparisons when models change.

Model routing decision table for product teams

// COMMENTS

ON THIS PAGE