A change controls a planned addition, modification, or removal that can affect services. Normal changes usually need assessment and authorization before implementation. Standard changes follow an approved repeatable model. Emergency changes use an expedited authorization process; the word emergency doesn't remove accountability.
Plans should explain implementation, testing, and recovery. A backout plan describes how to restore the prior state if the change fails. Approval, scheduling, implementation, and review are distinct decisions. Don't infer that an approved change has already been implemented successfully. The simulator uses a simplified state model but preserves the table, ownership, risk, and plan fields you inspect at work. Match the available lifecycle to the organization's configured process instead of assuming every instance uses identical state choices.