Chapter 04 / Handoff and evaluation
Package the animation handoff
A delivery is complete when the receiving team can understand, import, test and maintain the work without reconstructing its assumptions.
Deliver a reproducible result
A reel shows selected moments under selected conditions. A production package explains what the data is, what it depends on and how it behaves when used as intended.
Agree on the package early. The final week is a poor time to discover that the receiver expected source scenes, a different skeleton, or playable evidence rather than standalone exports.
Define acceptance before the batch
Separate artistic approval from technical acceptance. A performance can be approved while its export still has an incorrect root orientation. Conversely, a technically valid file may fail the character brief. Give each type of review a named owner and a clear way to record status.
Use a representative first delivery to prove the process. Include a loop, a directional action and a contact-heavy move. These reveal different failure modes and help both teams refine expectations before the full asset count becomes expensive to revise.
Create a manifest that answers real questions
List each clip with its purpose, version, duration, sample rate, skeleton dependency and root-motion policy. Include intended loop behavior and any required event or curve definitions. Distinguish a genuine zero-length omission from an intentionally absent feature.
A CSV or plain-text manifest is often sufficient. The value comes from consistency, not the file format. Keep names stable enough for automated processing and avoid relying on folder position or a reviewer’s memory to identify the approved revision.
Preserve the export contract
Write down the authoring application and relevant version, exporter settings, units, axis conventions and frame range. State whether the range includes a reference pose or only the playable motion. Clarify how scale is handled and whether animation is baked onto the delivery skeleton.
If the receiver uses Unreal Engine or Unity, include the import settings that were actually tested. A generic recommendation is less useful than a small verified example. Autodesk FBX exports, glTF 2.0 assets and native project files have different capabilities and dependencies; name exactly what is provided rather than calling everything “the animation files.”
Package source without creating a dependency puzzle
When source delivery is agreed, include the scenes and supporting files needed to reopen the work. Identify external references, custom tools, plugins and licenses. Do not assume a recipient has the same local drive paths or internal scripts. Where a dependency cannot be distributed, explain the limitation before approval.
Keep source, exports and review captures distinguishable. A simple folder structure with a readme is better than a complex hierarchy nobody follows. Version-control systems such as Perforce Helix Core or Git with Git LFS can support production, but the handoff should remain understandable outside one person’s workspace.

A practical package
Keep the evidence next to the data
- Readme and asset manifest
- Agreed source and runtime exports
- Skeleton and dependency versions
- Import recipe and representative test scene
- Review capture, change log and known issues
Validate what can be checked automatically
Automated checks can flag missing files, unexpected skeleton names, empty tracks, invalid ranges and inconsistent naming. They are especially useful for preventing familiar errors from returning in large batches. Run them before delivery and again after import where practical.
Automation cannot fully judge weight, intention or the quality of an interrupted transition. Pair machine checks with a short human review in the target context. Keep the test representative: a loop in an isolated viewer is not evidence that the same motion behaves correctly when layered, compressed and driven by a controller.
Review compression and platform behavior
Compression settings can alter small contacts or introduce visible drift. Inspect hands on props, feet on the ground and any close-up facial work after runtime processing. A high-quality source is necessary, but it is not the final artifact the player sees.
Check a build representative of the target hardware and character load. Record the build identifier and test conditions so comparisons remain meaningful. When a problem appears only under particular conditions, provide those conditions rather than treating the exported clip as the only possible cause.
Close the loop with actionable feedback
A useful issue report names the asset version, reproduction steps, expected behavior and observed result. Attach a capture with enough context to show the input and state. Distinguish blocking failures from polish requests so the team can prioritize without silently changing the agreed scope.
Finish with an explicit acceptance record and a list of remaining issues, each with an owner. Preserve the approved package rather than overwriting it with an untracked revision. Good delivery is a continuation of the animation craft: it protects the performance as other people integrate, evaluate and eventually maintain it.