A project report reflects the outcomes of a project. It is written by an author who should be appointed on commencement of a project.

A project report is published to an international community. It should be concise and written for a predominantly business-level readership. Industry jargon should be avoided. It is good practice to include a glossary.

Additional project material may be published alongside a project report. This may include technical documentation and user research including audio and video content. The publication of audio and video content must be in accordance with express consent given by individuals who have participated in the user research. The full names and other identifying information of individuals who have taken part in user research must not be published. Note that this also applies to presentations that relate to the project.

In the spirit of collaboration, all participants in a project should reach a consensus on the content of a project report, in a timely manner. However, participants may hold differing views and these should be fairly and objectively reported, along with disclaimers if appropriate.

A project report should be approved and signed off by the participants as a true reflection of the outcomes. All agreed feedback and review dates will be adhered to, ensuring timely issuing of project reports. If a minority of participants are unwilling to sign off the paper, the OIX Executive Committee can provide an arbitration function. The OIX Executive Committee approve all project reports before they are published to ensure they adhere to the OIX vision and mission and have the right to remove a white paper that has been published.

The project report should be accompanied by a short abstract for publication on the OIX website.