Download the ITP template
XLSX
Inspection and test plan (Excel)
Header block, 12 columns, drop-downs for each party's intervention and for status, NCR rows in red, frozen header row, filters and a How to use sheet.
CSV
Inspection and test plan (CSV)
The example rows as plain CSV (UTF-8), for Google Sheets or any other tool.
Both files are free under CC BY 4.0, with no form to fill in. The XLSX opens in Excel, Google Sheets, LibreOffice and Numbers. The CSV carries the table only; the header block is in the XLSX.
What it is for and who uses it
Most purchase orders for engineered equipment ask for an ITP before manufacture starts. The customer approves it, then uses it to plan who attends which test. For the background, see the inspection and test plan guide.
- Quality engineers who write the plan and keep it current.
- Project managers who need to know which hold points stop production.
- Customer and third-party inspectors who plan visits from it.
Example rows: 6-inch Class 600 ball valve order
| Step | Activity | Acceptance criteria | Record | Mfr | Customer | Third party | Status | Remarks |
|---|---|---|---|---|---|---|---|---|
| 1 | Design documents approved (GA drawing, datasheet) | PO and PS-VAL-001 3.1 | Returned drawings with review code | R | R | - | Done | |
| 2 | Material certificates for pressure-containing parts reviewed against the PO | PS-VAL-001 4.2 and 7.2; material specification | Certificate review checklist | H | R | R | Not started | Type 3.2 certificates required (PS-VAL-001 7.2). |
| 3 | Positive material identification of alloy parts | Customer specification, where required | PMI report | W | - | - | Not started | Only where the PO calls for PMI. |
| 4 | NDE of castings and forgings | PS-VAL-001 8.1; referenced acceptance standard | NDE reports | H | R | R | Not started | NDE operator qualifications to be on file. |
| 5 | Dimensional check of machined parts | Drawing tolerances | Dimensional report | H | - | - | Not started | |
| 6 | Assembly check, including seat insert material | BOM-BV-0600; agreed deviation EX-03 | Assembly checklist | H | - | - | Not started | RPTFE seats per accepted deviation EX-03. |
| 7 | Shell pressure test | Product standard named in PS-VAL-001 9.4; agreed deviation EX-08 | Pressure test report | H | W | W | Not started | Give the notice period the PO requires. |
| 8 | Seat tests | As step 7 | Pressure test report | H | W | W | Not started | |
| 9 | Operational and torque check | Torque calculation TQ-BV-06 | Functional test report | H | W | - | Not started | |
| 10 | Painting: surface preparation and dry film thickness | PS-PNT-002 or agreed deviation EX-07 | Coating inspection report | H | S | - | Not started | |
| 11 | Final inspection: marking, tagging, flange protection, packing | PS-VAL-001 8.4 and 11 | Final inspection report | H | W | W | Not started | |
| 12 | Documentation review and release for shipment | VDRL-VAL-001 | Inspection release note | H | H | R | Not started | Shipment held until the release note is signed. |
The file also has columns for stage, procedure and record number. Every example value is invented: the project, customer, purchase order and every document, certificate, heat and report number do not exist. Standards are named but not quoted.
Intervention codes
| Code | Common meaning |
|---|---|
| H (hold) | Work does not go past this step until the named party has attended or released it in writing. |
| W (witness) | The named party is notified and may attend. If they do not attend after due notice, work may go on. |
| R (review) | The named party reviews the record (certificate, report or procedure) rather than attending. |
| S (surveillance) | The named party may monitor the activity at random, without a fixed notification. |
| - | No intervention by that party at this step. |
Projects define their own codes, and some use more levels. If the purchase order gives a legend, use it and edit the drop-downs to match.
Columns and what to write
| Column | What to write |
|---|---|
| Step | Step number, in the order the work happens. |
| Activity / characteristic | The inspection or test, and what it checks. |
| Stage | When it happens: material receipt, machining, assembly, testing, painting, final, documentation. |
| Procedure / reference | The procedure or document that says how the check is done. |
| Acceptance criteria | Where the pass/fail criteria come from: specification clause, drawing, code or procedure. Do not copy standard text. |
| Verifying record | The record the step produces, such as a certificate, report or checklist. |
| Manufacturer | Manufacturer's intervention: H, W, R, S or - (drop-down). |
| Customer | Customer's intervention: H, W, R, S or - (drop-down). |
| Third party | Third-party inspector's intervention: H, W, R, S or - (drop-down). |
| Record no. | Number of the record once it exists. |
| Status | Not started, Notified, Done, Released or NCR raised (drop-down). NCR rows turn red. |
| Remarks | Notice period, agreed deviations that change the step, or anything else the inspector needs. |
How to use the template
- Fill in the header block: purchase order, the specification and agreed deviation list the plan follows, and the ITP number and revision.
- List every inspection and test in the order the work happens, from design approval and material receipt to final release. One check per row.
- For each step, name the procedure, where the acceptance criteria come from and the record it produces. Point to clauses; do not copy standard text.
- Set the intervention for each party: H (hold), W (witness), R (review), S (surveillance) or - (none). Use the customer's own codes if the PO defines them.
- Where an agreed deviation changes a step, say so in the step and in Remarks, so the inspector checks what was agreed.
- Send the ITP for approval before manufacture starts. Do not pass a hold point without written release.
- As work goes on, add the record number and status for each step. Rows with an NCR raised turn red.
- Before release, filter Status for anything that is not Done or Released. Every such row needs an answer before shipment.
Checking an ITP against the customer's requirements
In OdysseyGPT's Inspection & Testing module, ITP Validator (beta) and Inspection Readiness Check (beta) check an ITP against the customer's quality requirements and show which records are still missing before an inspection. Every finding cites the page it came from, and your engineers decide what to do with it. These tools are in beta: you can request access, and we onboard each team ourselves.
Want us to run the check for you?
Send your ITP and the customer's quality requirements. We send back what is covered, what is missing and what still needs evidence before the FAT.
