CAD foundations · Lesson 16 · Approx. 7 minutes including practice
Native and neutral CAD files
Native files preserve software-specific structure; neutral files support interchange but may lose features or metadata. Confirm receiving software and version. Verify exported units, geometry and assembly structure after translation.
Step 1: Receiving need
A documentation workflow, not an equipment operating sequence. Animation starts only when you choose Play.
Know what an export preserves
A native CAD file may include features, assembly relationships and software-specific metadata. An interchange file may preserve only some of that information. Agree the receiving software, version, required file types and intended use before export. A neutral file opening successfully is only the first check. Units, geometry, body count, orientation and product structure can still differ from the native model. Do not promise full editability merely because a format is commonly used.
Prepare and check the work
Create a small transfer test before exporting a large package. Open the output in the receiving workflow, compare a known dimension and verify the expected components. Check external references and missing fonts or textures if those matter to the agreed deliverable. Record export settings and the source revision. Deliver a manifest describing which file serves which purpose and what limitations were observed during validation.
Worked example · demonstration only
A recipient sees a model at the wrong scale after import. Check the source and target unit interpretation using a known approved dimension. Correct the transfer settings and repeat the validation; do not scale the geometry blindly and call it equivalent.
Guided practice and review evidence
Use only a demonstration dataset for this exercise: Write a delivery matrix listing native, STEP, DXF and PDF outputs with their purpose. Before starting, write down the question the finished record should answer and identify the source information you would need on a real job. Keep a separate list of missing inputs. Prepare a first draft, then compare it with the topic-specific checks above. Ask another person to follow your references without explaining them verbally. Record where they hesitate, what information they cannot locate and any different interpretation. Keep a brief review log with four columns: observation, proposed action, responsible reviewer and closure evidence. Revise the example and repeat the information-finding check. Your evidence of completion is the revised demonstration record plus that log, not simply time spent reading. Do not upload client information to the academy or practise on operating equipment.
What good completion looks like
A useful result can be understood by someone who did not prepare it. They can identify its purpose, applicable item, source and review status, and they can distinguish confirmed information from unresolved questions. Pay particular attention to this failure mode: An export that opens successfully can still omit reference information. Check the output in the format the recipient will use. A native file, spreadsheet and exported PDF can expose different problems. Keep the source revision and the issued output linked, and record any limitations of the handover. On a real project, follow the customer's authorised checking and approval arrangements before the information is used. The knowledge check below tests understanding of this lesson; it does not assess practical competence or authorise regulated work.
Practical workflow
- Establish the source: identify the approved input, document revision and person responsible for its technical content. Record missing information as an open question.
- Prepare a small representative example before applying the approach to a whole project. Check identifiers, units, references and the intended reader’s needs.
- Ask the nominated reviewer to check technical meaning. Capture the response, resolve comments and issue only under the agreed document-control process.
Review checklist
- Can another reader identify the source and applicable revision?
- Are assumptions and unresolved decisions clearly recorded?
- Is there evidence of the required review before issue?
Educational material and demonstration examples. Not accredited training, practical competency assessment or authority to perform regulated work. Use current approved sources and your responsible technical authority on real projects.