CAD foundations · Lesson 8 · Approx. 7 minutes including practice
Dimensions and units
A dimension expresses a required value with a defined unit and context. Check the drawing’s unit convention and avoid duplicate dimensions that may conflict. Functional requirements must come from the design authority.
Step 1: Source value
A documentation workflow, not an equipment operating sequence. Animation starts only when you choose Play.
Keep values, units and references together
A dimension is meaningful only with its unit, reference and applicable tolerance. Check the drawing’s general unit note and any local exception. Different source documents may use different conventions; copying a number without its unit is a common route to a large error. Distinguish nominal dimensions from reference dimensions and from actual measurements. The documentation preparer should communicate approved requirements, not infer a functional requirement from a rough model or a photograph.
Prepare and check the work
Choose dimension placement that allows the reader to identify the feature without tracing across unrelated geometry. Avoid repeating a controlling dimension in multiple places unless the project convention defines how duplicates are managed. When units change, verify both the numerical conversion and the precision appropriate to the approved source. Do not create false accuracy by adding decimal places. Check the native drawing and exported PDF together, including truncated values and displaced extension lines.
Worked example · demonstration only
A supplier sketch states 2.5 but does not identify the unit. Mark the value as unresolved and request confirmation. Adding mm because the rest of the project uses millimetres would turn an unknown into an apparently authoritative requirement. Record the response before updating the controlled drawing.
Guided practice and review evidence
Use only a demonstration dataset for this exercise: Review a sample for missing units, duplicate dimensions and unclear references. 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: A conversion between inches and millimetres requires controlled precision and review. 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.