Test Method Version Control That Stops Old Procedures Running
Author
Neerav Singh
Technical Product Specialist
Author
Neerav Singh
Technical Product Specialist
Reading Time
3 min read
Test Method Version Control That Stops Old Procedures Running
Revision D of a test procedure can be approved on day 1 and still lose to revision B on the day 2, because revision B is the laminated copy taped to the rig.
The pace of external change makes that gap expensive. The figures below come straight from regulators and assessors.
| What changed | How often or how much | Source |
|---|---|---|
| UN vehicle regulations | WP.29 meets 3 times a year to adopt amendments | UNECE |
| Amendments voted in one session | 27 amendments to existing UN Regulations plus 1 new regulation in June 2025 | EU Council decision for WP.29 session 196 |
| Where assessors find problems | Around 38% of A2LA ISO/IEC 17025 nonconformities concern equipment records, with technical records also in the top 5 | A2LA findings published by Ideagen |
Many version control failures in test labs begin with words. One engineer says "current" and means the latest draft. Another says "released" and means the version a customer approved last year. The quality manager says "obsolete" and the technician hears "older but still fine for this rig". Fix the vocabulary and a large part of the process fixes itself.
What follows is a working glossary of the 9 terms that decide whether old test methods keep running. Each entry gives a plain definition, the way labs usually get it wrong and what good control looks like in practice.
Effective date
The date a revision becomes the one every new test must use. Approval and effectiveness are separate events, and many labs record only the first.
A revision approved on 1 March with no effective date leaves technicians guessing. Some switch immediately, others finish the week on the old version and a few never hear about the change. A stated effective date, often set 1 or 2 weeks after approval to allow training, gives everyone the same line to cross.
Superseded
A revision that has been replaced by a newer one but may still apply to tests already in progress or to a customer who contracted against it. Superseded methods stay visible and searchable, clearly labelled with what replaced them and when.
Treating superseded and obsolete as the same word causes real damage. A lab that deletes superseded revisions loses the ability to show an assessor exactly which method produced a report issued 2 years ago.
Obsolete
Obsolete describes a revision that must never be used again for new work. ISO/IEC 17025 clause 8.3.2 requires obsolete documents to be withdrawn or clearly marked so nobody uses them by mistake.
The classic obsolete document is a printout. A technician prints the procedure during induction, keeps it by the shaker and carries on using it long after 2 newer revisions are released. Printed copies should carry the revision, the print date and the words "uncontrolled when printed", and the lab should collect them at every release.
Controlled copy
Any copy of a method whose distribution the lab tracks and updates. A procedure on the controlled system is a controlled copy. A PDF emailed to a supplier, a screenshot on a phone or a data sheet saved to a desktop is not.
Data sheets and calculation templates are the controlled copies labs forget most often. A spreadsheet with an embedded acceptance limit of 5% keeps calculating against 5% after the procedure moves to 3%, and the report it produces still says pass. An independent battery and HV lab that later moved to TITAN found its test configurations lived only in individual files rather than a shared repository, so every new programme started from scratch. A shared catalog of templates generated from the released method gave it one approved starting point for every test type.
Point of use
The place where the work happens: the rig, the chamber, the track or the bench. Clause 8.3.2 expects the current revision to be available there.
The strongest control puts the procedure inside the digital test record the technician is already filling in, so the steps, limits and checklists on screen are always the released revision. In TITAN's test catalog, procedures move through approval workflows, every site sees only the released version and an audit trail records who released what and when.
In-flight test
A test that was booked, planned or started under one revision when a newer revision became effective. Many version control policies ignore this term, which is how labs end up running half a test on revision C and half on revision D.
Clause 7.2.1.3 expects a lab to use the latest valid version of a method unless that is not appropriate or possible. Continuing an in-flight test on the older revision is allowed, but only as a recorded decision with a justification, often agreed with the customer. Linking every booking to a specific revision lets the scheduler list every affected test the moment a new revision is released, so the method owner can decide test by test.
Normative reference
The external standard an internal procedure implements, such as a UN regulation, an ISO method or an SAE recommended practice. Each internal procedure should record the reference and its exact revision.
UN regulations evolve through series of amendments and supplements with transitional provisions, and WP.29 adopts changes 3 times a year. Labs that track normative references on a watch list, reviewed monthly against session outcomes and standards body publications, see changes coming months before they enter into force. Without a watch list, the first warning usually comes from a customer or an assessor.
Type approval work makes this term unavoidable. Each report must cite the version of the regulation that applied to that vehicle on that date. A national type approval authority running homologation testing across several departments relied on disconnected systems and manual coordination before moving to TITAN, and producing audit ready documentation was a constant struggle. Unifying customer intake, test management and traceability in one connected system gave it audit ready documentation for each submission.
Method verification
Confirmation that a lab can correctly perform an established method with its own equipment and staff. Clause 7.2.1.5 requires verification before a method is introduced, and a significant revision to a standard method can trigger it again.
Verification records belong with the revision they cover. An assessor reviewing a revision D report will look for evidence that revision D was verified before the first revision D result was issued. A verification record from an earlier revision does not cover the new one.
Method validation
Proof that a method itself is fit for its intended use. Clause 7.2.2 requires validation for non-standard methods, lab-developed methods and standard methods used outside their scope or modified.
The difference from verification is simple to state. Verification checks that the lab can run a proven method correctly. Validation goes a step further and establishes that a new or changed method produces correct answers at all. Labs that modify a standard procedure to suit their fixtures often need validation and record only verification, and assessors catch it.
Putting the 9 terms to work
A glossary changes behaviour once it reaches the test record. For each test, the record should show:
| Term | What the test record captures |
|---|---|
| Effective date | Which revision was effective on the test date |
| Superseded and obsolete | Status of the revision used and the date it changed |
| Controlled copy | Template or data sheet version used to capture results |
| Point of use | Confirmation the released procedure was presented at the rig |
| In-flight test | Any decision to continue on an older revision, with approver |
| Normative reference | External standard and revision implemented |
| Method verification | Link to the verification record for that revision |
| Method validation | Link to validation where the method was modified or developed in-house |
Clause 7.5 asks for technical records detailed enough to repeat a test. Given that technical records already sit among the most common assessment findings, capturing these fields automatically when the test runs removes a whole category of risk. Most of this list overlaps with the controls a lab already needs for ISO 17025 accreditation.
Same words, same revision
Version control breaks down in conversation long before it breaks down in software. When a method owner, a technician and an assessor all mean the same thing by effective, superseded and in-flight, old procedures have nowhere left to hide.
Take these 9 definitions into your next quality meeting and ask each method owner to apply them to one live procedure. Any term they cannot answer from the record marks the next control to build. For labs running homologation testing against regulations that move 3 times a year, that shared vocabulary is what keeps every report tied to the revision that produced it.
FAQ
What is the difference between a superseded and an obsolete test method?
A superseded method has been replaced but may still apply to tests already in progress or contracted against it. An obsolete method must never be used for new work and must be withdrawn or clearly marked under ISO/IEC 17025 clause 8.3.2.
What is the difference between method verification and method validation?
Method verification confirms a lab can correctly perform an established method on its own equipment. Method validation proves that a new, modified or non-standard method is fit for its intended purpose.
How should a lab handle tests already scheduled when a procedure is revised?
Every scheduled test linked to the old revision should be flagged for review. The method owner then decides whether to move each test to the new revision or continue the old one with a documented justification, often agreed with the customer.
Ready to Keep Every Test on the Right Revision?
Bring procedure control, revision history and audit-ready test records together with TITAN.