In order to deal with inconsistent information during software development processes (or other similar processes) it is necessary to model the kind of inconsistencies in an appropriate way. Based on such a model ways to represent inconsistencies and methods to deal or manage inconsistent information can be adopted. In this short position paper we sketch a possible model of inconsistency in information about software development processes and briefly describe how a graph rewrite approach can be applied to describe the management of such inconsistencies (cf. for information concerning the particular graph grammar approach). The process of handling inconsistencies is usually divided in two parts. First of all, one needs to detect an inconsistency and then, it can be dealt with in some way. In two recent papers , , we have discussed the detection of inconsistencies in the context of the ViewPoints framework . In this position paper, we discuss what can be done if inconsistencies occur at a general level. Thus the reminder of this statement is organized in the following way. First we briefly discuss a particular model of inconsistency in software development process which is based on the idea to follow all possible and impossible traces of development actions taken, at least conceptually. Next we show how such traces can be represented as graphs, and modification of these graphs can be represented by graph rewrite rules. The next step is then to show how graph rewrite rules can be systematically derived (not automatically yet) from the representation of the aforementioned development traces.