the description of the structure of the management bodies with the definition of the various roles and responsibilities, including those of the technical assistance units, is too perfunctory (14). This weakness may subsequently lead to conflicts between the various bodies responsible (15); in addition, the agreements are not precise enough in the matter of the management's obligation to draw up work schedules, annual budgets and implementation reports;
the agreements examined did not contain an automatic obligation to carry out evaluations during implementation, regular external audits and ex post evaluations;
too often the texts did not permit a clear distinction between the contributions made by the authorities of the recipient countries in terms of finance and in terms of the human and material resources made available to the projects;
In order to complete the range of customary arbitration possibilities, in the Court's view the financing agreements ought to contain a clause stating the consequences should one or the other of the signatories default on his commitment.
As from 1992 the Commission undertook to introduce a method of managing cycles of projects called Project Cycle Management. This approach should allow greater control of the management of each stage of the project from the preparatory phase to the ex-post evaluation. However, this approach was not followed in the case of the projects of the Third Protocols since it was introduced after they were drawn up. Nor was it used in a systematic fashion for the projects financed within the framework of the Fourth Protocols.
Information technology
In its Special Report No 3/91 the lack of an adequate system for the accounting and management of the Protocols was highlighted (16). The situation has not improved very much since then. First, there are inadequate links between the Commission's financial accounts (SINCOM, OLAS-Budget (17)) and the RAP application developed in-house by DG 1B for project and financial management data concerning projects under the Protocols. Secondly, RAP suffers from a number of weaknesses which reduce its value as a tool for management and control purposes. Conceptual weaknesses include difficulties in accounting for projects where several currencies are used, and, where a single project is financed from more than one Protocol, the necessity to account separately for each of these financing components.