The research presented in the literature thus far on process deviations, inconsistencies and general nonconformance have all been very generic, process wide methodologies. Their application has also been limited to one domain, such as the software, business or manufacturing process. In this paper we differentiate between activity/general process nonconformance and resource based non-conformance which we treat as different and the mechanism for testing is treated in a different way. This research is aimed at identifying instances of non-conformance between an instantiation of a generic process and its associated process model by examining only the resources specified and observed. We propose a conceptual design model illustrated with a simple case study on this topic which although is not based on a software engineering process, illustrate simply how our model can benefit a real world situation across many domains alongside software engineering.