01
Record the frame before exporting
Identify the source file and version, the units used in the project and the relevant origin and axis directions. If the model has its own local frame inside a larger assembly, describe that relationship too. In the component example, a screenshot showing the origin and a short note about orientation may be more useful than a filename alone. Record the export settings that could affect interpretation. The goal is to make the assumptions available to the receiving person, not to prescribe one coordinate convention for every tool or every project.
02
Choose a small reference check
Before moving a complex scene, select a simple reference object or a few known points that the team can inspect in both environments. State what should be compared and where those reference values came from. The hypothetical team could use a clearly identified edge and orientation marker from its source model, then record how each appears after import. A mismatch becomes a question to investigate rather than a reason to adjust the model by eye. Keep the check modest and documented; it is a diagnostic aid, not a complete validation of every aspect of the exported geometry.
03
Keep conversion steps in the record
If the receiving tool requires a scale adjustment, axis conversion or other transformation, record that step alongside the imported file. Avoid silently editing an asset until it looks plausible, because a later transfer may repeat or undo the change. In the example, the team would retain the original export and describe the adjustment applied in the receiving scene. That makes a subsequent comparison easier to reproduce. The final handoff should separate source assumptions, transfer settings and receiving adjustments, giving the next person a concise explanation of how the displayed result was obtained.