CrossView change enables the input of all changes and, with the approval of the right people, subsequent scheduling. Once CrossView is implemented, there should be no change to a computer environment that has not been first recorded in CrossView. (CrossView makes allowance for last minute and emergency changes, so the excuse that "the process interfered with the event" need not apply.) Changes progress through various workflow statuses, and these statuses require participation of the right person as the change progresses through them. Once it is established as a formal process that all changes are recorded in CrossView, changes can no longer be scheduled until all the approvals have been given; the responsible individuals now know what changes are scheduled. Further, a change's successful implementation can be monitored to ensure that proper consideration is given before it takes place.
Change management is a vital step to gaining control of a computer environment and what happens in it. Analysis such as "how many changes caused problems" can be done and action taken to ensure that procedures are "tightened up". Time estimates for changes can also be monitored to see how often the estimates are over-running. Much greater control is gained over delivery of service when control is established over change.