IMAGE
{% hint style="success" %} For guidance on common form features and functions, see [**Working with Forms**](/interfacing-help-files/end-users/exploring-apps/working-with-forms.md). {% endhint %} *** {% stepper %} {% step %} ### Identify, Classify, & Assign Ownership Provide the information needed to uniquely identify, classify, and assign ownership of the change request.IMAGE
* **Subject of the Change:\*** Enter a brief, descriptive title. * [**Change Type**](#user-content-fn-1)[^1]**:** Select the type of change being requested. {% hint style="info" %} #### Standard Change Types * **Document Change:** Updates to controlled documents, procedures, or work instructions. * **Process Change:** Updates to business processes, workflows, or operational methods. {% endhint %} * [**CR Manager:**](#user-content-fn-2)[^2]**\*** Select the user, role, or group responsible for reviewing the request. {% hint style="warning" %} If the selected **change type** has a predefined reviewer, their name or title will automatically appear in the field. You can update this if needed. {% endhint %} * [**Business Division:**](#user-content-fn-3)[^3] Select the primary functional unit (department) associated with the request. * Selecting a division filters the options shown in the **Business Line** field. * [**Business Line:**](#user-content-fn-4)[^4] Select the specialized unit within the selected division. * **Requested Action:** Select the action to be performed (e.g., Add, Update, Delete). {% hint style="danger" %} If expected options are missing from dropdowns, contact your administrator. {% endhint %}━━━━━━━━━━━━━━━━━━━━━━━━━━━
**Read-Only Fields** (🔒) * **Change Request ID:** A unique identifier used for tracking and reference. * **Date Requested:** The date the request was created (current date). * **Requestor:** The logged-in user who submitted the request. *** {% endstep %} {% step %} ### Define Priority & Timeline Specify the urgency, importance, and expected completion timeline for the change.IMAGE
* **Priority:\*** Select the priority level for the request (e.g., Minor, Major, Critical). * **Value:\*** Select the overall value or importance of the change (e.g., Low, Medium, High). * **Due Date:\*** Select the date by which the request must be completed (today or a future date). * **Impact:\*** Select the estimated impact level of the change (e.g., Low, Medium, High). *** {% endstep %} {% step %} ### Describe & Justify Change Provide details explaining the purpose and need for the change.IMAGE
* **Description:\*** Provide a detailed description of the change, including scope and objectives. * **Justification of the Change**: Explain the rationale for the change, detailing the problem or need it addresses. * **Relevant Documents**: Upload any files that provide background, justification, or context for the request. *** {% endstep %} {% step %} ### Identify Impacted Areas Identify the areas impacted by the change.IMAGE
* [**Site(s):**](#user-content-fn-5)[^5] Select one or more affected locations. * [**Department:**](#user-content-fn-6)[^6] Select one or more affected departments. * [**Project(s):**](#user-content-fn-7)[^7] Select one or more affected projects. * [**Product(s):**](#user-content-fn-8)[^8] Select one or more affected products. *** {% endstep %} {% step %} ### Add Additional Impact Details (Optional) Select the **Do you want to add additional impact details?** checkbox to reveal additional fields:IMAGE
#### 5.1 Impacts Evaluate potential effects of the proposed change on the project, product, or service. * **Quality Evaluation:** Consider how the change may improve, reduce, or otherwise influence quality. * **Impact on Deadlines:** Indicate whether the change may cause delays, accelerate timelines, or require schedule adjustments. * **Impact on Deliverables:** Describe how project outputs may be affected, including any changes to scope, format, or completeness. #### 5.2 Affected Documentation Identify documentation that may be affected by the proposed change.IMAGE
To link affected documentation, follow these steps: 1. **Select Module** * In the **Select Module** field, choose the module containing the relevant documentation. * **Available Modules:** Process, Document, Rule, Control, or Capability. * Once a module is selected, the **Select Folder** field appears. 2. **Select Folder** * In the **Select Folder** field, click the :angle-down: icon to open a form displaying a tree structure of documentation folders. * Double-click the desired folder to select it. 3. **Select Documentation** * Once a folder is chosen, its child items populate the **Selected** **Objects** grid. * Check the **Selected** box for each item you want to assign. * To apply your changes, click **Save Changes** or click outside the grid. * To discard them, click **Discard Changes**. 4. **Assign Documentation** * Click **Assign Selected** to finalize the assignment. 5. **Review Assigned & Impacted Documentation** * Assigned objects appear in the **Assigned Objects** grid. * If any objects are impacted by the assigned ones, they will appear in the **Impacted Objects** grid. Otherwise, this grid is hidden. {% hint style="success" %} To assign documentation from multiple modules and folders, repeat this process as needed. {% endhint %} {% hint style="info" %} #### Additional Notes * To view an item's description, click inside the **Description** column. * To navigate directly to an item, click its link in the **Link to Object** column. {% endhint %} #### 5.3 Cost Evaluations Estimate the financial impact of the change:IMAGE
Click **Add** to to create a new cost evaluation.IMAGE
1. **Define Details** Complete the relevant fields to capture the necessary cost information for the evaluation: * [**Cost Types:**](#user-content-fn-9)[^9] Select the type of cost being evaluated. * [**Category:**](#user-content-fn-10)[^10] Select the relevant cost category. * Selecting a category filters the options in the **Subcategory** field. * [**Subcategory:**](#user-content-fn-11)[^11] Select the appropriate subcategory. * **Note:** This field may not be applicable for all categories. * **Other:** Enter additional details if needed. * **Quantity:** Enter the number of units or hours. * **Unit Cost:** Enter the cost per unit or hour. * [**Currency:**](#user-content-fn-12)[^12] Select the applicable currency for the cost. * **Description:** Provide a brief description of the cost. {% hint style="info" %} The **Total Cost** is automatically calculated based on the values entered for **Quantity** and **Unit Cost**. {% endhint %} *** 2. **Save Changes** When ready to save, choose one of the following options: * **Save and New:** Click to save the cost evaluation and open a new form to add another. * **Save and Close:** Click to save the cost evaluation and close the main form.IMAGE
{% hint style="info" %} #### Commenting Guidelines Comments remain visible throughout the workflow for transparency and communication. * You can **edit**, **delete**, or **reply** to your own comments. * You can **reply** to others' comments but cannot edit or delete them. {% endhint %} *** {% endstep %} {% step %} ### Submit Request Click **Submit** to enter the request into the **Change Request Management** workflow, routing it to the designated reviewer for [planning and approval](/interfacing-help-files/end-users/change-request-application/navigating-the-change-request-management-workflow/review-and-plan-change-request.md). *** {% endstep %} {% endstepper %} *** ## See Also| Cover image | |||
|---|---|---|---|
| Tracking & Monitoring Change Requests | Monitor the status and progress of change requests using lists and dashboards. | App-V16-Icons-1.png | Tracking & Monitoring Change Requests |
