Introduction

The members of the RIXML Buyside Working Group have been meeting to discuss issues surrounding usage of their readership data and to develop a set of usage reporting standards that buyside and sellside firms can use to form their bilateral agreements. The members of this group worked with a number of sellside firms, including RIXML firms and others, to define a set of usage reporting standards that address the needs of both traditional static research content (PDFs, etc.) and the newer, more interactive research content. Significant progress has been made to understand the similarities and differences of the various delivery methods and to set standards that firms can choose to use as the basis of their agreements with their research partners.

Because the needs of all firms are unique, the goal of this initiative was not to create a boilerplate agreement; instead, the goal is to provide a set of standards that buyside and sellside firms can use as the basis for their discussions when developing bilateral agreements regarding how sellside firms can use buyside firms’ readership and content access data of research content. 

This document does not represent the views of any individual firm or of RIXML; instead, it is meant to identify the key usage reporting-related issues firms will need to discuss as they develop their bilateral agreements and to highlight areas where there seems to be broad consensus – and where there does not.

Working document and comment period

While we have taken great care to gather and incorporate significant input during the course of this project, we also recognize the importance of having a comment period to provide a chance to obtain additional feedback. This comment period will begin on August 16, 2024 and end on September 15, 2024. A final version of the document will be posted after that date.

The current version of the RIXML Usage Reporting Standards can be found here.

Comment period feedback

Please reach out to This email address is being protected from spambots. You need JavaScript enabled to view it. with any comments, questions, or feedback.