1. Inspect every renderer, not only the root
MeshRenderer and SkinnedMeshRenderer components can live deep in nested prefab hierarchies. A visual glance at the root object is not enough when submeshes or child objects have separate material arrays.
Unity QA guide
Find missing prefab material slots before a Unity asset reaches production.
A prefab can look correct in one scene and still contain an empty material slot that appears later in a variant, spawned object or buyer project. Missing material references are cheap to catch before handoff and expensive to explain after release.
2. Distinguish empty slots from intentional placeholders
Some workflows deliberately leave a slot for runtime assignment. Document those cases so an automated QA report does not turn a valid design decision into accidental cleanup.
3. Check variants after the base prefab
Variants can override material arrays independently from their base. Review both the source prefab and the variations that actually ship or enter scenes.
4. Test after moving the asset
Broken material links often reveal themselves after a package export, folder move or handoff. Reopen the prefab in the destination project and verify that all referenced materials still resolve.
5. Keep a repeatable report
When many assets are involved, record the prefab path and renderer with the missing slot. A repeatable QA pass is faster than rediscovering the same problem during release preparation.
Scan prefab material slots in one pass
The free Unity Asset Preflight Auditor reports prefab renderers with missing material slots and exports the findings to CSV. It does not automatically edit the prefab.