Add a Sub Job to a Procore Project

Last updated
Save as PDF

Objective

To add a sub job to a Procore project using the project's Admin tool.

Background

In Procore, a sub job allows you to compartmentalise job costs within a project. Once they are added to Procore (or imported via an integrated ERP system) you can monitor your project budgets and costs against them to help you better determine if you are making money on your project. For example, if your project is a multi-story commercial building, you might create a separate sub job for the build of each floor. Or, if your project is a multi-unit development, you might create a separate sub job for each individual structure.

After a sub job has been created, you can issue specific line items on the Programme of Values (BOQ) for a variation to the sub job.

Things to Consider

Required User Permission:
- 'Admin' level permission on the project's Admin tool.
Prerequisites:
- The Sub Jobs feature must be enabled. See Enable Sub Jobs.
  Note: If your company has implemented the Procore + Sage 300 CRE® integration, see below for how to enable sub jobs.
- Before you can add a sub job to a project, a standard cost code list must be added at the company level (see Add, Edit and Delete Company Cost Codes). For sub jobs, cost codes are copied over from the company level standard cost code list and not the project level cost code list.

For companies using the

ERP Integrations tool: Show/Hide

QuickBooks®:

Sub jobs are NOT supported.

Sage 100 Contractor®:

To configure the ERP Integrations tool for Sage 100 Contractor®. See Sage 100 Contractor®: Setup Guide.
To enable the Sub Jobs feature in Procore. See Enable Sub Jobs for Sage 100 Contractor®.
To import a sub job into Procore, you must:
- Create a Phase in Sage 100 Contractor®. See your Sage 100 Contractor® documentation for instructions.
- Follow the steps in Add a Phase from Sage 100 Contractor® to a Procore Project as a Sub Job.

Sage 300 CRE®:

To configure the ERP Integrations tool for Sage 300 CRE®. See Sage 300 CRE®: Setup Guide.
To enable sub jobs, see Enable Sub Jobs for Sage 300 CRE®.
To add a sub job and export it to Sage 300 CRE® as an 'Extra', see the Steps below.
Note: There is a maximum character limit for 'Extras' in Sage 300 CRE®. See What is the maximum character length for a Sub Job?
Alternatively, you can create an 'Extra' in Sage 300 CRE® and then import it into Procore, see Add a Sage 300 CRE® Extra to a Procore Project as a Sub Job.
If you are exporting a Sub Job from Procore to Sage 300 CRE®, a code is required prior to export. Once the Sub Job has been synced with Sage 300 CRE®, a code can no longer be applied, preventing the Sub Job from being used in the Main Contract Bill of Quantities.

Viewpoint® Spectrum®

Sub jobs are NOT supported.

Integration by Ryvit:

Sub jobs are NOT supported.

Yardi Voyager®

Sub jobs are NOT supported.

UndefinedNameError: reference to undefined name 'integrations_mri' (click for details)
Callstack: at (Media_Library/Language_Specific_Media/Reusable_Snippets/Reusable_Text_Snippets), /content/body/div[13]/div[2]/div[1]/div/p[7]/strong/span, line 1, column 1 at wiki.page() at (products/online/user-guide/project-level/admin/tutorials/add-a-sub-job), /content/body/div[3]/ul/li[3]/div/pre, line 2, column 10

Sub jobs are NOT supported.

For companies using the

ERP Integrations tool: Show/Hide

UndefinedNameError: reference to undefined name 'integrations_myob' (click for details)
Callstack: at (Media_Library/Language_Specific_Media/Reusable_Snippets/Reusable_Text_Snippets), /content/body/div[13]/div[2]/div[2]/div/p/strong/span, line 1, column 1 at wiki.page() at (products/online/user-guide/project-level/admin/tutorials/add-a-sub-job), /content/body/div[3]/ul/li[3]/div/pre, line 2, column 10

To configure the ERP Integrations tool for

UndefinedNameError: reference to undefined name 'integrations_myob' (click for details)

Callstack:
    at (Media_Library/Language_Specific_Media/Reusable_Snippets/Reusable_Text_Snippets), /content/body/div[13]/div[2]/div[2]/div/ul/li[1]/span, line 1, column 1
    at wiki.page()
    at (products/online/user-guide/project-level/admin/tutorials/add-a-sub-job), /content/body/div[3]/ul/li[3]/div/pre, line 2, column 10

. See

UndefinedNameError: reference to undefined name 'integrations_myob' (click for details)

Callstack:
    at (Media_Library/Language_Specific_Media/Reusable_Snippets/Reusable_Text_Snippets), /content/body/div[13]/div[2]/div[2]/div/ul/li[1]/a/span, line 1, column 1
    at wiki.page()
    at (products/online/user-guide/project-level/admin/tutorials/add-a-sub-job), /content/body/div[3]/ul/li[3]/div/pre, line 2, column 10

: Setup Guide.

To enable sub jobs, see Enable Sub Jobs for

UndefinedNameError: reference to undefined name 'integrations_myob' (click for details)

Callstack:
    at (Media_Library/Language_Specific_Media/Reusable_Snippets/Reusable_Text_Snippets), /content/body/div[13]/div[2]/div[2]/div/ul/li[2]/a/span, line 1, column 1
    at wiki.page()
    at (products/online/user-guide/project-level/admin/tutorials/add-a-sub-job), /content/body/div[3]/ul/li[3]/div/pre, line 2, column 10

Alternatively, you can create an 'Project Task' in

UndefinedNameError: reference to undefined name 'integrations_myob' (click for details)

Callstack:
    at (Media_Library/Language_Specific_Media/Reusable_Snippets/Reusable_Text_Snippets), /content/body/div[13]/div[2]/div[2]/div/ul/li[3]/span, line 1, column 1
    at wiki.page()
    at (products/online/user-guide/project-level/admin/tutorials/add-a-sub-job), /content/body/div[3]/ul/li[3]/div/pre, line 2, column 10

and then import it into Procore, see Import a ERP Sub Job to a Procore Project.

If you are exporting a Sub Job from Procore to

UndefinedNameError: reference to undefined name 'integrations_myob' (click for details)

Callstack:
    at (Media_Library/Language_Specific_Media/Reusable_Snippets/Reusable_Text_Snippets), /content/body/div[13]/div[2]/div[2]/div/ul/li[4]/span[1], line 1, column 1
    at wiki.page()
    at (products/online/user-guide/project-level/admin/tutorials/add-a-sub-job), /content/body/div[3]/ul/li[3]/div/pre, line 2, column 10

, a code is required prior to export. Once the Sub Job has been synced with

UndefinedNameError: reference to undefined name 'integrations_myob' (click for details)

Callstack:
    at (Media_Library/Language_Specific_Media/Reusable_Snippets/Reusable_Text_Snippets), /content/body/div[13]/div[2]/div[2]/div/ul/li[4]/span[2], line 1, column 1
    at wiki.page()
    at (products/online/user-guide/project-level/admin/tutorials/add-a-sub-job), /content/body/div[3]/ul/li[3]/div/pre, line 2, column 10

, a code can no longer be applied, preventing the Sub Job from being used in the Main Contract Bill of Quantities.

Demo

Add a Sub Job to a Project

Navigate to the project's Admin tool.
Click Sub Jobs.
Notes:
- If the Sub Jobs link is not visible or available, it must be enabled. See Enable Sub Jobs. (Note: If your company has implemented the Procore + Sage 300 CRE® integration, see Enable Sub Jobs for Sage 300 CRE).
- Before you can add a sub job to a project, a standard cost code list must be added at the company level (see Add and Edit Company Cost Codes). For sub jobs, cost codes are copied over from the company level standard cost code list and not the project level cost code list.
- If your company has implemented the ERP Integrations tool with the Integration by Ryvit, QuickBooks®, Sage 100 Contractor®, or Viewpoint® Spectrum®, you cannot create a sub job in Procore. You must create the sub job in your integrated ERP system and then import them. For more information, see Which integrated ERP systems support the 'Sub Job' concept?
Type the following information:
- Sub Job. Enter the name that you want to assign to the sub job.
  Note: If your company has implemented the Procore + Sage 300 CRE® integration, see What is the maximum character length for a Sub Job?
- Code. The code is used as an abbreviation for the sub job in the Budget and Bill of Quantities (BOQ) import templates. You can enter any combination of alphanumeric characters.
  
  Note
  If you are planning on creating a Sub Job on Procore and subsequently exporting it into Sage 300 CRE®, a code is required prior to exporting to Sage 300 CRE®. Once the Sub Job has been synced with Sage 300 CRE®, a code can no longer be applied, preventing the Sub Job from being used in the Main Contract Programme of Values.
Click the + icon to add the sub job to your project.
Choose from these options:
- If you want to include sub jobs on BOQ line items, see Add a Line Item to a Programme of Values.
  OR
- If you want to add cost codes to a sub job, continue with Add Cost Codes to a Sub Job below.

Add Cost Codes to a Sub Job

Navigate to the project's Admin tool.
This reveals the Admin page.
Click the Sub Jobs links in the right pane.
This reveals the Sub Jobs page.
Locate the sub job. Then click View.
This opens the Sub Jobs's Cost Codes page.
Add the codes from the Standard Cost Codes List to the Sub Job Cost Codes list.
This list shows all the Standard Cost Codes from the Company level Admin tool and not the project. The steps for adding cost codes to a sub job are the same as what is described in Add and Edit Project Cost Codes.

Next Steps

Assign Default Cost Types To Cost Codes

Objective

Background

Things to Consider

Demo

Steps

Add a Sub Job to a Project

Note

Add Cost Codes to a Sub Job

Next Steps

See Also