{"revision":"c10276e953456835cdbb1f3a60d58ae1980be353","document":{"id":18460,"path":"governance-risk-compliance/third-party-risk-management/tprm-create-engmt-form.md","title":"Create New Third-party engagement form","bundle":null,"doc_type":null,"release":"australia","body":"\n# Create New Third-party engagement form\n\nUse the create new third-party engagement form to capture all the information that you need to create a third-party engagement record in Digital resilience third-party registers using Third-party Risk Management. As a third-party risk assessor you can create a third-party engagement record.\n\n\n
\n\nField\n\n\n\nDescription\n\n
\n\nName\n\n\n\nUnique name for the engagement. Ideally, mention the product or service that is the subject of the engagement.\n\n
\n\nThird party\n\n\n\nThe third party for whom you are creating this engagement record.\n\n
\n\nType\n\n\n\nType of product or service to be provided by the engagement organization.\n\n
\n\nStart date\n\n\n\nEnter start and end dates to define how long the engagement is valid.\n\n
\n\nEnd date\n\n\n\nPreferred dates for the beginning and end of interactions with the third party.\n\n
\n\nStatus\n\n\n\nSelect the current status of the engagement. Available options are:\n\n - **Active**\n- **Onboarding**\n- **Prospect**\n- **Active unauthorized**\n- **Terminated**\n- **Onboarding rejected**\n\n
\n\nRisk rating\n\n\n\nDisplays the risk rating assigned to the engagement after an assessment has been performed.\n\n
\n\nEngagement tier\n\n\n\nThe tier used for this engagement.\n\n
\n\nAnnual spend\n\n\n\nThe annual monetary spend associated with this engagement's services.\n\n
\n\nEngagement manager\n\n\n\nSpecify the person who will monitor, prioritize, and act on responses to external questionnaires, issues, and tasks. Select the lock to lock/unlock the field.\n\n
\n\nBusiness owner\n\n\n\nSpecify the person who is familiar with the engagement organization and the product or services that will be engaged. Select the lock to lock/unlock the field.\n\n
\n\nNotes\n\n\n\nEnter text that describes the engagement to other users.\n\n
\n\nThird-party engagement: Contact\n\n
\n\nStreet, City, State/Province, ZIP/Postal code, Country, Phone, Fax\n\n\n\nStandard contact information for the engagement organization.\n\n
\n\nLatitude and Longitude\n\n\n\nThe **Latitude** and **Longitude** values are used to mark the location on the Risk concentration map. See [TPRM Risk concentration map](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/governance-risk-compliance/third-party-risk-management/tprm-ws-risk-concentration-map.md).\n\n
\n\nRisk ratings\n\n
\n\nComputed risk rating\n\n\n\nCalculated **Computed risk rating**. This field is auto-filled.\n\n The value is overall risk rating for the third party, calculated after the assessment by rolling up all of the TPR assessors' risk ratings.\n\n
\n\nOverride risk rating\n\n\n\nOption to override the computed rating.\n\n If you select the check box, then specify the following values:\n\n- Overridden risk rating: Select the new risk rating.\n- Overridden on: Date that overridden risk rating or justification is updated.\n- Justification: Enter the reason for overriding the value.\n\n
\n\nOverridden risk rating\n\n\n\nRating that has been manually changed by a user, overriding the rating that was calculated by a system. Available options are:- **1 - Very High**\n- **2 - High**\n- **3 - Moderate**\n- **4 - Low**\n- **5 - Very Low**\n\n
\n\nOverridden on\n\n\n\nDate that overridden risk rating or justification is updated.\n\n
\n\nJustification\n\n\n\nReason for overriding the value.\n\n
\n\nAssessment risk rating\n\n\n\nRisk rating for the assessment. This field is auto-filled.\n\n
\n\nEngagement risk rating\n\n\n\nRisk rating for the engagement. This field is auto-filled.\n\n
\n\nSubsidiary risk rating\n\n\n\nRisk rating for the subsidiary. This field is auto-filled.\n\n
\n\nRisk intelligence rating\n\n\n\nScore that corresponds to the likelihood and consequence of a risk event. This field is auto-filled.\n\n
\n\nRelated lists on the form\n\n
\n\nEngagement contacts\n\n\n\nEngagement contacts for the third-party engagement.\n\n
\n\nBusiness services\n\n\n\nBusiness services related to the third-party engagement.\n\n
\n\nTiering assessments\n\n\n\nTiering assessments for the third-party engagement.\n\n
\n\nRepeating assessments\n\n\n\nRepeating assessments for the third-party engagement.**Note:** You can create repeating assessments if you are using the classic assessment engine. You can configure rules that auto-generate and send questionnaires and doc requests to engagements and third parties using the Event-driven management feature if you are using the Smart Assessment Engine. For more information, see [Configure a risk assessment to recur on a schedule](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/governance-risk-compliance/third-party-risk-management/define-repeating-vend-assess.md) and [Event-driven management — automate assessment processes](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/governance-risk-compliance/third-party-risk-management/tprm-event-drvn-mgt-rule-create.md).\n\n
\n\nAssessments\n\n\n\nAssessments for the third-party engagement.\n\n
\n\nThird-party risk areas\n\n\n\nRisk areas related to the third-party engagement.\n\n
\n\nIssues\n\n\n\nIssues related to the third-party engagement.\n\n
\n\nTasks\n\n\n\nTasks related to the third-party engagement.\n\n
\n\nEntity types\n\n\n\nEntity types related to the third-party engagement.\n\n
\n\nDigital resilience information\n\n\n\nDigital resilience information for the third-party engagement. You can add the following parameters:- Name\n- Third party\n- Identification code of ICT third-party service provider\n- Type of code to identify the ICT third-party service provider\n- Name of the ICT third-party service provider\n\n**Note:** When the Type of code is set to LEI and you enter or update the identification code, the system validates it against the GLEIF database and auto-populates the Legal name and Country of headquarters fields. For more information, see [Validate Legal Entity Identifier codes for DORA reporting](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/governance-risk-compliance/third-party-risk-management/tprm-valid-lei.md).\n\n
"}}