A clean handoff is not a folder full of files. It is a package that lets another person identify the editable source, reproduce the export and recognize a correct result without asking you to reconstruct the process from memory.
Separate sources from generated outputs
Label the Blender source, exported interchange files and engine-side configuration clearly. Record Blender, rig-generator and destination versions. Include required external textures and document any dependencies the recipient must obtain separately.
Keep license information with third-party assets and motion sources. Do not assume that possession of an exported file grants permission to redistribute its source content.
Include the movement and skeleton contract
State the intended skeleton, forward direction, scale convention and root-motion policy. Identify attachment bones and facial channels that gameplay expects. Note any known limitations with concrete examples rather than a vague “may need cleanup.”
Provide a short diagnostic action with a reach, crouch and locomotion segment. Include a reference capture showing the expected result.
Ask the recipient to reproduce one revision
Have a second person import the asset and repeat a harmless source change using your notes. Record where the instructions were insufficient and fix the package.
The best handoff evidence is a successful repeat by someone who did not build the original rig. It tests the documentation, file organization and export assumptions at the same time.
For the bigger picture, use our free Rigify migration workflow and three-engine import test plan.
Official references and scope
Sources checked October 18, 2026. Interface names and capabilities can change; use the documentation for your installed version. The workflow above is an editorial checklist, not a published hands-on benchmark.

