AUSTRALIAN MANAGEMENT. GLOBAL CAPABILITY.12-month work warranty →
CDXCAD & DOCUMENTATION EXPERTISE
Let’s talk ↗

HOME / ACADEMY

CDX Academy

← All 40 lessons

Quality and handover · Lesson 33 · Approx. 7 minutes including practice

Nonconformance records

A nonconformance record describes a departure, its disposition and the authorised decision. Distinguish correction from investigation into causes. Documentation staff record approved decisions rather than deciding technical acceptability.

Follow the information flow

Step 1: Requirement

A documentation workflow, not an equipment operating sequence. Animation starts only when you choose Play.

Record the departure and the authorised decision

A nonconformance record should describe the observed departure from an identified requirement, its location and the affected items. Use factual language and attach authorised evidence where useful. Separate the immediate containment or correction from investigation into causes and longer-term corrective action. A documentation preparer records the decisions; acceptance of a technical deviation must come from a person with the required authority.

Prepare and check the work

Give the record an identifier and track status, owner, disposition, approval and verification. Avoid wording that assumes blame or declares acceptability before review. Link any resulting drawing or procedure changes to the record. If a concession applies only to specified items, make that boundary visible. Close the record only when the agreed evidence and authorisations are present.

Worked example · demonstration only

A component differs from the released drawing, but a workshop note says it should be fine. Record the actual difference and refer it for authorised disposition. Do not treat the note as a formal acceptance or revise the drawing solely to hide the departure.

Guided practice and review evidence

Use only a demonstration dataset for this exercise: Create a blank NCR form with description, evidence, owner, disposition and closure fields. 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 accepted deviation requires the appropriate approval, not just a closed status. 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

  1. Establish the source: identify the approved input, document revision and person responsible for its technical content. Record missing information as an open question.
  2. Prepare a small representative example before applying the approach to a whole project. Check identifiers, units, references and the intended reader’s needs.
  3. 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?

Knowledge check

Answer all three correctly to record completion. You can review the lesson and retry.

1. Who determines technical acceptance of a deviation?
2. What should you do with missing or conflicting technical information?
3. What does this academy completion demonstrate?
Sign in to record completion

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.

LET’S MAKE YOUR NEXT PROJECT CLEARER

From your technical knowledge.
To a professional deliverable.

Request a quote