Rejected Requests Report

The Rejected Requests Report provides a record of all Academic Requests that have been rejected by an institution before being progressed into a Content Request. This report acts as an audit trail for declined requests, helping institutions keep track of what was rejected and why.

You can navigate to the Rejected Requests report by selecting the Reporting tab on the left hand side menu on the dashboard, and choosing the report from the drop-down menu, and create the report by selecting which usage data date range, and clicking Download Report. 

When a Request Can Be Rejected
Academic Requests can only be rejected when they meet both of the following conditions: 

• The request came from: 
– the Academic Request Form (ARF), or 
– an RLMS integration (e.g., Talis Aspire)

• The request is still located in New Academic Requests and has not yet been progressed into an active Content Request.

 
What Appears in This Report 
The Rejected Requests Report includes:

• All Academic Requests rejected by the HEI 
• Any rejection reason selected at the time of rejection 
• Notes added by the user 
• Basic request details (e.g., course, title, requester)

 

What Does Not Appear
The following items do not appear in this report:

• Content Requests (these cannot be rejected - only deleted) 
• Deleted requests of any kind 
• Requests rejected after link generation or after progression to active status 
• Failed RLMS syncs or incomplete draft requests

Deleted Content Requests are not reported anywhere in DCS 2.0.