Skip to main content
Procore

(Beta) Create a Custom Workflow Template

  1. Last updated
  2. Save as PDF
 In Beta
This page details functionality that is not available in Procore's production environment. Access to the features documented here is limited to specific Procore customers who have signed the required agreement to participate in Procore's Company level Workflows Tool Beta Program. The content on this page is for informational purposes only and all information and content on this page is subject to change without any prior notice. To learn more, see About the Workflows Beta Program.
 Important
This article outlines the steps for creating a new workflow template in the company level Workflows tool. Some features listed are in a closed beta and may not be available. For more information on which tools are available in the open beta, see About the Workflows Beta Program. 

Objective 

To create a custom workflow template in the Company level Workflows tool. 

Things to Consider

  • Required User Permissions:
    • To view, create or edit a custom workflow at the company level:
      • 'Admin' level permissions on the Company level Workflows tool. 
        OR
      • 'Read Only' or 'Standard' level permissions on the Company level Workflows tool with the 'View Custom Workflows' and 'Create and Edit Workflow Templates' granular permission enabled on your permissions template. 

Steps

Add a Custom Workflow 

  1. Navigate to the Company level Workflows tool. 
  2. Click the Create button. 
  3. In the 'Add a Workflow' dialogue box, do the following:
    • Name *. Enter a name for your new workflow. 
    • Tool *. Select the tool and item for which you are creating the new workflowclipboard_e721b0e88fb6135835d3abf368c7514a3.png.
      • Subcontractor Payment application
      • Correspondence/Custom Tools
         Note: If you select Correspondence/Custom Tools, you will also be required to choose a Type before continuing to the next step.
      • Main Contract
      • Subcontract
      • Purchase Order
      • Budget Change
      • Main Contract Variation - Single Tier
      • Main Contract Variation - Two or Three Tier
      • Commitment Variation - Single Tier
      • Commitment Variation - Two or Three Tier
      • Main Potential Variation
      • Commitment Potential Variation
      • Document Management
  4. Click Create.
    Procore automatically opens the workflow builder and creates an 'Untitled' first step for you. 

Update the First Step in the Custom Workflow 

  1. Begin by selecting the type of step (Response Step, Condition Step) you will use at the start of the workflow. 
    workflows-first-step-choice.png
  2. Follow the instructions for the selected step type:

Add a Response Step to a Custom Workflow  

  1. Enter the following information in the General Information section:
    • Step Name. Enter a name for the step.
    • Type. Select Response Step.
    • Item Status. Enter the item status that will be associated with this workflow step.
    • Days to Complete. Enter the number of days the 'Responsible Group' has to complete the workflow step. Then select Calendar Days or Business Days from the drop-down list. Once the set number of days passes, Procore sends a reminder email until the step is complete.
    • Optional: Notification Recipients. Select the groups or roles that should receive an automated notification when the workflow step is NOT completed within the number of days specified under Days to Complete. The recipients named here will also receive an email when the workflow step is completed. The default groups include:
      • Workflow Manager. A workflow manager is a Procore user who must be designated on a project.
      • Item Creator. An item creator is a Procore user who created the item on a project.
      • Distribution Group. After you publish this workflow and assign it to a project, you can define different group members when configuring the custom workflow in the Project level commitments tools.
  2. Enter the following information in the Assignees section:
    • Assignee Role. Select the role of the user assigned to this step.
      • Optional: Click Create Template Role to create a unique role for this custom workflow.
    • Decision Type. Select the type of decision being made for this step:
      • First responder decides. There can be multiple assignees but only one response is required to progress to the next step in the workflow.
      • Multiple responders decide. There can be multiple assignees and multiple responses. You can determine the next step when all responders (not assignees) select the same response. You can also choose the next step when all responders are not in agreement.
  3. Enter the following information in the Responses section:
    • If Response is OR If All Responders Decide. Select a response from the list.
    • Go to Step. Select another workflow step to become the current step if the response above is chosen.
      • Optional: Click Add Step if you want the workflow to progress to a step that has not yet been created. You will be prompted to choose a type and name for the new step.
    • Otherwise. If the decision type is set to Multiple responders decide, select or create the next step in the workflow if the responses are NOT unanimous.
  4. Repeat the previous step to continue adding responses to this workflow step.
  5. Choose from these options:
    • Cancel. Click this button to discard any changes you have made.
    • Save as Draft. Click this button to save a numbered 'Draft' version of the workflow. Choose this option when you are still working on creating your custom workflow. 
      OR
    • Save and Publish. Click this button to create a newly published version of the workflow. Choose this option when you are ready to assign your workflow to a project.

Add a Condition Step to a Custom Workflow 

Condition steps allow a workflow path to be routed differently depending on whether the conditions of the step are met. To create a condition step, follow the instructions below. 

  1. Enter the following information in the General Information section:
    • Step Name. Enter a name for the step.
    • Type. Select Condition Step.
    • When. Select the first part of the hypothesis in the conditional statement. Different conditional statements exist for each tool. See Conditional Statements By Tool. 
      • Greater than. If your organisation requires additional signatures for amounts greater than or equal to a specified amount, you will want to choose this option and enter an amount in the field to the right.
        OR
      • Less than. If you want the step to function when the hypothesis is less than a specified number.
      • Is. If you want the step to function when a certain field is selected for a custom field.
      • Is Checked. If you want the step to function when a custom field tickbox is checked.
      • Contains any of. If you want the step to function when one or more multi-select options are chosen for a custom field.
    • Then. Select a step from the drop-down list or create a new one by clicking the Add Step button. 
    • Otherwise. Select a step from the drop-down list or create a new one by clicking the Add Step button. This is the step that will be next in the workflow if the current step's conditions are NOT met.
  2. Choose from these options:
    • Cancel. Click this button to discard any changes you have made.
    • Save as Draft. Click this button to save a numbered 'Draft' version of the workflow. Choose this option when you are still working on creating your custom workflow. 
      OR
    • Save and Publish. Click this button to create a newly published version of the workflow. Choose this option when you are ready to assign your workflow to a project.

Conditional Statements by Tool

Budget Changes... Show/Hide  

Condition Definition
Amount The total BOQ amount of the budget change being approved.

Commitments... Show/Hide  

Condition Definition Example
Original Contract Amount The total BOQ amount of the contract being approved.

A workflow needs to follow different approval paths depending on the amount of the contract being approved.
Total Amount of Approved Cost Objects

The total BOQ amount of the 'Approved' Commitments, Commitment Variations and Direct Costs on the project. The BOQ amount of the workflow item is included in the total.

Formula... Show/Hide  

Approved Commitments + Approved CVs + Approved Direct Costs = Total Amount of Approved Cost Objects

Route the approval path of the workflow when the total amount of other approved contracts, variations and direct costs is over or under a specified amount.
Total Amount of All Cost Objects

The total BOQ amount of all 'Approved' and 'Pending' Commitments, Commitment Variations and Direct Costs on the project. The BOQ amount of the workflow item is included in the total.

Formula... Show/Hide  

Approved and Pending Commitments + Approved and Pending CVs + Approved and Pending Direct Costs = Total Amount of All Cost Objects

Route the approval path of the workflow when the total amount of other pending or approved contracts, variations and direct costs of any status are over or under a specified amount 
Amount Over budget on Approved Cost Objects

The project's total budget amount subtracted from the combined total amount of all 'Approved' Commitments, Commitment Variations and Direct Costs.

Formula... Show/Hide  

Approved Commitments + Approved CVs + Approved Direct Costs - Total Budget Amount = Amount Over Budget on Approved Cost Objects

Route the approval path of the workflow if the contract being approved and other already approved contracts, variations and direct costs are going to take your project over budget by a specific amount.* 
Amount Over Budget on All Cost Objects

The project's total budget amount subtracted from the combined total amount of all 'Approved' and 'Pending' Commitments, Commitment Variations and Direct Costs.

Formula... Show/Hide  

Approved and Pending Commitments + Approved and Pending CVs + Approved and Pending Direct Costs - Total Budget Amount = Amount Over Budget on All Cost Objects

Route the approval path of the workflow if the contract being approved and other pending or approved contracts, variations and direct costs are going to take your project over budget by a specific amount.* 
% of Budget Allocated to Approved Cost Objects

The percentage of the project's total budget amount used by the combined total amount of 'Approved' Commitments, Commitment Variations and Direct Costs.

Formula... Show/Hide  

(Approved Commitments + Approved CVs + Approved Direct Costs) ÷ Total Budget Amount = % of Budget Allocated to Approved Cost Objects

Route the approval path of the workflow if the contract being approved and other already approved contracts, variations and direct costs are going to take your project over budget by a specific percentage. *
% of Budget Allocated to All Cost Objects

The percentage of the project's total budget amount used by the combined total amount of all 'Approved' and 'Pending' Commitments, Commitment Variations and Direct Costs.

Formula... Show/Hide  

(Approved and Pending Commitments + Approved and Pending CVs + Approved and Pending Direct Costs) ÷ Total Budget Amount = % of Budget Allocated to All Cost Objects

Route the approval path of the workflow if the contract being approved and other pending or approved contracts, variations and direct costs are going to take your project over budget by a specific percentage.* 
Custom Fields (Single-Select, Multi-Select or Tickbox)
Note: Single-Select and Multi-Select fields must be marked Required in the. See Create New Configurable Fieldsets.		 Move the workflow based on the value of the custom field as set up within the workflow template builder. Route the approval path of the workflow based on a custom field of "Contract Type" or "Building #". If the "Building #" is 2, route the workflow to John. If the "Building #" is 1, route the workflow to Susan.

Commitment Variations... Show/Hide   

Condition Definition Example
Amount The total BOQ amount of the variation being approved.

A workflow needs to follow different approval paths depending on the amount of the contract being approved.
Total Amount of Approved Cost Objects

The total BOQ amount of the 'Approved' Commitments, Commitment Variations and Direct Costs on the project. The BOQ amount of the workflow item is included in the total.

Formula... Show/Hide  

Approved Commitments + Approved CVs + Approved Direct Costs = Total Amount of Approved Cost Objects

Route the approval path of the workflow when the total amount of other approved contracts, variations and direct costs is over or under a specified amount.
Total Amount of All Cost Objects

The total BOQ amount of all 'Approved' and 'Pending' Commitments, Commitment Variations and Direct Costs on the project. The BOQ amount of the workflow item is included in the total.

Formula... Show/Hide  

Approved and Pending Commitments + Approved and Pending CVs + Approved and Pending Direct Costs = Total Amount of All Cost Objects

Route the approval path of the workflow when the total amount of other pending or approved contracts, variations and direct costs of any status are over or under a specified amount 
Amount Over budget on Approved Cost Objects

The project's total budget amount subtracted from the combined total amount of all 'Approved' Commitments, Commitment Variations and Direct Costs.

Formula... Show/Hide  

Approved Commitments + Approved CVs + Approved Direct Costs - Total Budget Amount = Amount Over Budget on Approved Cost Objects

Route the approval path of the workflow if the contract being approved and other already approved contracts, variations and direct costs are going to take your project over budget by a specific amount.* 
Amount Over Budget on All Cost Objects

The project's total budget amount subtracted from the combined total amount of all 'Approved' and 'Pending' Commitments, Commitment Variations and Direct Costs.

Formula... Show/Hide  

Approved and Pending Commitments + Approved and Pending CVs + Approved and Pending Direct Costs - Total Budget Amount = Amount Over Budget on All Cost Objects

Route the approval path of the workflow if the contract being approved and other pending or approved contracts, variations and direct costs are going to take your project over budget by a specific amount.* 
% of Budget Allocated to Approved Cost Objects

The percentage of the project's total budget amount used by the combined total amount of 'Approved' Commitments, Commitment Variations and Direct Costs.

Formula... Show/Hide  

(Approved Commitments + Approved CVs + Approved Direct Costs) ÷ Total Budget Amount = % of Budget Allocated to Approved Cost Objects

Route the approval path of the workflow if the contract being approved and other already approved contracts, variations and direct costs are going to take your project over budget by a specific percentage. *
% of Budget Allocated to All Cost Objects

The percentage of the project's total budget amount used by the combined total amount of all 'Approved' and 'Pending' Commitments, Commitment Variations and Direct Costs.

Formula... Show/Hide  

(Approved and Pending Commitments + Approved and Pending CVs + Approved and Pending Direct Costs) ÷ Total Budget Amount = % of Budget Allocated to All Cost Objects

Route the approval path of the workflow if the contract being approved and other pending or approved contracts, variations and direct costs are going to take your project over budget by a specific percentage.* 
Custom Fields (Single-Select, Multi-Select or Tickbox)
Note: Single-Select and Multi-Select fields must be marked Required in the fieldset. See Create New Configurable Fieldsets.		 Move the workflow based on the value of the custom field as set up within the workflow template builder. Route the approval path of the workflow based on a custom field of "Contract Type" or "Building #". If the "Building #" is 2, route the workflow to John. If the "Building #" is 1, route the workflow to Susan.

Correspondence/Custom Tools... Show/Hide  

Condition Definition
Cost Impact Value The amount entered in the 'Cost Impact' field on the correspondence item.
Custom Fields (Single-Select, Multi-Select or Tickbox)
Note: Single-Select and Multi-Select fields must be marked Required in the fieldset. See Create New Configurable Fieldsets.		 Move the workflow based on the value of the custom field as set up within the workflow template builder.

Main Contracts... Show/Hide  

Condition Definition Example
Original Contract Amount The total BOQ amount of the contract being approved. A workflow needs to follow different approval paths depending on the amount of the contract being approved.
Custom Fields (Single-Select, Multi-Select or Tickbox)
Note: Single-Select and Multi-Select fields must be marked Required in the fieldset. See Create New Configurable Fieldsets.		 Move the workflow based on the value of the custom field as set up within the workflow template builder. Route the approval path of the workflow based on a custom field of "Contract Type" or "Building #". If the "Building #" is 2, route the workflow to John. If the "Building #" is 1, route the workflow to Susan.

Main Contract Variations... Show/Hide  

Condition Definition Example
Amount The total BOQ amount of the variation being approved. A workflow needs to follow different approval paths depending on the amount of the contract being approved.
Custom Fields (Single-Select, Multi-Select or Tickbox)
Note: Single-Select and Multi-Select fields must be marked Required in the fieldset. See Create New Configurable Fieldsets.		 Move the workflow based on the value of the custom field as set up within the workflow template builder. Route the approval path of the workflow based on a custom field of "Contract Type" or "Building #". If the "Building #" is 2, route the workflow to John. If the "Building #" is 1, route the workflow to Susan.

Subcontractor Payment applications... Show/Hide  

Condition Definition
Net Amount The amount being billed on the payment application with retention applied.
Original Commitment Value The original BOQ amount commitment associated with the payment application.

*Conditional statements linked to the project’s budget are based on the total amount of the budget column selected on the Custom Reporting Budget View located in the company level Admin tool. See Set Up a Budget View for Custom Reporting.

 

Add an End Step (Successful) to a Custom Workflow 

A finish step defines the end of a workflow. A finish step indicates the custom workflow is complete. 

  1. Click the icon-blue-plus-pfcp.png icon attached to an existing step in the workflow builder and choose End Step (Successful).  
  2. Enter the following information in the General Information section:
    • Step Name. Enter a name for the step.
    • Item Status. Select Approved or Complete.
    • Optional: Notification Recipients. Select the groups or roles that should receive an automated notification when the workflow step is completed. The default groups include: 
      • Workflow Manager. A workflow manager is a Procore user who must be designated on a project.
      • Item Creator. An item creator is a Procore user who created the item on a project.
      • Distribution Group. After you publish this workflow and assign it to a project, you can define different group members when configuring the custom workflow in the Project level commitments tools.
  3. Choose from these options:
    • Cancel. Click this button to discard any changes you have made.
    • Save as Draft. Click this button to save a numbered 'Draft' version of the workflow. Choose this option when you are still working on creating your custom workflow. 
      OR
    • Save and Publish. Click this button to create a newly published version of the workflow. Choose this option when you are ready to assign your workflow to a project.

Add an End Step (Unsuccessful) to a Custom Workflow 

  1. Click the icon-blue-plus-pfcp.png icon attached to an existing step in the workflow builder and choose End Step (Unsuccessful).
  2. Enter the following information in the General Information section:
    • Step Name. Enter a name for the step.
    • Item Status. Select Terminated.
    • Optional: Notification Recipients. Select the groups or roles that should receive an automated notification when the workflow step is completed. The default groups include: 
      • Workflow Manager. A workflow manager is a Procore user who must be designated on a project.
      • Item Creator. An item creator is a Procore user who created the item on a project.
      • Distribution Group. After you publish this workflow and assign it to a project, you can define different group members when configuring the custom workflow in the Project level commitments tools.
  3. Choose from these options:
    • Cancel. Click this button to discard any changes you have made.
    • Save as Draft. Click this button to save a numbered 'Draft' version of the workflow. Choose this option when you are still working on creating your custom workflow. 
      OR
    • Save and Publish. Click this button to create a newly published version of the workflow. Choose this option when you are ready to assign your workflow to a project.