Document control · Lesson 1 · Approx. 7 minutes including practice
Document numbers and naming
Define a stable identifier separate from the filename description. A number identifies the document; a revision identifies its approved state. Avoid encoding details that change often, such as the current project manager.
Step 1: Identifier reservation
A documentation workflow, not an equipment operating sequence. Animation starts only when you choose Play.
Separate identity from description
An identifier should survive a title correction, a change of owner and a move between folders. Decide whether the numbering sequence is project-based, product-based or organisation-wide before issuing numbers. Reserve numbers through one register so two people cannot allocate the same identifier independently. A descriptive filename helps a person browse, but the controlled number remains the key that links drawings, specifications, review comments and issue records. Avoid placing a revision inside the permanent identifier; keep it in a separate metadata field.
Prepare and check the work
Define the fields before making a naming rule. For a demonstration drawing, CDX-DEMO-001 identifies the record, A identifies its revision and Frame arrangement describes its title. A draft working filename may include a date, but that date does not prove approval. Test the scheme with drawings, manuals, attachments and supplier documents. If an external customer has its own numbering scheme, preserve both identifiers in mapped fields and agree which appears in the title block.
Worked example · demonstration only
Two departments submit CDX-DEMO-001 for different parts. Do not overwrite either file or guess which is correct. Preserve both working copies, quarantine the conflict in the register, ask the document controller to allocate a replacement number and record the mapping. Then check affected BOMs, links and transmittals before release.
Guided practice and review evidence
Use only a demonstration dataset for this exercise: Create a register for five drawings with number, title, revision, status, owner and location. 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: Two files have the same number but different titles. Escalate the collision before issue rather than silently renaming one. 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.