A project report is more than a project facts file. It profiles the project to a greater detail and is much closer to the reality. It often includes sections prepared by different agencies. Structure of a project report varies according to the purpose for which it is created and by whom. Just the same, reports have following sections, but not necessarily in this order.

1. Conditions of origin of a problem,

2. Definition of the problem,

3. Probable courses for settlement of the problem,

4. Characteristic conditions for which the solution is sought,

5. Environmental conditions within which the project can operate,

6. Skills required to detail, execute and operate the project,

7. Input-Output requirements for project execution and operations,

8. Cost-benefit ratio,

9. Risks and management of it,

10 Other implications,

11 Time schedules,

12 Human and material resources required.

A project report is used by both, the professional and the client, to focus on the goal. It becomes a holy document against which the creation is re-validated, from time to time, during planning, execution and operation. It provides a quality control bench mark, against which everyone: Client, Designers or Planners, Contractors Vendors, Overseeing agencies (government, social), Operators (managers), and Users, evaluate the performance.

A project profile once prepared, becomes a very significant document. Its unauthorized exposure destroys its patent-ness, and premature release to anyone (including an uncommitted client) creates a liability. Information contained in a project report is often exploratory, but is interpreted to be a promise or guarantee.