In Procore, a project template is a pre-configured Procore project that streamlines new project creation and reduces manual configuration. Templates automatically copy various settings to new projects. However, not all settings are transferred; some settings must be configured manually on new projects. To learn how to get started with project templates, see Configure a Project Template.
This table identifies the settings that are copied to new projects created with a project template.
| Tool | Item | Additional Information |
|---|---|---|
| Procore Tools | Configure Settings |
Most of the advanced setting configurations for each tool except for Programme and the Project Home will carry over to a new project. See the "Configure Advanced Settings" tutorials on the site for more information on each of a tool's specific advanced settings. Note: Project level Observation Templates will not carry over to a new project. |
| Action Plans | Configure Settings > Notifications | Notifications settings are copied to the new project. |
| Admin (Company Level) | Project Settings > Defaults > Programs | The list of Programs added to the template are copied to the new project. See Add a Custom Program. |
| Admin (Company Level) | Tool Settings > Supported Tools > Fieldsets | Fieldsets assigned to a project template are copied to the new project. See What are configurable fieldsets and which Procore tools support them? |
| Admin (Project Level) | Project Settings > Active Tools | Any selected active tools are copied to the new project. |
| Admin (Project Level) | Project Settings > Classifications | The settings for a project's classifications are copied to the new project. To learn more about classifications, see Which Procore tools support 'Classifications'? |
| Admin (Project Level) | Project Settings > Equipment | The items added to the Equipment Name list are copied to your new project. |
| Admin (Project Level) | Project Settings > General | These settings are copied to the new project:
|
| Admin (Project Level) | Project Settings > Locations | The setting for the Only Allow Locations to be Created in the Location Manager Above tickbox under Location Settings is copied to the new project. Note: When the tickbox is cleared, users are able to create locations from any location field in the Procore web application. |
| Admin (Project Level) | Project Settings > Webhooks | Project level Webhooks configurations including Notification Endpoint and Authorization Header field values are copied to new projects. Note: Only Webhooks configured in the default Procore namespace are copied to new projects. |
| Admin (Project Level) | Project Settings > Work Breakdown Structure |
These items are copied to the new project:
|
| Admin (Project Level) | Project Settings > Working Days | Working Days are carried over to your new project. See Set Project Working Days. |
| Admin (Project Level) | Project Settings > ERP Integration Settings | Both the 'Allow project to be synced with ERP' and 'Enable ERP Job Cost Transaction Syncing' settings are carried over to your new project. See Create a Project and Enable ERP Job Cost Transaction Syncing on a Procore Project. |
| Tendering | Configure Settings | All settings on the Tender Package Default Settings page are carried over to new projects. See Configure Advanced Settings: Tendering. |
| Budget | Autocalculate Forecast to Complete by Default | The setting in this tickbox is carried over to your new project. See Configure Settings: Budget and Use the 'Forecast to Complete' Feature. |
| Budget | Enable Advanced Forecasting | The setting in this tickbox is carried over to your new project. See Configure Settings: Budget. |
| Budget | Require Net Zero Budget Change Amounts | The setting in this tickbox is carried over to your new project. See Configure Settings: Budget. |
| Variations | Configure Settings > Variation Configuration | 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 | Commitments List | Fields in the General tab on purchase orders and subcontracts carry over, excluding Number (#), Contract Company, Payment application Contacts, Default Distributions and Attachments. In addition, a commitment's status is updated to 'Draft' in the new project. Line items in the Bill of Quantities tab also carry over to a new project, except for the cost code assignment. This is because project codes do not carry over to new projects. The budget code on the BOQ retains the cost type assignment. |
| Commitments | Commitments List |
Fields in the General tab on purchase orders and subcontracts carry over, excluding Number (#), Contract Company, Payment application Contacts, Default Distributions and Attachments. In addition, a commitment's status is updated to 'Draft' in the new project. |
| Commitments | Compliance Template | For customers with Procore Pay, the 'Compliance Template' setting under the 'Contract Configuration' is copied to the new project. |
| Correspondence | Configure Settings | The following configurations are copied to the new project for each correspondence type on the project template: Enable Email Reminders for Overdue Items tickbox, Responses will be due number, Default Description text and Email Settings. |
| Site Diary | Configure Settings > Project Settings (Site Diary Settings) |
The Site Diary Settings from the source project are copied to the new project. |
| Directory | Project Directory (Users & Companies) | If the project template contains users and companies in the Project Directory tool, they will be added to any new project created with the template. Users with global permissions templates assigned to them on the source project will be assigned the same permissions templates on the new project. Users with project specific permissions templates assigned to them on the source project will be assigned the same tool permissions (without a permissions template selected) on the new project. |
| Documents | Document Folder Structure | Under the project's Documents tool, the folders will carry over in the same structure. See Create a Standard Folder Structure. Note: Any files that are located within those folders will NOT carry over as they are most likely project-specific documents that may not be relevant to each new project. |
| Documents | Files in the Root Folder of the Documents Tool | Files that exist at the root level of the Documents tool (outside of other folders) will carry over. See Can I copy files in the Documents tool to another project? for more detail. Files can be added to the root folder by uploading or moving files to that area of the Documents tool. |
| Drawings | Configure Settings > Discipline Abbreviation Setup | Drawing Discipline Abbreviations set up in the Drawings tool's configure settings will carry over to new projects. See Configure Default Drawing Disciplines. |
| Emails | Configure Settings > Communication Settings | Communication Settings that determine who can send emails into Procore using a project's or tool item's inbound email address will carry over to new projects. See Configure Advanced Settings: Emails. |
| Emails | Configure Settings > Communications "Private" By Default | The setting for the Communications "private" by default tickbox is carried over to new projects. |
| Estimating | Estimates | All estimates and data, except the Quantity column, are carried over to new projects. |
| Inspections | Configure Settings > Create Inspection Template | Inspections template and related data are carried over to new projects. See Create a Project Level Inspection Template. |
| Inspections | Configuration Settings > Configurations | 'Private by Default', forcing users to create an Observation on item failure and Inspection Notifications are carried over to new projects. See Configure Advanced Settings: Project Level Inspections. |
| Incidents | Configure Settings | Private by Default |
| Payment Applications | Configure Settings | Only the settings under the Default Billing Period, Emails and Other sections are carried over to new projects. |
| Meetings | Configure Settings | All settings on the Meetings Settings page, including 'Meeting View' and 'Automatically Show Previous Minutes', are carried over to new projects. See Configure Advanced Settings: Meetings. |
| Observations | Configure Settings > Observation Settings | The settings for Observations Private by Default and Observations will be due in X working days by default are carried over to new projects. |
| Photos | Configure Settings | All settings on the Photo Settings page are carried over to new projects. See Configure Advanced Settings: Photos. |
| Main Contracts | Bill of Quantities Tab | 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. |
| Main Contracts | Contract Configuration | The settings under 'Contract Configuration' are copied to new projects. See Configure Settings: Main Contracts. |
| Snag List | Configure Settings > Snag List Settings > Snag Item Types | The list of 'Punch Item Types' created in the Configure Settings page of the project's Punch List tool. See Create Punch Item Types. |
| Snag List | Configure Settings > Snag List Settings > snag Emails | The Punch email settings configured in the Configure Settings page of the project's Punch List tool. See Configure Emails. |
| Snag List | Configure Settings > Snag List Settings > Snag List Templates | The project-level snag templates be carried over to a new project. See Create a Project Level Snag Item Template. |
| RFIs | Configure Settings > RFI Settings | The following settings are carried over to the new project: RFI Manager, Allow Private RFIs, RFIs Private by Default, Answers to New RFI Questions Will Be Due, Enable Email Reminders for Overdue RFIs, Only Show Official Responses to Standard and Read Only Users, and Prefix RFI Numbers by Project Stage. |
| RFIs | Configure Settings > RFI Settings > RFI Emails | Any email settings configured in the Configure Settings page of the RFIs tool are carried over to the new project. See How do I control which emails are sent by Procore during the RFI process? |
| Programme | Configure Settings > General | Any programme settings in this section. See Configure Advanced Settings: Project Programme. |
| Programme | Configure Settings > File Management | The Filename Filter is carried over to the new project. See Configure Advanced Settings: Project Programme. |
| Submittals | Configure Settings > Submittal Responses | Any custom submittal responses that have been created in the source project are carried over to the new project. See Manage Custom Submittal Responses. |
| Submittals | Configure Settings > Submittal Emails | Any email settings configured in the Configure Settings page of the Submittals tool are carried over to the new project. See When does the Submittals tool send email notifications to Procore users? |
| Submittals | Number Submittal by Spec Section | This setting is carried over to the new project. |
| Timesheets | Configure Settings > Timesheets Settings | Time Entry Settings and any Additional Fields that are enabled will carry over to new projects. |
| Daywork Sheets | Configure Settings > Daywork Settings | Daywork Emails settings for Creator, Company Signee and Customer Signee will carry over to new projects. |
| Daywork Sheets | Configure Settings > Change Events Export Options | Summarise Labour Line Items and Summarise Equipment Line Items selections will carry over to new projects. |
| Workflows | Company level Workflows tool > Assigned Projects | All templates assigned to the project template will also be assigned to the new projects created from that template. |
| Workflows | Project level tool > Tool Configuration Settings > Workflow Settings | Template configurations for workflows for all tools will carry over, including assignees to steps, workflow manager and distribution group. |
The following table identifies the items that do NOT carry over to a new project when that new project is based on a project template.
| Tool | Item | Additional Information |
|---|---|---|
| All Project Tools | Configure Settings > Default Distribution | The members of a 'Default Distribution' list. |
| Admin (Company Level) | Custom fields | Custom fields created for a Project level tool. See Create New Custom Fields. |
| Admin (Company Level) | Company Settings > Webhooks | Company level Webhooks. See Configure Company Webhooks. Only Project level Webhooks carry over. |
| Admin (Project Level) | Project Settings > General | Project Name, Active Project, Job Number, Project Description, Square Feet, Job Phone, Job Fax, Address, City, Country, State, County, Zip, Latitude/Longitude, Estimated Start Date, Estimated Completion Date, Warranty Start Date, Warranty End Date, Actual Start Date, Projected Finish Date, Actual Start Date, Projected Finish Date, Parent Job, Estimated Project Value, Office, Project Flag, Departments, Program, Tender Type, Owner Type, Region, Copy Directory From, Project Logo, Language - Country |
| Admin (Project Level) | Project Settings > Locations | Tiered locations. See Add Tiered Locations to a Project. |
| Change Events | Change Events Settings > Attachments | These settings do not carry over (see Set Attachment Settings):
|
| Commitments | Purchase Orders & Subcontracts | These items do not carry over (see Create a Commitment):
|
| Correspondence | Configure Settings > Tab Settings > Default Distribution | The 'Default Distribution' list. See Configure Advanced Settings: Correspondence. |
| Site Diary | Manpower Categories | Individual site diary entries, emails, change history and any configuration settings created under the Manpower Categories area of the Site Diary Settings page. See Create Manpower Entries. |
| Permissions (Company Level) | Project Permissions Templates | All project specific permissions templates. See Create a Project Permissions Template.
NoteUsers assigned to a specific project permissions template on the source project are assigned the same tool permissions on the new project. However, without the permissions template selected. |
| Emails | Configure Settings > Email Settings | These settings (see Configure Advanced Settings: Emails):
|
| Drawings | Drawing Sheets | All automatic drawing sheet links. See Automatic Drawing Sheet Linking. |
| Home | Configure Settings > Project Home Settings | These settings (see Update the Project Home Settings):
|
| Home | Home > Project Team | All project team members. See Add the Project Team to the Project Home Page. |
| Home | Home > Project Links | All project links. See Add, Modify or Remove Project Links on the Project Home Page. |
| Payment Applications | Payment applications Settings > Lien Waivers | All 'Lien Waivers' settings for Procore Pay. See Configure Settings: Payment applications. |
| Payment Applications | Payment applications Settings > Subcontractor Workflow Settings | The Subcontractor Workflow Settings for Payment application Management. See Configure Settings: Payment applications. |
| Meetings | Project Meetings | All meetings. This includes the meeting categories, templates and agenda structures. See Meetings. |
| Photos | Albums | All albums. See Create a Photo Album. |
| RFIs | Configure Settings > RFI Settings | These settings (see Configure Advanced Settings: RFIs):
|
| Reports (Project Level) | Reports | All canned and custom reports. See Reports. |
| Programme | Programme | Any integrated project programme. See Programme. |
| Specifications | Spec Sections | All project spec sections. See Manually Create Spec Sections. |
| Submittals | Configure Settings > Submittal Workflow Templates | All submittal workflow templates. See Manage Submittal Workflow Templates. |
| Tasks | Tasks | All tasks. See Add a Task. |
| Daywork Sheets | Configure Settings > Daywork Settings | These settings (see Configure Advanced Settings: Daywork Sheets):
|