Skip to main content
Procore

Configure a Project Template

  1. Last updated
  2. Save as PDF

Objective

To configure an existing project as a project template so it can be applied when creating new projects in your company's Procore account. 

Background

In Procore, you can select an existing project to use as a template for creating new projects. This allows you to save the existing project's common settings and then later apply those settings to a new project (i.e., at the time a new project is created). For information about the common settings and items that are saved with a project template, see Items that will carry over to your new project below. 

Things to Consider

  • Required User Permissions:
    • 'Admin' level permissions on the Company level Directory tool.
  • Additional Information:
    • In order to create a project template, Contact Support or your Procore point of contact. A Procore team member will mark the desired project as a template for you. 
    • You may create an unlimited number of project templates. 
    • You can modify existing templates. However, modifications do NOT retroactively apply to projects previously created from that template. Changes to existing templates are only applied to new projects created from that template after the changes are saved.  

  • For companies using the icon-erp-synced2.png ERP Integrations tool: If you will be importing a job from an integrated ERP system to add to Procore as a new project, you will need to select the project template to apply to your new Procore project. For details, visit Things to Know About Your ERP Integration.
     

Steps

  1. Request to Enable a Project as a Template in Procore
  2. Confirm that Your Project Template is Active

1. Request to Enable a Project as a Template in Procore

Send a request to your Procore point of contact or Procore Support asking them to convert a project to a template. You can use an existing project in your company's account or you can create a new one. Include the following details in your request:
 

  • Project Name and Number. To find the project name and number, navigate to the Portfolio tool and locate the desired project in the Projects list. See Search the Company Portfolio for Projects.
  • Project ID. To find the project ID, open the project in Procore. Then look in the URL in your browser's address bar. The Project ID is the number that appears in the URL when viewing your project. If you're still not sure of your project's ID number, you can send the complete link to the project in your request instead.

 

2. Confirm that Your Project Template is Active

After your Procore point of contact confirms that your desired project has been converted to a template, do the following:

  1. Navigate to the company's Portfolio tool. 
  2. Click Create Project.  
  3. Open the Template drop-down list. If the name of your new template appears in the list, the template is active and ready for use when creating new projects. It may take a few minutes after activation for a template to become available for use. 

 

What carries over from a project template?

This table identifies the settings and data that DO and DO NOT carry over to new projects created from a project template. 

Tool

Carries Over

Does NOT Carry Over
Action Plans

Configure Settings

  • Notification settings
  • Company level templates are automatically available on all projects where the Action Plans tool is enabled
  • Action Plan templates created at the Project level
Admin (Company Level)

Programs

  • Programs List

Fieldsets

  • Fieldsets assigned to the template project

Company Settings

  • Webhooks
    • Company level webhooks
      Note: Project level webhooks DO copy over
Admin (Project Level)

Project Settings

  • General
    • Project Information
      • Delivery Method
      • Project Stage
      • Project Type
      • Logo
      • Photo

    • Project Location

      • Country
      • Timezone
      • Address
      • City
      • County
      • Postcode
      • Phone
      • Fax
    • ERP Integrations
      Note: These settings are only available to accounts with a Procore-built ERP integration.
      • Allow Project to be Synced with ERP 
      • Enable ERP Job Cost Transaction Syncing
        Note: 'Allow Project to be Synced with ERP' must also be enabled to allow 'Enable Job Cost Transaction Syncing' to carry over.

    • Advanced

      • Office
      • Departments
      • Program
      • Flag
      • Region
      • Tender Type
      • Owner Type
      • Parent Project
      • Warranty Start and End dates
      • Enable Docusign
      • Prevent Overbilling on this Project
      • Non-Commitment Costs
      • Labour Productivity for Budget, Change Events and Variations
      • Quickbooks Customer
  • Active Tools
    • Tools marked as active
  • Work Breakdown Structure
    • Procore's default 'Cost Type' segment item(s) and all custom cost type segment item(s).
    • Any custom segment items added to the project template.
    • The ON/OFF setting that includes and excludes 'Segments' in the budget code structure. 
    • The project template's budget code structure and its segment arrangement in the template.
  • Working Days
    • Selected Working Days
  • Locations
    • Only Allow Locations to be Created in the Location Manager
  • Webhooks
    • Project level Webhooks, including:
      • Authorization Header
      • Notification Endpoint
        Note: Only Webhooks configured in the default Procore namespace are copied to new projects.
  • Equipment 
    • Equipment Name list

Project Settings

  • General
    • Project Information
      • Project Name
      • Project Number
      • Total Value
      • Start Date
      • Completion Date
      • Actual Start Date
      • Projected Finish Date
      • Project Sector
      • Work Scope
      • Square feet
      • Description
    • Project Location
      • County
      • Latitude
      • Longitude
    • Advanced
      • Language - Country
  • Work Breakdown Structure
    • Cost Codes
    • Sub Jobs
  • Locations
    • Tiered location lists
  • Classifications
    • Classifications table
Tendering

Configure Settings

  • Tendering Configuration
    • All settings
  
Budget

Configure Settings

  • Budget Settings
    • Forecasting
      • Autocalculate Forecast to Complete by default
      • Enable Advanced Forecasting
    • Budget Changes
      • Require a Budget Change Adjustment to Change Event association
      • Require net zero Budget Change amounts
      • Allow budget changes to be billed on main contract payment applications

Budget

  • Values within the budget itself
  • Budget views assigned to the template project
Change Events

Configure Settings

  • Change Event Settings
    • Syncing Objects
      • Maintain Budget Codes across all Line Items in sync
    • Column Display
      • Display Revenue ROM, Latest Price, Latest Cost and Over/Under columns
      • Display UoM, Revenue Qty, Revenue Unit Cost, ROM Unit Qty and ROM Unit Cost Columns
    • Attachments
      • Copy attachments from RFQ responses to Main PVs
      • Copy attachments from RFQ responses to Commitment VARs
    • Budget ROM
      • Budget ROM for In Scope
      • Budget ROM for Out of Scope
      • Budget ROM for TBD Scope
    • Budget Changes
      • Prevent Budget Changes and Main Potential Variations on the same Change Event Line Item

Configure Settings

  • Default "Main Contract (For Markup Estimates)" for new change events
Variations

Configure Settings

  • Variation Settings
    • Show Line Items on Main Contract Variation PDFs
    • Show Line Items on Commitment Variation PDFs
    • Change Reason Behaviour

The variation configuration you establish in a project template will be carried over to new projects based on the template. You can pick either a single tier, two tier or three tier variation configuration for both the main contract and commitment sides. The configuration for variation tiers can be different between the main contract and commitment sides.

  
Commitments

Configure Settings

  • Contract Configurations
    • All Contract Configuration Settings
    • All Default Contract Settings

Individual Subcontracts and Purchase Orders

  • General information
    • Title
    • Executed
    • Default Retention
    • Description
  • Bill of Quantities
    • Line items, including:
      • Amount
      • Description

Configure Settings

  • Contract Configurations
    • All Default Distribution settings and selections

Individual Subcontracts and Purchase Orders

  • General information
    • Contract number (#)
    • Company
    • Attachments
    • Payment Application Contacts
    • Access for Non-Admin Users
    • Status
      Note: All Commitments carry over to the new project with the status marked as 'Draft.'
  • Bill of Quantities
    • Cost code assignment
Connection Manager

Configure Settings

  • Connection Manager Emails
    • Notification selection (All Users or Specific Users)
  • Downstream Connections
    • Automatically Configure Connections
  
Correspondence

Configure Settings

For each Correspondence Type:

  • Enable Email Reminders for Overdue Items
  • Responses will be due number 
  • Default Description
  • Email Settings

Configure Settings

  • Default Distribution 
Site Diary

Configure Settings

  • All settings carry over except the items noted in the 'Does Not Carry Over' column. 

Configure Setttings

  • Manpower Categories
  • Default Distribution

Site Diary

  • Site Diary entries
Directory

Directory

  • Companies
  • Users, including:
    • User data 
      Note: A user's project role is the only information from their Directory profile that does not carry over.
    • Permissions
      • If their assigned Permissions Template in the template is global, it will be assigned in the new project
      • If their assigned Permissions Template in the template is project-specific, the template will not be applied. Instead, the correlating tool-level permissions from the project-specific template will be applied through their Directory listing. 
        Note: Granular permissions are not available in Directory-managed permissions. They can only be assigned in permission templates. As a best practice, always use permission templates to manage user permissions.

Directory

  • Users' project role assignment
Documents

Documents

  • Folder structure
  • Files at the root of the Documents tool that are NOT within a folder

Documents

  • Files within folders
Drawings

Configure Settings

  • Drawing Log Settings
    • Drawing Log Subscribers
    • Number of Drawings per Page
    • Allow standard level users to delete published markup
    • Enable Drawings by Area
    • Edit Drawings Disciplines
  • Discipline Abbreviation Setup
    • Abbreviations
    • Discipline names

Drawings

  • Individual drawings uploaded to the tool

Configure Settings

  • Drawings Log Settings
    • Connected Project
      • Upstream Project
      • Administrative Email Recipients
    • Edit Drawing Sets
Emails 

Configure Settings

  • Email Settings
    • Communication Settings
    • Communications "private" by default

Configure Settings

  • Email Settings
    • ​​​​​​​Inbound email address
    • Default Distribution
    • Copy tags from another project
Estimating

Estimates

  • All estimates and their data, except for the Quantity column

Configure Settings

  • Units

Estimates

  • Values in the Quantity column

Proposal

  • Proposals
Incidents

Configure Settings

  • Private by Default

Configure Settings

  • Default Distribution
Inspections

Configure Settings

  • Private by default
  • Configure Notifications
  • Inspections template and related data 

Configure Settings

  • Default Distribution
  • Templates in the Recycle Bin
Instructions

Configure Settings

  • Project Instruction Settings
    • Instructions Private by Default
    • Number Instructions by Type

Configure Settings

  • Project Instruction Settings
    • Default Distribution
  • Instruction Types
    • Type
    • Prefix
Payment applications (without Procore Pay)

Configure Settings

  • All settings

Payment Applications

  • Individual payment applications
Payment applications (with Procore Pay)

Configure Settings

  • First-Tier Waivers

    • When should first-tier waivers be requested? 

  • Sub-Tier Waivers

    • Enable sub-tier waivers

      • How should sub-tier waivers be collected on this project?

        • Require unconditional waivers from all sub-tiers before paying the next payment application

        • Require either a conditional or unconditional waiver from each sub-tier before paying the current payment application and ensure a complete set of unconditional waivers before paying the next payment application

        • Require unconditional waivers from all sub-tiers before paying the current payment application

      • Display custom instructions

        • Custom instruction text

    • Require collection of extended sub-tier information for use on sworn statements or contractor affidavits

  • Templates

    • Progress Conditional (if enabled)

    • Progress Unconditional (if enabled)

    • Final Conditional (if enabled)

    • Final Unconditional (if enabled)

Configure Settings

  • First-Tier Waivers
    • ​​​​​​​Enable conditional waivers
    • Enable unconditional waivers
  • Property Owner
    • ​​​​​​​Property owner
Meetings

Configure Settings

  • All settings
  
Observations

Configure Settings

  • General
    • ​​​​​​​Set new Observations to private by default
    • Working Days to Complete Observation

 

Configure Settings

  • General
    • ​​​​​​​Default Distribution
  • Templates
    • Project level ​​​​​​​Templates
  • Types
    • ​​​​​​​Project level Types
Photos

Configure Settings

  • All settings

Photos

  • Albums
  • Album order

Photos

  • Individual photos
Main Contracts

Configure Settings

  • Contract Configuration
    • ​​​​​​​All settings
  • Contract Payment application Settings
    • A​​​​​​​ll settings
  • Funding Sources
    • ​​​​​​​Name 
    • Description

Main Contracts

  • General Information
    • ​​​​​​​Executed
    • Title
    • Default Retention
    • Description
    • Bill of Quantities

The data in the Bill of Quantities (BOQ) tab on the projects template is carried over to new projects. In addition, the Advanced Settings are carried over.

Configure Settings

  • Default Distributions
    • ​​​​​​​Main Contract
    • Main Contract Variation
    • Main Contract Potential Variation
Project Home

Configure Settings

  • Show current weather conditions   
  • Show today's programme    
  • Show project milestones

Project Home

  • Project links

Configure Settings

  • Project Home Settings
    • Persistent project message
    • Public notes (visible to non-admins)
  • Project Dates
    • Project dates

  • Project Home

    • Project team
Snag List

Configure Settings

  • Snag List Settings
    • Default Snag Item Manager
    • Default Final Approver
    • Snag List Items Private By Default
    • Snag Item Response Will Be Due*
    • Enable overdue emails for assignees
    • Configure emails by role
    • Snag Item Types
  • Snag List Templates
    • Template name​​​​​​​
    • Active/Inactive selection

Configure Settings

  • Snag List Settings
    • ​​​​​​​Default Distribution List​​​​​​​
    • Standard permission users who can act as a Snag Item Manager
  • Snag List Templates
    • ​​​​​​​Snag Item manager
    • Default assignee
    • Default final approver
    • Custom categories
RFIs

Configure Settings

  • RFI Manager
    • RFI Manager Selection
  • Private RFIs
    • Enable Private RFIs
    • RFIs Private by Default
  • RFI Responses
    • ​​​​​​​Days to answer RFI questions
    • Only show official responses to Standard and Read-Only users
  • RFI Number Prefixes
    • ​​​​​​​Enable prefix RFI numbers by number stage
    • Stage selection
    • Prefix
  • RFI Emails
    • Enable Email Reminders for Overdue RFIs
    • Email configuration matrix selections

Configure Settings

  • RFI Responses
    • ​​​​​​​Mark Assignees' reponses as required by default
  • Custom Fields
    • ​​​​​​​Custom Fields 1 & 2
  • RFI Emails
    • Default Distribution
Programme

Configure Settings

  • General
    • ​​​​​​​All settings
  • File Management
    • ​​​​​​​Filename filter

Configure Settings

  • File Management
    • ​​​​​​​Project ID (Primavera P6 Files Only)
  • Email Distribution
    • ​​​​​​​All settings
Specifications

Configure Settings

  • All settings

Specifications

  • Individual specification files uploaded to the tool
Submittals

Configure Settings

  • General
    • ​​​​​​​General Settings
      • ​​​​​​​All settings
    • Submittal Emails
      • ​​​​​​​Email Notifications configurations
  • Responses
    • ​​​​​​​Workflow Responses
  • Workflow Templates
    • Workflow templates

Configure Settings

  • General
    • ​​​​​​​Submittal Emails
      • ​​​​​​​Default Distribution
Tasks

Configure Settings

  • Set new Tasks to private by default
  • Days to Complete Task Items

Tasks

  • Task items

Configure Settings

  • Default Distribution
Timesheets

Configure Settings

  • Time Entry Settings
    • All settings
  • Lunch Tracking
    • ​​​​​​​All settings

Configure Settings

  • Employee Location Tracking
    • ​​​​​​​Project Address
Daywork Sheets

Configure Settings

  • Daywork Settings
    • ​​​​​​​Project settings
      • Daywork Emails
        • ​​​​​​​All settings
          Note: One or more tickboxes must be marked in the email settings matrix for the Default Distribution Group in order for Distribution Group members to carry over from the template.
    • Global Settings (Inherited from Company level)
      • Daywork Sheet Sections
        • ​​​​​​​All selections
  • Change Events Export Options
    • ​​​​​​​Summarise Labour line items
      • ​​​​​​​Group Labour totals
    • Summarise Equipment line items
      • ​​​​​​​Group Equipment totals
  
Transmittals

Configure Settings

  • Transmittals Private by Default

Configure Settings

  • Distribution Group
Workflows (Company level)

Assigned projects

  • All templates assigned to the project template will also be assigned to new projects created from that template.
  
Workflows (Project level)

Tool Configuration Settings

  • Workflow Settings
    • ​​​​​​​Template configurations for workflows for all tools will carry over, including assignees to steps, workflow manager and distribution group.