I've spent a fair bit of time knocking checklists. I think they are unprofessional and quite unnecessary for internal process audit where all you should be doing is establishing compliance to document.
But Steven's checklist for vertical audit seems to be the exception to my rule and I think I'll follow his example in future. To keep on track and cover everything in this type of investigation is very difficult. In fact, in my esperience, you get pulled off line and never get back, so it's just another sample audit, when, in Steven's words, it should be a 'complete' vertical audit. As Claes says, it's the interfaces that cause most of the problems and typical documentation tends to ignore the interfaces, so we need a means to check them thoroughly.
I never heard the term 'vertical' audit before or any name for the activity. I would also like to hear more from you, Steven, on the subject.
rgds, John C