How to hand over CAD for a product film: files, revisions and acceptance

Short answer. A digital product film needs more than a model archive. The receiving team needs to identify the marketed configuration, open its related files, check control dimensions and establish which scenes the data supports. Transfer a representative sample first, record the findings and then agree the full package. Give later model changes a revision identifier and a list of affected scenes.

This handbook helps a marketing coordinator assemble that package with an engineer. The practical outputs are a completed source index, questions for the product owner and a readiness decision for each scene. The 3D packshot service describes the broader production format. This article focuses on the handover of engineering information.

1. Define what is being transferred

CAD contains engineering information about an object's form and construction. For a video project, distinguish that information from a prepared visual asset. A model can be appropriate for its engineering purpose while leaving unanswered questions about shot size, visible configuration or whether internal components may be shown.

State the purpose of the transfer before selecting an export. Assessing an exterior orbit and preparing an exploded assembly view require different checks. Even when both use the same source file, the evidence needed to call it sufficient will differ.

Define the product boundary as well. An engineering assembly may contain production components, experimental parts and optional accessories. Advertising depicts a selected configuration. If the delivered product differs from the complete assembly, describe the difference and mark it on a reference view.

A useful statement might be: assess the package for three scenes of product A, body revision C; show the production exterior without manufacturing fixtures; internal construction is outside the current scope. The receiving team can investigate that statement without guessing the intended campaign.

2. Assign four decision roles

The coordinator assembles the package and consolidates comments. An engineer confirms configuration, dimensions and component function. A product owner authorises the selected version for customer-facing use. The brand team approves visible graphics and wording.

One person may hold several roles in a small company. The decisions should still remain identifiable. Marketing approval of a composition is not automatically engineering approval of a mechanism.

Record a contact and an alternative for each role. If an engineer is unavailable, the creative discussion can continue where it does not depend on the unanswered technical point. Mark which question blocks which scene rather than treating every missing answer as a project-wide stop.

One coordinator returns the agreed response to the production team. Preserve the basis of engineering comments: a drawing identifier, revision or approved diagram. Consolidation should make decisions clearer without removing the evidence behind them.

3. Transfer scenario A: exterior presentation

The first scenario shows a closed product: body, front panel and selected recognisable details. Consider a hypothetical desktop measuring instrument. The planned shots are a front view, an orbit and a connector close-up. All examples in this guide are illustrative planning scenarios.

The complete internal assembly may be unnecessary, but removing components without agreement creates another uncertainty. The engineer identifies what must remain visible; the production team identifies the areas reached by the proposed camera. Together they define the package required for those views.

The index includes the body, panel, connector, control dimensions and reference views. Panel wording has a separate source. If the display shows an interface, provide approved interface artwork or agree that it will not be readable in this shot. An interface image embedded in an engineering file may not be the campaign's current approved version.

Readiness means the visible parts of the selected configuration are available, control dimensions are confirmed and mandatory views do not expose unknown areas. If the orbit reveals an unconfirmed rear panel, obtain the missing information or restrict the camera movement. That is a concrete scene decision.

4. Transfer scenario B: assembly, cutaway and movement

The second scenario explains how a product opens or is constructed. Exterior resemblance is insufficient. The receiving team needs component names, starting positions, the meaning of movement and a person who can confirm the explanation.

For a hypothetical filter unit, the scenes include opening a cover and separating a replaceable element. The engineer identifies the opening direction, relevant axis, permitted position and membership of the assembly. If separation is an explanatory presentation, record that it is not intended to depict a service disassembly sequence.

Make simplifications specific. Small fasteners might be omitted from a wide exploded view while the filter seat remains visible. An instruction to remove unnecessary details is too broad: participants may disagree about which details explain the product.

Review the internal configuration separately before discussing final lighting. A clear draft view with labelled components allows the buyer to check their relationships. This catches a misplaced part before attention moves to the finished image.

If internal information cannot be provided, a diagram of the operating principle may be an alternative. That changes the representation and the claims it supports. Agree the change before producing the final scene.

5. Transfer scenario C: incomplete or mixed sources

The third scenario combines an older model, photographs of the current item and selected updated drawings. Work may still be possible, but the package needs a map of what is known. Identify confirmed shape, documented changes and areas that would otherwise require an assumption.

Suppose the old instrument model has a previous handle while a new drawing describes the revised front panel. Record that the body comes from revision B, the panel is updated using document C and the handle still needs confirmation. Calling the whole package revision C would conceal its mixed status.

Connect each uncertainty to a scene. An unconfirmed handle may not prevent a front-panel close-up, but it may prevent approval of the full orbit. This allows independent work to proceed without implying that every source is ready.

A sample transfer is especially useful here. The receiver inspects one relevant component and reports what can be read, what needs preparation and what remains a question for the engineer. A fuller assessment follows that evidence rather than relying on the existence of a large archive.

6. A completed file index

The following example describes the exterior instrument film. Filenames are illustrative; their connection to decisions is what matters.

product_A_revC. Purpose: Source assembly of the selected product. Status: Current exterior. Confirmation owner: Engineer.

export_A_revC. Purpose: Sample for opening and inspection. Status: Import review pending. Confirmation owner: Receiver and engineer.

dimensions_revC.pdf. Purpose: Body and panel control dimensions. Status: Approved. Confirmation owner: Engineer.

front_side_back.pdf. Purpose: Views identifying mandatory details. Status: Approved. Confirmation owner: Product owner.

panel_text_EN_v04. Purpose: Visible panel wording. Status: Approved for English. Confirmation owner: Brand team.

differences_B_to_C.md. Purpose: Changes from the older model. Status: Confirmed. Confirmation owner: Engineer.

scene_requirements.xlsx. Purpose: Scene-to-source dependencies. Status: In review. Confirmation owner: Coordinator.

open_questions.md. Purpose: Uncertainties, dates and owners. Status: Open. Confirmation owner: Coordinator.

Add the transfer date and exact location to each row where useful. If the export is undecided, state the available source format and ask which sample the receiver needs. Several guessed conversions can make discrepancies harder to diagnose.

Check that the index points to supplied materials rather than inaccessible internal drives. If something will arrive later, record its expected date. A filename in a list should not create the impression that an absent file has already been delivered.

The index should also make obsolete reference material recognisable. Keeping an older drawing can help explain a change, provided its purpose is explicit. Place it in a clearly labelled reference section rather than alongside current files with an equally authoritative name.

7. Map each scene to its evidence

A scene dependency map turns a general source list into a practical assignment. It explains why a missing document matters.

S01, front view. Audience purpose: Recognise the instrument model. Required information: Body, panel and designation. Start condition: Configuration agrees.

S02, orbit. Audience purpose: Understand form and overall size. Required information: Confirmed visible sides. Start condition: No unresolved rear area.

S03, connector. Audience purpose: Understand connection location. Required information: Component geometry and reference. Start condition: Engineer confirms component.

S04, opening. Audience purpose: Understand access to the block. Required information: Assembly parts and movement. Start condition: Operating principle approved.

The project does not need to contain all these scenes. The map connects promised content to available information. If S04 is excluded, its mechanism data should not automatically become a requirement for starting S01.

Add shot size and prohibited assumptions. Examples include preserving exact model wording or avoiding presentation of a service-only mode as a user function. Such instructions make accuracy review more useful than a general demand for maximum realism.

Where a scene is optional, mark that status. The estimate can then show what changes if it is removed or added. Otherwise, a speculative idea in a reference document can quietly become an expected deliverable.

8. Check scale using named dimensions

A millimetres label in an interface does not complete a handover check. Autodesk's official documentation distinguishes display units from the scene's underlying system unit: changing displayed measurements does not change the object. This supports checking dimensions after opening rather than relying only on a setting label. Autodesk, Using Units, 2025 documentation, checked 27 September 2026.

A practical check is independent of software choice. The engineer selects a control measurement and identifies its endpoints. The receiver reports the value after import. If values disagree, check that both parties measured the same points, used the same revision and interpreted the units correctly.

Provide several distances on different parts of the object. For example, identify body width excluding the protruding connector, height including feet and spacing between mounting points. The descriptions remove ambiguity that a single number labelled width cannot resolve.

Do not silently scale the model to match one measurement. If the overall dimension then agrees but component spacing does not, the issue may concern configuration or revision. Record the discrepancy before deciding how to correct it.

9. Ask engineers questions they can resolve

A useful question contains an object, a source and an observed difference. Instead of asking which model is right, say that revision B places the handle on the right while the confirmed product photograph shows it on the left, then ask which position S02 should use.

For configuration, ask which accessories belong to the marketed package and which must not appear installed together. For movement, ask what moves relative to what, which positions are permitted and whether the animation shows an operating action or an explanatory arrangement.

For an unseen area, ask whether the camera may expose it. For marking, request the current approved artwork. For an older file, ask which components remain valid. Identify prospective parts so a campaign does not unintentionally depict an unapproved configuration.

The answer should lead to an action: use, replace, exclude or wait for data. If a decision is made verbally, the coordinator records it for confirmation. Otherwise, participants may later remember different versions of the same discussion.

10. Run a representative sample transfer

Select a small sample that exposes the main risk: a difficult joint, a distinctive contour or a moving assembly. Include a reference view, control measurement and expected outcome. Testing only the simplest component may say little about the actual task.

The receiver checks opening, visible part membership, orientation and control dimensions. Return clear images and an observation list. Advertising lighting is unnecessary at this stage; the purpose is to establish that both parties are examining the same product.

Use the result to agree the full-transfer format and preparation requirements. If another export is needed, record the reason. Keep a note of the tested variant and what changed in the replacement so the cause remains traceable.

The sample should end with a decision more useful than file opened successfully. For example: exterior scenes can proceed; the opening sequence requires separate components; panel text will be supplied as independent artwork. That statement connects technical inspection to production.

11. Manage revisions after approval

Give every delivery an identifier. State the previous version, reason for the update and changed components. Retain the older package as the basis of earlier approvals rather than silently overwriting it.

A change record needs four practical fields: what changed, why, which scenes are affected and who confirmed the decision. A changed invisible component may have limited impact. A revised panel in a close-up needs a renewed check of every scene showing that panel.

The production team identifies consequences before the buyer approves the revised work. A new revision does not necessarily cancel every previous decision, but it should not be assumed harmless either. The scene map makes both assumptions testable.

When preparing different languages, track geometry revision separately from wording version. Replacing an English panel graphic should not be mistaken for a new body model, and a genuine geometry update should not hide inside an artwork delivery.

12. Accept the source package explicitly

Source-package acceptance asks whether the agreed actions can be carried out with the received information. It precedes approval of the finished visual treatment.

Assign each scene a practical status: ready for the next stage, ready under listed conditions, or waiting for a specific answer. Conditions must be observable. Improve the model slightly is vague; replace the handle using document C before S02 identifies the work.

Record the package identifier, reviewed scenes, unresolved elements, owners and next stage. The engineer confirms product information. The coordinator confirms the agreement is complete. The receiver identifies remaining preparation.

If approval restricts the camera, include that restriction in the scene. A later request for a new angle returns to the data map. This prevents limited approval from being treated as permission to expose every part of the object.

13. Frequent handover errors and useful remedies

The archive is called final but its revision is unknown. Request the source owner, date and matching configurations. Mark the state unconfirmed until resolved.

Dimensions agree only after manual adjustment. Preserve the original import findings and check endpoints and units. Visual fitting does not establish why the mismatch occurred.

Every accessory appears in one assembly. Identify the marketed package and mark exclusions on a reference view. The scene should not leave the supplied configuration ambiguous.

A new panel arrives without a change note. Compare it with the accepted revision and log affected scenes. Reapprove the changed requirements specifically.

An engineering graphic contains obsolete text. Assign a separate authoritative marking source rather than reconstructing wording from memory.

Successful opening is treated as complete readiness. Return to the scene map: is there enough evidence for the movement, interior and close-up? Readiness depends on intended use.

14. Write a short transfer completion record

A completion note can be stored beside the index. For example: package A-C-02 accepted for S01–S03; body confirmed against drawing C; panel uses EN-v04; rear area remains unconfirmed and excluded from S02; next stage is preparation of control views; connector answer required before S03.

This exposes both authorised work and a specific dependency. The note does not need to reproduce every message. When an issue closes, update its decision and date while retaining the original observation. Future reviewers can understand why a view was restricted.

For a long project, include a marked image of the configuration. It does not replace the model but helps a new coordinator recognise a different product variant. This is often more practical than expecting someone to infer the configuration from dozens of filenames.

Resolve internal buyer disagreements before presenting them as instructions. If engineering and marketing propose different configurations, decide which is appropriate for the campaign. Sending contradictory answers as equally valid instructions transfers a business decision to the supplier.

End the record with a next action and owner: re-export a component, confirm a view or prepare a visual test. Acknowledged does not tell the team whether production can continue.

15. Submit a package that supports an assessment

Collect the index, scene map, control dimensions, configuration list and open questions. Identify the sample available for a trial transfer. If the package is incomplete, describe the available sources accurately.

For a CGI product film, request a scene-by-scene conclusion: usable information, required preparation and decisions needed from your team. See the pricing page for the current commercial context.

Attach the package to the project brief. The first discussion can then address actual information gaps, transfer choices and accuracy boundaries. The creative work has a clear foundation: everyone knows which product is being shown and which evidence supports that representation.

Related planning guides

CGI product variants: plan colours, labels and SKU changes. How to scope a family of product videos around controlled assets, distinguishing colour changes from geometry, artwork and scene changes.

AI, CGI and 3D: choosing the production method