Quality Plan vs ITP: Define Control Without Duplication

A quality plan and an inspection and test plan (ITP) are related, but they should not be treated as interchangeable templates unless the contract says so. A quality plan normally explains how quality will be managed for a project, contract or defined output. An ITP turns a work package into a sequence of checks, criteria, intervention points and records. Many projects need both, linked rather than duplicated. However, names vary among clients, industries and jurisdictions. The contract’s definitions, prescribed forms and approval rules therefore control. Use the selector below to establish the document architecture before fabrication starts.

Begin with the Contract, Not the Labels

Use this selector as the opening clarification, then verify every result against the contract.

This is a selection aid, not a substitute for the contract. A client template may deliberately combine the two levels.

The question is not “Which definition is correct?” It is “Which document set proves that this contract will be managed and the work will be inspected as required?” Start with the hierarchy that creates obligations:

1. contract conditions, purchase order and quality clauses;
2. project specification, drawings and applicable standards;
3. vendor document requirement list or deliverable register;
4. client templates, approval codes and document numbering rules;
5. agreed clarifications, deviations and meeting decisions.

Record the exact term, required submission date, approving party, status code and effect of non-approval. A document marked “reviewed” may not have the same contractual effect as one marked “approved” or “accepted.” Never assign those meanings from habit.

The terminology warning matters. The IAEA’s procurement quality guidance notes that a quality plan used to monitor conformity may sometimes be called an ITP and that the names can be interchangeable in some circumstances. Its comparison then shows different depths in two regulatory examples. That is evidence against a universal naming rule, not permission to ignore the project definition.

When the contract is ambiguous, submit a one-page proposed hierarchy. Show the umbrella plan, the intended ITP list, supporting procedures, checklists and final records. Ask the buyer to confirm whether the structure meets the deliverable requirement before the supplier writes several overlapping documents.

Compare the Documents at Different Zoom Levels

ISO 10005:2018 gives guidance for establishing, reviewing, accepting, applying and revising quality plans. ISO says the guidance can apply to a process, product, service, project or contract, whether or not the organization has an ISO 9001-conforming management system. It also states that the document provides guidance rather than requirements. A contract must therefore adopt or define the applicable obligation.

For many fabrication projects, the practical distinction is one of control level:

These are useful defaults, not universal definitions. Some contracts place detailed inspection steps inside a quality plan. Others require a quality plan plus many ITPs. The deliverable is adequate only when its content, authority and traceability meet the governing requirements.

Put Management Controls in the Quality Plan

The quality plan should explain how the delivery-specific quality system will operate. It does not need to reproduce every corporate procedure. It should identify the applicable procedure, its revision and any project-specific addition. A usable plan normally answers questions such as:

• What product, work or contract does the plan cover, and what is excluded?
• Which requirements and approved documents form the baseline?
• Who owns quality, engineering, document control, purchasing, production, inspection and final release?
• How are suppliers and subcontractors selected, flowed down, monitored and changed?
• How are competence, inspection resources and measuring equipment controlled?
• How are drawings, specifications, concessions and revisions distributed?
• How are nonconformities contained, reviewed, approved and closed?
• Which internal audits, surveillance or management reviews are planned?
• Which ITPs, procedures, registers and final records form the subordinate package?

The NSW Government Quality Management Guidelines provide one concrete contract model. In that model, the Quality Management Plan can include an index of quality procedures, proposed ITPs and an audit schedule, while ITPs are submitted for nominated activities. This is a useful example of an umbrella-and-work-package relationship, but its timing and contractual language apply to that procurement context, not automatically to another project.

Avoid two common failures. A generic corporate manual is not automatically a project quality plan because it may not identify this order, its interfaces or its deliverables. Conversely, a quality plan should not become a copy of every ITP row. It should govern the subordinate controls and provide a navigable index to them.

Put Executable Gates in Each ITP

An ITP should be usable where the work occurs. Each row needs enough information for the responsible person to know what is checked, against which released requirement, at what stage, by what method and frequency, with whose intervention, and in which record the result will be retained.

A minimum row logic is:

work stage → characteristic or requirement → acceptance basis and revision → verification method → frequency or population → responsible parties → intervention code → record → status

The acceptance basis must be specific. “As per specification” is weak when several specifications, revisions or drawing notes could apply. The method and frequency must also be separate: a dimensional characteristic can have one method but different inspection populations by lot, zone or criticality.

The IAEA comparison illustrates the activity-level character of an ITP in one regulated manufacturing context: the working document tracks a component or assembly through fabrication, identifies manufacturing steps and provides space for required approvals. That example should not be copied as a universal form, but it shows why an ITP must follow the actual production route.

Do not expand this comparison article into a welding, NDT or coating template. For the execution-level document chain, use East Baoyu’s Steel Fabrication ITP guide, which links material certificates, procedures, inspections and the final manufacturing record.

Connect Both Documents with One Coverage Crosswalk

The most reliable way to prevent gaps and duplication is to map every material contract requirement across both control levels. A crosswalk can be a sheet in the quality plan, a controlled register or a separate schedule referenced by both documents.

Run the crosswalk in both directions.

• Requirement-to-control test: every applicable contract clause must point to a plan section, ITP row, procedure or record. An unassigned requirement is a gap.
• Control-to-requirement test: every inspection, approval or record request must point back to a contract, specification, approved drawing, risk decision or agreed procedure. An unsupported control can add cost or create an accidental obligation.

Do not repeat detailed acceptance criteria in several documents unless the contract requires it. Prefer one controlled source and exact references from the other documents. When duplication is unavoidable, assign one master source and a revision-reconciliation rule.

Assign Approval, Intervention and Change Authority

A signature box is not an authority model. Define who prepares, checks, submits, reviews, accepts, releases and revises each document. Then define what each intervention code means under the contract.

• Quality-plan submission: name who accepts the management framework and whether acceptance releases work or only closes document comments. Client review does not silently transfer the supplier’s contractual responsibility.
• ITP approval: name the parties that approve the base ITP and later revisions. Production must not rely on an unapproved revision when approval is a prerequisite.
• Hold point: name the release authority, required evidence and release record. Do not proceed merely because an inspector did not attend.
• Witness point: define notice, attendance waiver and the waiver record. Waived attendance does not waive the supplier’s required inspection.
• Nonconformity or concession: name the disposition authority and when design or buyer approval is required. An inspector’s observation is not automatically design authorization.
• Change: define which changes trigger crosswalk review, revised ITP rows, reapproval or notification. Apply an approved change only to the defined effective items or lots.

In the cited NSW model, work cannot proceed beyond a nominated hold point without the Principal’s endorsement, while a witness point gives the Principal an opportunity to attend. The same guidance states that endorsement does not release the contractor from its obligation to meet the contract. Treat this as a clear example, then confirm the definitions and notice rules for the actual project.

Test the Package Before Work Starts

Do not approve the document set because both filenames exist. Run a readiness test against the actual first work package.

The result may be different for different contracts. A low-risk repeat item might use ITPs supported by existing procedures when the contract permits it. A custom, multi-supplier fabrication package may need one quality plan and several ITPs. A client may accept one combined document if it covers both management and execution controls. The selection is valid only when the buyer confirms the architecture and the readiness test passes.

Do not solve “quality plan vs ITP” by choosing the better label. Build a controlled hierarchy in which the quality plan governs the delivery, each ITP controls a defined work package, and the crosswalk proves that every requirement reaches one owner, one verification route and one record. Where the contract combines the names, preserve the same functions inside the accepted form. Before work starts, close ambiguous authority, missing references, orphan requirements and unapproved changes. That is what turns a document package into a usable quality-control system.

Related Resources

• Quality & Manufacturing — commercial parent and evidence-request route.
• Steel Fabrication ITP — activity-level inspection and record chain.
• Project Document Register — control deliverables, revisions and due dates.
• Steel Fabrication Drawing Approval Workflow — control the drawing baseline feeding the ITP.

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

Next Step: Submit the Quality-Document Basis

Send the contract quality clauses, specification and drawing index, vendor-document requirements, client templates, proposed ITP list, intervention-code legend and authority matrix. East Baoyu can review the inputs and propose a document hierarchy, coverage gaps and the next clarification route. The final deliverables, approvals, manufacturing responsibility and release authority remain subject to the applicable quotation and contract.