Two documents decide whether a capital project can prove it built what it promised: the inspection and test plan and the non-conformance report . One describes how quality will be verified before work starts. The other records what happened when the verification did not go to plan. When the two are managed as a single system, a quality manager can trace any weld, skid, or commissioning step from the specification through the inspection evidence to the final closure record. When they are managed separately, both degrade into paperwork that satisfies nobody.
This guide is written for quality managers, QA leads, and project quality teams running fabrication, construction, and commissioning scopes. It covers how an ITP should be structured, where ITPs commonly fail, how the handoff to an NCR should work, and how to trend non-conformances so the same issue stops recurring.
First, a Note on Terminology
In industrial quality management, ITP stands for Inspection and Test Plan, and NCR stands for Non-Conformance Report. The acronym ITP is also used in medical literature for an unrelated blood disorder. If you have landed here from a search for clinical information, this article is not the right source. Everything below refers to the inspection and test planning documents used in manufacturing, fabrication, construction, and commissioning.
An NCR is sometimes called a non-conformance report, a nonconformity report, or a deviation report depending on the organisation and the client. The label matters less than the discipline: a written record of a requirement that was not met, the disposition agreed to fix it, and the evidence proving the fix worked.
What an ITP Actually Does on a Project
An inspection and test plan is a control document attached to a defined scope of work. It lists the activities that must be verified, the characteristics or acceptance criteria being checked, the method of verification, the record produced, and the point at which the activity must be witnessed or released before the next step proceeds.
The most useful way to think about an ITP is as a schedule of interventions. It tells the inspector where to be, the contractor when to stop, and the client what evidence they will receive. A well-built ITP prevents two expensive failures: inspection that arrives after the work is buried, and inspection that is repeated because nobody defined the acceptance criteria up front.
Anatomy of a Workable ITP
Most functional ITPs share the same skeleton, regardless of the discipline they cover. The content differs by scope, but the columns do not.
- A unique ITP number and a clear statement of the scope it governs, with reference to the applicable specification or drawing revision.
- An ordered list of activities, sequenced the way the work is actually built, not the way the specification is written.
- The characteristic or parameter being verified, expressed as a measurable acceptance criterion wherever possible.
- The verification method, such as visual examination, dimensional check, non-destructive testing, pressure test, or functional test.
- The intervention point: hold, witness, review, or monitor, and who is entitled to sign at each one.
- The record to be produced and retained, with a record identifier so it can be retrieved years later.
- Approval signatures from the parties who will rely on the plan.
The intervention coding is where most negotiation happens. A hold point stops work until the nominated party signs . A witness point notifies the party that the activity is happening and allows attendance without stopping the work if they decline. A review point requires documents to be submitted after the fact. Monitor means records are kept and made available. Getting these designations wrong in either direction creates problems: too many hold points and the schedule stalls, too few and critical characteristics go unverified.
Where Inspection and Test Plans Fail in Practice
The failure modes repeat across projects, and almost all of them are preventable at the planning stage.
The first is generic copy-and-paste. A plan lifted from a previous project and lightly edited rarely matches the actual specification, and it invites the field team to ignore it. The second is missing acceptance criteria, which turns every inspection into a debate about what "acceptable" means. The third is a plan that is technically correct but not sequenced to the construction method, so the hold point lands after the concrete is poured or the pipe is buried.
The fourth, and most damaging, is an ITP that never connects to the non-conformance process. When an inspection fails, the record shows a red mark and nothing else. There is no NCR number, no disposition, no closure evidence, and no traceability between the ITP line item and the corrective action. That gap is where audit findings are born.
From ITP Breach to NCR: The Handoff That Decides Everything
The moment an inspection against an ITP line item fails, three things should happen in sequence. The affected item is identified and, where relevant, physically segregated or tagged so it cannot move forward. The ITP line item is annotated with the failure and a cross-reference to the NCR number. The NCR is raised and routed to the responsible party.
This handoff is where quality systems are won or lost. If the ITP record does not carry the NCR reference, the two systems drift apart and the closure file for that scope becomes impossible to reconstruct. A useful rule is that every ITP line item with a failed or conditional result must show an NCR number, and every closed NCR must show the ITP line item that generated it.
Inside the NCR Lifecycle
A non-conformance report moves through predictable stages. The table below sets out what each stage is for and what evidence it should leave behind.
Two stages get skipped most often: extent of condition and closure verification. Asking whether the same problem exists on other units costs time now and saves far more later. Verifying that the fix was actually performed as described, rather than accepting a stated intention as closure, is the difference between a record and a claim.
Disposition Decisions and Why They Get Contested
Most disposition routes fall into a small number of categories: rework to meet the original requirement, repair to an agreed alternative, use as is with documented technical justification, or rejection. The disputes tend to focus on repair and use-as-is, because both involve accepting something other than what the specification described.
Regardless of the route chosen, the disposition should state the technical basis for the decision, name the authority approving it at the level the project requires, and define how the outcome will be verified. A disposition that cannot be re-verified later is not a disposition, it is a note. Where a project has a client or third-party witness role defined in the ITP, that same role generally needs visibility of the NCR outcome for the same scope.
Trending and Root Cause: Getting Beyond Counts
A quality manager who reports only the number of open NCRs is describing workload, not performance. Useful trending cuts the data by discipline, by supplier or subcontractor, by work package, by failure mode, and by time. A cluster of dimensional non-conformances on one fabrication line tells a different story than the same count scattered across ten scopes.
Root cause analysis should scale to the significance of the issue. A single isolated defect may need nothing more than a correction and a note. A repeat failure, or a failure that could have compromised integrity, warrants structured analysis and a corrective action that changes the process rather than the individual record. The test of a good corrective action is whether the same non-conformity stops appearing in the trend log over the following months.
Practical Controls for the Year Ahead
The mechanics of ITP and NCR management are stable, but the expectation of traceable, retrievable, and reviewable records has risen across capital projects and regulated manufacturing. A few controls do most of the work.
- Register every ITP against a scope and a revision, and retire superseded versions explicitly so the field team cannot work to an obsolete plan.
- Give each ITP line item a unique identifier so inspection results, NCRs, and closure evidence can all point to the same reference.
- Require an NCR number on any failed or conditional ITP result, and check the pairing during internal audits.
- Keep the closure approval separate from the implementation role where resourcing allows, so verification is genuinely independent.
- Review the NCR trend log at a fixed cadence with construction, engineering, and supplier quality in the room, and assign named owners to actions.
- Test retrieval. Pick a closed NCR at random each quarter and confirm you can produce the ITP reference, disposition, re-inspection evidence, and approval signatures without asking three people.
None of this requires exotic software. It requires the ITP and the NCR to be treated as two halves of one traceability chain, from planning through evidence to closure. Teams that get that chain right spend less time defending their records and more time preventing the failures that generate them.
Questions we get on this topic
What is the difference between an ITP and an NCR?
An Inspection and Test Plan is a forward-looking control document. It defines what will be inspected, how, against which criteria, and at what intervention point. A Non-Conformance Report is retrospective. It records a requirement that was not met and drives the item through evaluation, disposition, implementation, and verified closure. The ITP sets the standard; the NCR handles departures from it.
Who should approve a non-conformance disposition?
Approval authority depends on the disposition route and the project's defined rules. Rework back to the original requirement usually sits with the responsible party's quality function. Repair or use-as-is decisions typically need engineering authority, and often client or third-party visibility where the ITP assigns them a witness role for that scope. Confirm the authority matrix before the first NCR is raised.
How long should ITPs and NCRs be retained?
Retention periods are set by the contract, the client's requirements, and any applicable regulatory obligations for the asset class. Because these vary, confirm the specific retention period with the project owner and the relevant authority rather than assuming a default. The practical rule is to retain them at least as long as the asset record needs them for verification and audit.
Can an ITP be revised after work begins?
Yes, and it often should be. Construction methods, supplier details, and scope clarifications change. Revisions must go through the same approval route as the original plan, carry a new revision number, and be issued to everyone holding a controlled copy. Superseded versions should be withdrawn so that nobody inspects against an outdated plan.
What makes an NCR closure defensible in an audit?
A defensible closure shows four things: the original condition described with enough detail to locate it, an approved disposition with a technical basis, evidence that the agreed work was performed, and a re-verification result confirming the requirement is now met. If any of those four is missing or relies on a verbal assurance, the closure is likely to be challenged.
Quality briefs, straight to your inbox
Field-tested guidance on inspection, audits and project quality systems — one issue on the first Tuesday of each month, written for people who have to make them work.
See past issues →- What is a Non-Conformance Report (NCR)?A plain-English guide to non-conformance reports — what an NCR is, what goes on the form, the lifecycle from detection to closure, the five disposition options, and where the NCR stops and CAPA begins.
- Vendor surveillance: scoping your way out of riskA tiering approach to surveillance intensity that keeps critical supply moving without blind spots.
- Types of NDT methods: RT, UT, PT, MT, VT and ECTRadiography, ultrasonics, penetrant, magnetic particle, visual and eddy current each find a different family of defects. Here is how each method works, its limitations, and how specifications decide which one applies.
Need independent quality assurance on your project?
Talk to our team about inspection, auditing and QMS support.