Items that carry over to your new project
The following table identifies the project items that are carried over when you create a new project based on a template.
|Project Settings & Tab Configuration (Project Admin Tool)||The following settings from the General page of Project Settings copied to your new project: County Override checkbox, Latitude/Longitude Override checkbox, Office list, Project Type list, Enable DocuSign setting, Prevent Overbilling on the Project setting.|
|Advanced Setting Configurations||Most of the advanced setting configurations for each tool except for Schedule and the Project Home will carry over to a new project. See "Configure Advanced Settings: [Procore tool]" in the site for more information on each of a tool's specific advanced settings.|
|Project Directory (Companies & People)||If the project template contains companies and people in the Directory tool, those companies and persons will be added to any new project created with the template.|
|Document Subfolder Structures||Under the project's Document's tab, the subfolder structure will carry over. However, none of the files located within those subfolders will be carried over because they are most likely project-specific documents that should not be added to every new project. For example, you may want all projects to place their files into folders where the same folder names and folder structure are used across all projects. See Create a Standard Folder Structure.|
|Files in the Root Document Directory||Files that are placed at the root (topmost) level and are not located in the subfolder, will be carried over. For example, you may want the same safety regulations document added to each new project. Files can be added to the main project folder via Procore Drive, or by dragging and dropping a document to the top of the folder tree to your project's folder from a subfolder in the web application.|
|Change Order Configuration||The change order 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 change order configuration for both the prime contract and commitment sides. The configuration for change order tiers can be different between the prime contract and commitment sides.|
|RFI Email Preferences||All RFI email preferences in the template are carried over to new projects.|
|Prime Contract's Schedule of Values||All prime contract schedule of values data in the template are carried over to new projects.|
|Schedule Integration Selection||If you have identified a particular schedule integration in a project template, that selection will be carried over to new projects created from the template. However, any schedule data that may exist in the template will not be carried over.|
|Cost Codes at the Company Level||Company level costs codes and related data in the template are carried over to new projects.|
|Punch 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.|
|Daily Logs||The Daily Log Settings from the source project are copied to the new project (Note: Individual daily log entries, emails, change history, and any configuration settings created under the Manpower Categories area of the Daily Log Settings page are NOT copied to the new project).|
|Project Inspection Templates||Inspection templates and related data are carried over to new projects.|
|Custom Submittals Responses||Any custom submittal responses that have been created in the source project are carried over to the new project. See Create Custom Submittal Responses.|
|Webhooks Configuration||Project level Webhooks configuration including Notification Endpoint and Authorization Header field values are carried over to new projects. Note: Only Webhooks configured in the default Procore namespace are carried over to new projects.|
Items that do NOT carry over to your new project
Any preference that is NOT in the list above including:
- Project Admin: General Settings. 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 (Override Imported Schedule Date, Projected Finish date (Override Imported Schedule Date, Parent Job, Estimated Project Value, Project Stage, Office, Project Flag, Departments, Program, Bid Type, Owner Type, Region, Copy People From, Project Logo.
- Subscribers/Tool-specific distribution groups: Any subscribers or default distribution group members that are set up in the configuration page of a tool will not be copied to the new project's configuration settings.
- Cost Codes. Project level cost codes.
- Daily Log. Individual daily log entries, emails, change history, and any configuration settings created under the Manpower Categories area of the Daily Log Settings page are NOT copied to the new project.
- Default Distribution Lists. On specific tools (RFIs, Submittals, etc.).
- Schedule Integration Data. However, as stated above, your selection of which schedule tool you would like to integrate with will carry over (MS Project vs. Primavera P6).
- Spec Sections.
- Drawing Sheets.
- Meetings. For example, types, templates, and agenda structure.
- Photos. Albums do not carry over to new projects.
- Project Home Configuration Settings.
- Project Links. Project Links do not carry over to new projects. See Add or Modify Project Links.
- Reports and Custom Reports.
- Company Level Webhooks. Only project level Webhooks are carried over from templates to new projects.
- Submittal Workflow Templates. Project level Submittal workflow templates do NOT carry over on a project template.