The ITP is more than a form.
The plan controls the route from planned verification to client acceptance. The useful record includes not only the field entry, but also the evidence, exception history, review comments and final approval that explain the outcome.
When each part is maintained separately, the engineering team can finish the work while the documentation remains incomplete. That gap creates late administration, repeated questions and avoidable handover risk.
From field work to client acceptance
- 01Plan the testDefine the activity, criteria, evidence and required review points.
- 02Complete the workGive the field team the current controlled instructions.
- 03Capture the resultRecord values, observations and outcome while the work is happening.
- 04Attach evidenceConnect photographs and supporting records to the exact activity they prove.
- 05Submit for reviewRoute the complete record to the accountable reviewer.
- 06Resolve commentsKeep comments and revisions attached to the original work.
- 07Record approvalMake the decision, authority and date explicit.
- 08Hand overReuse the accepted records without rebuilding the package.
What creates avoidable ITP administration?
- Entering the same result into a form, spreadsheet and client register.
- Saving photographs in folders that do not identify the test they support.
- Sending flattened PDFs back and forth during review.
- Maintaining a separate manual status register.
- Discovering missing evidence after the team has left site.
Rowsys is purpose-built for engineering and specialist contractors that need to complete the work, prove it once and get it accepted faster.
Document-led versus connected ITP delivery
| Document-led process | Connected ITP workflow |
|---|---|
| Paper or PDF form plus a separate register. | The controlled plan, result and status remain connected. |
| Photographs are saved in project folders. | Evidence is linked to the test and acceptance criteria. |
| A coordinator manually reconciles progress. | Status is derived from the actual field and review state. |
| Comments and revisions move through email. | Review history stays with the original activity. |
Frequently asked questions
What is an inspection and test plan?
An inspection and test plan (ITP) defines what must be inspected or tested, when it will happen, who is responsible, the acceptance criteria, the evidence required and the points at which work must be reviewed or approved.
What should ITP software do?
ITP software should keep the controlled plan, field result, supporting evidence, exceptions, review comments, revisions and approval connected. It should make outstanding work visible without requiring a separate manual register.
Why do completed tests still delay handover?
A test can be physically complete while its result, evidence, signature, review or approval remains incomplete. When those records are split across paper, spreadsheets, PDFs and folders, teams often discover the gap late and must reconstruct the package.
Can digital ITPs reduce return visits?
They can reduce avoidable return visits when engineers capture the required result and evidence at the source, and when missing information or failed acceptance criteria are surfaced while the team is still in the field.