1. Home
  2. Glossary
  3. Model evaluation
AI glossary · Models & training

Model evaluation

Model evaluation: Model evaluation is the process of measuring how well an AI model performs on a defined set of tasks, using test data, benchmarks, human ratings, or automated checks, to decide whether it is accurate and safe enough for a given use.

A model that seems impressive in a demo can fail badly on your actual work. Evaluation replaces impressions with measurement. You assemble a set of realistic inputs with known good answers, run the model on them, and score the results. For classification and extraction, scoring is mechanical: did it pick the right category, did it pull the right invoice total. For open-ended writing, teams use rubrics, human reviewers, or a second model acting as a judge.

Public benchmarks are one kind of evaluation. They are useful for comparing models in general, but they say little about your task. The evaluation that matters is the one built from your documents, your customers' questions, and your edge cases. It does not need to be big. Fifty to a hundred well-chosen examples, including the ugly ones, will tell you more than a leaderboard.

Evaluation is not a one-time gate. Models get updated, vendors swap the model under a product, and your data drifts. Keep your test set, rerun it when anything changes, and track the score over time. Teams that skip this discover a regression from an angry customer instead of from a dashboard.

Example at work

An insurance agency wants an AI assistant to draft policy summaries for clients. Before rollout, the office manager collects forty past policies along with the summaries their most experienced agent wrote. She runs the assistant on each, and two agents grade the drafts for accuracy and missing exclusions. Three types of coverage are consistently mishandled, so those get a rule in the prompt before anyone uses it with a client.

Why it matters

Evaluation is how you go from 'it seems to work' to knowing it works, and it is the strongest defense against quiet failures after a model update. Anyone deploying AI in a process others depend on should be able to say what was tested, on what, and when.

Related terms