# Model Card

A model card documents a specific model's intended uses, evaluation evidence, limitations, and operating conditions so others can assess whether to use it.

- Type: artifact
- Domain: Engineering & architecture
- Level: Intermediate
- Last reviewed: 2026-09-26
- Original: [Soroush’s Product Wiki](<https://wiki.soroush.uk/topic/model-card/>)

## What it means

A model card is a structured report accompanying a trained model and its version. It connects intended and unsuitable uses with training information, evaluation methods, performance across relevant groups and conditions, and known limitations. It describes the model as a reusable component; a system card may cover the wider application, including tools and safeguards. Neither document is a certification.

## Why it matters

Teams buying or adapting a model need evidence beyond a leaderboard score. A card helps expose mismatches between a supplier's tests and the proposed product, identify missing evaluation, and preserve assumptions when ownership changes.

## When to use it

Read or create a model card when selecting, releasing, adapting, or materially updating a model. Scale detail to the decisions readers must make. For a product composed of several models and tools, supplement the cards with evaluation of the assembled system.

## How it works

1. Identify the model version, owner, intended users, supported tasks, and deployment assumptions.
2. Describe training and evaluation data at an appropriate level, linking dataset documentation and recording unknowns.
3. Report evaluation methods, metrics, sample sizes, and results across relevant groups and operating conditions.
4. Record unsuitable uses, known failures, mitigation dependencies, and unresolved questions without presenting them as solved.
5. Review the card with product and technical owners, publish to the appropriate audience, and update it with model releases.

## A practical example

A support platform considers a sentiment classifier whose card reports tests only on English consumer reviews. The PM identifies a mismatch with multilingual business support tickets and requires local evaluation before using its scores to prioritize queues.

## Where it breaks

Cards are often self-reported, incomplete, or stale. Results depend on the test population and cannot establish performance in a new workflow. Some training details may be unavailable, and publishing a limitation does not control its consequences.

## Common mistakes

- Publishing only favorable aggregate scores without evaluation conditions.
- Treating a supplier's model card as approval for the entire product.
- Copying documentation across versions without checking changed behavior.
- Using intended-use statements to imply unsupported guarantees.

## Visualization

[View the visualization on the website](<https://wiki.soroush.uk/topic/model-card/#visualization-model-card>)

## Sources

1. [Model Cards for Model Reporting](<https://arxiv.org/abs/1810.03993>) — ACM Conference on Fairness, Accountability, and Transparency · Peer-reviewed research
2. [Model Cards](<https://huggingface.co/docs/hub/model-cards>) — Hugging Face · Official documentation

## Related topics

- [Model Evaluation](<https://wiki.soroush.uk/topic/model-evaluation/>)
- [Foundation Model](<https://wiki.soroush.uk/topic/foundation-model/>)
- [Dataset Card](<https://wiki.soroush.uk/topic/dataset-card/>)
