project scope management

Your Contract Enshrines Your Project Scope Management

Project Scope Management in the construction industry is enshrined in a legally binding Head Contract with the client. Constructions companies then look to their Project Software to help them manage any changes in this scope.

Budget Phase

In Muli, Project Scope is initially dealt with in the Budgetary phase where all elements having a cost, quality or verification impact on a project are identified.


The project's framework should incorporate the company's previous knowledge of risks - “things” that may happen that will have an impact upon the project's successful outcome.  Muli terms these “Risk2Do's” and by assigning Risk2Do's to elements of the project, management can ensure issues are addressed to reduce negative outcomes on the project.

Scope Changes

As the project unfolds, there will be changes in scope that need to be managed. These originate when the client or subcontractor requests changes to the scope of works or contract documents.  To manage these Muli has adopted a framework of:

  • Ballpark Variations – raised once a change in scope of works is known
  • Submitted Variation – when the scope of works is quantified, a firm $amount is submitted for client  approval 
  • Approved Variation – after the client approval is received

Muli's software can be utilised by both the Construction Company and Subcontractors. So a Construction company using Muli would have a Head Contract with their client – who is at the top tier. But a Subcontractor using Muli would have a Head Contract with the Construction Company – who they see as their client.


Managing your Contract Variations correctly is key to project cost management.