Key Fields & Conditional Logic in Change Management

How Your Input Shapes the Form

When filling out the main "Change Management" form, some of your selections will dynamically change the fields you see or need to complete. This ensures the form is tailored to the specific type and complexity of the change you are proposing.

"Type of Report" Drives Form Structure

In the initial "Improvement Details" section, your choice in the "Type of Report" field (e.g., "Document Change," "Engineering Change," "Improvement") is crucial.

• What it does: It determines which specific sets of fields will appear next, ensuring you provide relevant information for that category of change. For example, selecting "Document Change" will prompt for document titles and IDs, while "Engineering Change" will ask for drawing numbers and asset details.

Evaluation Questions Trigger Deeper Assessment

The "Evaluation" section contains several Yes/No questions designed to gauge the potential impact and complexity of the change.

• What it does: If you answer "Yes" to any of these key evaluation questions (e.g., regarding modifications, new materials, or policy deviations), the system will then display more detailed sections like "Details (Reasons for Change)" and "Assessment." This ensures that changes with higher potential impact undergo a more thorough review. If all evaluation questions are "No," these detailed sections may not be required.

Risk Score Determines Scope Detail

In the "Assessment" section, the "Risk Score" you assign (e.g., Low, Medium, High, Very High) has a direct impact.

• What it does: If the Risk Score is "Medium" or higher, the "Defined Scope" section will appear. This section is for thoroughly planning and documenting all aspects of a more significant change, including costs, expected outcomes, legal considerations, and implementation plans. A high or very high risk score will also make the "Associated Hazards/Risks" field mandatory.

How Your Input Affects Workflow

Certain data you enter can also influence how the change request moves through its workflow:

• Path from "Implementation" stage:

  • If the initial "Evaluation" questions indicated a more complex change (any "Yes" answers), the workflow will typically proceed from "Implementation" to "Implementation Review."
  • If the "Evaluation" questions all indicated a very simple change (all "No" answers), the workflow might proceed directly from "Implementation" to "Closed."

• Path from "Review" stage:

  • If, during the "Review" stage, you indicate that "Is a further review required?" is "Yes" and set a future "Next Review Date," the change will move to "Review Pending Activation."
  • Otherwise (if no further review is needed, or the date is not in the future), it will proceed to "Closed."

Understanding these key fields and conditional behaviors will help you navigate the Change Management process more effectively and ensure all necessary information is captured for your specific change.