> For the complete documentation index, see [llms.txt](https://docs.zephyrintel.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.zephyrintel.com/documents/model-manuals/what-a-model-manual-is-and-how-assets-inherit-it.md).

# What a model manual is and how assets inherit it

A model manual is a document uploaded once for a brand and model. Signal shows it on every asset that matches that brand and model, without you attaching it yourself.

### How matching works

Signal compares the brand and model code you set on the manual against each asset's own brand and model code.

| Field      | How it matches                                                                                     |
| ---------- | -------------------------------------------------------------------------------------------------- |
| Brand      | Partial match. The asset's brand only needs to contain the manual's brand text.                    |
| Model code | Exact match. The asset's model code must match the manual's model code, ignoring case and spacing. |

An asset needs both a brand and a model code recorded for a model manual to reach it.

### Where you see it in Signal

A matching manual appears on an asset's Documents tab alongside documents uploaded directly to that asset. There is nothing to configure on the asset itself. It inherits the manual automatically once its brand and model code match.

### Notes

If an asset's brand or model code is missing or misspelled, it will not match a model manual even if the manual is correct. Check the asset's Technical tab if a manual you expect to see is missing.
