Change Control Policy

Purpose:

Establish a standard of accountability to maintain a record of changes for quality assurance.

Policy:

LightForce administrators will follow this policy to plan, approve, commit and roll-back changes where appropriate.

Proposal:

Changes to the Production Environment Information Technology must be documented and communicated. Proposed changes must include, at a minimum:

• Date of proposal and proposed date of change
• Owner contact information
• Nature of the change
• Roll-back plan

Approval:

Proposals must be approved by necessary stakeholders across the Organization responsible for systems affected by the proposed change.

• Written approval from stakeholders
• Proposed changes must be evaluated for Security Compliance by IT Admins
• Emergency changes that require an immediate implementation (i.e. break/fix, incident response, etc.) may be implemented without following the formal change control process, but may not circumvent documentation requirements, even if documented after the change.

Scheduling/Communication:

Once approved, changes must be scheduled with stakeholders and necessary resources.

Follow-Up Assessment:

Once completed or Rolled back, an assessment should be performed to evaluate success, potential issues and confirm production systems are operational.