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 30 · Approx. 7 minutes including practice

Manufacturing data records

An MDR compiles required evidence against an agreed index. It may include approved drawings, inspection records, certificates and test reports. Compilation cannot replace missing inspections or create proof of work that was not performed.

Follow the information flow

Step 1: Agreed index

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

CDX demonstration documentation sample
Demonstration sample: inspect the information structure and identification cues. Not a real client project or an instruction for equipment use.

Compile evidence without creating it

An MDR is an organised evidence package matched to an agreed index. Its contents depend on the contract and product, and may include approved drawings, material records, inspection evidence and test reports. A compiler checks completeness, identity and traceability. Compilation does not certify the product or replace a missing inspection. Keep planned requirements separate from the evidence actually received and from open exceptions.

Prepare and check the work

Start with the approved index and define each required record’s source and owner. Check legibility, signatures where required, dates, equipment identifiers and revision references. Link certificates to the relevant item through supplied traceability evidence. Use an exception register for missing or inconsistent records. Do not rename a document to imply a qualification or approval that its contents do not provide.

Worked example · demonstration only

The index requires a final inspection record, but only an unsigned form is supplied. List the requirement as outstanding and ask the responsible inspector for the actual record. Filling in a result from assumption would undermine the entire evidence package.

Guided practice and review evidence

Use only a demonstration dataset for this exercise: Create an MDR index with record owner and completeness status. 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: Keep a missing certificate as an open item; never fabricate a replacement record. 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. What should an MDR compiler do with missing inspection evidence?
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