DURING THE PROJECT, A CHANGE REQUEST CAN FREQUENTLY BE MET WITH DREAD. BUT IN FACT IT’S, A REALITY IN THE BUSINESS WORLD AND OFTEN CHANGE REQUESTS ARE SUBMITTED FOR LEGITIMATE REASONS. IN OUR CONSTANTLY CHANGING BUSINESS ENVIRONMENT, IT IS IMPOSSIBLE FOR ANYONE TO BE AWARE OF WHAT IN PARTICULAR THEY WILL NEED TO ACHIEVE THE OBJECTIVES AT THE START OF A PROJECT.

Therefore, the best way to handle change is by managing it rather than avoiding it. Although teams should resist unnecessary changes, it is important to stay open to new opportunities that could bring more value to the project and the organization.

Very simple definition of change request is a proposal to alter a product or system, often brought up by the client or another team member. During a project, this can happen when a client wants to change or alter the deliverables agreed upon.

A change request is a request to increase, decrease or modify any document, deliverables, work order, task, quantity of requested material or baseline. It is a formal, written request that occurs after the parameters of the project have been agreed to or baselined and when the project is underway. In ISETIA you can keep documentation regarding change request and apply dynamic workflow on any request.

ISETIA Provide Change Request Module to allow system users to digitalize their requests online on common data environment.

An approved change request is a type of change request that has been processed through integrated change processes. The change request is often submitted by requesters, reviewed by different parties, and approved by stakeholders of the project. ISETIA has flexible role base privileges systems which gives opportunity for organization to state who can request, who can approve, what are required documents for approval, document check lists, and approval checklists. All requests history will be recorded in system such as when requested, when approved and when accounted by stage movement in ISETIA Board.
Moreover ISETIA also gives possibilities to communicate, add comments, notes and remarks for all change requests.

Each Industry and organization have different templates and requirements for data collection during change request process. User can create a necessary data set of attributes (Unlimited User Defined Fields) and configure an appropriate views and forms, suitable to manage the data flexibly in ISETIA.
These are collections of details, related with Tasks, Work Orders, Contract Items, BoQ Items and any process element which is located on ISETIA Board.

Change Request can describe many technical parameters that are going to change and will require approval, both from the investor and from the contractor. Change Request Module provides perfect visibility of all the changes and the approval process. It’s an extension of process management functionality. Thanks that large number of details will be able to be captured with the single Task, Work Order, Process Items Card.

Typical usage of Change Request Module is Change Request Management, where dozens of fields may represent baseline data vs proposed attributes of the change request.

Five tips on effective management of change requests:

  1. Request any supporting materials.
  2. Determine whether the change request is inside or outside the scope.
  3. Have your team assess the priority of the change request.
  4. Approve or reject the change request.
  5. Decide on a course of action going forward.

ISETIA helps to manage and track your workflow and will ensure that every team member stays in the loop.  Each step is recorded by a built-in stage log that will allow to go back and retrace your steps if anything goes wrong.

The ability to control change is paramount to project success.