Submitting Change Requests

Change requests are the starting point of the change control process. Any authenticated user can submit a new change request to propose a modification to documents, processes, equipment, systems, or suppliers.

Creating a New Change Request

To submit a new change request:

1. Navigate to Change Control from the main menu
2. Click the New Change Request button
3. Complete the required form fields
4. Click Create Change Request to submit

Required Fields

The following fields must be completed to submit a change request:

Field	Requirements
Title	Must be between 3 and 200 characters. Provide a brief, descriptive title for the change.
Description	Must be at least 10 characters. Provide a detailed description of the proposed change.
Change Type	Select one: Document, Process, Equipment, System, or Supplier.
Priority	Select one: Critical, High, Medium, or Low.
Reason for Change	Must be at least 10 characters. Explain why this change is needed.

Optional Fields

Field	Description
Assign To	Enter a user ID to assign the change request to a specific person. You can leave this empty and assign later.

Caution

All required fields must pass validation before the form can be submitted. The system will display specific error messages if validation fails — for example, if the title is too short or the reason is missing.

Editing an Existing Change Request

To edit a change request you previously submitted:

1. Navigate to Change Control from the main menu
2. Find the change request in the list and click the pencil (edit) icon
3. Update the fields as needed
4. Click Save Changes

Note

Only the original requester or an administrator can edit a change request.

Additional Fields Available When Editing

The edit form includes all fields from the creation form plus the following additional fields for planning purposes:

Field	Description
Affected Areas	A comma-separated list of areas impacted by the change (e.g., Production, Quality, Regulatory)
Estimated Effort	A description of the expected effort (e.g., “2 weeks”, “40 hours”)
Estimated Cost	A numeric cost estimate in dollars
Implementation Plan	A step-by-step description of how the change will be implemented
Rollback Plan	A description of how to revert the change if issues arise
Verification Method	How the change will be verified after implementation
Training Required	A checkbox indicating whether training is needed for this change

Tip

Completing the implementation details early helps assessors and approvers make informed decisions. Fill in the implementation plan, rollback plan, and verification method whenever possible.

Priority Levels

Select the appropriate priority level based on the urgency and impact of the change:

Priority	When to Use
Critical	Safety-related changes or issues requiring immediate action
High	Changes with significant business or compliance impact
Medium	Standard changes with moderate impact
Low	Minor improvements or cosmetic changes

What Happens After Submission

After a change request is created:

1. The system assigns a unique change number automatically
2. The request status is set to the initial lifecycle state
3. You are redirected to the change detail page
4. The change appears in the Change Control list for all users to view
5. Authorized assessors can proceed with an impact assessment