The Request third-party risk due diligence option lets an employee submit a structured request that starts due diligence on a third party or engagement. The supported request types are onboarding a new engagement, reassessing an existing engagement, reassessing an existing engagement for contract renewal, and offboarding an engagement with due diligence. Each type determines the questions the requester answers and the assessment activity that follows.
Duplicating an engagement is a record-management operation and cancelling an engagement is a lifecycle action; neither requests due diligence, so both are excluded. Offboarding without due diligence also exists as a lifecycle path, but it is not offered here because the selection is specific to due-diligence requests.
The value of this design lies in its consistency. A business user who wants to engage a supplier does not need to understand questionnaires or tiering; the request captures context such as the engagement, the products or services involved, and the business owner, and the risk team then drives the assessment. Reassessment variants allow existing relationships to be re-evaluated at renewal without creating duplicate third-party records.
[Reference: Study Guide – Third-party Supporting Processes: Due Diligence Requests and Engagement Lifecycle.]
Contribute your Thoughts:
Chosen Answer:
This is a voting comment (?). You can switch to a simple comment. It is better to Upvote an existing comment if you don't have anything to add.
Submit