In project management, a change order is a component of the change management process, whereby changes from the agreed upon scope (limitations) of the project's work require a mutual agreement.
Change orders are common to most projects, and very common with large projects. After the original scope (or contract) is formed, complete with the total price to be paid and the specific work to be completed, a client may decide that the original plans do not best represent his definition for the finished project. Accordingly, the client will suggest an alternate approach. [....]http://en.wikipedia.org/wiki/Change_request
A change request is a document containing a call for an adjustment of a system; it is of great importance in the change management process.
A change request is declarative, i.e. it states what needs to be accomplished, but leaves out how the change should be carried out. Important elements of a change request are an ID, the customer (ID), the deadline (if applicable), an indication whether the change is required or optional, the change type (often chosen from a domain-specific ontology) and a change abstract, which is a piece of narrative (Keller, 2005). An example of a change request can be found in Figure 1 on the right.
Change requests typically originate from one of five sources: (i) problem reports that identify bugs that must be fixed, which forms the most common source, (ii) system enhancement requests from users, (iii) events in the development of other systems, (iv) changes in underlying structure and or standards (e.g. in software development this could be a new operating system) and (v) demands from senior management (Dennis, Wixom & Tegarden, 2002)