--- sourceDocument: Yokohama Governance, Risk, and Compliance sourceDocumentLink: https://servicenow-prod.fluidtopics.net/r/yokohama/governance-risk-compliance Release : - yokohama ft:locale : - en-US ft:publication_title : - Yokohama Governance, Risk, and Compliance ft:clusterId : - grc bundleId : - grc workflow : - Technology --- # Create new control form # Create new control form {#ariaid-title1} * Release version: Yokohama * * Updated March 12, 2026 * * ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 4 minutes to read Use the create new control form to capture all the information that you need to associate a control with a third party or engagement using the Third-party Risk Management application. As a third-party risk admin, you can create a control. {#tprm-control-record-form__table_FloorForm__entry__2}{#tprm-control-record-form__mutliple-control-entity-co} | Field | Description | |-|-| | Name | Name of the control. | | Number | Unique identification number. | | Entity | Related entity. Note: If you change the state of the entity to Active from Retired state, then the manually created control on the entity also moves to the Draft state. | | Inherit from control objective | Option to indicate whether the control is created through item generation process. For more information, see [Multiple controls for a unique entity--control objective combination](https://servicenow-prod.fluidtopics.net/08QwDEGpjVsVOLGm_nk9MA "You can create multiple controls for a unique combination of an entity and a control objective to get granular control information."). | | Control Objective | Related control objective. | | Owning group | Group that owns the policy. | | Owner | User that owns the policy. Note: The owner is always added as a respondent. The control owner that you select belongs to the owning group. | | Sync with entity owner | Option to sync control with entity owner. | | Key control | Indicator that the control is a key control. | | Weighting | Value used to calculate the control score effectiveness. Based on the control weighting, in the control score effectiveness value is calculated ​ | | Status | Control status. Possible choices are: * Compliant * Non-compliant * Not applicable {#tprm-control-record-form__ul_ssp_wsx_rw} | | State | Control state. Possible choices are: * Draft In this state, all compliance users can modify the control. Only available when creating a one-off control. One-off controls are possible but not recommended. * Attest When the control is created from a control objective, controls are in this state. Note: When a control is set back to draft, the attestation is canceled. * Review Controls are automatically moved to review from the attestation phase. * Monitor In this state, all compliance managers can move the control from review to monitor. * Retired Compliance managers or administrators can move a control from Monitor to Retired. Note: When a control is retired: * Associated indicators do not run * Associated attestations are canceled * Changes to associated control objectives do not update the control {#tprm-control-record-form__ul_kcj_yhm_vfb} {#tprm-control-record-form__ul_rfr_55x_rw} | | Exempt | Mark the control as exempted. | | Function | List of options: * Standard control * Common control {#tprm-control-record-form__ul_kwc_45d_v2c} Note: All existing controls are termed as standard controls. You can convert a standard control to common and reverse its function as standard if you so require. However, by default all controls whether existing or created are standard. For more information, see [Convert standard control to common control and add reliant entities](https://servicenow-prod.fluidtopics.net/LydIelxLV4Fe18swSw1YuA "Mark a control as common and associate reliant entities to it. Test the common control tied to the primary entity. The reliant entities inherit the results of the common control."). | | Enforcement | List of options: * Mandated * Voluntary {#tprm-control-record-form__ul_onk_xsx_rw} | | Category | List of options: * Acquisition or sale of facilities, technology, and services * Audits and risk management * Compliance and Governance Manual of Style * Human Resources management * Leadership and high-level objectives * Monitoring and measurement * Operational management * Physical and environmental protection * Privacy protection for information and data * Records management * System hardening through configuration management * Systems continuity * Systems design, build, and implementation * Technical security * Third Party and supply chain oversight * Root * Deprecated {#tprm-control-record-form__ul_o1d_ysx_rw} | | Type | List of options: * Acquisition/Sale of Assets or Services * Actionable Reports or Measurements * Audits and Risk Management * Behavior * Business Processes * Communicate * Configuration * Data and Information Management * Duplicate * Establish Roles * Establish/Maintain Documentation * Human Resources Management * Investigate * IT Impact Zone * Log Management * Maintenance * Monitor and Evaluate Occurrences * Physical and Environmental Protection * Process or Activity * Records Management * Systems Continuity * Systems Design, Build, and Implementation * Technical Security * Testing * Training {#tprm-control-record-form__ul_rgw_zsx_rw} | | Classification | List of options: * Preventive * Corrective * Detective * IT Impact Zone {#tprm-control-record-form__ul_dyv_zsx_rw} | | Frequency | Frequency at which the control is tested. This field is for the control's testing and reporting purpose. List of options: * Event Driven * Daily * Weekly * Monthly * Quarterly * Semi-Annually * Annually {#tprm-control-record-form__ul_aqv_zsx_rw} Note: For information on the difference between the Frequency field for a control and the Attestation Frequency field in an entity, see [KB0694607](https://support.servicenow.com/kb_view.do?sysparm_article=KB0694607). | | Description | Description of the control. | | Additional Information | Additional information about the control. | | Attestation || | Attestation | Select from a list of options. * Other attestation types can be configured. * If this field is populated, then the Attestation Respondents field automatically becomes mandatory, and the owner is made the respondent. {#tprm-control-record-form__ul_z4x_2tx_rw} Note: If the user changes the attestation type in the control objective, all the related controls are changed also. | | Attestation respondents | * Users assigned to the attestation of this control. * Only a user with the sn_grc.user role can be added as a respondent. {#tprm-control-record-form__ul_x3v_4zc_rw} Note: When both the Attestation and Attestation respondents fields are set, attestations are created when you select Attest. | | Attestation frequency | Frequency at which attestations on the control are triggered. If the field has no value selected, then the associated entity's Attestation frequency value defaults to this field. Option for attestation frequency. * Daily * Weekly * Monthly * Quarterly * Semi-Annually * Annually {#tprm-control-record-form__ul_xlz_gd2_b2c} Note: After the attestation is complete, the control moves to Review and Monitor states. The control is then monitored for its next due date of attestation. You have the option to trigger the control's attestation frequency based on the attestation's Created date or the last completed attestation's Updated date. This option is based on the value in Trigger control attestations based on the created or updated date of the last completed attestation system property. | | Activity Journal || | Additional comments | Public information about the control. | | Settings || | Functional domain | Functional domain for the control objective. | [Table 1. Control form] {#tprm-control-record-form__table_FloorForm} **Related tasks** * [Manually add a control to a third party or engagement](https://servicenow-prod.fluidtopics.net/3eKZvDGLQh1geL5q0MKGzA "If you’re using both Policy and Compliance Management and Third-party Risk Management, you can associate controls with third parties and engagements. Controls can be marked as compliant or non-compliant.")