﻿# Create an RFC

> [HTML Version](add-rfc.html)

To add an RFC, go to the [main page](servicedesk-main-page.md) or the **RFC** app and click **+ RFC**. In the window that opens, fill in the fields:  

**General** block:  

- **Name\***. The name of the RFC.  

- **Type\***. The type of the RFC: **Standard**, **Normal**, **Emergency**.  

- **Standard change\***. This field appears if **Standard** is selected as the type. Specify which [standard change](regular-rfc.md) needs to be implemented.  

- **Initiator\***. Employee proposing the RFC.  

- **CAB**. Employees who will approve the RFC.  

- **Resources required**. If the selected standard change includes a table of required resources, it will appear on the RFC creation page.  

**Description** block:  

- **Purpose of change\***. Reason for proposing the change.  

- **Change description\***. Detailed information about what is being modified.  

- **Risk exposure\***. Reflects how strongly the RFC implementation may affect service delivery: **Low**, **Significant**, **Highest**.  

- **Expected result\***. Planned effect of implementing the change.  

**Risks** block:  

- **Degree of risk\***. Likelihood of negative consequences from implementing changes: **High**, **Medium**, **Low**.  

- **Risks**. Description of potential negative consequences.  

- **Cost of change**. Enter the amount required to execute the change.  

**Related Objects** block:  

- **Related services**. Services that may be affected by the change. The list of available items is stored in the [Services](services.md) app.  

- **Related CMDBs**. Assets whose operation may be impacted. The list of available assets is stored in the **CMDB** app.  

- **Related problems**. Issues that will be resolved after implementing the changes. You can select an existing problem or add a new one using the **+** **Create** button. The new item will be saved in the [Problems](problems.md) app.  

In the right column, also specify:  

- **Priority**. Urgency of request execution: **Urgent**, **High**, **Normal**, **Low**.  

- **Responsible\***. Employee responsible for the change.  

After filling in the fields, click **Save**.  

The new change request will be registered in the system with the **New** status and submitted for review to the CAB approver.  

If no CAB approver is specified, the request will receive the **Assessment and planning** status and immediately proceed to the employee responsible for workload evaluation.