An inspection test plan, usually shortened to ITP, is the document that decides in advance what will be checked, against which requirement, by whom, and which record proves it. On a fabrication job in Indonesia it is often the only page that the vendor’s shop floor and a head office far away will read in the same way.
Most ITPs fail not because they are missing, but because they are written to be approved rather than used. This guide on how to write an inspection test plan comes from the working end of QA/QC: the plans inspectors carry to site, the arguments that follow a vague plan, and the small drafting habits that prevent them.
- What an ITP is, and what it is not
- The anatomy of a usable ITP
- Writing the plan around real production
- Acceptance criteria that can be cited
- Intervention levels and the rules around them
- Review, approval and revision control
- A quick test for weak plans
- Frequently asked questions
What an ITP Is, and What It Is Not
An ITP is a control map. It lists the sequence of activities in a job and, for each one, the control applied to it. It is not a work procedure, which explains how to perform a task, and it is not a checklist for one inspection, which captures readings on the day. The ITP sits above both and points to them.
Many projects derive the ITP from a wider quality plan. ISO 10005 offers guidelines for quality plans, and the plan itself operates inside the vendor’s quality management system, the kind of system that standards such as ISO 9001 describe. The ITP is the part of that structure that faces the shop floor, translating quality intentions into specific stops and records.
The practical test of a good ITP is simple. Could an inspector who has never visited this workshop pick it up, walk the production route and know exactly what to look at and what to sign? If the answer is no, the plan is not finished, however many signatures it carries.
The Anatomy of a Usable ITP
Formats vary, but useful plans tend to carry the same columns:
- Activity: one clear step in the production sequence, in the order it actually happens.
- Reference document: the procedure, drawing or specification clause that governs it.
- Acceptance criteria: the measurable limit or standard clause, not the word “satisfactory”.
- Frequency or extent: every item, a defined sample, or each batch.
- Record: the report, log or certificate that proves the check, with its form number if there is one.
- Intervention: the level of control for each party, usually coded as hold, witness or review.
- Sign-off: a place for name, date and signature against each party.
Letter codes such as H, W and R are widely used for intervention, but they are a convention, not a universal standard. Define every code on the first page of the plan so nobody has to guess what a “W” means for a particular client.
Writing the Plan Around Real Production
The most common drafting error is writing the plan from the specification instead of from the work. A specification lists requirements by topic, while production happens in sequence. An ITP that follows topic order forces inspectors to hunt through it, whereas one that follows the production route lets them move with the job.
Granularity matters too. “Welding” is too coarse to control anything. Splitting it into welder and procedure qualification review, joint fit-up, root pass, interpass checks, final visual inspection and NDT gives each stage its own criteria and its own record. The same applies to coating, hydrotesting and final assembly.
A reliable way to build the plan is to start from the vendor’s route card or traveler, the document that follows the item through the shop, and overlay the controls onto it. This forces the plan and the real process to match, and it exposes steps the specification never mentioned but the workshop actually performs, such as outsourced machining or galvanizing.
Acceptance Criteria That Can Be Cited
“Per specification” is not an acceptance criterion. It hands the inspector a whole document to search through, and it invites a different reading from each party. A criterion should name the clause, the code and edition, or the numeric tolerance, so that a pass or fail can be defended later without argument.
Be honest about gaps. If the contract is silent on a point, say so during review and agree an interpretation in writing. A plan that hides a gap behind vague wording only postpones the dispute to the day when the work is finished and rework is expensive.
This is also where foreign owners should watch for template contamination. Plans are often adapted from an earlier project, and old standards, obsolete equipment names or another client’s requirements survive in cells nobody re-read. A read-through by someone who did not write the plan usually finds them.
Intervention Levels and the Rules Around Them
Intervention codes only work if the rules behind them are written down. Typically a hold point means work must not proceed until a named party has released it in writing. A witness point means the party is invited and may attend, and work can proceed after the notice period if they do not. A review point means records are examined, before or after the work, without anyone being present. These are common conventions, so confirm how your own contract defines them.
Notice mechanics deserve the same precision. State how much notice is needed, by what means and to whom. Say what happens if an inspector cannot attend, for instance whether a witness point lapses and whether a hold point is rescheduled. Local calendars matter: public holidays and the Eid period can remove several working days from a plan that assumed an ordinary month.
Finally, decide who decides. If the buyer’s engineer and the third-party inspector disagree about releasing a hold point, the plan should say whose view prevails. Silence on this is where schedule slips quietly accumulate.
Review, Approval and Revision Control
An ITP is a controlled document. It should carry a revision number, a date and a note of what changed, and old revisions should be withdrawn from the shop floor. Plans that circulate as loose copies in several versions are a reliable source of arguments about which controls were agreed.
Approval should come before the first activity covered by the plan, not after. Where fabrication starts before the ITP is signed, the work already done has no agreed controls and often no records. Making ITP approval a gate to production release is a simple and effective safeguard.
Language is a practical issue on Indonesian projects. Plans are commonly written in English for the client, while shop-floor documents may be in Bahasa Indonesia. Use consistent terms for each activity in both, and consider a short bilingual glossary, so that “fit-up” on the plan and the local term on the route card are clearly the same step.
A Quick Test for Weak Plans
Before approving a plan, scan it for these warning signs:
- Activities such as “inspect as required” or “general checks” with no criteria.
- Every line marked as a hold point, which usually means nobody thought about risk.
- No record named for a check, so there is nothing to show later.
- References to standards without an edition or clause.
- No place for the vendor’s own sign-off, which shifts all responsibility to the inspector.
- A revision history that stays at revision 0 on a long project.
G.I Quality Services lists vendor surveillance, documentation review and third-party inspection among its services, and each of those activities depends on a plan of this kind. Whichever team is appointed, reading the ITP together at kick-off, line by line, is one of the cheapest quality investments on a project.
Frequently Asked Questions
What does ITP stand for in inspection?
ITP stands for inspection and test plan, also written as inspection test plan. It is the document that lists each activity, its acceptance criteria, the records required and which parties verify it.
Who writes the ITP?
Usually the vendor or contractor drafts it, because they know the production sequence. The buyer or its engineer reviews and approves it, and a third-party inspector often comments on whether the controls are practical to execute.
What is the difference between an ITP and a quality plan?
A quality plan describes how quality will be managed for a project or product in general. The ITP is the more specific part that lists the inspection and test stops along the production route.
How detailed should an ITP be?
Detailed enough that every activity has its own criteria and record, but not so detailed that it repeats the procedures. If an inspector must open three other documents to know what to check, the plan is too thin.
Can an ITP be changed during a project?
Yes, through revision control. Changes should be reviewed and approved by the same parties as the original, and any reduction in hold or witness points should be agreed explicitly by the buyer.
Do small purchases need an ITP?
Often a short one-page plan is enough. Even a simple purchase benefits from stating what will be checked before shipment and which records will be provided.