Scope

• Files CRs for Production Services
• Files CRs for significant Non-Production changes
• Version Releases
• Non-routine configuration changes
• Support and Handling Changes
• Documenting changes to test/dev environments
• Not filing CRs for inconsequential/insignificant changes

Timing

• Files CRs in with more than enough lead time (versus just in time filing)
• Normal CRs are filed at least 48 hours before implementation
• Limit amount of Emergency CRs filed
  

Accuracy

• CRs clearly define scope of work
• CRs clearly indicate impact to services/CIs
• CIs are linked approprately to CR
• Completes CR following implementation
• Mark Actual Start/End Dates
• Set as Complete

Communication

• Stakeholders are updated reliably
• Additional communication (if necessary) is completed
• Communicates any unknowns or additional risks that are discovered directly to Change Manager

Other references: