An inspection and test plan (ITP) says what will be inspected or tested, at what stage, against which acceptance criteria and who has to be involved. An inspection test record (ITR) is the completed evidence that one of those inspections or tests was actually carried out on a specific item, with the result and the signatures. A checksheet is the form the ITR is recorded on, and on many projects the two words are used interchangeably. In short: the ITP is the plan, the ITR is the proof, and the completion certificate is the summary that says a whole system has been proven.
Why the difference matters
Most arguments about inspection paperwork at the end of a project come from people using the same words for different things. The QA/QC team talks about "the ITP" and means a plan for a work package. The completions team talks about "ITRs" and means thousands of tag-level records in a database. The client's inspector asks for "the checksheets" and means the signed forms in the dossier.
If those documents aren't deliberately linked, you get the classic failure: every line on the ITP has been signed off somewhere, but nobody can show which record proves which check on which tag. Getting the hierarchy straight early saves weeks of reconciliation later.
What is an ITP?
An inspection and test plan is a planning document, normally prepared by the contractor for each discipline, work package or subcontract and approved by the client (or their representative) before the work starts. It sits underneath the project quality plan and translates specifications into a sequence of verification activities.
A typical ITP line contains:
- Activity — for example, receipt inspection of cable drums, weld visual inspection, hydrotest, insulation resistance test.
- Reference documents — the specification, drawing, standard or procedure that defines the requirement.
- Acceptance criteria — what "good" looks like, or a pointer to where that is defined.
- Frequency or extent — every item, a percentage sample, or first-off only.
- Verifying document — the record that will prove it was done, usually an ITR or form number.
- Intervention points — what each party does at that step: hold, witness, review or surveillance, typically coded H, W, R and S. The codes and their exact meaning vary between clients.
What an ITP is not: it isn't a method statement (that explains how the work is done safely), and it isn't a record. An approved ITP with no completed records behind it proves nothing.
ITP scope and level
ITPs are written at activity level, not tag level. A single electrical ITP might cover every motor on the project in half a dozen lines. That is the point: it defines the rules once, and the ITRs apply them to each item.
What is an ITR?
An inspection test record is the tag-level (or item-level) evidence. One ITR is completed for one tag or one defined item, such as a motor, a cable, a line, a loop or a test pack, and it records:
- the tag number, and usually the system and subsystem it belongs to
- the form or template it was completed on, with its revision
- the result of each check, with measured values where there are any
- remarks, and any punch items or non-conformances raised
- who performed it, who witnessed it, and when
In completions work, ITRs are usually split by stage. "A" records cover construction and mechanical completion checks on dead equipment, and "B" records cover pre-commissioning tests, some of which need the equipment energised or pressurised. Some projects add further categories, and frameworks such as OPERCOM use their own names for the equivalent records, so check your contract's terminology. We explain the stage split in more detail in pre-commissioning vs commissioning.
Checksheet vs ITR: are they the same thing?
Often, yes. "Checksheet", "check record", "inspection record", "test sheet" and "ITR" are all used for the same document depending on company and region. The more useful distinction is between the template and the completed record:
- The template (sometimes called the form or ITR type) is the blank, controlled form, for example "Motor inspection — LV". It is written once, revision-controlled and referenced from the ITP.
- The completed ITR is one instance of that template filled in for one tag, for example the LV motor inspection for pump motor P-101A-M.
A project might have a few hundred templates and tens of thousands of completed records. When people say "we need 30,000 ITRs", they mean completed instances, not 30,000 different forms.
What goes on each discipline's templates (the specific checks for electrical, mechanical, piping, instrumentation and so on) is a large subject in its own right. You can find detailed discipline ITRs and inspection checklists at checksheets.com, so we won't repeat them here.
How the inspection documents fit together
The table below shows the full chain, from plan to certificate.
| Document | Question it answers | Level | Typically prepared by | Output |
|---|---|---|---|---|
| Project quality plan | How will quality be managed on this project? | Project | Contractor QA | Approved plan, list of ITPs |
| Inspection and test plan (ITP) | What must be verified, when, and who intervenes? | Discipline or work package | Contractor QA/QC, approved by client | Approved ITP referencing forms |
| ITR template / checksheet | What exactly is checked on this type of item? | Equipment type or activity | Completions or QC engineers | Controlled blank form |
| Completed ITR | Was this check done on this tag, and did it pass? | Tag or item | Inspector or technician, with witnesses | Signed record |
| Punch item or NCR | What is wrong, and how bad is it? | Tag or item | Anyone finding a defect | Open item to clear |
| Completion certificate | Is this whole system or subsystem complete? | System or subsystem | Completions, signed by contractor and client | Signed certificate |
The flow, step by step
- Specifications and the quality plan set the requirements and list the ITPs the project needs.
- ITPs are written and approved for each discipline or scope, naming the verifying form for each activity.
- Templates are allocated to equipment types. A matrix maps each tag class (motor, transmitter, valve, line) to the ITR templates it needs. This is where the ITP's activities become concrete forms.
- The tag register drives the ITR list. Every tag in every system gets the ITRs its class requires. This is why a clean tag register and settled systemisation matter so much; see systemisation in commissioning.
- Inspections and tests are executed and witnessed according to the intervention points in the ITP.
- Failures become punch items or NCRs, categorised by how much they block progress. See punch list categories A, B and C.
- Certificates are issued for each system or subsystem once all required ITRs are complete and only permitted punch items remain open. The chain is covered in commissioning certificates explained.
- Records go into the handover dossier, organised by system.
Where the ITP and the completions system collide
The most common friction point is organisation. QA/QC tends to think in work packages, areas and lots: "all welds in test pack 12". Completions thinks in systems: "everything on the firewater ring main". Both views are legitimate, and on a well-run project they are two views of the same records.
Problems start when they are two separate sets of records. The QC inspector fills in a weld visual form for the QC file, and then someone completes a near-identical "A" ITR for the completions database. Signatures get duplicated, results can disagree, and the client's auditor finds two versions of the truth.
A few practical rules help:
- One check, one record. If the ITP requires a check that the completions system also needs, make the ITP's verifying document the ITR itself.
- Tag every record. Even QC records that are naturally area-based, such as a batch of concrete cubes, should reference the tags or systems they support where that makes sense.
- Mirror intervention points on the form. If the ITP says the client must witness a test, the ITR template should carry a witness signature block, and the record shouldn't close without it.
- Control template revisions. When a form changes mid-project, decide whether completed records need re-doing and record that decision.
Common mistakes with ITPs, ITRs and checksheets
- ITPs that reference form numbers that don't exist yet, or were renamed.
- Every line coded as a hold point, so the client's inspectors become a bottleneck and holds get waived informally.
- ITR templates copied from a previous project without checking them against this project's specification.
- Completed ITRs that can't be traced back to a tag, or tags with no ITRs allocated at all.
- Certificates signed on the basis of a spreadsheet count rather than a check of the actual records.
- Records filled in after the fact from memory, which is exactly what witnesses and hold points exist to prevent.
A structured completions management system removes most of these by linking tags, templates, records and certificates in one place.
Managing inspection documents in Accord and Checksheets
Accord holds ITRs against the project's system, subsystem and tag hierarchy. It supports "A" mechanical-completion inspections and "B" pre-commissioning tests with defined acceptance criteria, enforces the dependency so "B" records cannot start until prerequisite "A" records are approved, and includes a witnessing workflow with accept, reject and personal queues. Certificates follow an enforced dependency chain, so they cannot be issued without their prerequisites.
Checksheets generates checksheet and ITR templates with AI in minutes, carries tag, system, subsystem and test pack metadata, lets inspectors fill them on a phone with Pass / Fail / N/A and photos, and routes them for email approval with digital signatures.
Frequently asked questions
Is an ITP the same as an ITR?
No. An ITP is a plan that lists the inspections and tests required for a scope of work, with acceptance criteria and intervention points. An ITR is the completed record proving that one of those inspections or tests was done on a specific item. The ITP normally names the ITR form used as its verifying document.
Who approves an inspection and test plan?
The contractor responsible for the work usually prepares the ITP and the client or their representative reviews and approves it before work starts. Where a third-party inspection body or certifying authority is involved, they may add their own intervention points. The exact approval route is set by the contract and the project quality plan.
What is the difference between a checksheet and an ITR?
On many projects there is no difference; the terms are used for the same document. Where a distinction is made, "checksheet" often refers to the blank template and "ITR" to the completed, signed record for a particular tag.
Do you need an ITR for every tag?
Every tag should have the ITRs its equipment type requires, as defined by the ITP and the template allocation matrix. Some items are covered by records at a different level, such as a test pack covering several lines or a loop check covering several instruments. What matters is that every tag can be traced to the records that prove it.
What are A and B ITRs?
"A" ITRs usually cover construction and mechanical completion checks, carried out on equipment that isn't energised or in service. "B" ITRs usually cover pre-commissioning tests, such as functional checks and energised tests. Naming varies between companies and frameworks, so confirm the definitions in your project's completions procedure.