1. Home
  2. Glossary
  3. Model card
AI glossary · Safety, ethics & policy

Model card

Model card: A model card is a standardized document published alongside an AI model that describes what it was built to do, how it was trained and tested, where it performs well or poorly, and what its known risks and limitations are.

Think of a model card as the nutrition label or spec sheet for an AI model. The format was proposed in a 2019 research paper by Margaret Mitchell and colleagues as a way to make model makers state, in one place, the intended uses, the evaluation results broken out by group, and the situations where the model should not be used. Most major labs now publish something along these lines for each release, sometimes under the name 'system card' when it covers the whole product rather than the bare model.

A good card tells you the model's knowledge cutoff, its context window, the languages it handles, the benchmarks it was measured on, what safety testing was done, and which uses the vendor prohibits. It should also be honest about weaknesses: known biases, tasks it fails, and behaviors that changed from the previous version. Cards vary a lot in quality. Some are detailed technical reports; others are a marketing page with a table.

For buyers, the card is where due diligence starts. If a vendor cannot point you to documentation like this for the model under their product, that is itself useful information. Model cards are also becoming a compliance artifact, referenced by procurement checklists and by emerging AI regulation that asks providers to document their systems.

Example at work

A compliance officer reviewing a proposed AI contract-review tool asks the vendor which model powers it and pulls up that model's card. The card lists the knowledge cutoff, the safety evaluations run, and a note that the model is not intended for legal advice without human review. Those three facts go straight into the risk assessment and the usage policy.

Why it matters

A model card is the fastest way to learn what a model is and is not built for, straight from the people who built it. Reading one before adopting a tool takes twenty minutes and can save you from deploying the wrong model for a regulated or high-stakes task.

Related terms