In Depth
Software you can inspect. A model you mostly have to describe. A model card fills that gap with the facts a downstream user needs to deploy responsibly: what the model is meant to do, the populations and conditions it was tested on, how well it performed, what it should not be used for, and the failure modes its builders already know about. The format traces back to a 2018 proposal for "model cards for model reporting," and it has since become a common convention across the industry.
The most important section is often the one teams skip: limitations and out-of-scope uses. A card that only lists impressive accuracy numbers is marketing. A useful card says where the model degrades, on which inputs, which populations, and which edge cases, because that's what a careful deployer needs to know before putting it in front of users. An honest limitations section is also a small liability shield. It documents that you disclosed a known boundary rather than letting a buyer assume it didn't exist.
Cards are now spreading from convention into expectation. Enterprise procurement teams increasingly ask for one as part of security review, and emerging AI regulation pushes toward documentation duties that a model card helps satisfy. The EU AI Act, for instance, attaches technical documentation and transparency obligations to higher-risk systems.
What It Looks Like
A vendor's intake agent runs on a fine-tuned model. Its card states the intended use (triaging routine patient questions), the data and populations it was evaluated on, measured accuracy, and a plain limitations section: not validated for pediatric cases, degrades on non-English input, must not be used for diagnosis. When a hospital's review team reads it, they don't have to guess at the boundaries. And if the agent is later misused for diagnosis, the card is evidence the vendor drew the line clearly.
Why It Matters For AI Vendors
A model card is one of the cheapest pieces of governance evidence to produce and one of the most frequently requested. It speeds enterprise review by answering questions before they're asked, it documents the disclosures that matter if a claim ever turns on "did the vendor warn us," and it forces the team to write down limitations they might otherwise leave fuzzy. For a model the vendor didn't train, the card is also where they record what they verified about a third-party system before building on it.