Inspection and Test Plan: Define Notice, Waiver and Release

An inspection and test plan (ITP) controls work only when every intervention point has an operating rule. Before the activity starts, define what triggers notice, who receives it, when the item becomes ready, whether attendance can be waived, who may accept the evidence, what authorizes work to continue, and how an exception is escalated. The H/W/R/S letters are not enough because their meanings and contractual effects can vary. Use the project’s own definitions; treat examples from standards bodies and government contracts as references rather than imported obligations. The practical next step is to test one planned ITP event from notice through release before the first irreversible operation.

Start With the Intervention Rule, Not the Letter Code

An ITP row usually names an activity, requirement, inspection or test method, frequency, responsible parties, intervention code and record. Those fields describe what should happen. They do not necessarily define the transaction among the supplier, buyer, inspector, designer and release authority.

ISO 10005:2018 provides guidance for establishing, reviewing, accepting, applying and revising quality plans for a defined output. ISO also states that the document gives guidance rather than requirements. The contract, specification, approved quality documents and agreed clarifications therefore have to establish the project obligation.

Create an ITP Intervention Rule Sheet before approving the first activity plan. This is an East Baoyu editorial framework, not an industry-standard form.

Use role titles or contract functions, not only individual names. People can change; the authority attached to the role must remain clear. Where one person performs several functions, retain the separate decisions so a signature does not silently mean notice received, inspection passed and work released at the same time.

Map Each ITP Row to One Decision Event

Start from the actual work sequence. Give each control point a defined entry state and exit state. “Inspect welding” is not an event. “Verify the identified production-weld population after visual acceptance and before coating, then record the result and release status” is closer to an executable event, but its exact criteria, method, population and authority still have to come from the project documents.

Build the row around this chain:

released requirement → bounded work scope → readiness prerequisites → inspection or test → result → disposition → authority to proceed → retained record

Do not let the ITP become the master source for requirements that belong in an approved drawing, specification, procedure or acceptance standard. Reference the controlled source and revision. If a requirement changes, the ITP should point to the new baseline rather than preserve a conflicting copy.

Define the inspection population. A frequency such as “sample,” “first item” or “10%” is incomplete unless the population, selection method, rounding rule, distribution, escalation after failure and effective lot are known. The person performing the work should not have to invent these rules at the inspection point.

The activity schedule in IAEA TECDOC 1910 is a useful scoped example: it separates activity description, reference, verifying documents, verification code, parties, responsible person and acceptance signature. That document concerns quality assurance in nuclear facilities and activities. Its format demonstrates traceable event logic; it is not a ready-made ITP for an unrelated project.

Make Notice a Controlled Record

A calendar invitation or short email may alert an inspector, but it is not automatically adequate notice. The project protocol should state the minimum content and the system of record. A usable notice normally identifies:

• the ITP, revision, row and intervention code;
• the exact item, lot, location or work package;
• the planned date, time and time zone;
• site access, remote link or inspection location;
• the readiness prerequisites and their status;
• documents and records available for advance review;
• the sender, recipients and required response time;
• whether the notice is original, revised, postponed or cancelled.

Do not issue readiness notice merely to preserve the schedule. If prerequisites are incomplete, state the gap and forecast; otherwise the inspector may mobilize for an event that cannot produce a valid result. Define who can declare readiness and who can withdraw it.

In the IAEA example, progression beyond a witness point is linked to formal notification under an agreed notification-of-readiness period. The NSW Government Quality Management Guidelines contain a different, contract-specific construction model with stated notice periods and Hold/Witness effects. These sources support one general lesson: the notice rule must be agreed. They do not establish a universal number of hours for another contract.

If the public page cannot render the diagram, follow the same text sequence: readiness, notice, response, intervention or valid waiver, result, release and bounded progression. Every negative branch returns to a recorded correction or escalation path.

Separate Attendance, Waiver, Acceptance and Release

These states answer different questions:

• Attendance records whether the nominated party participated.
• Waiver records that a party gave up an opportunity to attend under an authorized rule.
• Acceptance records a decision about conformity against the stated basis.
• Release records permission to progress beyond a control point.

A party can attend and still reject the result. A buyer can waive attendance while the supplier’s own inspection remains mandatory. A test can pass while work remains held for a missing record or another authority. A review comment can close without authorizing production. The ITP protocol should prevent one status from being inferred from another.

IAEA TECDOC 1910 distinguishes first-, second- and third-party verification and gives scoped definitions for hold and witness points. Within that example, a hold point restricts progression pending the applicable purchaser intervention, while a witness point can allow progression after the agreed notice condition. The NSW construction model likewise distinguishes Hold and Witness effects and states that principal endorsement does not release the contractor from its obligation to meet the contract. Confirm which, if any, of these effects the actual project adopts.

Avoid verbal waiver for a consequential event. If an urgent verbal decision is permitted, define who may give it, what contemporaneous evidence is required and when the controlled record must follow. Silence is a waiver only if the contract or approved protocol explicitly says so and the notice conditions were satisfied.

Keep the Work Status Controlled After a Nonconformity

When a result fails, freeze the affected scope before discussing the solution. Identify the items, lot, location, requirement, actual result and any work that may depend on it. A broad production stop may be unnecessary, but an unbounded continuation can spread the problem or conceal evidence.

The ITP event should link to the project’s nonconformity route. Record immediate containment, investigation owner, proposed disposition, required design or buyer involvement, correction or repair instructions, repeat inspection, and the authority that closes the event. An inspector’s observation does not automatically authorize a design deviation.

If partial release is allowed, describe the released population positively. “All except failed items” is weak when the affected population is uncertain. Use item numbers, lots, zones or drawing positions, and record restrictions. Link the release to the accepted result and any remaining actions.

Re-entry requires evidence. After correction or approved disposition, repeat the necessary inspection or test, record the new result without overwriting the original, and obtain the required release. The history should show why the scope stopped, what changed and which authority allowed progression.

Re-plan the Event When the Baseline or Sequence Changes

ISO 10005 includes revising a quality plan within its guidance. Apply that principle to the operating event: review the ITP and any open notices when a change can affect scope, method, criteria, frequency, responsibilities, timing or evidence.

Typical triggers include a new drawing revision, specification clarification, material source, subcontractor, procedure, inspection method, test laboratory, production route, work sequence or responsible authority. A change does not always require a completely new ITP, but the project should decide whether affected rows need revision, reapproval or a new notice.

Do not edit a live event invisibly. Mark the superseded notice, preserve the original timestamp, issue the revised basis and identify the affected scope. If a change arrives after inspection, determine whether the previous result remains applicable. If not, define re-verification before release.

Schedule movement is also controlled. A notice for Tuesday does not automatically cover Wednesday, a different shift or another production lot. Establish the permitted timing window and the conditions that trigger re-notification. Where the buyer requests postponement, record the schedule effect and the agreed next action rather than leaving the event in an ambiguous “pending” state.

Audit the First Live ITP Event

Do not wait for the final dossier to discover that the ITP process was only theoretical. Rehearse the first event using a representative work package, then observe the first live execution and follow the record through closeout.

The active UFGS 01 45 00 Quality Control uses preparatory, initial and follow-up phases for U.S. Department of Defense construction. Before a definable feature of work begins, its preparatory phase reviews the applicable requirements and prerequisites; the initial phase observes the first segment; follow-up checks continue and are documented. This is a sector-specific specification, not a supplier ITP rule. A project can nevertheless adapt the sequence as an audit pattern:

1. Rehearse: verify the requirement, scope, prerequisites, notice path, participants, forms and release authority.
2. Observe: watch the first event and record where the written protocol does not match actual work.
3. Follow through: confirm the result, exception closure, release, record indexing and repeat-event control.

Use the audit to test behavior, not just fields. Did the notice reach the right authority? Could the inspector identify the bounded population? Was the current criterion available? Did the work crew understand whether it could proceed? Could the document controller retrieve the evidence by event ID? Did a change reach both the ITP and schedule?

Repeat the audit when a new supplier, crew, site, method or major revision changes the operating conditions. The trigger should follow project risk and contract requirements, not a universal frequency.

Pass the ITP Operational-Readiness Gate

Approve, revise or hold the plan using evidence from one representative event.

An inspection and test plan is ready when the work team and every intervention party can make the same decision from the same controlled state. The ITP should show more than what will be checked: it should define how a valid event is opened, observed or waived, accepted, released, corrected and revised. Keep sector examples within their scope, and let the project contract control terminology and authority. Before the first irreversible operation, run one event through the complete protocol. Any ambiguous notice, signature or progression rule is a reason to revise the plan before it becomes a production dispute.

Related Resources

• Quality & Manufacturing — review East Baoyu’s quality and evidence scope.
• Steel Fabrication ITP — connect material, welding, NDT, dimensional and coating checks to retained records.
• Quality Plan vs ITP — select the document hierarchy before writing activity controls.
• Vendor Document Requirement List — define deliverable obligations and review states before award.

References

• ISO 10005:2018 — Quality management: Guidelines for quality plans
• IAEA TECDOC 1910 — Quality Assurance and Quality Control in Nuclear Facilities and Activities
• NSW Government — Quality Management Guidelines for Construction
• UFGS 01 45 00 — Quality Control

Next Step: Submit the ITP Control Basis

Send the contract quality clauses, proposed ITP and legend, applicable work schedule, notification rule, authority matrix and one representative control point. East Baoyu can return an input-gap map and clarification list covering scope, notice, response states, release evidence and change triggers. The project’s designated authorities remain responsible for approving the ITP, technical criteria, inspection scope and permission to proceed.