CAD foundations · Lesson 7 · Approx. 7 minutes including practice
Reading orthographic views
Orthographic views describe the same part from different directions. Establish the projection convention before relating features between views. Use sections and details to understand hidden geometry rather than guessing from an isometric picture.
Step 1: Projection convention
A documentation workflow, not an equipment operating sequence. Animation starts only when you choose Play.
Relate views before reading features
An orthographic drawing represents the same object through aligned views. Begin with the stated projection convention and the view labels; do not assume the arrangement from a familiar template. Trace a simple visible feature across the views and ask which dimensions belong to it. An isometric view can help orientation but normally should not be scaled to derive manufacturing dimensions. Hidden lines, centre lines and section marks have different meanings and need to be read in context.
Prepare and check the work
Work systematically from the main view to adjacent and section views. Use the cutting-plane reference to locate a section and verify its viewing direction. A detail view enlarges a defined region and may have a different scale. Record any ambiguity in feature alignment or section identification as a review query. If a scanned source is distorted, do not compensate by guessing dimensions. The drawing’s approved values and notes govern, subject to clarification by the responsible authority.
Worked example · demonstration only
In a demonstration bracket drawing, a hole appears central in the isometric view but is offset in a dimensioned plan view. Use the dimensioned requirement to frame a query and verify the approved drawing. Do not move the hole in CAD merely to match the illustration’s appearance.
Guided practice and review evidence
Use only a demonstration dataset for this exercise: Identify one hole and trace it through three views on an approved sample drawing. 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: Do not scale a printed drawing to infer a manufacturing dimension. 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.