Document control · Lesson 4 · Approx. 7 minutes including practice
Transmittals and issue records
A transmittal records exactly what was issued, to whom and for what purpose. Include document numbers, revisions and the requested response. Preserve the package as issued rather than rebuilding it later from working folders.
Step 1: Check recipients
A documentation workflow, not an equipment operating sequence. Animation starts only when you choose Play.
Record the issue as an event
A transmittal is evidence of an issue event. It identifies the recipient, date, purpose and exact files sent, rather than simply linking to a folder that may later change. Distinguish issue for review, issue for information and authorised final issue using the agreed terminology. State what response is expected and by when. The sender should be able to reconstruct the package from its issue record without relying on memory or on the current contents of a working directory.
Prepare and check the work
Prepare a manifest with document numbers, revisions, titles and filenames. Verify the recipient list against the authorised distribution list and confirm whether the material is confidential. Package the specific files, check links and record the issue reference in the register. If a file is missing, correct the package before issue. If a mistake is discovered afterwards, send a controlled correction that clearly supersedes the affected item; do not edit the historical transmittal to conceal the error.
Worked example · demonstration only
A reviewer says the wrong drawing revision was received. Compare the archived manifest and package against the review request. Record the mismatch, withdraw the unsuitable issue where appropriate and issue a replacement with a clear reference to the earlier package. Retain both events so the sequence remains understandable.
Guided practice and review evidence
Use only a demonstration dataset for this exercise: Prepare a sample transmittal for a review package of three drawings. 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 review issue must not be labelled approved for manufacture. 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.