Annual Needs Assessment - Speaker Bureau
Written by Michelle Henley
Updated at January 22nd, 2024
Table of Contents
Use Case
- Annual Needs Assessment - Speaker Bureau (ANA) request type is used to plan priorities, budget allocation, and resources for the upcoming calendar or fiscal year.
- This request type differs from the Consulting - ANA in that it includes specific speaker individuals, while the Consultant - ANA includes only information about the planned engagements and no individual consultants.
Key Features
-
Annual Needs Assessment - Speaker Bureau requests are separated into two sections:
- Activity Details section to capture the details related to the event.
- Speaker Details section to capture the details of the consultants.
Things to Note
• Submitting
- An ANA - Speaker Bureau request allows the submitter to identify speakers that will take part in different speaking engagements.
- There are no payment amounts associated with this request type and the request does not take into consideration the type of support to be provided.
- An ANA - Speaker Bureau request can be submitted with or without a speaker, with a capability to add speakers post submission or approval of the request.
- Integrate with Veeva or Reltio (IQVIA) Master Data Management Providers (MDM) to allow search and selection of HCPs from those MDM databases.
- Changes can be made after the request is approved. However, that will require the request to be re-approved by all the approvers based on the workflow configuration.
- Speakers can be added to the request after the activity is fully approved. Newly added speakers will follow the approval workflow as configured during the implementation process.
- Initially selected approvers can not be changed at the time of re-submitting the activity or the consultants.
• Approving
- The approver(s) needs to approve the activity and speakers separately. The activity must be approved first before taking approved action on the speakers.
- Additional speakers can be added after the initial submission which are subject for review based on the approval workflow configuration.
- Approvers can approve or reject the activity or recipients. Once an activity is rejected, it moves all speakers to canceled status. A Rejected request can not be re-submitted.
- Approvers also have the ability to request for more information from the submitter on the activity and/or on individual speakers during the approval process. In such instances, the activity or speaker needs to be re-submitted by the submitter after the updates have been made. Depending on the approval workflow configuration, the request will go back to the same approver for review or approval workflow can be initiated from the beginning.
• Oversight
- In-request screening using either Refintiv or RDC to compare individual and organization names against watchlist data.
• Request Features
Key Features
- Editor Collaboration allows different users to collaborate on filling details of the engagement.
- Approver Collaboration allows one of many approver collaborators to approve in any one approval step.
- Automated Approver Collaboration is used to automatically assign approver collaborators.
- Assign tasks to yourself, other users, or even third-parties.
- Easy-to-follow Request History tracks a complete audit trail of the changes and actions taken on the request throughout the approval process.
- Request Version Comparison allows for the ability to compare between different versions of the request if updates are made to the request before, during, and after the approval process.
- Business Owner configuration allows for requests to be submitted on behalf of someone else or to identify the actual business owner of the request.
Configurable Components
|
Request Configurations |