You are able to designate certain tags to indicate why interpreters are removed from requests by your scheduling team. If a user with Admin or Scheduler authority removes an interpreter from an request, a pop-up will appear for you to enter a reason. This is just like the pop-up for you to enter a reason for a void/cancellation.
If you do not wish to track this, simply leave it as No Reason. If you wish to track this, you will need to designate tags for this purpose. This is done through Administration – Maintain Tags. By double-clicking in a field, you are able to designate a tag as Default (meaning it can be entered on a request), Voided Reason Only or Unassigned Reason.
While the voided tags do show on the request, the unassigned reason tags do not show on the request. That is because multiple interpreters can be unassigned for various reasons. To see the reason for an interpreter who has been removed, you must look in the audit log for the request.
In addition, there are reports that can help you to track and manage these unassignment reasons.
The "Interpreter Unassigned Reasons" report will be deployed to your site that shows:
1. By Unassigned Reason the request, interpreter, date of service, date that the interpreter was unassigned and the scheduler.
2. By interpreter the request, unassigned reason, date of service, date that the interpreter was unassigned and the scheduler.
3. By scheduler the request, interpreter, unassigned reason, date of service and date that the interpreter was unassigned.