Document control · Lesson 3 · Approx. 7 minutes including practice
Document registers
A register is a control tool, not just a filename list. Track expected deliverables even before files exist. Use a clear status vocabulary so missing, draft, reviewed and issued records are distinguishable.
Step 1: Deliverable list
A documentation workflow, not an equipment operating sequence. Animation starts only when you choose Play.
Build a register around decisions
A useful register answers four questions: what is required, where is it, what state is it in and who needs to act next? Start from the contracted deliverables and include records that have not yet been produced. Use separate columns for document status and workflow action. For example, draft may be the status while waiting for supplier information is the next action. Mixing those concepts in one free-text field makes reporting unreliable and hides overdue decisions.
Prepare and check the work
Choose mandatory fields including identifier, title, revision, document type, responsible owner, required date, status and controlled location. Add review due date, applicability and issue reference if they support the project. Use a defined vocabulary, restrict duplicate identifiers and check dates for obvious errors. Give ownership to a named role rather than everyone. At each review, compare the register with the actual files and issue records; a green spreadsheet cell cannot prove that a document exists.
Worked example · demonstration only
The register lists an inspection report as complete but the folder contains an unsigned template. Change the record to an accurate state, identify the missing evidence and assign a follow-up. Do not manufacture signatures or mark completion based on a verbal expectation. The register should expose the gap so the responsible person can resolve it.
Guided practice and review evidence
Use only a demonstration dataset for this exercise: Build a register containing two missing, two draft and one approved document. 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 green cell is not evidence of approval; record the approver and approval reference. 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.