Quality and handover · Lesson 31 · Approx. 7 minutes including practice
Inspection and test plans
An ITP identifies agreed inspections, responsibilities and required records. Hold and witness points have contractual significance and must be agreed by the responsible parties. Documentation support can format and control the plan from approved inputs.
Step 1: Contract requirement
A documentation workflow, not an equipment operating sequence. Animation starts only when you choose Play.
Separate requirements, responsibilities and records
An ITP describes planned inspection and test activities, their acceptance references, responsible parties and required evidence. Hold and witness points must reflect the agreement between the relevant parties. Documentation staff may prepare the structure and populate approved information, but they do not create inspection authority by adding a signature box. Keep the plan distinct from completed results so an empty form cannot be mistaken for proof of inspection.
Prepare and check the work
For each activity, identify the stage, applicable requirement, responsible role, notification arrangements and resulting record. Confirm the meaning of each point type with the contract owner. Check the sequence against the actual manufacturing process and escalate activities placed after they would become inaccessible. Changes to requirements or release points need authorised review, not an informal spreadsheet edit.
Worked example · demonstration only
A hold point is discovered after the relevant assembly has been closed. Record the issue and refer it to the responsible parties for disposition. Do not retrospectively mark the point as witnessed or assume later photographs are equivalent evidence.
Guided practice and review evidence
Use only a demonstration dataset for this exercise: Identify the owner, evidence and approval fields on a supplied ITP. 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 remove a hold point to resolve a schedule conflict. 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.