Use of VT29 check lists

There is no requirement to use the check sheet. Never has been. I've always used the VT40 and will be using blank ones when we make the switch next week.

I still use the VT40 for any testing.

I'm using the vt29 - It has replaced the vt40. Wording from dvsa is;

Inspection checklists

The current MOT inspection form (VT40) has been replaced by the new VT29 and VT29M inspection checklists.

The new checklists can be found under the ‘MOT forms’ link on your homepage

Link;

www.gov.uk/guidance/use-the-new-mot-testing-service

Yep. Do what you want, only passing on information about the vt29 which was what the original poster was asking

I printed out a load of VT29s when we started, since the VT 40s were no longer going to be available, But thanks to pete's link I will be using the VT40s again as the VT29s only record a small part of the information I want to keep to hand on the vehicle.

Yes but personally don't see the point of having both on comp 2?

Thanks guys

Considering that the VT29 shows VOSA at the top and separate brake reading boxes for imbalance at the bottom I don't think they're suitable for Comp 2. Shock absorbers are shown as an exterior item (remnants of the bounce check?). Not only are we trying to create our own VSI database, perhaps we should also create a checklist that actually relates to the test as it stands today.

NO prizes but is anyone up for it?

About MOT modernisation
It’s being done to update and simplify MOT processes and policies to help improve road safety and test quality.
---------------------
Using the new MOT testing service
• the VT40 and vehicle specific information (VSI) have been removed
• they didn’t use it
• it wasn’t reliable
• they preferred to use other data services

VT40 for brake test entry's with Date of first use, Cylinder capacity, Make/Model, Fuel Type, VIN, REG, Colour Issuers name, Date. Time. RESULT = MORE TIME CONSUMING & LESS EFFICIENT, is not an improvement.

vehicle specific information (VSI) TESTERS NEED THIS SPECIFIC INFORMATION under a DUTY OF CARE result = affects road safety, Testers safety, cars safety & has a negative effect on test quality.

WHAT OTHER DATA SERVICES? RESULT = autodata have yet to provide brake weights & abs light info on Autodata updates: 13916 Vehicle updates Since: 01/2015 Last update: 30/06/2015 272 Feature enhancements Since: 01/2015 Last update: 13/08/2015...they still want to sell you WALLCHARTS for the information we need for testing!
Nominated testers (NTs) should refer to manufacturer or other reliable data (eg brake test weight charts, technical manuals etc) when a vehicle weight isn’t made available.
Anti-Lock Braking and Electronic Stability Control Systems, Supplementary Restraint Systems (SRS, electronic parking brake (EPB), electronic power steering Malfunction Indicator Lamp (MIL), Fluid/Gas/Air Suspension, RESULT = MOT PROCESS BECOMES EXPONENTIALLY COMPLICATED (AND IN YEARS TO COMES UNWORKABLE; with the systems in play on cars today even the dealers cannot spec check them accurately)!
----------------------------------------------
When not to use contingency testing
Under existing MOT scheme rules, if you have any problems (eg software, broadband or IT equipment failure) using the new service you:
• have up to one hour after a vehicle’s test to enter the test results
• must enter these results before the vehicle leaves your vehicle testing site
•
IF YOUR SMOKE HEAD GOES DOWN you can revert to visual testing smoke for one day, and then stop testing
IF YOUR RBT GOES DOWN, USE YOUR Decelerometer
in most cases you can limp on...less you get a power cut. WITH MODERNASATION eg software, broadband or IT equipment failure YOU HAVE ONE HOUR!
phoned on this one & Atos informed; I will be given a contingency code...THIS NEEDS CLARIFICATION = When not to use contingency testing (especially in view of the current situation)

Conclusion:
Testers need VT40 with Date of first use, Cylinder capacity, Make/Model, Fuel Type, VIN, REG, Colour Issuers name, Date. Time
Testers need VSI on this VT40
And clarification of ' When not to use contingency testing'