A schedule of conditions aims at exhaustively defining the Spécification S basic of a produced or a service to be realized. In addition to the basic specifications, it describes its methods of execution. It defines also the objectives to be reached and aims to well tallying a mission. In-house, the schedule of conditions is used for to formalize the Besoin S and to explain them to the various actors to make sure that everyone is of agreement. It is then used to select the Prestataire and to organize the relation throughout the Projet. He is regarded as a Référentiel Contractuel divided by the person receiving benefits and the internal team, which makes a fundamental tool of it of Communication of the Project manager.

the schedule of conditions is a contractual document it acts as contract between the general Obligation of information with respect to its customer (Code of consumption, Livre Ier, Ier title, Ier chapter).

Technical part in a Schedule of conditions

The technical part of a Schedule of conditions must be limited to to enumerate the proven technical constraints . The recourse to such or such waiter of applications, the operational budget, the platform of deployment for example. The most current error is to confuse Préférence S and Contrainte S. This causes incomprehension and handing-over of causes as late as dramatic. To cure this problem, it is necessary to entrust the drafting of the schedule of conditions to nona technician and to provide the same level of detail for each besoin.

One can also call upon an expert to validate the coherence of the schedule of conditions. That reduces considerably the risks for a budget ranging between 300 and 500 euros.
A schedule of conditions consists of 2 great parts a functional tree structure and a table of functional analysis: it is the functional schedule of conditions. A schedule of conditions must enumerate functions of service. The specifications are a specimen of what the customer must know about his project and what it will consume.

Hatim Hammouch

Example of schedule of conditions of an Internet site

• Context
• Object of the project
• Organization of the project
• Steering committee
• Task force
• Control of work
• Control of work
• Providing
• Environment the project
• Existing functional
• Existing technique

; Chapter 2 - Description of the future site

• Perimeter of the project
• Positioning of the future site
• general Description of the project
• Description of the functional needs
• functional Requirements in “face office”
• functional Requirements in “back office”
• functional key Points
• Description of the technical needs
• technical Architecture
• software Configuration
• hardware Configuration
• Safety
• Taken again existing

; Chapter 3 - Awaited services

• Presentation of the services awaited
• Framework of the answer
• general Information
• Documents to give at the time of the invitation to tender
• Schedule price
• Selection criteria
• Requirements
• technical Requirements
• ergonomic Requirements and graphs

; Appendices ; Contact

Source: " Project control web" Eyrolles edition, second edition.

External bonds

• detailed Explanation of the components of a schedule of conditions

• PMToolbox: Resources and tools for the management of project
• DOCALIS: Tool for drafting of schedule of conditions Internet on line and paying