---
title: "Inspection & Test Plans: Better ITP Evidence at Handover | eviFile"
description: Stop chasing ITP evidence at handover. See how structured, live records can improve traceability, assurance and visibility throughout delivery.
---

[![header-logo](https://blog.evifile.com/hubfs/evifile-2026/images/header-logo.svg)](https://evifile.com/)

- [Home](https://evifile.com)
- [Who we support](https://evifile.com/who-we-support)
- [Solutions](https://evifile.com/solutions)
- [How it works](https://evifile.com/how-it-works)
- Resources 
    - [Blogs](https://blog.evifile.com/resources/blog)
    - [Case Studies](https://blog.evifile.com/resources/case-studies)
    - [White Papers](https://evifile.com/resources/whitepapers)
- [About eviFile](https://evifile.com/about)

[Book a demo](https://evifile.com/book-a-demo)

[Back to blog](https://blog.evifile.com/blog)

Progressive Assurance

# Inspection & Test Plans: Stop Searching for Evidence at Handover

[evifile](https://blog.evifile.com/resources/blog/author/evifile)

Sector

- Rail

Services

- Progressive Assurance

In this story

 In This Story +

An approved ITP tells you what is supposed to happen. It does not necessarily tell you whether it did, or make the evidence easy to find when someone needs to prove it.

That distinction matters on major programmes, where an ITP can be properly reviewed, approved and stored in the CDE while the information needed to demonstrate compliance is being created across site inspections, test results, photographs, forms and other systems.

For much of delivery, there may be little reason to question this. Inspections are taking place, tests are being completed and work is progressing. The problem becomes apparent when someone needs the complete picture and discovers that proving what happened means piecing together information from several places.

Handover is often where that becomes impossible to ignore.

![contractor on site holding laptop](https://blog.evifile.com/hs-fs/hubfs/contractor.png?width=1120&height=280&name=contractor.png)

## The plan isn't the problem.

ITPs perform an important role. They define what needs to be inspected or tested, the relevant acceptance criteria, responsibilities and, where required, the points at which work needs to be witnessed or held.

The difficulty comes after approval, when the plan and its supporting inspection record begin to separate.

Consider a typical inspection. The work is checked, photographs are captured and an issue is identified. Remedial work follows and a subsequent inspection confirms that the item can be accepted.

Six months later, could someone who was not there follow that same history? Could they trace the original requirement through to final acceptance without opening several systems or asking the people involved?

Across one inspection, that may only cost a little time. Across thousands of inspections, tests, assets and work packages, it becomes a much larger assurance problem.

## Handover is just where you find out.

Missing information is not always the issue. Often, the information is there, but the relationships between it are difficult to see.

A photograph might exist without a clear connection to the inspection it supports. Test results may be held separately from the ITP requirement. An activity can appear complete while supporting information remains outstanding. Where something failed and was subsequently corrected, the route to final acceptance may depend on somebody knowing where to look.

These gaps are easier to resolve while the work is active and the people involved still have the context. Leave them until handover and teams are no longer assuring the work as it happens; they are reconstructing its history.

That is why a folder full of records is not necessarily the same thing as assurance. What matters is whether those records can demonstrate what was required, what happened and what supports the outcome.

## What changes when the ITP stays connected to the work?

The alternative is not to replace the ITP or the CDE. It is to retain a clear line between each requirement and the work completed against it.

That gives teams a clearer view of:

- Outstanding inspections and tests that still require attention
- Activities recorded as complete where supporting information is missing
- Results that have not met the agreed acceptance criteria
- Corrective actions and the subsequent inspection or test that closed the issue
- Evidence associated with the relevant asset, location or work activity

Instead of waiting for handover to expose the gaps, teams can see assurance status while there is still an opportunity to act.

That is the principle behind progressive assurance: building confidence in the final record throughout delivery rather than trying to establish it at the end.

[Explore Progressive Assurance](https://evifile.com/progressive-assurance)

## Seven million checks, one connected record.

The need for this becomes more obvious as the volume of information grows.

During the Midland Main Line electrification programme, SPL Powerlines used eviFile to capture more than **7 million digital quality checks**, including quality check sheets and Inspection & Test Plans.

At that scale, the question is not simply where millions of records should be stored. It is how they retain enough context to remain useful: which requirement they relate to, where the work took place, what the outcome was and what still needs attention.

[Read how SPL Powerlines approached Progressive Assurance](https://blog.evifile.com/case-studies/how-spl-powerlines-delivered-progressive-assurance-on-major-rail-project-upgrade)

It is a challenge that extends beyond one programme. eviFile is used across infrastructure and energy environments involving organisations including AtkinsRéalis, Network Rail, TRU, Drax and Cadeler, where large volumes of delivery information need to remain usable long after the activity has taken place.

The technology matters, but so does the principle behind it. Assurance is more useful when it is created as part of delivering the work, rather than treated as a separate exercise that follows it.

![electric power lines in field](https://blog.evifile.com/hs-fs/hubfs/power%20lines.png?width=1028&height=257&name=power%20lines.png)

## The record should already exist.

This is where eviFile changes the way ITP information can be managed.

ITP requirements, inspections, tests and supporting evidence can be connected within the same structured workflow, with information captured against the work it relates to. That makes it possible to understand assurance status during delivery while retaining the history behind the final outcome.

The purpose is not to create more digital records. Most major programmes already have more than enough information. The opportunity is to make that information easier to trust, interrogate and use.

By the time handover arrives, the team should not be discovering whether the evidence exists or reconstructing how an item reached acceptance. The record should already show them.

[See how eviFile supports Digital Handover](https://evifile.com/digital-handover)

## Handover should be confirmation, not investigation.

If establishing ITP status still means opening documents, checking trackers and searching across different systems, there is a disconnect between the plan and the evidence being created during delivery.

Bringing the two together earlier means handover becomes what it should have been all along: confirmation of an assurance record built throughout delivery, rather than an investigation into work that has already happened.

[![ITP blog banner-final](https://blog.evifile.com/hs-fs/hubfs/ITP%20blog%20banner-final.png?width=1032&height=258&name=ITP%20blog%20banner-final.png)](https://evifile.com/book-a-demo)<https://evifile.com/book-a-demo><https://evifile.com/book-a-demo>

Found this useful? Share it with your team.

 Share article

## Talk to us about your ITP process.

Whether you’re dealing with disconnected evidence, manual tracking or handover gaps, we can show you how eviFile could help.

Keep reading

## Related articles

[All articles](https://blog.evifile.com/resources/blog)

### [Progressive Assurance Your Project Runs on WhatsApp (Until It Doesn't) How to reconnect P6 to execution and eliminate shadow systems Your master programme lives in P6. It shows what was intended. Then execution begins.... evifile September 24, 2026 7 min Read](https://blog.evifile.com/resources/blog/your-project-runs-on-whatsapp-until-it-doesnt)

### [Progressive Assurance CDEs are Document Platforms. You need a Data Platform. Here's the paradox: CDEs are working exactly as designed. They're managing documents beautifully. Organising files. Controlling versions.... evifile September 24, 2026 7 min Read](https://blog.evifile.com/resources/blog/des-are-document-platforms.-you-need-a-data-platform)

### [Progressive Assurance eviFile: The Complete Delivery Platform Most people know eviFile for one thing. Data Governance. Or Progressive Assurance. Or Handover. But that’s underselling what we actually built. ... evifile September 24, 2026 7 min Read](https://blog.evifile.com/resources/blog/evifile-the-complete-delivery-platform)

[![footer-logo](https://blog.evifile.com/hubfs/evifile-2026/images/footer-logo.svg)](https://evifile.com/)

© 2026 eviFile. Define it. Control it. See it.

- [Privacy](https://evifile.com/privacy-policy)
- [Contact](https://evifile.com/contact-us)

```json
{
  "@context" : "https://schema.org",
  "@type" : "BlogPosting",
  "author" : {
    "@type" : "Person",
    "name" : "evifile",
    "url" : "https://blog.evifile.com/resources/blog/author/evifile"
  },
  "dateModified" : "2026-09-28T18:56:41.926Z",
  "datePublished" : "2026-09-24T08:32:17.000Z",
  "headline" : "Inspection & Test Plans: Better ITP Evidence at Handover | eviFile",
  "mainEntityOfPage" : {
    "@id" : "https://blog.evifile.com/resources/blog/progressive-assurance/inspection-test-plans-better-itp-evidence-at-handover",
    "@type" : "WebPage"
  },
  "publisher" : {
    "@type" : "Organization",
    "logo" : {
      "@type" : "ImageObject",
      "url" : "https://blog.evifile.com/hubfs/evifile-2026/images/eviFile-logo-_blue.png"
    },
    "name" : "eviFile"
  }
}
```