---
title: Inspection test plan software
description: Your inspection test plan, run as the job. Every hold point becomes a sign-off on the step it belongs to, and the work below it waits until that is signed.
canonical: https://stratumsoftware.io/inspection-test-plan-software.html
updated: 2026-08-16
---

FOR WORKSHOPS AND INSPECTION PROVIDERS WORKING TO CLIENT ITPs

# Your inspection test plan, run as the job.

Every hold point on the ITP becomes a sign-off on the step it belongs to. Work below one that has not been signed waits until it is. Send us an inspection test plan you work to today and we will show you the workflow it becomes.

[Send us one ITP ->](#start)

How it usually goes

## The inspection test plan is a spreadsheet. The job is somewhere else.

- The plan says hold point. Nothing on the job flags it, so it gets picked up two steps later.

- The sign-off happened. The initials are in a box, on a page that never got scanned.

- The spreadsheet is on version four. Version three is still open on someone's laptop.

- Someone gives up the day before handover, matching sign-offs back to steps.

What changes

## The plan and the job become the same thing.

Nothing about the way your people work has to change. What changes is that the plan stops being a separate document somebody has to remember.

We build your ITP into the job template: the steps in the order you run them, the fields on each one, the hold points where you put them, the photographs where you require them.

Your team reviews it and approves it before anyone uses it. Templates move through draft, reviewed, approved and live.

Then your people work the job on a tablet. The plan is the screen in front of them.

Hold points

## Nothing gets past a hold point by accident.

- Hold points sit inside a step, not only at the end of one, and a step can carry several.

- Fields below an unsigned hold point are disabled, so nobody has to remember to wait.

- Each signature is recorded against the step and the position it belongs to.

- Where the template calls for a photograph, the step waits for it, and a guide image shows the shot.

Client ITPs

## One template, every client.

### Different plan for every client

Whole steps, whole tables and individual fields show or hide depending on the job, so one template can cover formats that used to need a document each.

### When the formats are genuinely different

Then it is one template each, and we will say so when we look at your set. Conditional steps hide the parts a client does not want. They do not turn one document into forty.

### One job, several documents

A job template carries several client-facing report templates. The same captured data comes out in whichever format that client expects.

### Non conformance reports

Anything your people fill in by hand can be built the same way: an NCR, a final check sheet, a release note, a job card. Send the form and we will build the workflow behind it.

### Manufacturer's Data Reports

MDR documents generate from the same job data as everything else. We do not hold or verify third party material or mill certificates, so the outside paperwork is still yours to gather.

### Accreditation and standards

Working to ISO 17025, ISO 17020, ISO 3834 or ISO 19443? [How the records line up against the standards](https://stratumsoftware.io/audit-evidence-software.md).

How it works

## Five steps, starting from the plan you already use.

- Send us one ITP, inspection report or check sheet you already issue.

- We build the job template from it: the steps, the fields, the hold points and the photo requirements.

- Your team reviews and approves it. Templates move through draft, reviewed, approved and live.

- Your people work the job on a tablet: measurements, photographs, checks, hold points, sign-offs.

- The branded client report generates from what they captured, the moment the job closes.

Inside it

## Built for a plan that has to be followed in order.

- Hold points configured per step and signed individually, each recorded against its own step.

- Required photographs are enforced, with a guide image so the right shot gets taken.

- Sixteen field types, including measurement, photograph, dropdown, date and auto-calculated.

- Auto-calculated fields work out limits and fits against ISO 286, so nobody reads them off a chart.

- Real tables with merged cells, and every value stored as data you can report on.

- Lookup tables scoped to your company, so your own specification data sits alongside published reference data.

- Both the internal record and the client-facing report generate from the same captured data.

- Unlimited users. No per-seat charge.

Start here

## Send us one inspection test plan.

Send one document your people work to today: an ITP, an inspection report, a final check sheet. We build it into a draft workflow and a branded sample report, and show you what your team would see. Back to you within 24 hours.

Name

Work email

Company

Your role

Whose ITP do you work to? Select...Our ownOur clients', a different one eachA mix of bothISO 9001ISO 17025ISO 17020ISO 3834 or weld standardsAS 3788 or pressure equipmentNot sure yet

Where the plan lives now Select...ExcelWordPDFPaperSharePointERP or CMMSDedicated QA softwareOther

Where does the plan slow the job down?

Your document stays confidential. We use it only to build your draft, and we do not train models on it. [How we handle your data](https://stratumsoftware.io/privacy.md). Client details in it? Redact them, or send a blank template. The layout is all we need.

Attach a document (optional: PDF, Word, Excel or a photo, max 4 MB)

Stratum Track is built and run from **Perth, Western Australia**. The person who reads your document is the person who builds your workflow.

---

Stratum Software Pty Ltd, Perth, Western Australia. Machine-readable facts: https://stratumsoftware.io/facts.json
