Change Requests can be created by users with permission of Quality Owner, Approver and Editor. 

Note: This video was created using V1.26.0. Enzyme is updated weekly so some elements may change.

Create Change Requests

Change Requests can be created by users with permission of Quality Owner, Approver and Editor.

  1. To create a change request, click on the Change Request button in the secondary navigation menu.

2. In the Change Request pop-up, enter a title, description, and a justification for the change. If enabled by the Admin in Company Settings, a title and description may be required. The description and justification fields are in rich text, allowing you to upload attachments and format the font and layout.

3.Scroll the available and check the ones you’d like to add to the Change Request. You can also search for items or filters to add them. Once your filters show all your approvals you can add all of them at the same time.

4. The approvers that will be populated to the change request will be based on the roles and users defined in the Approval Settings by the Admin. Also if module based access or Product specific approvals are enabled by the admin, this will impact the approvals that will show.

If approvals have not been set up for the document, Quality Owners will have an option to do so from the Change Request. The Change Request will automatically be saved. The quality owners will be able to access the draft from the Approvals Module.

Individual approvers in bold are required and cannot be removed from the Change Request. Roles in bold must have at least one user approving for that role. Individual approvers and roles that are not bold are optional and can be removed. At least one approver (other than yourself) is required.

Once approvers are finalized and when the Change Request is submitted, all listed approvers will receive a notification and must approve the Change Request. Any single approver (or role) can deny the request.

5. If the Admin has implemented the Change Request Analysis Questions (CRAQ), then they must be answered prior to submitting the Change Request for approval.

Note: CRAQ questions must be answered if there are production version documents (A.0, B.0 etc) on the change request.

6. Add any general comments, attachments, controlled documents and tags. Tags allow you to easily search the Change Request using universal search feature or the filters in the approvals module.

7. The Change Request can be saved as a draft or, if all required fields are complete, can be submitted for approval by clicking Request Approval.

8. Users can view their change request and take action as needed from their Dashboard, Notification Bell or Approvals module.

At any time you can view the Comment and History for the Change Request.

If you have any questions, you can reach us through the in-app chat or email us at

Did this answer your question?