Skip to main content
Procore (en-GB)

Create a Main Contract Variation (MCV)

Objective

To create a Main Contract Variation (MCV).

Background

Things to Consider

  • Required User Permission:
    • 'Admin' on the project's Main Contracts tool.
  • Limitations:
  • For companies using the icon-erp-synced2.png ERP Integrations tool: Show/Hide  
    • Integration by Procore: Viewpoint® Spectrum® 
    • Integration by Ryvit: Viewpoint® Vista™
      • MCV exports are NOT supported.
    • QuickBooks®
      • MCV exports are NOT supported.
    • Sage 100 Contractor®
      • MCV exports are NOT supported.
    • Sage 300 CRE®:
      • Title. The MCV title must be 30 characters or less. 
      • Number (#). The MCV number be five (5) characters or less. 
      • Status. The main contract must be in the Approved status.
      • Associated Line Item. For each line item that you add to the variation's Bill of Quantities (BOQ), you may designate one (1) associated line item for each variation line item or the same associated line item for all variation line items.  Note: The Associated Line Item list is only visible and available when the ERP Integrations tool has been configured to work with Sage 300 CRE® and the export main contract variations capability has been switched on in Procore by your Integration Implementation Specialist.

Steps

  1. Navigate to the project's Main Contracts tool.
  2. Locate the main contract to work with in the list. Then click View
  3. Click Create Main Contract VAR.
    create-main-contract-change-order.png
  4. Complete the following fields:
    • #. This field automatically populates based on the number of MCVs already created. By default, the number will automatically increment by one. However, you can manually enter a different number, if desired.
      Note: If you manually enter a number, the next MCV that's created will automatically increment by one, based upon this specified value.
    • Date Created. Shows the date and time that the MCV was created. Note: You cannot modify this date.
    • Revision. Displays the MCV's revision number. When a MCV is first created, its revision number is zero. A MCV could have multiple revisions because of feedback from a reviewer/approver. 
    • Created By. Displays the name of the user that created the MCV.
    • Title. Enter a title name for the MCV that describes the packaged VR requests included.
    • Status. Select the current state of the MCV:
      • Approved. Indicates the MCV has been approved. Costs are reflected as 'Approved Changes' in the budget.
      • Draft. Indicates the MCV still needs to be modified before it can be submitted for review. Costs are not reflected in the budget.
      • No Charge. Indicates the MCV has no associated financial charge and no costs will be reflected in the project's budget.
        Note: These statuses reflect the budget in the ways listed above for the 'Procore Standard Budget' view. To learn more, see Set up a New Budget View.
      • Pending - In Review. Indicates the MCV is currently being reviewed by an approver. Costs are reflected as 'Pending Changes' in the budget.
      • Pending - Not Pricing. Indicates the MCV is pending and is not actively being priced. Costs are reflected as 'Pending Changes' in the budget.
      • Pending - Not Proceeding. Indicates the MCV is pending and the work is not currently taking place. Costs are reflected as 'Pending Changes' in the budget.
      • Pending - Pricing. Indicates the MCV is pending and is currently out for pricing. Costs are reflected as 'Pending Changes' in the budget.
      • Pending - Proceeding. Indicates the MCV is still pending and the work is being completed. Costs are reflected as 'Pending Changes' in the budget.
      • Pending - Revised. Indicates the MCV has been modified since its initial submission. Costs are reflected as 'Pending Changes' in the budget.
      • Rejected. Indicates the MCV  was rejected. Costs are not reflected in the budget.
      • Void. Indicates the MCV was voided. Costs are not reflected in the budget.  
    • Private. Check this box if you want to make the MCV  private and visible only to users with 'Admin' on the Main Contracts tool. 
    • Due Date. Select a due date for when the MCV must be approved by. 
    • Invoiced Date. Select the date when the MCV was invoiced.
    • Designated Reviewer. Select a designated reviewer to approve the MCV . See Review and Approve/Reject Main Contract Variations (MCV).
    • Paid Date. Select the date that payment was received for the MCV.
    • Reviewer. This field is auto-populated after the designated reviewer reviews or approves the MCV.
    • Description. Enter a more detailed description of the MCV.
    • Programme Impact. If known, you can provide an estimate of the number of additional days that would potentially be added to the current project programme if the MCV were approved.
    • Revised Substantial Completion Date. Enter a revised substantial completion date. The main contract's substantial Completion Date is updated after the MCV status' is set to 'Approved'. Note: This field is only visible when it is enabled. See Configure Settings: Main Contract.
    • Executed. Mark this checkbox after the MCV is fully executed.
    • Variation Requests. If the Main Contract's tool is configured for 3-tier variations, select any variations related to this MCV from this drop-down list.  See Configure the Number of Main Contract Variation Tiers.
    • Potential Variations. If the Main Contract's tool is configured for 2-tier variations, select any potential variations related to this MCV from this drop-down list.  See Configure the Number of Main Contract Variation Tiers.
  5. Choose one (1) of these options:
    • To create the MCV, click Create.
      OR
    • To create the email and send email notifications, click Create & Email