Professional practice · Lesson 40 · Approx. 7 minutes including practice
Confidentiality and technical sign-off
Use only authorised source material and agree access arrangements before sharing sensitive information. A documentation preparer is not automatically the responsible engineer. Record review decisions and keep the sign-off authority clear throughout the job.
Step 1: Purpose & NDA
A documentation workflow, not an equipment operating sequence. Animation starts only when you choose Play.
Keep confidentiality and approval boundaries visible
Confidential information includes more than drawings. Commercial terms, supplier details, source data and product configurations may also need protection. Confirm the purpose, authorised recipients and permitted systems before sharing. An NDA sets obligations but does not replace operational controls. Offshore access, subcontractors and hosting arrangements need to be addressed explicitly where relevant. Do not put client information into public AI services or public demonstration material.
Prepare and check the work
Separate preparation, checking and approval roles in the engagement. A technically experienced preparer does not automatically hold statutory or contractual sign-off authority for the job. Record the nominated reviewer, applicable scope and evidence needed for approval. If a requirement is missing, raise it as a question rather than inventing it. Use approved sharing methods, retain a controlled issue record and follow agreed return or deletion requirements at close-out.
Worked example · demonstration only
A customer asks the documentation team to sign a declaration that the equipment complies with every applicable requirement. Check the engagement scope and refer certification to the responsible authorised person. CDX can assemble the supporting records and comment-closure evidence without claiming a sign-off it cannot provide.
Guided practice and review evidence
Use only a demonstration dataset for this exercise: Prepare a responsibility matrix for client, preparer, reviewer and approver. 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: Do not upload client drawings to public AI services or claim approval without evidence. 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.